If your documentation, admin runbooks or application settings still say “Azure AD”, you are not alone. Microsoft renamed Azure Active Directory to Microsoft Entra ID, and the old name lingers in code, scripts and conversations. The good news is that the rename was mostly a branding change. The more important news is that it arrived alongside several real deprecations that do affect applications.
This article summarizes what Microsoft says changed, what did not, and what is worth checking in your own systems.
The rename in brief
According to Microsoft Learn, the new name was publicly announced on July 11, 2023. Name changes across Microsoft experiences started on August 15, 2023, display names for licenses and service plans changed on October 1, 2023, and most text changes were completed by the end of 2023.
Microsoft gives three reasons for the change: to reflect the product’s multicloud and multiplatform scope, to reduce confusion with Windows Server Active Directory, and to unify the Microsoft Entra product family.
That family now includes several products. Microsoft Entra ID is the one that used to be Azure AD. Others include Microsoft Entra ID Governance, Microsoft Entra External ID, Microsoft Entra Verified ID, Microsoft Entra Workload ID, Microsoft Entra Internet Access and Microsoft Entra Private Access.
What did not change
Microsoft is explicit that existing deployments, configurations and integrations keep working without any action. Specifically:
- Sign-in URLs, APIs, PowerShell cmdlets and the Microsoft Authentication Library (MSAL) stay the same, along with developer tooling.
- Features and capabilities are unchanged; only the names moved to the Microsoft Entra brand.
- Licensing, terms, service-level agreements and pricing are unchanged.
In other words, you do not need to change code just because the product name changed.
What did change: names
Licenses and service plans
| Old display name | New display name |
|---|---|
| Azure Active Directory Free | Microsoft Entra ID Free |
| Azure Active Directory Premium P1 | Microsoft Entra ID P1 |
| Azure Active Directory Premium P2 | Microsoft Entra ID P2 |
Feature names
Features previously branded “Azure AD” now carry the Microsoft Entra name. A few examples from Microsoft’s glossary:
| Old term | New term |
|---|---|
| Azure AD tenant | Microsoft Entra tenant |
| Azure AD Conditional Access | Microsoft Entra Conditional Access |
| Azure AD Connect | Microsoft Entra Connect |
| Azure AD Domain Services | Microsoft Entra Domain Services |
| Azure AD multifactor authentication | Microsoft Entra multifactor authentication |
| Azure AD managed identities | Managed identities for Azure resources |
Microsoft discourages acronyms, but where one is unavoidable it suggests ME-ID in place of AAD, noting that it is not an official abbreviation.
Names that did not change
Some names deliberately stayed:
- Active Directory (Windows Server Active Directory, AD DS, AD FS) keeps its name. It is a separate, on-premises product.
- Azure AD B2C was not renamed. Microsoft also states that from May 1, 2025, Azure AD B2C is no longer available to purchase for new customers, and points to Microsoft Entra External ID as its newer solution for external identities.
- Developer assets such as the Microsoft identity platform and MSAL keep their names.
The changes that actually matter to developers
The rename itself needs no code changes. But the same Microsoft Learn page records several deprecations that do, and these are easy to overlook if you only hear about the new name.
- ADAL is deprecated. The Azure Active Directory Authentication Library still works in existing apps, but Microsoft no longer releases security fixes for it. Microsoft advises migrating to MSAL.
- Azure AD Graph is deprecated. It receives no new investment and no SLA or maintenance commitment beyond security fixes. New features arrive only in Microsoft Graph.
- Azure AD PowerShell was planned for deprecation on March 30, 2024. Microsoft recommends the Microsoft Graph PowerShell module instead.
- DirSync and Azure AD Sync are no longer supported and no longer work. Organizations still using them must upgrade to Microsoft Entra Connect.
If an older application or automation script still depends on any of these, the rename is a good prompt to fix it.
A practical checklist
For developers
- Search your codebase for ADAL packages and Azure AD Graph endpoints, and plan migration to MSAL and Microsoft Graph.
- Leave sign-in endpoints alone. Microsoft says existing login URLs stay the same, so there is no need to rewrite working authentication configuration.
- Update user-facing text that names the provider, following Microsoft’s renaming guidance. That guidance warns against breaking changes and against blind find-and-replace: a product mention becomes “Microsoft Entra ID”, while a feature mention becomes “Microsoft Entra” plus the feature name.
- Review automation scripts that use the Azure AD PowerShell module and move them to Microsoft Graph PowerShell.
For administrators
- Update runbooks and internal documentation to use Microsoft Entra terms, so new staff can match instructions to what they see in the portal.
- Use the Microsoft Entra admin center at entra.microsoft.com; Microsoft notes that the Azure portal also remains available.
- Confirm directory sync runs on Microsoft Entra Connect, not on retired DirSync or Azure AD Sync.
- Check license reports and procurement records for the new plan names so nothing appears to be missing.
For content and support teams
- Use “Microsoft Entra ID” on first mention. Microsoft’s guidance prefers the full name on second use too, with “Entra ID” only where space is truly limited.
- Keep “Active Directory” for the on-premises product. Mixing the two is the confusion the rename was meant to reduce.
- Consider a short note such as “formerly Azure Active Directory” next to the new name, which Microsoft suggests for the first year after updating content.
Why this matters beyond the name
Renames are cheap to ignore, and that is exactly why they cause friction later. A support engineer searching for “Azure AD Conditional Access” may miss current documentation. A new developer may copy an ADAL sample because an old wiki page still mentions it. Treating the rename as a short housekeeping project, with the deprecation checks above, avoids both problems.
How Devacon can help
We integrate applications with Microsoft Entra ID and other identity providers, and we help teams move older integrations from ADAL and Azure AD Graph to MSAL and Microsoft Graph. A typical engagement starts with an inventory of identity dependencies and ends with tested, updated integrations. Learn more about our identity and access management services.
Sources
Facts in this article were checked against the sources above on November 17, 2026. Standards and products change, so check the source before relying on a detail. Related service: Identity & Access Management.