Open the Roles and administrators page in most South African tenants and you will find a handful of IT staff, a departed consultant or two and a service account, all permanently assigned Global Administrator. Each can read and change almost every setting in Microsoft Entra ID and Microsoft 365. A phished password or a stolen session token on any of them is a tenant takeover.
Our cloud and infrastructure page lists privileged identity management among the hybrid identity controls OAS configures. This guide explains what Privileged Identity Management (PIM) does, which settings matter, and the order to roll it out without locking anyone out.
What standing access costs you
A permanently assigned role is what Microsoft calls an active assignment: the account holds the permissions from assignment until someone removes them, and nothing is checked when they are used. Microsoft's guidance is to assign Global Administrator to fewer than five people, and the Entra admin centre shows a warning card once a tenant reaches five or more. Many tenants we review are well past that.
PIM replaces active assignments with eligible ones. An eligible administrator holds no permissions until they activate the role, and activation can require multifactor authentication, a written justification, a ticket number and a named colleague's approval. The activation expires after a set number of hours.
Licensing and emergency access first
PIM needs Microsoft Entra ID P2 or Microsoft Entra ID Governance licences. P2 is included in Microsoft 365 E5, which is why our Microsoft 365 E5 security article lists PIM among the features many E5 customers pay for and never switch on. Licences must cover every user with an eligible or time-bound assignment, every approver and everyone in an access review. If the licence lapses, Microsoft removes eligible assignments and the PIM settings while permanent active assignments carry on.
Before you change any assignment, create two cloud-only emergency access accounts with a permanent active Global Administrator assignment, the one exception to the rule that nothing should be permanently active:
- Create them in the
.onmicrosoft.comdomain, never synchronised or federated from on-premises Active Directory. - Register a phishing-resistant method that differs from your normal administrator accounts; Microsoft recommends FIDO2 security keys.
- Exclude them from every Conditional Access policy that blocks or restricts sign-in, and keep them out of automated clean-up of unused accounts.
- Alert on every sign-in. A break-glass account signing in without a drill underway is an incident.
- Test them at least every 90 days, and again whenever an administrator leaves.
Without these accounts a PIM mistake can lock the whole tenant. Microsoft documents the exact failure: every Global Administrator is eligible rather than active, activation requires approval, and no approver is configured, so nobody can approve anybody.
Role settings that do the work
Each Entra role has its own settings in PIM. For Global Administrator, Microsoft's example configuration is a sensible starting point:
- Activation maximum duration. The slider allows one to 24 hours. Microsoft's example is one hour for Global Administrator, two for Exchange Administrator and eight for Helpdesk Administrator: the duration tracks the damage a role can do.
- Require multifactor authentication on activation, or better, a Conditional Access authentication context, which lets a policy insist on a phishing-resistant method or a compliant device at the moment of activation. Our guide to phishing-resistant MFA and passkeys covers why the method matters.
- Require justification and ticket information. The ticket field is free text, not checked against your service desk, but it makes the audit trail readable.
- Require approval, with at least two named approvers so that leave does not block an activation. Microsoft's zero-trust guidance treats an approval gate on Global Administrator as a defence against an attacker who has phished a credential and would otherwise activate the role within seconds.
- Assignment duration. Eligibility that expires, say every three months, forces a review; permanent eligibility still requires activation every time.
A rollout order that keeps people working
Microsoft notes that organisations usually start with Global Administrator and take Azure resource roles one subscription at a time. Our sequence follows that advice:
- Discover. Export every assignment to Global Administrator, Privileged Role Administrator and Security Administrator, and remove accounts that no longer need the role.
- Downgrade where possible. Many Global Administrators only need Exchange, SharePoint, Intune or User Administrator.
- Create and test the emergency access accounts, and confirm the sign-in alert fires during a drill.
- Configure the Global Administrator role settings and pilot with one or two administrators, checking MFA, approval, notification and expiry.
- Convert the rest from active to eligible. The rollback is simple: PIM can make an eligible assignment active again from the same screen.
- Extend to Security Administrator and the other roles carrying Microsoft's "privileged" label, then to Owner and User Access Administrator on your Azure subscriptions.
- Review and alert. PIM keeps 30 days of audit history; Microsoft suggests one administrator reads it weekly and exports it monthly. Turn on PIM's security alerts, and alert on any new permanent assignment to Global Administrator.
How PIM fits with Conditional Access
PIM controls when a role is held; Conditional Access controls where and how an account signs in. An administrator who activates Global Administrator from a compliant device can, by default, use the activated role from a second session on an unmanaged laptop, because the check happens once. The fix is a Conditional Access policy that targets eligible administrators directly, so that every sign-in by that account requires a compliant device and a phishing-resistant method. Our article on Conditional Access policies that work sets out the policies most tenants need.
Together, the two controls turn "who is a Global Administrator" from a list that grows for years into a question whose answer changes by the hour and is recorded in a log you can show an auditor. OAS configures PIM, the emergency access accounts and the supporting Conditional Access policies as part of its Microsoft 365 security reviews.
Sources
- Microsoft Learn: Plan a Privileged Identity Management deployment
- Microsoft Learn: Configure Microsoft Entra role settings in Privileged Identity Management
- Microsoft Learn: Manage emergency access accounts in Microsoft Entra ID
- Microsoft Learn: Best practices for Microsoft Entra roles
- Microsoft Learn: Microsoft Entra ID Governance licensing fundamentals
- Microsoft Learn: Configure Microsoft Entra for Zero Trust: Protect engineering systems
Move your administrators to just-in-time access with OAS cloud and infrastructure services.
