Access granted by ticket and never removed is the main source of privilege creep, and Microsoft Entra entitlement management exists to replace it with requestable, approved, time-limited bundles of access. Entitlement management is the Microsoft Entra ID Governance feature that automates access request workflows, assignments, reviews and expiry for internal users, external guests and, increasingly, service principals and agent identities. This guide explains how access packages, catalogues and policies work, how to delegate administration safely, the integrations and agent identity features that bring non-human identities into scope, what to log, and a hardening baseline. It is for identity engineers and IGA owners running Entra ID; for product selection across vendors, see the IGA Buyer's Guide. Product details were checked against Microsoft Learn on 27 October 2026 and some features described are in preview, so confirm current status before relying on them.
This is an independent guide from NHI Mgmt Group, based on Microsoft's public documentation as of November 2026. It is not sponsored or reviewed by Microsoft. Product features change, so confirm settings against Microsoft's current documentation.
Key takeaways
- Design catalogues around ownership, not technology. A catalogue is the unit of delegation, so align it with the business or resource owners who should approve and maintain the access inside it.
- Every policy needs an expiry and a review. Assignments without an end date recreate the standing access problem entitlement management is meant to solve.
- External user lifecycle is a setting, not a project. By default, guests who lose their last assignment are blocked and removed after 30 days, but only guests that entitlement management invited or that were converted to governed.
- Delegated roles are privileged roles. Catalogue owners and access package managers decide who gets access to their resources; protect, review and limit them like other admin roles.
- Agents and service principals can now be governed the same way. Access packages can grant groups, API permissions and Entra roles to agent identities, with a human sponsor accountable for each.
How identity and access work in entitlement management
Microsoft's model has a small set of objects:
| Object | What it is | Design guidance |
|---|---|---|
| Catalogue | A container of related resources and access packages; the unit of delegation | One per business area or resource owner group (for example Finance applications, Partner collaboration). Avoid one catalogue per package and one catalogue for everything. |
| Resource and resource role | An asset with grantable roles: security group, Microsoft 365 Group or Team, enterprise application, SharePoint Online site; in preview, API permissions for agents and service principals, and SAP IAG business roles | Add resources only to the catalogue whose owners are accountable for them. |
| Access package | A bundle of resource roles needed for a task or project, always inside a catalogue | Name for the job ("Accounts payable clerk"), not the resource ("SAP-AP-group"). |
| Policy | Rules on the package: who may request (internal users, connected organisations, service principals, agents), approval stages, duration and reviews | Separate policies for employees and externals, each with its own approvers and expiry. |
| Assignment | An identity's grant of all resource roles in a package, usually time-limited | Can come from request, direct admin assignment, automatic rules or lifecycle workflows. |
| Connected organisation | An external Entra directory or domain whose users may request access | One per partner; ties guest lifecycle to the relationship. |
Entra roles are not a direct resource type in the core model. The usual pattern is a role-assignable group placed in an access package, with the Entra role assigned to that group; Microsoft 365 licences and Azure roles can be governed through groups in the same way. For roles that should be activated just in time rather than held for the assignment period, combine the group with Privileged Identity Management; see the Privileged Identity Management (PIM) Guide.
External users
When an approved requester from a connected organisation is not yet in the directory, entitlement management creates a B2B guest account without sending an invitation email; the user gets an email when access is delivered. Under Lifecycle of external users, the defaults block sign-in when a guest's last assignment ends and remove the guest after 30 days (0 removes immediately). For this to work, cross-tenant inbound settings must allow the partner tenants, external collaboration allow or block lists must not exclude partner domains, and conditional access policies that would block guests (device or location requirements, for example) need the Entitlement Management application excluded. Microsoft recommends setting "Guests can invite" to No, so access arrives only through governed packages. See the Entra ID Cross-Tenant Access and B2B Guest Governance Guide.
Separation of duties
An access package can be marked incompatible with other access packages or with security-enabled groups (including dynamic groups and groups synced from AD). A user holding the incompatible access cannot request the package, and administrators cannot make an incompatible new assignment either. The relationship is one-way, so add it on both packages for mutual exclusion, and existing overlapping assignments are not removed: the Additional access count on the Separation of duties page lists them for clean-up. See the Segregation of Duties Guide.
Admin roles and privileged access
| Role | Scope | Can do | Risk if misused |
|---|---|---|---|
| Identity Governance Administrator (directory role) | Tenant | All entitlement management tasks; can add applications (not groups or sites) as catalogue resources | Can grant itself or others any packaged access |
| Global Administrator | Tenant | Everything, including adding any group, application or site to any catalogue | Full control; keep out of day-to-day governance |
| Catalogue creator | Tenant | Create catalogues and become their first owner; cannot add resources it does not own | Catalogue sprawl |
| Connected Organization Administrator | Tenant | Create and manage connected organisations | Opening the tenant to new partner directories |
| Catalogue owner | Catalogue | Manage resources, packages, policies and other owners in the catalogue | Changing approvers or removing expiry for sensitive resources |
| Access package manager | Catalogue | Create and edit packages and policies; assign and remove identities | Creating a policy that auto-approves broad access |
| Access package assignment manager | Catalogue | Directly assign and remove identities; cannot edit packages or policies | Direct assignments that bypass approval |
| Catalogue reader | Catalogue | View packages | Low |
Microsoft notes that User Administrator can no longer create catalogues or manage packages in catalogues it does not own, so legacy delegation built on that role should move to Identity Governance Administrator or catalogue roles. Make Identity Governance Administrator an eligible PIM role with approval, keep catalogue owners to named resource owners, and review catalogue role holders at least quarterly. A policy edit is effectively a privilege grant: treat it as a change.
Integrations, API tokens and service accounts
- Microsoft Graph automation: scripts and pipelines that manage packages use the
EntitlementManagement.ReadWrite.Allpermission. An application holding it as an application permission can create policies and assignments tenant-wide, so prefer delegated access with a catalogue role, or a managed identity or certificate-authenticated app with a named owner, and never a client secret in a script. See the Azure Entra Client Secrets Security Guide. - Custom extensions (Logic Apps): an access package policy can call a Logic App when a request is created or approved, when an assignment is granted or removed, and 14 days or one day before an assignment expires. Request-stage extensions can use Launch and wait, pausing the request until the workflow calls the Graph resume API, and can deny requests at the created or approved stages, which is useful for external SoD or background checks. Extensions created after 17 March 2023 use proof-of-possession tokens; convert older "regular" extensions. The Logic App's own identity and connectors become part of your governance trust chain, so give them owners and least privilege.
- Connected applications and provisioning: an enterprise application added as a resource only governs its app role assignments. Whether the user is created in the downstream system depends on provisioning (SCIM or connectors); check that removal deprovisions as well as unassigns. The Entitlement Catalogue and Application Onboarding Guide covers onboarding at scale.
- Service principals and agent identities: policies can target "users, service principals, and agent identities in your directory", with All agents for Entra Agent ID identities and All service principals for other workloads. Packages can grant security groups, delegated and application OAuth permissions for Microsoft Graph and other APIs, and Entra roles. An agent can request a package itself through an
accessPackageAssignmentRequest, its sponsor can request on its behalf, or an administrator can assign directly. Sponsors receive expiry notifications and can request extension; if they do nothing, access ends on the expiry date, and if a sponsor leaves, sponsorship transfers to their manager. Microsoft lists agent governance licensing as Microsoft 365 E7, or Microsoft Agent 365 with Entra P1 or Microsoft 365 E3. See the Microsoft Entra Agent ID Guide.
Governing agent and service principal access through packages is a meaningful change for NHI programmes: it gives machine access the same request, approval, expiry and accountability trail as human access, instead of permissions granted once in the app registration and never revisited. Start with agents that request application permissions to Microsoft Graph, the most powerful and least reviewed grants.
Logging and detection
Entitlement management events appear in the Entra audit log under the EntitlementManagement category and are kept for 30 days in Entra itself. Send audit logs through Diagnostic settings to Log Analytics, Microsoft Sentinel or another SIEM for longer retention. Useful detections:
- Policy changes:
CreateEntitlementGrantPolicyandUpdateEntitlementGrantPolicyoperations, especially changes that remove approval, extend or remove expiry, or widen who can request (for example to all users or all connected organisations). - Direct assignments: assignments made by administrators rather than through requests, in sensitive catalogues.
- Catalogue role changes: new catalogue owners and access package managers.
- Access granted outside packages: the Application role assignment activity workbook shows app role changes not made through entitlement management, such as direct grants by a Global Administrator.
- Agent and service principal requests: requests for application permissions or Entra roles by agent identities, and extensions requested by sponsors.
- Connected organisation changes: new partner directories or domains.
Metrics that show the programme is working:
| Metric | Target or direction |
|---|---|
| Share of access to onboarded resources granted through packages rather than direct assignment | Rising towards 100 percent |
| Package policies without an expiry or review | Zero, or each documented |
| Guest accounts not governed by entitlement management | Falling; convert or remove |
| Median request-to-fulfilment time | Stable or falling, so users do not route around the process |
| Agent and service principal assignments with an active sponsor | 100 percent |
| Existing SoD conflicts (Additional access count) | Falling to zero |
Hardening baseline
- Plan catalogues and owners: list resource owners for the first wave of applications, groups and sites, and create catalogues per owner group with named catalogue owners. Restrict catalogue creation to a small group.
- Set external user lifecycle: keep block and remove enabled, choose the removal delay (30 days is the default), set "Guests can invite" to No and configure cross-tenant access per connected organisation.
- Pilot one catalogue: choose a contained use case, such as a partner project or one department's applications. Run packages in parallel with existing group memberships, then convert existing members into assignments so they gain an expiry.
- Write policies with expiry, approval and reviews: for example 90 to 180 days for employees, 30 to 90 days for externals, two-stage approval for sensitive resources, and recurring access reviews on the policy. See the Access Reviews Guide.
- Add SoD incompatibilities for known toxic combinations, both directions, and clean up the Additional access list.
- Remove the back doors: once a resource is governed, stop direct group and app role assignments to it, and alert on them.
- Bring in NHIs: create agent and service principal policies with sponsors, short expiry and approval by the API owner for application permissions.
- Roll back safely: disabling a policy stops new requests without removing existing assignments; removing a resource role from a package removes that access from all assignees, so test changes on a copy of the package first.
Decision guidance: small tenants can start with one partner catalogue and one sensitive application, which alone fixes most guest sprawl. Large organisations should drive birthright access from lifecycle workflows and automatic assignment policies and reserve request-based packages for non-birthright access; see the Joiner-Mover-Leaver Guide. Where many non-Microsoft applications and complex SoD rules are in scope, compare entitlement management with a dedicated IGA platform before building extensive custom extensions.
| Control | NIST SP 800-53 Rev. 5 | NIST CSF 2.0 |
|---|---|---|
| Request, approval and expiry of access | AC-2, AC-2(3) | PR.AA-05 |
| Separation of duties | AC-5 | PR.AA-05 |
| Least privilege for delegated admins | AC-6 | PR.AA-05 |
| External personnel | PS-7 | GV.SC-07 |
| Audit of access changes | AU-2, AU-6 | DE.CM-03 |
Common misconfigurations
- Policies with no expiry: packages become a slower way to grant permanent access.
- "All users" or "All connected organisations" requestors on sensitive packages with self-approval or a single approver who approves everything.
- Ungoverned guests left behind: guests invited before entitlement management are not covered by the lifecycle settings until converted to governed.
- Direct assignments continuing alongside packages, so reviews of package assignments miss the real access.
- Over-broad Graph automation: a service principal with
EntitlementManagement.ReadWrite.Alland a long-lived client secret can rewrite every policy. - One-way SoD rules that block only one direction of a toxic combination.
- Agent identities with no sponsor or sponsors who approve every extension without review.
Practitioner checklist
- Define catalogues by resource ownership and assign named catalogue owners.
- Restrict catalogue creation and make Identity Governance Administrator a PIM-eligible role.
- Give every policy an expiry, approval stages and a recurring access review.
- Enable external user block and removal, and set "Guests can invite" to No.
- Convert existing guests and group members into governed assignments.
- Configure SoD incompatibilities in both directions and clear existing conflicts.
- Stream EntitlementManagement audit events to the SIEM and alert on policy and role changes.
- Replace secrets on automation apps with managed identities or certificates and scope their permissions.
- Govern agent and service principal access through packages with sponsors and short expiry.
- Alert on direct assignments to resources that are governed by packages.
Standards and references
- Microsoft Learn: What is entitlement management?
- Microsoft Learn: Delegation and roles in entitlement management
- Microsoft Learn: Govern access for external users in entitlement management
- Microsoft Learn: Configure separation of duties checks for an access package
- Microsoft Learn: Governing agent identities with access packages
- Microsoft Learn: Trigger Logic Apps with custom extensions in entitlement management
- Microsoft Learn: Archive logs and reporting on entitlement management
- NIST: SP 800-53 Rev. 5
Related NHI Mgmt Group resources: IGA Buyer's Guide · Entra ID Security Guide · Access Reviews Guide · Microsoft Entra Agent ID Guide