Under attack? Get incident response help

Identity and access

Turning permanent Entra admin roles into time-limited ones

How a small Microsoft 365 team can move Global Administrator and other roles to PIM activations with MFA and approval, and which settings lock you out.

Also in:TürkçeDeutschFrançaisEspañolItalianoPolskiNederlandsEesti

Illustration: Turning permanent Entra admin roles into time-limited ones

Permanent Global Administrator assignments are the first thing to remove from a Microsoft 365 tenant, and Privileged Identity Management (PIM) lets a small team do it without making admin work miserable. The admin keeps the role as eligible, activates it for a few hours with MFA and a stated reason, and the privilege expires on its own. The risk sits in a handful of settings that can lock you out or quietly weaken the control.

What changes when a role becomes eligible

Microsoft's PIM overview is clear that an eligible assignment gives the same access as a permanent one. The only difference is that the person must act before using it. An active assignment needs no action.

Duration adds a second axis, so there are four combinations: permanent eligible, permanent active, time-bound eligible and time-bound active. Activation can demand MFA, a business justification, a ticket number or approval from a named approver. PIM can also send a notification each time a privileged role is activated. Audit history for role assignments and activations covers the past 30 days.

PIM needs licences. Check Microsoft's Entra ID Governance licensing fundamentals before you plan the rollout, because the answer depends on your tenant.

Decide which roles go first

Start with a list of who holds privileged roles today. Remove people who no longer need them. Microsoft Entra access reviews can automate the discovery and the removal.

Then prioritise. The deployment plan says to put every Global Administrator and Security Administrator under PIM first, because those accounts do the most damage when compromised. The Privileged label on roles in the Entra admin center helps you find other high-privilege roles.

The target is zero permanently active assignments, with one exception: the emergency access accounts. Microsoft recommends two cloud-only accounts with permanent Global Administrator, not tied to any individual, for the day normal admins are locked out.

Configure role settings

Settings are per role. Go to ID Governance > Privileged Identity Management > Microsoft Entra roles > Roles, pick the role, select Role settings, then Edit and Update. You need at least Privileged Role Administrator to do this. Changing one role's settings does not touch another's.

The activation maximum duration runs from one to 24 hours. Microsoft's plan shows example values, not defaults to copy:

RoleMFAApprovalActivation duration
Global AdministratorYesYes, by another Global AdministratorOne hour
Exchange AdminYesNoTwo hours
Helpdesk AdminNoNoEight hours

For a team of three or four admins, approval by a colleague on Global Administrator is workable. Lower-risk roles can skip it and rely on MFA, justification and notifications.

Settings that cause trouble

Approval with nobody to approve. If every Privileged Role Administrator and Global Administrator is only eligible, approval is required and no approvers are configured, you are locked out of the tenant. Without named approvers, the active Privileged Role Administrators and Global Administrators are the default approvers, and in that state there are none. Name at least two approvers, as Microsoft recommends, and keep the emergency accounts.

Conditional Access authentication context. Create and enable the Conditional Access policy before you select the context in the PIM role settings. If no policy targets the context, PIM falls back to requiring MFA. That fallback does not apply when the policy is switched off, in report-only mode, or excludes an eligible user. Do not scope one policy to both the authentication context and a directory role. The user has no role at activation time, so the policy would never apply.

MFA that never prompts. Users with strong credentials, or an earlier MFA in the same session, may not be asked again on activation. To force a fresh check, use the authentication context with Authentication Strengths. Set sign-in frequency to Every time in the policy's session controls. A 10-minute window still applies: activating a second eligible role inside it does not prompt again, across Entra roles, Azure resource roles and PIM for Groups.

Activation does not pin the session. The context only governs the moment of activation. A user can activate from a compliant device and then use the role from another browser or device. To close that gap, add a second Conditional Access policy that targets directory roles.

Who controls the policies. Anyone who can manage Conditional Access can change or remove the activation requirements, or block eligible users. Treat those accounts as highly privileged.

Fields that look stronger than they are. The ticket number on activation is information only, and PIM does not check it against a ticketing system. MFA on active assignment applies when an admin creates the assignment, not when the role is used, since the user is already active in it.

Time-bound assignments also generate work. Extend and renew requests for Entra roles need approval from a Global Administrator or Privileged Role Administrator, so expect them in someone's inbox.

Test, roll back, and watch the log

Do not start with your own account. Create test users, write down the expected behaviour for each role (MFA, approval, notification, expiry), and compare it with what happens. Microsoft notes that organisations often start with Global Administrators for Entra roles.

If PIM misbehaves in production, rollback is simple. Open the role, select the ellipsis next to each eligible user and choose Make active.

Afterwards, have one administrator read the audit events weekly and export them monthly. If nobody on the team has time, that review is a sensible task for managed security monitoring.

Where to start

  1. List every holder of a privileged role, remove the ones who no longer need it, and confirm your licensing covers PIM.
  2. Create or verify two cloud-only emergency access accounts with permanent Global Administrator, and keep them out of normal use.
  3. Configure the Global Administrator role settings: MFA, justification, a short activation duration and at least two named approvers.
  4. Pilot with test users and one or two real admins, then convert the remaining permanent assignments to eligible.
  5. Add Conditional Access authentication context only after its policy is enabled, and schedule the weekly audit read. If you want a second opinion on the design, our consulting team can review it.

How we can help

Consulting and training

We assess where you stand, set priorities with you and train your staff to recognise attacks.

Contact us
AngelForce team

Written by the AngelForce team: security consultants with CEH, LPT Master and CISA certifications who test, monitor and defend systems for organisations across Europe.

Written with AI assistance from public sources listed below, and reviewed by the AngelForce team before publication.

Sources

  1. learn.microsoft.com/en-us/entra/id-governance/privileged-identity-management/pim-configure
  2. learn.microsoft.com/en-us/entra/id-governance/privileged-identity-management/pim-deployment-plan
  3. learn.microsoft.com/en-us/entra/id-governance/privileged-identity-management/pim-how-to-change-default-settings

Articles about Identity and access

Tell us what you need to protect

Describe your environment and what you want to achieve. We will reply by email.

Contact us
info@angelforce.eu +372 5705 2044

AngelForce OÜ · Tallinn, Estonia