Azure AD is now Microsoft Entra ID: what actually changed
Microsoft announced the Azure AD to Entra ID rename in July 2023 and finished the visible relabelling by the end of that year. No tenant, protocol, or licence changed, but the naming split across docs, certifications, and job specs still causes confusion.
Microsoft announced on 11 July 2023 that Azure Active Directory would be renamed Microsoft Entra ID. The change rolled out in phases: relabelling across Microsoft surfaces from 15 August 2023, SKU and service-plan display names on 1 October 2023, and most remaining naming strings by the end of that year.
Nothing technical changed. Deployments, configurations, and integrations continued working with no action required. Licensing, terms, SLAs, product certifications, support, and pricing all stayed the same. Entra ID is the identity service; Entra is the wider family that also covers Internet Access, Private Access, and Permissions Management.
Worth keeping straight: Entra ID is not Active Directory. Windows Server AD, the on-premises directory, kept its name and is a different product with a different protocol surface. Microsoft renaming the cloud service did nothing to the domain controllers in your data centre.
Why it matters
Renames are cosmetic until they are not. Three years on, the split naming still shows up in stale documentation, in certification titles, in job specs asking for "Azure AD" skills, and most awkwardly in security tooling and audit reports that reference one name while your tenant reports the other. When you inherit an estate, check whether "AD" in a runbook means the cloud service or the on-premises directory, because the SSO and OAuth surfaces involved are entirely different. See our Microsoft Entra ID profile for where it sits against other platforms.
Source: Microsoft Learn: new name for Azure Active Directory
Related on Start with Identity
- BlogGoogle Workspace puts FIDO2 keys into the Windows login, days after Entra makes passkeys default
Google began rolling out FIDO2 security keys as a second factor at Windows sign-in for all Workspace customers on 13 July. Microsoft is making passkeys the defa
- BlogAkeyless ships Runtime Authority, authorising AI agents per action instead of per session
Agents hold no secrets and get no standing privilege. Every action is authorised at the moment it happens, and the audit trail links the originating prompt to t
- BlogC1 ships enterprise-managed authorization, putting SSO in front of MCP agents
The identity platform formerly called ConductorOne now issues short-lived scoped tokens for MCP servers under the open enterprise-managed authorization extensio
- GuideConditional Access Policies: A Complete Implementation Guide for Microsoft Entra
Master Microsoft Entra conditional access with risk-based policies, device compliance rules, location-based restrictions, and real-world deployment patterns.
- VendorMicrosoft Entra External ID
strong
- VendorMicrosoft Entra Permissions Management
strong