Skip to content

Commit bf0b053

Browse files
authored
Merge pull request #178604 from lujiangfeng666/patch-18
Update concept-continuous-access-evaluation.md
2 parents f6c40f2 + 83c3ac5 commit bf0b053

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/active-directory/conditional-access/concept-continuous-access-evaluation.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -169,6 +169,9 @@ More information about continuous access evaluation as a session control can be
169169

170170
With the latest CAE setting under Conditional Access, strict enforcement is a new feature that allows for enhanced security based on two factors: IP address variation and client capability. This functionality can be enabled while customizing CAE options for a given policy. By turning on strict enforcement, CAE will revoke access upon detecting any instances of either [IP address variation](#ip-address-variation) or a lack of CAE [client capability](#client-capabilities).
171171

172+
> [!NOTE]
173+
> You should only enable strict enforcement after you ensure that all the client applications support CAE and you have included all your IP addresses seen by Azure AD and the resource providers, like Exchange online and Azure Resource Mananger, in your location policy under Conditional Access. Otherwise, you could be blocked.
174+
172175
## Limitations
173176

174177
### Group membership and Policy update effective time

0 commit comments

Comments
 (0)