Access reviews - FAQs

In this article, you find questions to commonly asked questions about access reviews. Check back to this page frequently as changes happen often, and answers are continually being added.

Frequently asked questions

Can I stop a recurring access review series at any time?

While there's no direct "Stop" button for a series, you can edit the series to set an earlier end date. This prevents new review instances from being generated after that date.

Do access reviews reflect real-time changes to users or access during the review period?

No. Access reviews capture a snapshot of access at the start of each review instance. Any changes made to user assignments, group membership, or reviewer configuration after the review begins isn't reflected in that instance. These updates will instead be captured in the next instance of the review if it's a recurring review. At the start of each recurrence, the system reevaluates and retrieves the latest information about users, resources, and reviewers.

I completed an access review but don’t see any changes yet. Why?

When a reviewer completes an access review, it means they submit their decisions. However, changes to access aren't applied until the review reaches its scheduled end date.

If the review is set to auto-apply, the system applies the decisions shortly after the end date. If auto-apply is not enabled, an administrator must manually apply the results. You can confirm whether auto-apply is enabled in the review’s configuration settings.

Note

Even if a reviewer completes their review early, for example on day 1 of a 10-day review, access changes still won’t take effect until the end of the review period.

What happens if reviewers miss the review deadline?

If reviewers don’t take action by the review end date, the system automatically applies the admin configured default decision, for example either approve, deny, or take recommendations, for users who weren’t reviewed.

How can admins view upcoming reviews in a recurring series?

There are several scenarios where the system is unable to apply review outcomes, especially for denied users:

  • Reviewing members of a synced on-premises Windows Server Active Directory group: If the group is synced from on-premises Windows Server Active Directory, the group can't be managed in Microsoft Entra ID and therefore membership can't be changed. -Reviewing a resource (role, group, or application) with nested groups assigned: For users who have membership through a nested group, we won't remove their membership from the nested group, and therefore they retain access to the resource being reviewed.
  • User not found: A user not being found, or other similar errors, can also result in an apply result not being completed.
  • Reviewing the members of mail enabled group: The group can't be managed in Microsoft Entra ID, so membership can't be changed.
  • The Application uses group assignment: Reviewing an Application that uses group assignment won't remove the members of those groups, so they retain the existing access from the group relationship for the application assignment.

Why don’t new group owners appear as reviewers during an ongoing group access review?

When a group or team access review starts, only the group owners at the time the review begins are assigned as reviewers. If group ownership changes during the review like for example, new owners are added or existing ones are removed, those changes don't affect the current instance. The original reviewers remain unchanged. However, for recurring reviews, any updates to group ownership will be reflected in the next review instance.

How can I see which reviewers were notified for an access review?

Once an access review starts, you can use the contactedReviewers API to retrieve the list of all users who were, or would have been, notified via email to perform reviews. Even in scenarios where notifications were turned off, the API still provides the list of reviewers along with timestamps indicating when notification would happen.

Next steps