Microsoft cloud
Entra
Microsoft Entra
Microsoft Entra is Microsoft's product family name for identity and network access services, introduced in 2023 as an umbrella brand that consolidated what had previously been marketed under separate names.
Why Entra matters in a Microsoft estate
Entra matters because Microsoft 365, Azure, Windows 365, Teams, and related services are usually managed as one estate. The term connects to planning, cost, configuration, security, and day-two operational decisions across that estate.
How Entra shows up in practice
Most visibly, it renamed Azure Active Directory to Microsoft Entra ID, while keeping its underlying service, tenant structure, and object model unchanged. The Entra family now spans several distinct products beyond the core identity directory: Entra ID for authentication and authorisation, Entra ID Governance for access reviews, entitlement management and identity lifecycle workflows, Entra Permissions Management for cloud infrastructure entitlement management across Azure, AWS and GCP, and Entra Verified ID for decentralised identity credentials. Entra Internet Access and Entra Private Access together form Microsoft's Security Service Edge offering, as an alternative to traditional VPN-based remote access. For anyone who has worked with Microsoft identity services for a while, the rename is the single most important thing to understand about Entra.
Existing Azure AD tenants, app registrations, Conditional Access policies, and PowerShell/Graph API objects were not migrated or restructured; they were simply renamed in the portal and documentation. An organisation's actual tenant, its directory schema, and its licensing (Entra ID Free, P1, P2) carried over directly, rather than requiring any technical migration project. This matters practically because a good deal of tooling, scripting, and third-party documentation still refers to "Azure AD," "AAD," or the old module names like AzureAD and MSOnline. Teams working across mixed-vintage documentation need to recognise these as the same underlying service, rather than assuming a newer or different product is being described.
The commercial reason behind the rebrand was to position identity as the centre of a broader security perimeter that also includes network access. This reflects Microsoft's argument that in a cloud-first, zero-trust world, identity and network edge controls need to be managed as one coherent stack, rather than as separate identity and networking products bought from different places. For licence and cost management purposes, the practical entity that actually matters remains Entra ID and its P1/P2 tiers, since that is what drives per-user cost and what underpins Conditional Access, multi-factor authentication enforcement, and single sign-on across the rest of the Microsoft 365 and Azure estate. The wider Entra family products are generally separate, additively licensed services that an organisation adopts individually, rather than an all-or-nothing suite purchase.