Introduction

Azure Active Directory (Azure AD) Access Reviews enables organizations to manage user access to applications, groups, and resources. It provides a structured framework for periodically reviewing and auditing who has access to what, ensuring that only the necessary permissions are granted and maintained. This is crucial for maintaining a strong security posture, meeting compliance requirements, and reducing the risk of unauthorized access.

What are Access Reviews?

Azure AD Access Reviews is a feature that allows you to create and manage review cycles for access rights. You can define who should perform the review (e.g., resource owners, managers, or specific users), what they should review, and how frequently these reviews should occur. The process typically involves:

Azure AD Access Reviews Workflow
Diagram illustrating the Azure AD Access Reviews workflow.

Key Benefits

Common Scenarios

Azure AD Access Reviews are valuable in numerous scenarios, including:

How Access Reviews Work

The process typically involves the following steps:

  1. Creation: An administrator creates an access review, defining the scope (e.g., a Microsoft 365 group, an Azure AD security group, or an application).
  2. Reviewer Assignment: The administrator specifies who will perform the review. This can be:
    • The group/application owner(s)
    • Specific users
    • Users themselves (self-review)
  3. Review Period: A start and end date for the review cycle is set, along with a recurrence pattern (e.g., monthly).
  4. User Action: During the review period, assigned reviewers receive email notifications and can access the Access Reviews portal. They can approve or deny access for each user.
  5. Automated Actions: If automated actions are configured, the system can automatically revoke access for users whose access is denied or not reviewed within the specified timeframe.
  6. Policy Enforcement: Access reviews can enforce policies related to least privilege and separation of duties.

Getting Started

Prerequisites

To use Azure AD Access Reviews, you need:

Creating an Access Review

Here’s a simplified overview of how to create an access review:

  1. Navigate to the Azure portal and select Azure Active Directory.

  2. In the left navigation menu, under Identity Governance, select Access Reviews.

  3. Click New access review.

  4. What do you want to review?: Select the type of resource (e.g., Groups, Applications).

  5. Select Members: Choose specific groups, applications, or users.

  6. Settings:

    • Review name: Provide a descriptive name.
    • Review frequency: Choose daily, weekly, monthly, quarterly, or annually.
    • Duration of review: Set how long the review will be open.
    • Start date: Choose when the review begins.
    • Reviewers: Select who will perform the review.
    • Auto-apply results to resource: Configure whether to automatically remove access or require manual approval.
    • Send reminder emails: Enable reminders for reviewers.

  7. Click Start.

Tip: For reviewing guest users, ensure they are in an Azure AD B2B collaboration tenant.

Best Practices

Frequently Asked Questions (FAQ)

What is the difference between Azure AD Identity Protection and Access Reviews?

Azure AD Identity Protection focuses on detecting and responding to risks associated with user identities and sign-ins (e.g., leaked credentials, impossible travel). Access Reviews, on the other hand, is about ensuring that the right people have the right access to the right resources over time.

Can I review access to Azure subscriptions or resource groups?

Access Reviews can be used to manage access to Azure AD groups and applications. For managing access to Azure resources (like subscriptions, resource groups, or individual resources), you would typically use Azure Role-Based Access Control (RBAC) and potentially review group memberships that grant these roles.

What happens if a reviewer doesn't respond?

If you configure a review to automatically apply results, you can specify whether to remove access for users who don't respond, or to have the access remain unchanged. It's often recommended to remove access if no explicit approval is given after a reasonable period.