Skip to content

Commit d4f60c5

Browse files
authored
Merge pull request #102273 from barclayn/table-add
adding table per Fionna
2 parents 9d5cf74 + e42eff4 commit d4f60c5

File tree

1 file changed

+16
-2
lines changed

1 file changed

+16
-2
lines changed

articles/active-directory/governance/create-access-review.md

Lines changed: 16 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.tgt_pltfrm: na
1111
ms.devlang: na
1212
ms.topic: conceptual
1313
ms.subservice: compliance
14-
ms.date: 05/21/2019
14+
ms.date: 02/06/2020
1515
ms.author: ajburnle
1616
ms.reviewer: mwahl
1717
ms.collection: M365-identity-device-management
@@ -88,7 +88,7 @@ For more information, see [License requirements](access-reviews-overview.md#lice
8888

8989
![Create an access review - Upon completion settings](./media/create-access-review/upon-completion-settings.png)
9090

91-
1. If you want to automatically remove access for users that were denied, set **Auto apply results to resource** to **Enable**. If you want to manually apply the results when the review completes, set the switch to **Disable**.
91+
1. If you want to automatically remove, access for users that were denied, set **Auto apply results to resource** to **Enable**. If you want to manually apply the results when the review completes, set the switch to **Disable**.
9292

9393
1. Use the **Should reviewer not respond** list to specify what happens for users that are not reviewed by the reviewer within the review period. This setting does not impact users who have been reviewed by the reviewers manually. If the final reviewer's decision is Deny, then the user's access will be removed.
9494

@@ -123,6 +123,20 @@ By default, Azure AD sends an email to reviewers shortly after the review starts
123123

124124
If you have assigned guests as reviewers and they have not accepted the invite, they will not receive an email from access reviews because they must first accept the invite prior to reviewing.
125125

126+
## Access review status table
127+
128+
| Status | Definition |
129+
|--------|------------|
130+
|NotStarted | Review was created, user discovery is waiting to start. |
131+
|Initializing | User discovery is in progress to identify all users that are part of the review. |
132+
|Starting | Review is starting. If email notifications are enabled, emails are being sent to reviewers. |
133+
|InProgress | Review has started. If email notifications are enabled emails have been sent to reviewers. Reviewers can submit decisions until the due date. |
134+
|Completing | Review is being completed and emails are being sent to the review owner. |
135+
|AutoReviewing | Review is in a system reviewing stage. The system is recording decisions for users who were not reviewed based on recommendations or pre-configured decisions. |
136+
|AutoReviewed | Decisions have been recorded by the system for all users who were not reviewed. Review is ready to proceed to **Applying** if Auto-Apply is enabled. |
137+
|Applying | There will be no change in access for users who were approved. |
138+
|Applied | Denied users, if any, have been removed from the resource or directory. |
139+
126140
## Create reviews via APIs
127141

128142
You can also create access reviews using APIs. What you do to manage access reviews of groups and application users in the Azure portal can also be done using Microsoft Graph APIs. For more information, see the [Azure AD access reviews API reference](https://docs.microsoft.com/graph/api/resources/accessreviews-root?view=graph-rest-beta). For a code sample, see [Example of retrieving Azure AD access reviews via Microsoft Graph](https://techcommunity.microsoft.com/t5/Azure-Active-Directory/Example-of-retrieving-Azure-AD-access-reviews-via-Microsoft/m-p/236096).

0 commit comments

Comments
 (0)