You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/governance/conditional-access-exclusion.md
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,8 @@ Unfortunately, some users may still have a valid reason to sign in from these bl
37
37
38
38
Another example might be that you have a Conditional Access policy [blocking legacy authentication for the vast majority of your users](https://cloudblogs.microsoft.com/enterprisemobility/2018/06/07/azure-ad-conditional-access-support-for-blocking-legacy-auth-is-in-public-preview/). However, if you have some users that need to use legacy authentication methods to access your resources via Office 2010 or IMAP/SMTP/POP based clients, then you can exclude these users from the policy that blocks legacy authentication methods.
39
39
40
-
>[!NOTE] Microsoft strongly recommends that you block the use of legacy protocols in your tenant to improve your security posture.
40
+
>[!NOTE]
41
+
>Microsoft strongly recommends that you block the use of legacy protocols in your tenant to improve your security posture.
41
42
42
43
## Why are exclusions challenging?
43
44
@@ -90,7 +91,8 @@ Now you can create a Conditional Access policy that uses this exclusion group.
90
91
91
92
7. Select the exclusion group you created.
92
93
93
-
>[!NOTE] As a best practice, it is recommended to exclude at least one administrator account from the policy when testing to make sure you are not locked out of your tenant.
94
+
>[!NOTE]
95
+
> As a best practice, it is recommended to exclude at least one administrator account from the policy when testing to make sure you are not locked out of your tenant.
94
96
95
97
1. Continue with setting up the Conditional Access policy based on your organizational requirements.
96
98
@@ -103,7 +105,8 @@ Let's cover two examples where you can use access reviews to manage exclusions i
103
105
Let's say you have a Conditional Access policy that blocks access from certain countries/regions. It includes a group that is excluded from the policy. Here is
104
106
a recommended access review where members of the group are reviewed.
105
107
106
-
>[!NOTE] A Global administrator or User administrator role is required to create access reviews.
108
+
>[!NOTE]
109
+
>A Global administrator or User administrator role is required to create access reviews.
107
110
108
111
1. The review will happen every week.
109
112
@@ -139,7 +142,8 @@ that is excluded from the policy. Here is a recommended access review where memb
139
142
140
143

141
144
142
-
>[!IMPORTANT] If you have many exclusion groups and therefore need to create multiple access reviews, we now have an API in the Microsoft Graph beta endpoint that allows you to create and manage them programmatically. To get started, see the [Azure AD access reviews API reference](https://developer.microsoft.com/graph/docs/api-reference/beta/resources/accessreviews_root) and [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/td-p/236096).
145
+
>[!IMPORTANT]
146
+
>If you have many exclusion groups and therefore need to create multiple access reviews, we now have an API in the Microsoft Graph beta endpoint that allows you to create and manage them programmatically. To get started, see the [Azure AD access reviews API reference](https://developer.microsoft.com/graph/docs/api-reference/beta/resources/accessreviews_root) and [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/td-p/236096).
0 commit comments