Privileged role assignments in Azure should be reviewed on a regular schedule
This check looks at whether the people and apps holding high-privilege roles in Azure are put through a recurring access review. The safe setting is a scheduled review of privileged role assignments, with a named reviewer who confirms or removes each assignment.
Why it matters
Privileged access tends to pile up. Someone is made Owner for a migration, a contractor gets User Access Administrator for a week, a project ends, and nobody removes the assignment. Each leftover assignment is a standing path to change or delete resources, and it is exactly what an attacker hopes to find after taking over one account.
A recurring access review forces an owner to say, on a schedule, who still needs each privileged role. Microsoft Entra supports this with access reviews, and Privileged Identity Management can run them for Azure resource roles. The review does not remove risk by itself; it makes sure stale access is noticed and gets a decision.
Sources: What are access reviews? (Microsoft Learn) and Azure roles, Microsoft Entra roles and classic roles (Microsoft Learn).
How to check it yourself
Portal: in the Microsoft Entra admin center open ID Governance → Privileged Identity Management → Azure resources → pick the subscription → Access reviews. Also look at ID Governance → Access reviews. You want to see a review that targets privileged roles such as Owner, Contributor and User Access Administrator, that recurs, and that has finished runs.
Read-only commands: the first lists current privileged assignments, the second lists configured review definitions. Neither changes anything.
# Azure CLI: who holds privileged roles right now
az role assignment list --all `
--query "[?roleDefinitionName=='Owner' || roleDefinitionName=='Contributor' || roleDefinitionName=='User Access Administrator'].{who:principalName, role:roleDefinitionName, scope:scope}" -o table
# Microsoft Graph PowerShell: configured access reviews
Connect-MgGraph -Scopes "AccessReview.Read.All"
Get-MgIdentityGovernanceAccessReviewDefinition -All | Select-Object DisplayName, StatusIf the second command returns nothing that covers those roles, the setting is not met.
How to fix it
Portal: in Privileged Identity Management → Azure resources → your subscription → Access reviews → New. Choose the privileged roles in scope, set the review to repeat (quarterly is a common choice), name the reviewers (resource owners or managers rather than the role holders themselves), decide what happens when a reviewer does not answer, and start the review.
Script: reviews can also be created with Microsoft Graph. The request below creates something in your tenant, so test it in a non-production subscription first. ConfigCobra only reports the gap and never creates the review for you.
Connect-MgGraph -Scopes "AccessReview.ReadWrite.All"
# Build the review definition in a JSON file (scope, reviewers, recurrence), then:
Invoke-MgGraphRequest -Method POST `
-Uri "https://graph.microsoft.com/v1.0/identityGovernance/accessReviews/definitions" `
-Body (Get-Content .\privileged-review.json -Raw) -ContentType "application/json"Reference: Create an access review of Azure resource and Microsoft Entra roles in PIM (Microsoft Learn).
What changes when you fix it
Reviewers (subscription owners, security leads or managers) get a recurring task and must answer for each assignment. Plan time for it: the first review of a long-neglected subscription is the longest.
Role holders may lose access if a reviewer denies the assignment or, depending on your settings, if nobody responds. People who rely on a role for occasional work should be told in advance, and eligible (just-in-time) assignments are a better fit than permanent ones for them.
Automation and service principals with privileged roles can be included too; removing one that a pipeline still uses will make that pipeline fail, so check what an identity does before you deny it. Nothing else in the subscription changes: resources and their configuration stay as they are.
Included in
| Benchmark | CIS ID | Profile |
|---|---|---|
| CIS Microsoft Azure Foundations v6.0.0 | 5.3.4 | Level 1 |
More checks in Identity Services
- Ensure that Azure Admin Accounts Are Not Used for Daily OperationsCIS 5.3.1
- Ensure that Guest Users are Reviewed on a Regular BasisCIS 5.3.2
- Ensure That Use of the 'User Access Administrator' Role is RestrictedCIS 5.3.3
- Ensure Disabled User Accounts do not Have Read, Write, or Owner PermissionsCIS 5.3.5
Check this on your Microsoft Azure
ConfigCobra runs this check with every other control of the CIS Microsoft Azure Benchmarks, read-only.