How to Run Entra ID Access Reviews: Step-by-Step
A step-by-step guide to setting up Microsoft Entra ID access reviews to enforce least-privilege access and pass compliance audits.
Why Access Reviews Matter
Over time, user access rights naturally accumulate as employees change roles, join projects, or gain temporary permissions that are never revoked. This access creep is a leading cause of audit findings and a significant attack surface expansion. Microsoft Entra ID access reviews automate the process of periodically verifying that each user’s access remains appropriate, replacing manual spreadsheet-based recertification processes that are slow and error-prone.
Step 1: Identify What Needs to Be Reviewed
Start by cataloging high-risk access scenarios: privileged role assignments like Global Administrator, access to sensitive applications containing financial or health data, and guest user access to internal resources. Prioritize reviews based on risk rather than attempting to review every group and application simultaneously, since review fatigue among approvers reduces the quality of decisions made.
Step 2: Confirm Licensing and Prerequisites
Access reviews require Microsoft Entra ID Governance or Entra ID P2 licensing. Confirm your tenant has the appropriate license assigned to the users who will be included in or administer reviews, since review creation will fail without proper licensing in place.
Step 3: Create a New Access Review
In the Entra admin center, navigate to Identity Governance and create a new access review. Select the scope, which can be a specific group, an application’s assigned users, or Azure AD role assignments like privileged administrator roles. Define the review frequency, such as quarterly for standard application access or monthly for privileged roles, aligning the cadence to the sensitivity of what is being reviewed.
Step 4: Assign Reviewers
Choose who will perform the review: the resource owner, the user’s manager, a designated group of reviewers, or self-review where users attest to their own continued need for access. For privileged roles, manager or dedicated security team review is strongly preferred over self-review, since self-attestation for high-risk access provides weaker assurance for auditors.
Step 5: Configure Auto-Apply and Fallback Settings
Decide whether access should be automatically revoked if a reviewer does not respond within the review period, or whether a fallback reviewer should be escalated to instead. For privileged access reviews, configure automatic revocation on non-response, since this enforces accountability and prevents stale access from persisting indefinitely due to reviewer inaction.
Step 6: Set Up Recurrence
Configure the review to recur automatically on your defined schedule rather than manually recreating it each cycle. Recurring reviews ensure consistent compliance evidence over time, which is particularly valuable for organizations subject to SOC 2, ISO 27001, or similar audit frameworks requiring documented periodic access recertification.
Step 7: Monitor Progress and Act on Results
Use the access reviews dashboard to track completion rates and send reminders to reviewers who have not responded as the deadline approaches. Once a review cycle completes, verify that access removal actions actually took effect in connected applications, particularly for applications using just-in-time or federated provisioning where removal timing can vary.
Step 8: Document for Audit Purposes
Export access review results and decisions for your compliance evidence repository. Auditors typically want to see not just that reviews occurred but that inappropriate access identified during reviews was actually remediated in a timely manner, so maintain a log connecting review findings to remediation actions.
Regular, well-structured Entra ID access reviews are one of the most effective controls for reducing identity-related risk and satisfying compliance requirements. Symhas helps organizations design and operationalize identity governance programs across Microsoft and multi-cloud environments. Contact Symhas to strengthen your access review program.
Frequently Asked Questions
What license is required for Entra ID access reviews?
Access reviews require Microsoft Entra ID Governance or Entra ID P2 licensing assigned to the relevant users and administrators.
How often should privileged role access be reviewed?
Monthly or quarterly reviews are recommended for privileged roles like Global Administrator, given the high risk associated with unauthorized or stale privileged access.
Can access reviews automatically remove access?
Yes, reviews can be configured to automatically revoke access if a reviewer denies it or fails to respond within the defined review period.
