Microsoft Entra PIM, also known as Privileged Identity Management (PIM), reduces standing administrator access by letting users activate eligible roles temporarily, subject to authentication, approval and time limits. Configuring PIM doesn’t remove existing permanent permissions; review and remove those assignments separately.
The important distinction is eligibility versus active access. Establish the role, scope and recovery arrangements first, then configure activation controls and test the complete workflow.
What Microsoft Entra PIM controls
Eligible and active assignments
An eligible assignment gives someone permission to request activation. An active assignment gives them the role’s permissions immediately. Activation creates temporary active access, which expires after the configured period.
Eligibility still carries risk because the user can activate under its configured conditions. Include eligible assignments in access reviews, even when the administrator has not activated recently.
Directory roles and Azure resource roles
Microsoft Entra directory roles control identity and Microsoft 365 administration. Azure role-based access control (RBAC) roles govern resources such as subscriptions, virtual machines and storage accounts.
Microsoft’s PIM overview covers both, but their policies are configured separately. PIM sits within Identity Governance, alongside access reviews, entitlement management and lifecycle workflows. Conditional Access complements these controls by evaluating authentication and access conditions.

Establish licensing and recovery first
Match licences and administrative permissions
PIM requires Microsoft Entra ID P2 or Microsoft Entra ID Governance licensing. Applicable licensing includes users benefiting from eligible assignments and people approving activation requests. Microsoft 365 Business Premium includes Entra ID P1, which does not provide PIM by itself.
Use a Privileged Role Administrator account to manage Entra role assignments and policies. Azure resource configuration requires appropriate permissions at the selected resource scope. Microsoft’s deployment guidance separates these responsibilities.
Keep emergency access independent
Maintain at least 2 cloud-only emergency accounts with permanent active Global Admin (Global Administrator) assignments. Making these accounts PIM-eligible adds an activation dependency during recovery.
Protect them with phishing-resistant Multi-Factor Authentication, controlled credential custody and monitoring. Conditional Access exclusions do not remove Microsoft’s separate mandatory MFA requirements. Our guidance on Entra emergency access accounts covers these recovery arrangements.
Apply 8 controls before wider deployment
Use this baseline for privileged roles, then adjust activation periods and approval requirements to each role’s operational risk.
| Control | Configuration approach |
|---|---|
| Least privilege | Select the role and scope required for the task. |
| Eligible access | Replace ordinary permanent human access with eligible assignments. |
| MFA | Require an additional authentication factor for privileged activation. |
| Approval | Require approval for Global Administrator and Privileged Role Administrator. |
| Justification | Require a meaningful reason for activation. |
| Time limits | Set short activation periods and eligibility expiry for time-bound access where appropriate. |
| Notifications | Notify responsible administrators and approvers about relevant events. |
| Oversight | Review assignments, activation history and completed removals. |
These controls address different security risks. Approval does not compensate for an unnecessarily broad role, and a short activation period does not remove permanent access inherited elsewhere.
Select at least 2 available approvers for critical roles, but understand the approval model.
Native PIM activation requires 1 approval, even when several approvers are listed. Selecting 2 approvers does not enforce 2 separate approvals.
The four-eyes principle normally means the requester and an independent approver. If your policy requires 2 independent approvals in addition to the requester, add a separate approval workflow; the standard PIM setting does not provide that sequence.
Configure the Entra role activation policy
Older Azure Portal instructions use Azure Active Directory > Identity Governance > Privileged Identity Management. Azure Active Directory is now Microsoft Entra ID; the Entra admin centre provides the current configuration route.
- Open ID Governance > Privileged Identity Management > Microsoft Entra roles > Roles. Select the role, such as Privileged Role Administrator.
- Open Role settings > Edit. Under Activation, set Activation maximum duration. Microsoft supports 1 to 24 hours; choose a shorter period where the work allows.
- Enable the requirements for MFA, justification and approval as appropriate. Select named approvers rather than relying on an undocumented default.
- Under Assignment, configure eligible-assignment expiry and restrictions on permanent active assignments. Eligibility expiry determines how long activation remains available; it does not determine each activation’s duration.
- Under Notification, configure recipients for activation and assignment events. Select Update, then reopen the policy to confirm the saved configuration.
The activation authentication requirement does not necessarily produce a fresh prompt every time. An existing MFA claim can satisfy the basic requirement.
Where fresh authentication or phishing-resistant methods are required, configure an authentication context with the appropriate authentication strength and sign-in frequency. Test the policy in report-only mode before enforcement. Our explanation of Conditional Access policy failures helps distinguish missing prerequisites from incorrect policy scope.
Assign eligibility through controlled groups
Use eligible membership for team-based access
For eligible roles such as Entra directory roles, create a role-assignable security group with Assigned membership. Assign the required directory role to that group, then manage administrator membership through PIM for Groups.
In PIM > Groups, bring the group under management. Open Assignments > Add assignments, select Member, choose the administrators and set the assignment type to Eligible.
In this model, the group’s role assignment remains active. Individuals receive its permissions only while their group membership is active. This differs from giving a user an eligible directory-role assignment directly.
Configure the group activation policy separately
Open the group’s Settings, select Member, then configure activation duration, authentication requirements, justification, approval and notifications.
The directory-role activation policy doesn’t automatically become the group’s membership policy. Protect group ownership and membership administration because anyone able to add active members may bypass the intended activation process.
Where group-based management is unsuitable, direct eligible user assignments remain supported. Document the exception and include those users in the same review process.
Configure Azure RBAC at the narrowest scope
Azure resource roles use a separate PIM configuration surface. Open PIM > Azure resources, select the relevant subscription, resource group or resource, then open Settings, choose the role and select Edit.
Apply least privilege at both role and scope. A subscription assignment covers more resources than a resource-group assignment; a resource-group assignment covers more than an individual resource.
Microsoft’s Azure role settings guidance describes the activation, assignment and notification controls. Configure these for the selected scope rather than assuming Entra directory-role settings apply.

Review inherited permissions before removing direct assignments. Another group or parent-scope assignment may leave the administrator with standing access.
Test a complete DevOps activation
For an engineer maintaining an existing Azure virtual machine, configure eligible Virtual Machine Contributor access at the VM’s scope. Give networking tasks separate permissions where required rather than automatically granting subscription-wide Contributor.
The engineer opens PIM > My roles > Azure resources > Eligible assignments, selects the role and chooses Activate. They enter a justification, request a duration within the policy limit and satisfy the authentication requirements. If approval is enabled, access remains pending until approved.
For eligible group membership, activation happens through My roles > Groups instead.
Test the actual maintenance operation after approval, then test expiry and early deactivation. Microsoft’s role activation guidance explains the temporary assignment process.
Do not assume every application immediately discards cached permissions when activation ends. Confirm the behaviour of the administrative tools used in your environment, including any required sign-out or session refresh.
Monitor activity and review retained eligibility
Connect activation records to investigation
Review PIM audit logs for activations, approvals, assignment changes and unexpected permanent access. Correlate these records with Entra sign-in logs and subsequent administrative activity.
Use Azure Monitor diagnostic settings to export required Entra log categories to Log Analytics or another suitable destination. Define retention, alert ownership and response procedures separately. Exporting logs does not establish that anyone investigates them.
A successful second-factor challenge also does not establish user intent. Our guidance on Microsoft 365 device-code phishing explains why authentication evidence needs context.
Review active and eligible assignments
Set the frequency of access reviews according to role risk, Compliance requirements and other applicable obligations. A quarterly cycle can be appropriate, but it’s not a universal requirement.
For each access review, record the role, scope, reviewer, decision, justification and resulting change. Include eligible assignments, group memberships and direct assignments.
Distinguish non-responses from explicit approvals. For denied access, retain evidence that removal completed or assign a remediation task with an owner and deadline. An access review decision alone doesn’t prove that permissions were removed.
Frequently asked questions
Does configuring PIM remove permanent administrator access?
No. Existing active assignments remain until they expire or are removed. Review direct assignments, group membership and inherited Azure RBAC access before concluding that standing permissions have been eliminated. Preserve documented emergency-access exceptions.
Does PIM replace Conditional Access or managed identities?
No. PIM governs privileged activation; sign-in policies evaluate authentication and access conditions. Managed identities provide Azure workloads with an identity without manually maintained application credentials. They don’t use a human administrator’s interactive PIM activation workflow.
Make temporary access the operational default
A working Microsoft Entra PIM deployment requires more than eligible assignments. Activation policies, group controls, emergency access and evidence of completed reviews must work together.
Start with a limited administrator group, test the required tasks and remove the permanent permissions the pilot replaces.
Speak to our team about reviewing your Microsoft 365 and Azure administrative access, Conditional Access policies and security monitoring services.





1 Comment
[…] policies under PIM > Azure resources, separately from Entra directory-role policies. Our PIM configuration guidance explains the […]