Microsoft SC-500: Entra ID Identity Governance
Microsoft Entra ID Governance connects identity creation, access delivery, privileged activation, review and removal. The difficult work is defining authoritative triggers, accountability and proof that downstream systems reflect the decision. Each joiner, mover, leaver or external-access event should have a named source of truth and a verifiable end state. Provisioning a group is not enough if connected applications keep stale rights after the business relationship changes or a review denies continued access.
On this page
- Identify the authoritative trigger for each lifecycle
- Separate identity lifecycle from access lifecycle
- Govern packaged access around purpose and expiry
- Use access reviews to decide continued eligibility
- Control standing privilege with PIM and recovery exceptions
- Use automation with failure ownership and audit trace
- Extend ownership to guests and emerging nonhuman actors
- Resolve HR, IAM and application ownership
- Measure actual removal, not configured feature count
Identify the authoritative trigger for each lifecycle
Identity governance begins with a trustworthy reason why an identity exists and what relationship it represents. An employee may be created from an HR system, a guest from an approved partner engagement and a workload principal from an application owner. These are not interchangeable triggers. Identity lifecycle processes should know when a person joins, changes role or leaves, and access lifecycle processes should react to that change. A well-configured Entra tenant can still grant incorrect permissions if its authoritative department, manager or employment attributes are wrong.
Create a joiner-mover-leaver table for a staff member transferring from Finance to Operations. Name the source event, expected group or package changes, downstream applications and responsible owner. Then test a missing or late HR update. Does the workflow alert an operator and stop risky access from persisting, or silently wait until a periodic cleanup? The most useful governance evidence includes both the access decision and the source relationship that justified it.
Separate identity lifecycle from access lifecycle
Creating a Microsoft Entra account does not necessarily deliver every application role required for a job, and disabling the directory account does not automatically remove a local account in every external SaaS tool. Lifecycle Workflows, provisioning, access packages, dynamic or assigned groups and access reviews address different stages of the process. Choose one primary lifecycle mechanism for a resource where feasible so a manual group, an access package and a local app administrator do not each create independent unmanaged grants for the same entitlement.
For an application provisioned through SCIM, verify what happens when a user changes department or leaves. Confirm that the directory decision reaches the SaaS account within its actual propagation window and that a failed connector produces an operational exception. A recorded Entra disablement is incomplete evidence if the SaaS application still has a separate active credential. Keep ownership of the downstream provisioning path visible to both IAM and the business application team.
Govern packaged access around purpose and expiry
Entitlement management can package resource permissions with request, approval, duration and external-partner controls. Its purpose is not just a friendlier portal: it converts temporary business authorization into a lifecycle that can be reviewed and removed. A project package should not bundle unrelated administrative or financial capabilities for convenience. Catalog and package owners may be delegated business roles so the central identity team does not become the sole approver for every change, but that delegation must remain within meaningful resource boundaries.
Follow a short project assignment from request through expiration. Determine who could request it, whether approval added judgment, which roles became active and whether the target application revoked access at the end. If the project changes scope, inspect the consequences of adding a new resource to a package with existing assignees. The operating standard is an auditable business relationship, not an ever-growing group membership list. See Entra entitlement management for the package-level controls.
Use access reviews to decide continued eligibility
Access reviews are strongest when the reviewer understands the resource, why the principal has it and whether the relationship still justifies it. The most valuable targets include guest users, privileged assignments and high-sensitivity applications whose original request may be months old. A campaign that asks managers to approve hundreds of names with no activity or business context encourages blind approval. Review design should provide relevant evidence where supported and set a proportionate frequency based on risk and normal assignment duration.
Test the outcome of a denied review item, not only the completion of the review campaign. Does membership or eligibility disappear from the target resource, and does a downstream connector reflect it? If a resource owner repeatedly defers decisions, assign an escalation route rather than automatically treating silence as permanent permission. The goal is a demonstrable reduction in stale access; a high ‘campaigns completed’ metric is not proof when old rights continue to function.
One high-value review scenario is an external consultant who finished a project but still belongs to several collaboration groups. A reviewer should see the business purpose, relevant sponsor, assignment source and available activity evidence, then decide whether each entitlement remains necessary. Design the review outcome to revoke the correct access rather than indiscriminately disabling an account that may support an unrelated active engagement. Where auto-apply is enabled, first test how nonresponses, denied decisions and disconnected downstream applications are handled. The important success measure is access actually removed at the resource, not merely a completed reviewer campaign.
After a review closes, sample both a retained and a revoked assignment, verify downstream effective permissions and keep the decision trail. If a provisioning connector failed to remove membership, route the exception to an owner rather than treating the campaign’s status as proof of security. These are controls over continuing eligibility, distinct from initial authentication or one-time approval.
Control standing privilege with PIM and recovery exceptions
Privileged Identity Management adds eligible assignments, activation requirements, time limits and audit evidence for supported administrative roles and PIM for Groups scenarios. This reduces the amount of privilege available during ordinary work, but it must be paired with role scope and independent review of who should remain eligible. PIM does not decide whether a former employee or contractor still requires administrative access. Emergency access is a distinct, deliberately narrow exception where permanently usable credentials may be necessary to recover from authentication or PIM failure.
Design a privileged maintenance operation in which the operator receives eligible access, activates through the configured controls, performs the intended change and loses the active right afterward. Test that an ineligible principal cannot activate it and that relevant alerts reach the security owner. Separately rehearse recovery when the PIM workflow itself is unavailable. The emergency identity should be independently authenticated, securely held and rarely used, not a convenient way around the normal approval workflow.
Use automation with failure ownership and audit trace
Lifecycle Workflows and automatic assignment can make onboarding and offboarding faster, but they operate on events and data from other systems. Every automated transition needs an owner who understands the triggering condition, possible downstream failures and recovery method. An action that fails after half the target systems were updated requires reconciliation, not a blind replay that might duplicate accounts or grants. Store enough state to determine which step actually completed and whether a compensating removal remains required.
Simulate an outage in one downstream provisioning connector during an offboarding run. Confirm that successful revocations remain in place, the failed destination creates a visible exception and the next controlled retry is safe. Avoid declaring the whole leaver process complete merely because the workflow says ‘finished’. Governance automation becomes trustworthy when it fails visibly and can be reconciled to the actual resources, not when it simply removes manual tickets from the help-desk queue.
Extend ownership to guests and emerging nonhuman actors
External identities need a sponsor, allowed resources, an end to their business relationship and a method for verifying removal. Workload principals and newer agent identities similarly need purpose, owner, role scope and retirement conditions, although supported governance features and licensing may differ from established workforce identity processes. Do not assume a preview agent-governance feature has identical lifecycle behavior to human access packages. The durable question is who will notice when an identity is unused, compromised, overprivileged or no longer justified.
Build separate inventories for partners and application or agent principals. For each, record owner, access target, authorization type, last legitimate use and removal trigger. A production application may need a user-assigned managed identity that survives compute redeployment, while a short-lived worker identity should disappear with its resource. Governance succeeds when it can explain these differences rather than forcing every nonhuman principal into the same employee-oriented workflow.
Resolve shared ownership across HR, IAM and application teams
Identity governance often fails at organizational handoffs rather than at authentication. HR can confirm employment status but may not know which application contains regulated data; the IAM team can execute a workflow but cannot decide whether a contractor still needs a project entitlement; the application owner knows the business consequence but may not understand provisioning failures. Establish a responsibility map for decisions, system configuration, exceptions and evidence. An access review with no qualified reviewer is a procedural success but a poor security control.
At the next leaver or partner-access review, pick one difficult case and ask who supplies the authoritative event, who approves removal and who checks the target application’s result. Track how long disputed ownership takes to resolve and whether risky access remains active meanwhile. Fix missing business ownership and stale directory data at the source instead of compensating with ever-broader automation. This makes governance sustainable when teams, vendors and applications change.
Measure actual removal, not configured feature count
A governance dashboard can report many workflows, packages and review campaigns without demonstrating that access reaches the right person quickly or disappears at the right time. Useful measures include elapsed onboarding, failed offboarding connectors, stale privileged eligibility, unowned guests, expired packages with residual downstream rights and unresolved review decisions. The numbers need an accountable owner and a route to remediation. Legal and security audit evidence should show who approved an access grant, under which policy, what changed and when it was revoked.
Conduct a small quarterly sample across employment change, external project expiry and privileged-access activation. Trace source event, directory state, package or group membership, application permission and audit trail. Record exceptions with cause and resolution. If the sample shows recurring manual cleanup, simplify the authority path and fix source-data quality instead of adding yet another overlapping process. A mature Entra governance system lets access follow a real business relationship accurately over time.