In July 2023, Microsoft renamed Azure Active Directory to Microsoft Entra ID. Beyond the name change, Microsoft has progressively expanded the Entra family to include identity governance, permissions management, and verified ID capabilities. Understanding what is in the family — and what it means for your security posture — matters for any business running Microsoft 365.
What Is Actually Different
Entra ID is functionally the same service as Azure AD with the same capabilities. The renaming was partly cosmetic and partly strategic — positioning identity as a standalone security domain rather than a component of the Azure infrastructure stack. The underlying directory, authentication protocols, and integration points are unchanged.
Entra ID Protection
Entra ID Protection (formerly Azure AD Identity Protection) uses machine learning to detect anomalous sign-in behaviour — impossible travel, unfamiliar locations, sign-in from IP addresses associated with malicious activity. When risk is detected, it can trigger automated responses: requiring MFA, forcing password reset, or blocking access entirely. This capability is included in Microsoft 365 Business Premium and is a meaningful addition to the identity security layer.
Conditional Access and Entra
Conditional Access policies in Entra ID are the primary mechanism for implementing Zero Trust identity controls. They evaluate the identity, device compliance, location, and risk level of every access request and apply controls accordingly. Properly configured Conditional Access — requiring MFA for all access, blocking non-compliant devices, restricting access from high-risk locations — is the most impactful configuration investment in the Microsoft 365 stack.
Do I need to do anything because of the Azure AD to Entra ID rename?
No immediate action is required. Scripts, APIs, and integrations that reference "Azure Active Directory" or "AAD" continue to work — Microsoft is maintaining backward compatibility. Over time, documentation and references will shift to Entra ID. New implementations should use the Entra terminology from the outset.
