Four built-in Entra ID roles changed in a week, and there was no announcement attached. That is the part that matters. If you treat a built-in role as a fixed least-privilege contract, you are trusting something Microsoft clearly treats as a moving target.
The source post points to four roles with recent changes: Entra Backup Administrator, AI Reader, Tenant Governance Administrator, and Tenant Governance Relationship Administrator. Two of these are marked privileged in Microsoft’s own role reference today: AI Reader and Tenant Governance Administrator. That alone should be enough to get this onto your review list.
This is not me arguing that Microsoft should never evolve roles. Of course they will. New services ship, admin surfaces expand, and role definitions follow. The problem is operational: access approvals are usually made once, then forgotten. When the role definition changes later, your original approval no longer means what you thought it meant.
What changed in practice?
The source calls out a mismatch between tracked changes and Microsoft’s current documentation for Entra Backup Administrator. Microsoft documents it as a role for backup snapshots and recovery jobs. The tracked history suggests it should also be able to enable or disable hard deletion protection on users, groups, applications, and service principals. If that tracking is accurate, that is not a cosmetic change.
Microsoft’s current built-in roles reference also shows these descriptions:
| Role | Current Microsoft description | Privileged |
|---|---|---|
| Entra Backup Administrator | Manage all aspects of Microsoft Entra Backup, such as create recovery jobs and manage backup snapshots. | No label shown |
| AI Reader | Read all aspects of Microsoft 365 Copilot and AI-related enterprise services in Microsoft 365. | Yes |
| Tenant Governance Administrator | Manage all capabilities in the Microsoft Entra Tenant Governance service. | Yes |
| Tenant Governance Relationship Administrator | Manage all aspects of tenant governance relationships, except accepting requests. | No label shown |
The AI Reader role is the other one I would not wave through casually. Microsoft documents broad read access to Copilot settings and directory objects including users, groups, applications, service principals, role assignments, and role definitions. “Reader” sounds harmless until you read the actual permissions.
Why this matters more now
Entra roles are sprawling into Copilot, agent identities, backup, cross-tenant governance, and more. That means silent changes have second-order effects: yesterday’s narrow admin role becomes today’s access path into a new product area. If you are building Microsoft Copilot and AI agents, or tenant-to-tenant controls, your identity model gets more fragile if it depends heavily on Microsoft’s built-ins staying still.
For most tenants, there is no immediate incident here. But if you assigned any of these roles because they looked narrowly scoped a month ago, verify them now. This is exactly the sort of thing that should show up in an AI and automation audit or privileged access review, not after someone notices a weird permission in production.
What I’d do
First, review active and eligible assignments for these four roles. Then compare the role definition in Microsoft’s current reference with the version history from the community tracker cited by the source. If a role now grants more than you intended, remove the assignment or replace it.
Second, stop using built-in roles as if they were permanent design artifacts. They are convenient defaults, not stable contracts.
Third, where the permission surface really matters, look harder at custom roles. Microsoft notes in its own documentation that only a subset of built-in permissions is available for custom roles, so this is not a perfect escape hatch. But for sensitive operational areas, custom roles still age better than blind trust. And if your teams are automating reviews or provisioning around role assignments, this belongs in your automation workflow design, not in a quarterly spreadsheet.
My practical takeaway is simple: add role-definition drift to your regular Entra review process. Waiting for Message Center is waiting too late.
