Azure AD vs Entra ID: What Actually Changed?

You searched this because a doc, a certification, or a colleague used a name you did not recognize — and you wanted to be sure you had not missed a migration. You did not. Here is the whole story in one sitting.

New to cloud? CAMPUX is a free, build-first course. Start here →

Same product, new name — nothing breaks

Azure AD and Entra ID are the same product; Microsoft just renamed Azure Active Directory to Microsoft Entra ID in July 2023, and nothing about how it works changed. Same tenants, same users, same groups, same sign-in, same everything. If you know Azure AD, you know Entra ID — you are reading a new label on a box you already owned. There is no migration to run, no setting to flip, and no deadline to meet. The two names point at one service.

So when a Microsoft Learn page, an exam objective, or a job posting says "Entra ID" where your notes say "Azure AD," you can treat them as interchangeable and move on. That is the reassurance most people came here for, and it is the honest answer. The rest of this note explains the why, the exact list of things that did not move, and a cheat sheet you can keep next to you while the old name lingers in tooling.

Why Microsoft renamed it

Renames usually have a reason buried under the marketing, and this one has two worth knowing.

First, the word Azure was misleading. It made people think the directory only worked with Azure resources, when in practice the same identity secures Microsoft 365, apps on other clouds, and any SaaS you connect. Identity outgrew the Azure label years ago; the name lagged behind the product.

Second, the word Active Directory caused constant confusion with the on-premises Windows Server role of the same name. New engineers routinely conflated cloud "Azure AD" with the domain controllers running in a server closet. They are related but different systems, and the shared "AD" muddied every conversation and every troubleshooting session.

On top of both, Microsoft wanted a single family name — Microsoft Entra — to sit over a growing set of identity and network-access products, of which the directory is one member. Renaming the directory to Entra ID lets the family read as a set instead of a pile of unrelated names.

None of that changes how the service behaves. It changes how you talk about it, and it removes two long-standing sources of confusion for anyone new to the platform. If you have ever had to say "the cloud one, not the server one" in a meeting, the rename was aimed at you. The trade-off is a transition period where both names appear side by side, which is exactly the friction that sent you searching in the first place.

A rename is not a migration. The only thing you have to update is the word you use — the service underneath never moved.

What stayed exactly the same

This is the part that matters operationally, and Microsoft was deliberate about it. To keep the change from breaking anything, they left every technical surface untouched. Nothing on this list changed with the rename:

• Login URLs — sign-in still happens at login.microsoftonline.com. No new endpoint, no redirect to update.
• API endpoints — Microsoft Graph is still graph.microsoft.com. Your calls, scopes, and permissions are unchanged.
• Authentication libraries — MSAL and the Microsoft identity platform keep the same package names, methods, and behavior. No SDK swap.
• Tenant IDs and object IDs — the GUIDs that identify your directory, users, groups, and app registrations are permanent. Nothing regenerated.
• Licenses and entitlements — every capability in your old Azure AD plan carried over intact. The SKU display names updated, but what you pay for did not.
• PowerShell cmdlets and existing scripts — your automation keeps running. The command surface stayed put.

Read that list twice if you were worried. The rename was cosmetic by design. Your code, your Terraform, your conditional access policies, and your app registrations all kept working the day the name changed and every day since.

What "Microsoft Entra" now covers beyond ID

Here is the one genuinely new idea, and it is a source of mix-ups. Microsoft Entra is not just a new name for the directory — it is a product family, and Entra ID is one member of it. So "Entra" and "Entra ID" are not synonyms the way "Azure AD" and "Entra ID" are.

The directory — the users, groups, and sign-in you knew as Azure AD — is now Microsoft Entra ID. Alongside it, the Entra brand covers newer products for network access and identity governance, such as Entra Internet Access, Entra Private Access, Entra Permissions Management, and Entra Verified ID. You do not need those to use Entra ID, and most of them did not exist under the old Azure AD name. The practical takeaway: when someone says "Entra," ask whether they mean the whole family or specifically Entra ID — the directory. Nine times out of ten in identity work, they mean the directory.

Terminology cheat sheet: old name to new name

Keep this next to you while both names circulate. The left column is what your older notes, courses, and blog posts call things; the right column is what Microsoft calls them now.

One honest caveat on that B2C row. Microsoft Entra External ID is not simply Azure AD B2C with a new label — it is a next-generation customer identity product that Microsoft points new projects toward. Azure AD B2C still exists as its own supported offering for existing customers. So treat External ID as the successor, not a pure rename, and do not assume your B2C tenant silently became something else.

The gap: places you'll still see "Azure AD"

Even years after the rename, the old name has not vanished — and that is expected, not a mistake on your part. Deep technical surfaces keep the original identifiers precisely because changing them would break things, which is the whole point of the rename being cosmetic.

You will still meet "Azure AD" or "AAD" in:

• Microsoft Graph and API responses — property names, error strings, and schema fields that predate the rename keep their old spelling for compatibility.
• PowerShell module names — the legacy AzureAD module still carries the old name; the newer path is the Microsoft Graph PowerShell SDK.
• The Entra Connect installer — the downloaded file is still AzureADConnect.msi. That is normal; ignore it.
• Older docs, courses, and Stack Overflow answers — anything written before mid-2023, plus plenty written after out of habit.
• Certification material and exam questions — you should expect either name and read them as equal.

None of this signals a problem. When you see "Azure AD" in a code path or a file name, mentally read "Entra ID" and keep going. The mismatch between the friendly brand and the underlying identifiers is a feature of doing the rename without breakage — not a sign you missed a step.

There is a practical upside to knowing this. In an interview or on the job, being able to say "Azure AD and Entra ID are the same directory; the brand changed in 2023 but the endpoints and tenant IDs did not" marks you as someone who has actually worked with the platform rather than someone who memorized a screenshot. It also stops you second-guessing every doc you read: once you accept that both names are correct, the internet's mix of old and new spellings stops being noise and becomes easy to parse.

Questions people also ask

Is Entra ID the same as Azure AD?

Yes. Microsoft Entra ID is the new name for Azure Active Directory. It is the same service with the same features, tenants, and data — only the brand changed. Anything you learned about Azure AD still applies; you read the new name and carry on.

When did Azure AD become Entra ID?

Microsoft announced the change on July 11, 2023, and the new name began appearing across products from August 15, 2023. Licensing SKU names, such as Entra ID P1 and P2, updated on October 1, 2023. The rollout was gradual, so both names circulated for a while.

Do I need to change anything after the rename?

No. Login URLs, API endpoints, PowerShell cmdlets, authentication libraries like MSAL, tenant IDs, and licenses all stay the same. Your code, your app registrations, and your sign-in flows keep working untouched. The rename is cosmetic, not a migration.

Why did Microsoft rename Azure AD?

Two reasons. The Azure name suggested identity only worked with Azure, when it secures Microsoft 365, other clouds, and any app. And Microsoft wanted one family name — Microsoft Entra — over its growing set of identity and network-access products, of which the directory is one member.

Is Azure AD Connect now called Entra Connect?

Yes. Azure AD Connect is now Microsoft Entra Connect Sync. It is the same hybrid-identity sync tool that pushes identities from on-premises Active Directory to your cloud tenant. The installer file is still named AzureADConnect.msi, which is normal and safe to ignore.