Privileged Identity Management: just-in-time instead of standing admin rights for Entra roles and Azure resources
Key takeaways
- With Privileged Identity Management (PIM), admin roles are eligible rather than permanently active. Whoever needs a role activates it for a limited time, with MFA, a justification and, for critical roles, approval by a second person.
- PIM covers three areas: Microsoft Entra roles, Azure resource roles and groups (PIM for Groups). Settings apply per role, and for Azure additionally per resource.
- PIM requires Microsoft Entra ID P2 or Microsoft Entra ID Governance for everyone who is eligible, approves requests or performs access reviews.
- Two emergency access accounts deliberately remain permanently active Global Administrators. They are excluded from blocking Conditional Access policies and monitored without gaps.
- Activation history, approvals and access reviews are the evidence in an audit. The logs belong in a Log Analytics workspace, because Entra ID keeps them for only 30 days.
In assessments we often find permanently assigned Global Administrators in Microsoft Entra ID and Owner rights on entire Azure subscriptions. Each of these accounts holds its full rights around the clock. If one of them is compromised, for example through a phishing page that captures the sign-in token, the attacker can immediately change everything the role allows. For management this is a liability question: auditors working against ISO 27001 or NIS2, and cyber insurance questionnaires, ask how privileged access is limited and traced. Microsoft Entra Privileged Identity Management answers that question technically. This article explains how PIM works, which settings we recommend and what you need to license.
What is the difference between eligible and active assignments?
PIM has two types of role assignment. An active assignment takes effect immediately and requires no further step. An eligible assignment means the person may activate the role, but only holds it after activation and only for the configured duration. Once activated, the rights are identical to a permanent assignment. The difference is that the rights do not exist most of the time.
Both types can be permanent or time-bound, with start and end dates. Microsoft’s PIM deployment plan is clear: no permanently active assignments except for the emergency access accounts. When you introduce PIM, the Discovery and insights view helps. It lists existing privileged assignments and can convert permanent assignments into eligible ones.
How does activation work and which settings do we recommend?
The rules for activation are called role settings and apply per role. In the Microsoft Entra admin center, go to ID Governance > Privileged Identity Management > Microsoft Entra roles > Roles, select the role, then Role settings > Edit. You need at least the Privileged Role Administrator role. The most important settings:
- Activation maximum duration: how long an activation lasts at most, between 1 and 24 hours.
- On activation, require multifactor authentication: the person confirms with MFA before activating. If they already completed MFA in the same session, Entra ID might not prompt again. If you want a specific method, such as phishing-resistant MFA, at every activation, combine a Conditional Access authentication context with an authentication strength instead.
- Require justification on activation: a reason is mandatory, which makes the history readable in an audit.
- Require ticket information on activation: a ticket field. Entra ID does not check the number against your ticketing system; it is for documentation only.
- Require approval to activate: activation needs approval. Approvers do not need an admin role themselves. Microsoft recommends at least two approvers.
- Assignment duration: whether eligible assignments expire. Time-bound assignments force regular confirmation of rights.
Be careful with approval: if all Global Administrators and Privileged Role Administrators are only eligible, approval is required and no approver is configured, you lock yourself out of the tenant. The emergency access accounts described below, together with named approvers, prevent this.
We use the following values as a starting point. They follow the example tables in Microsoft’s PIM deployment plan and are adjusted to your operating model:
| Role | Max. activation | Authentication on activation | Approval |
|---|---|---|---|
| Global Administrator, Privileged Role Administrator | 1 hour | phishing-resistant via authentication context | yes, by a second person |
| Security Administrator, Conditional Access Administrator | 1 to 2 hours | phishing-resistant via authentication context | yes |
| Exchange, SharePoint, Intune Administrator | 2 to 4 hours | MFA | no, justification is enough |
| Helpdesk Administrator | up to 8 hours | MFA | no |
| Azure Owner and User Access Administrator (production subscriptions) | 1 hour | MFA or authentication context | yes, by other owners |
For Azure roles, you will find the settings under ID Governance > Privileged Identity Management > Azure resources: select the resource and open Settings. Owners and User Access Administrators of the resource can change them. Note that role settings at subscription level are not inherited by resource groups. If you assign roles on resource groups, set the role settings there as well.
Entra roles, Azure resource roles and PIM for Groups: what belongs where?
PIM manages three kinds of rights. The distinction matters because each has its own settings.
| Area | What it controls | Typical roles | Notes |
|---|---|---|---|
| Microsoft Entra roles | Administration of Entra ID, Microsoft 365, Intune and other online services | Global Administrator, Security Administrator, Exchange Administrator | Bring Global Administrator and Security Administrator under PIM first |
| Azure resource roles | Azure RBAC on management group, subscription, resource group or resource | Owner, User Access Administrator, Contributor | Always manage Owner and User Access Administrator through PIM; settings per resource |
| PIM for Groups | Time-bound membership or ownership of a security or Microsoft 365 group | Groups that carry Entra roles, Azure roles or app access | Separate policies for membership and ownership |
PIM for Groups is useful when several rights should be granted together, for example an operations team with Contributor rights on several subscriptions. Two points matter. First, groups that grant Entra roles must be created as role-assignable groups. Microsoft recommends requiring approval for such groups, because otherwise a less privileged administrator could reset a member’s password and activate the role on their behalf. Second, for roles with permissions in SharePoint, Exchange or the Microsoft Purview portal, Microsoft recommends PIM directly on the Entra role. Through PIM for Groups it can take considerable time after activation before all permissions take effect.
Which licence does PIM require?
PIM requires Microsoft Entra ID P2 or Microsoft Entra ID Governance. Entra ID P2 is available on its own and is included in Microsoft 365 E5. Microsoft 365 Business Premium includes only Entra ID P1, so you need to add P2 or ID Governance there.
You do not need licences for the whole workforce, but for these groups:
- People with eligible or time-bound assignments to Entra or Azure roles managed through PIM
- People with eligible or time-bound membership or ownership in PIM for Groups
- People who approve or reject activation requests
- People who are assigned to or perform an access review
One point for budget planning: if the licence expires, eligible assignments are removed and time-bound active assignments become permanently active. Without the licence, the model falls back into exactly the state you wanted to avoid. Microsoft only adds new governance capabilities to Entra ID Governance; P2 keeps its existing features.
How should you handle emergency access accounts?
Emergency access accounts (break-glass accounts) are the deliberate exception to just-in-time. They keep the tenant accessible when PIM, MFA or a Conditional Access policy fails or is misconfigured. Microsoft’s recommendations:
- At least two cloud-only accounts using the
*.onmicrosoft.comdomain, neither synchronised nor federated. - Global Administrator as a permanently active assignment, not an eligible one.
- Phishing-resistant sign-in with FIDO2 security keys or certificate-based authentication, separate from the methods of your normal admin accounts.
- Exclusion from Conditional Access policies that block or restrict sign-in, ideally through a dedicated group.
- An alert on every sign-in and every change to these accounts.
- A functional test at least every 90 days, with credentials stored in separate, secured locations.
For management this means the emergency access accounts are the only permanently privileged accounts. Every sign-in with them is an event that someone assesses and documents.
How do you prove in an audit that PIM is working?
An auditor wants to see three things: who may hold which role, who used it when and for what, and that the rights are confirmed regularly.
Access reviews are created in PIM for Entra roles and Azure resource roles under Access reviews > New. They can recur, for example quarterly, and apply results automatically. For reviewers who do not respond, choose “Remove access”. One limitation: if someone holds a role through a nested group, the review does not remove that group membership.
Logs: under Resource audit, PIM shows assignments, activations and policy changes for the past 30 days. The Entra audit logs are also kept for only 30 days with P1 or P2. Route them through a diagnostic setting to a Log Analytics workspace or to Microsoft Sentinel. Microsoft recommends reviewing the events weekly and exporting them monthly. For Azure roles, Assignments > Export in PIM exports all active and eligible assignments of a subscription, including child resources, as a CSV file.
Monitoring: two queries belong in every environment with Sentinel. The first reports changes to PIM role settings, for example when someone removes the MFA requirement. The second reports every sign-in of an emergency access account. Maintain these accounts in a Sentinel watchlist, here EmergencyAccounts.
AuditLogs
| where TimeGenerated > ago(1d)
| where OperationName == "Update role setting in PIM"
| extend Actor = coalesce(tostring(InitiatedBy.user.userPrincipalName), tostring(InitiatedBy.app.displayName))
| project TimeGenerated, Actor, Result, ResultReason, TargetResources
let EmergencyAccounts = _GetWatchlist('EmergencyAccounts') | project SearchKey;
SigninLogs
| where TimeGenerated > ago(1h)
| where UserPrincipalName in~ (EmergencyAccounts)
| project TimeGenerated, UserPrincipalName, ResultType, IPAddress, Location, AppDisplayName
PIM itself also raises security alerts, for example when there are too many Global Administrators or when roles are assigned outside PIM. How to have access requested and recertified through access packages is covered in our article on access packages in Entra ID Governance. Which devices administrators should work from is described in the article on the privileged access workstation concept.
Next step
Our Security Assessment, at a fixed price, shows which standing admin rights exist in your tenant and Azure subscriptions and which roles should move into PIM first. As part of our Azure Cloud Security services we introduce PIM with a role model, role settings and access reviews, and either hand it over to your team or run the reviews for you on an ongoing basis.
Frequently asked questions
Does PIM slow down administration?
An activation without approval takes only a few steps: select the role, enter duration and justification, confirm MFA. We recommend approval only for a small number of critical roles. If someone needs the same role every day, check whether a narrower role or a custom role with fewer rights would be enough.
Does every employee need an Entra ID P2 licence?
No. Licences are required for people with eligible or time-bound assignments, for approvers and for people who perform or are assigned to access reviews. In smaller organisations this is often only the administrators and a few managers.
Does PIM also apply to service accounts and automation?
PIM can assign roles to service principals and managed identities as well. Activation with MFA is not practical for automation, though. Give workload identities only the narrowest role on the smallest scope and monitor their assignments.
What happens if the P2 licence expires?
Eligible assignments are removed, time-bound active assignments become permanently active, ongoing access reviews end and the PIM settings are lost. Plan the licence as part of your security architecture, not as an optional add-on.
Book an introductory call