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 service, renamed — nothing in your tenant changed

Azure AD and Entra ID are the same service: Microsoft renamed Azure Active Directory to Microsoft Entra ID in July 2023, and nothing about your tenant, users, or configuration changed with the name. The honest caveat: some portal blades, license screens, and docs still say "Azure AD" years later, and the PowerShell modules changed separately.

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 if your confusion is wider than the rename — Azure AD vs Entra ID vs the on-premises Active Directory vs Domain Services — read What is Microsoft Entra ID, which untangles all four names in one place. This note stays on the rename itself: whether it is really the same thing, what genuinely changed around it, and the short list of things admins actually had to touch.

Is Azure AD the same as Entra ID?

Yes. Plainly, unreservedly yes. Entra ID is not a successor product, a v2, or a migration target — it is the same directory with a new name on the tin. Your tenant ID did not change. Your users, groups, app registrations, and Conditional Access policies did not move. Sign-in still happens at login.microsoftonline.com. If you passed an exam on "Azure AD" or wrote a runbook that says "AAD," every word of it still applies.

Here is the nuance that keeps the question alive, though. The rename landed in the middle of an era when several adjacent things really did change, and people reasonably blur them together:

• The old Azure AD Graph API was retired. The legacy graph.windows.net API is gone; Microsoft Graph (graph.microsoft.com) is the API for the directory now. If an old script died, this retirement is the likely culprit — not the rename.
• The MSOnline and AzureAD PowerShell modules were retired in favor of the Microsoft Graph PowerShell SDK. The retirements rolled out in phases through 2024–2025; as of 2026, treat both legacy modules as dead and check current docs for the exact state of any straggler cmdlets.
• License SKUs were renamed. Azure AD Premium P1 became Microsoft Entra ID P1, P2 became Entra ID P2, on October 1, 2023 — same features, same entitlements, new display names. If you are choosing between them, see Entra ID P1 vs P2.

So the accurate one-liner is: the service is identical, but the era around the rename retired the old API and the old PowerShell modules. When someone insists "things broke when it became Entra," that is usually what they are remembering.

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.
• Your data and configuration — Conditional Access policies, group memberships, role assignments, enterprise apps: all exactly where you left them.

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. The one caveat from the previous section stands: scripts on the retired MSOnline or AzureAD modules did eventually stop — because the modules were retired, not because the service was renamed.

Entra ID vs Active Directory (the on-prem one)

A different question hides inside the same search: is Microsoft Entra the same as Active Directory — the one running on Windows Server in a datacenter? No. Those are two different products that happen to share two words. On-premises Active Directory (AD DS) is a directory you host yourself on domain controllers, speaking Kerberos, NTLM, and LDAP, with Group Policy for management. Entra ID is a cloud service Microsoft hosts, speaking OAuth 2.0, OpenID Connect, and SAML over HTTPS — no domain controllers, no Group Policy. They can be connected with Entra Connect so one set of identities serves both worlds, but neither one is a rename of the other, and neither replaces the other by default. There is also a third sibling with a confusingly similar name — Microsoft Entra Domain Services, formerly Azure AD DS, a managed cloud version of the old-style directory. The full four-way untangle (AD vs Azure AD vs Entra ID vs Domain Services) lives in What is Microsoft Entra ID; the short answer here is simply: same words, different products.

What admins actually had to change

Nobody writes this part, so here it is: the real, complete to-do list the rename generated for a working admin. Inside the tenant, the answer is nothing — no setting, no policy, no re-registration. Around the tenant, a handful of small chores:

• Scripts on retired modules. Anything using MSOnline (Msol* cmdlets) or the AzureAD module (*-AzureAD* cmdlets) needed rewriting against Microsoft Graph PowerShell. This was driven by the module retirements, not the rename, but it landed in the same era and is the only genuinely breaking item on the list.
• Portal bookmarks. The dedicated home for identity work is now the Microsoft Entra admin center at entra.microsoft.com. The old blades inside portal.azure.com still work, so this is a convenience update, not a forced one.
• Doc bookmarks and internal wikis. Microsoft redirected most learn.microsoft.com URLs, so old links usually land somewhere sensible. Runbooks and onboarding docs that say "Azure AD" are worth a search-and-replace at your leisure — they are stale, not wrong.
• Vocabulary. Exam questions, job postings, and colleagues now mix both names freely. The only skill required is reading them as one thing.

That is the whole list. If a consultant tries to sell you an "Entra migration," ask exactly which of those four bullets they are charging for.

Why Microsoft renamed it

Two reasons worth knowing. The word Azure undersold the product — the directory secures Microsoft 365, apps on other clouds, and any SaaS you connect, not just Azure resources. And the words Active Directory caused endless confusion with the on-premises Windows Server role of the same name, as covered above.

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. 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 long transition period where both names appear side by side, which is exactly the friction that sent you searching in the first place.

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.
• Old scripts and forum answers — the retired MSOnline and AzureAD module names live on in a decade of scripts and Stack Overflow answers; the current 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 Azure AD the same as Microsoft Entra ID?

Yes. Microsoft Entra ID is Azure Active Directory renamed. Same tenant, same users, same features, same tenant and object IDs — only the name changed. Any doc, course, or exam question that says Azure AD applies to Entra ID unchanged; you can read the two names as one service.

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.

Did anything change when Azure AD was renamed?

Not inside your tenant. Users, groups, policies, app registrations, endpoints, and IDs were untouched. What did change, separately and around the same era: the old Azure AD Graph API and the MSOnline and AzureAD PowerShell modules were retired in favor of Microsoft Graph, and the license SKUs took Entra names.

Is Microsoft Entra the same as Active Directory?

No. Active Directory is the on-premises Windows Server directory that runs on your own domain controllers using Kerberos and LDAP. Microsoft Entra ID is Microsoft's cloud identity service, spoken over HTTPS with OAuth, OpenID Connect, and SAML. They can sync through Entra Connect, but they are different products.

What happened to Azure AD Premium P1 and P2?

They became Microsoft Entra ID P1 and Microsoft Entra ID P2 on October 1, 2023. The features and entitlements carried over unchanged; only the SKU display names updated. If your invoice or admin center shows the Entra names, you are on the same plan you already had.