CIO Brief: Renames Don't Change Risk — But Licensing Might
Retrospective: this article looks back at events from July 2023, written in 2026 with the benefit of hindsight.
The short version: In 2023, Microsoft renamed Azure Active Directory to Microsoft Entra ID. Nothing about security changed with the name. But renames are a good prompt to check what you're paying for — and whether you use it.
What the rename means for you
- Your configuration and access are unchanged.
- Product and license names in contracts and invoices changed.
- Older tools and scripts using retired technology need updating.
Why it's worth a look anyway
Microsoft's identity licenses (Entra ID P1 and P2) include significant security features — risk-based sign-in protection, just-in-time admin access, access reviews — that many organizations pay for but don't configure. A rename is a natural moment to compare what you have with what you use.
Questions to ask your team
- Which Entra ID license level do we have, and for how many users?
- Which security features in that license have we configured?
- Are any of our scripts using retired tools that could stop working?
- Are we paying for higher licenses for users who don't need them — or missing them for users who do?
What good looks like
Licenses matched to needs, the features you pay for turned on, and documentation and scripts up to date.
The decision
Ask for a license utilization review of Entra ID P1/P2 features. It's often the fastest way to improve identity security without new spending.
- Azure AD Becomes Microsoft Entra ID (July 2023): What Actually Changed Platform Changes
- How to Update Documentation, Scripts and Policies After the Entra ID Rename How-To & Hardening
- Entra ID Configuration Health Checklist How-To & Hardening