Treat EntraID as one control plane, not the whole programme. Map which applications are governed natively, which are federated, and which need separate entitlement management. Then ensure provisioning, access review, and revocation are executed where the entitlement actually exists, not only where authentication begins.
What changes when EntraID is only one control plane?
The main shift is scope. If teams treat EntraID as the only place identity is governed, they miss applications that authenticate elsewhere, entitlement stores that sit outside EntraID, and revocation paths that must be executed in another control plane. Good governance starts by identifying where each entitlement is actually created, approved, reviewed, and removed.
That means the access model has to follow the application estate, not the directory product. Some systems can be governed natively through EntraID, some are federated but still enforce access decisions in the target app, and some require separate entitlement management because the authoritative control over access lives outside EntraID.
When those boundaries are unclear, access reviews become incomplete and revocation becomes slow or inconsistent. The practical question is not “is the user in EntraID?” but “where does this application trust identity, where is privilege stored, and which system can actually change or revoke it?”
Where access governance usually breaks down
The common failure is assuming authentication and authorization are the same thing. EntraID may be the front door, but the application can still hold its own roles, entitlements, groups, or direct assignments. If review happens only at the front door, teams may certify a sign-in path while leaving standing access untouched in the downstream system.
Another break point is lifecycle ownership. If provisioning is done in one tool but deprovisioning is manual in another, revocation lags behind termination, role change, or vendor offboarding. That creates an exposure window even when the directory itself is clean.
- Federation can hide local privilege. Users may authenticate centrally while holding access that is governed locally.
- Application-native entitlements often need their own review cadence and owner, especially where business roles are not mirrored in EntraID.
- Revocation should be validated at the entitlement source, not assumed because a directory record changed.
How to structure governance across mixed estates
A workable model starts with an application inventory that classifies each system by control locus: native EntraID governance, federated authentication with app-local authorization, or separate entitlement management. That classification should then drive who owns provisioning, who performs reviews, and which workflow actually removes access.
For high-value applications, the review process should verify the effective entitlement, not just the identity object. If a user can still act in the target system after the directory account is disabled, the governance process has failed in the wrong layer.
Where possible, standardise the handoffs: source of truth for joiner-mover-leaver data, approval authority for role changes, and a tested revocation path for each application class. NIST Cybersecurity Framework 2.0 is useful here because it pushes teams to treat governance, protection, detection, response, and recovery as connected outcomes rather than isolated tasks.
How should teams govern access when EntraID is only part of the estate?
Teams should govern access at the entitlement source, not only at the identity provider. Where the app owns its own roles or permissions, that system needs its own control evidence, owner, and review process. Where federation exists, confirm that the target application still enforces least privilege and that offboarding is complete in both layers.
In practice, that means you need a clear decision rule for every application: if access can be granted, changed, or revoked outside EntraID, then EntraID cannot be the only governance record. The application or entitlement platform becomes part of the control surface, and its data must feed recertification and deprovisioning decisions.
Use authoritative controls to anchor that design. NIST AI 600-1 GenAI Profile is not the right fit here, but NIST SP 800-53 Rev 5 Security and Privacy Controls directly supports the access control, identification, authentication, and audit expectations that mixed estates need. CIS Controls v8 also helps by reinforcing account management, access control, logging, and asset visibility across systems that do not all live under one directory.
Risk and Threat Considerations
The risk is not just inconsistent administration, it is invisible privilege. When access exists in a federated app, local role store, or separate entitlement engine, an organisation can believe it has removed access while the user still retains operational capability. That creates lingering exposure after termination, role change, vendor exit, or incident response.
Failure mechanism: Governance is applied only to the authentication layer, while the application continues to trust a separate authorization or entitlement source. Reviews certify the wrong object, and revocation does not reach the system that actually grants access.
Impact: Users may retain access longer than intended, privileged activity may persist after offboarding, and audit evidence can overstate control effectiveness because it reflects directory state rather than effective application access.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST CSF 2.0, NIST SP 800-53 Rev 5 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | GV.OC-01 — Organizational Context | Mixed estates require defining where access governance lives across systems. |
| Recommendation — Map each application to its true access-control owner and governance boundary. | ||
| NIST SP 800-53 Rev 5 | AC-2 — Account Management | Separate entitlement stores need lifecycle control beyond the directory. |
| AC-6 — Least Privilege | Federated and app-native access still needs least-privilege enforcement at the target system. | |
| AU-2 — Event Logging | Effective access governance needs audit evidence from the systems that actually grant access. | |
| Recommendation — Maintain authoritative account and entitlement records for every access path. Restrict permissions at the application or entitlement source, not only in EntraID. Log entitlement changes where access is granted and revoked. | ||
| CIS Controls v8 | CIS-5 — Account Management | Access governance across multiple control planes depends on consistent lifecycle administration. |
| Recommendation — Centralize account lifecycle processes while validating downstream revocation in each application. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | The topic is fundamentally about governing access across different control points. |
| Recommendation — Define and enforce access rules consistently across every system that holds entitlements. | ||
Practitioner Guidance
What to verify: For each application, verify where entitlements are created, where reviews occur, and what system actually executes revocation. If those are different systems, document the handoff and test it with a real removal event rather than assuming the directory change is sufficient.
Decision rule: If the application can be administered independently of EntraID, treat it as a separate governance domain with its own owner, review evidence, and deprovisioning check. Do not accept a single directory-centric review as proof of full access control.
Practitioner takeaway: The strongest governance model is the one that follows effective privilege, not the one that only follows sign-in. If access survives outside EntraID, your control model has to survive outside EntraID too.
Related resources from NHI Mgmt Group
- How should security teams govern access when only part of the application estate is connected to SSO and SCIM?
- How should security teams govern access when SASE is part of the control stack?
- How should teams govern SaaS access when the application estate keeps changing?
- How should organisations govern physical access as part of IAM?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 5, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org