Microsoft SC-500: Entitlement Management in Entra ID
Entitlement management is a lifecycle around a business-purposeful access bundle. Effective design uses catalogs, policies, approval, expiration and removal together, rather than reducing access governance to a request form. An access package must express a real role or temporary business task and specify who approves it, how long it lasts and which systems honor its expiry. Otherwise a clean self-service interface can conceal standing permissions that are difficult to remove.
On this page
- Translate a business role into an access package
- Use catalogs as bounded ownership and delegation
- Treat assignment policy as the enforceable contract
- Design approvals that add real judgment
- Make temporary and external access actually expire
- Automate membership carefully when source attributes change
- Review package changes for existing assignees
- Prove the complete request-to-removal lifecycle
Translate a business role into an access package
Access packages work best when they represent a coherent business requirement, such as temporary access for external auditors or a project team’s collaboration and reporting tools. Start by identifying the underlying resource permissions: membership of security or Microsoft 365 groups, supported enterprise application roles and SharePoint access. A package should grant only resources needed for that role. Bundling unrelated high-impact permissions simply because the same requester wants them creates broad access that an approver may not understand. Name and describe the package in business language so the person requesting it can tell what it will allow.
Use a small design exercise for a six-week external financial audit. The required bundle might include a project SharePoint site and one read-only enterprise application role, but not Azure subscription administration. Record the business sponsor, access owner, expected start and end dates, and how removal will be verified. This reveals whether the bundle should be one package or several: access with different owners, sensitivity or duration may deserve a separate lifecycle rather than a convenient universal package.
Use catalogs as bounded ownership and delegation
Every package belongs to a catalog, which also defines a boundary for resource selection and delegated management. Central identity administrators can establish Entra ID Governance controls while business application owners manage suitable catalogs and packages without needing tenant-wide roles. The catalog should contain resources with a coherent operating owner, not every enterprise application in one large unreviewable pool. External-access eligibility and other catalog settings also affect who can discover and request packages, so delegation needs configuration review alongside human responsibility.
Create an ownership matrix for catalog owner, package manager, resource owner and approval authority. Test that an authorized catalog manager can edit the intended package but cannot add a sensitive resource from an unrelated catalog or grant themselves Global Administrator. If the design depends on one employee having all these roles, the process is fragile when they change jobs. Delegation should preserve a clear route to obtain legitimate access without expanding administrative privilege across the whole tenant.
Treat assignment policy as the enforceable contract
A package requires assignment policies that determine eligibility, request availability, approval steps, expiration and renewal or review behavior. One package can support different populations under different policies when the resources are the same but risk and workflow differ. An internal employee may have a simpler approval process than an external partner, while a highly sensitive package may require explicit resource-owner approval. The policies should reflect the business access obligation rather than merely mirror the options available in the Microsoft Entra portal.
Walk through a request made by a partner with no current tenant identity. Determine whether the connected organization and policy permit the request, whether B2B invitation is required, who receives the approval and when access becomes active. Then simulate the approval being denied and the assignment expiring. Record the actual group or application permission that should disappear. A policy that looks correct in configuration but does not remove downstream rights when it expires is not delivering the intended lifecycle.
Imagine a temporary audit project that requires a partner to read selected SharePoint files and use one internal reporting application. Build an access package only after the resource owners identify the exact groups or application roles that grant those permissions. The assignment policy should define eligible connected organizations, approved requesters, business justification, one or more real approvers, expiration and renewal or review behavior. Putting unrelated permanent finance permissions into the same package would make the friendly package name misleading, even if it shortened the initial approval workflow.
Test the entire path with a representative partner account. Before approval, the user should not receive the protected role. After an authorized request and approval, verify actual downstream membership and application access, not just an approved portal status. When the project ends, verify the assignment expires and the resource permission is removed. If the same guest has access through another independent package, do not assume the guest object itself must be deleted. The effective access decision must follow all legitimate assignments, not simply one package’s status.
Changes to the package should trigger impact review. Adding a resource role can extend access for current assignees as well as future requesters, while shortening the assignment duration can disrupt active projects. Record who approved a material package change, how existing assignees are affected and whether downstream provisioning delays alter the actual removal time. That evidence distinguishes governed entitlement management from a request form that merely automates permanent group membership.
Design approvals that add real judgment
Approval is useful only when the reviewer understands why the access is needed and can say no. A manager may know the employee’s job assignment, while an application owner knows the data or transaction consequence. Multi-stage approval is justified when the stages answer different questions; asking several managers to rubber-stamp one vague request can increase delay without reducing risk. Use request questions for meaningful information such as project, sponsor, intended purpose and end date, not fields that nobody uses during a decision.
For a sensitive package, examine an approval request containing a specific justification and another containing only ‘urgent access’. The workflow should make the latter request actionable by asking for clarification or denying it rather than auto-approving based on team membership. Test delegate, alternate approver and timeout behavior so legitimate work does not stall when the primary owner is absent. The evidence should include who approved the assignment and under which policy, not just that the user appeared in a group.
Make temporary and external access actually expire
Temporary access is one of entitlement management’s clearest benefits over standing manual group membership. Assignment duration should follow the real task, with renewal requiring a justified continuing need when appropriate. External user identities and partner relationships complicate cleanup: a guest might hold several independent packages or application roles, so one package’s expiry may not imply the account itself can safely be deleted. Connected organizations also need lifecycle review after contracts end or partner domains change.
Test expiration in a sandbox and inspect the resulting resource membership and application access rather than relying solely on the My Access status. Confirm that revoked access disappears within the expected provisioning window and that legitimate unrelated assignments are preserved. If removal fails because a connector or downstream system is unavailable, create an owned operational exception and confirm it is resolved. Access that is approved temporarily but stays usable indefinitely is a standing privilege disguised as governance.
Automate membership carefully when source attributes change
Some packages can use supported automatic assignment scenarios based on user attributes. This is valuable for predictable business relationships, but the automation is only as trustworthy as HR and directory data. Missing department codes, shared cost centers, stale manager records or delayed employment changes can cause incorrect assignment and removal at scale. Apply separation-of-duties controls when roles are genuinely incompatible, and understand which resource combinations should never be granted together even if several policies would otherwise approve them.
Pilot the attribute rule with representative joiner, mover and leaver records, including an incomplete or misclassified identity. Check who should have access according to authoritative business data versus who actually receives it. A mover should not retain both old and new sensitive roles indefinitely because asynchronous provisioning lagged. Document where manual review overrides automatic behavior and which system owns correction of the source attribute rather than hiding bad data with permanent package exceptions.
Review package changes for existing assignees
An access package is not a static list. When a manager adds a resource or broadens an underlying group role, current assignees may receive a new capability without submitting a new request. That makes package modification itself a security-sensitive operation. The change owner should understand whether it affects only future assignments or expands current access, and approvals should reflect that blast radius. Maintaining clear version history and resource ownership helps auditors distinguish the originally approved package from the permissions users hold today.
Before adding a new enterprise application role to the audit package, list active assignees and decide whether they were ever approved for that additional access. If not, create a separate package or require a fresh decision. Test the new role with one pilot user and verify that no unrelated group membership changed. Periodically retire obsolete packages after moving legitimate users to successors so a catalog does not become a graveyard of broad, unmaintained permissions.
Prove the complete request-to-removal lifecycle
A well-governed package has evidence for request, eligibility, approval, active membership, review, renewal and final removal. Managers and resource owners should be able to reconstruct why a particular partner had access on a date and when that authorization ended. Monitor long-pending approvals, repeated denials, unused packages and assignments that fail to expire. These signals identify problems with ownership and workflow even when the platform technically supports all the configured features.
Perform one complete lifecycle test with a requester, reviewer and application owner rather than stopping after the first approved My Access request. Verify the resulting app permission, then let the short test assignment expire and show the revoke in the target service. Record failures with the responsible connector or administrator. Entitlement management delivers security when temporary business relationships produce temporary permissions and evidence, not merely when users stop sending ad hoc access-request emails.