Update concept-conditional-access-grant.md #1302
Conversation
The idea is to explain the order in which the conditional access policy evaluates grant controls. MFA is at the top of the list, followed by device validation and then Terms of Use. That will help customers to understand how to read logs when grant control requires TOU or device ID and is pending MFA , TOU and device requirement will show as "failure"
|
@goncalo12345 : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 7490bc1: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
docs/identity/conditional-access/concept-conditional-access-grant.md
Outdated
Show resolved
Hide resolved
|
#label:"triaged" |
…ant.md Co-authored-by: John Flores <joflore@microsoft.com>
|
Learn Build status updates of commit cab4a6d: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
@MicrosoftGuyJFlo Could you review this proposed update to your article and enter Thanks! |
|
#sign-off |
The idea is to explain the order in which the conditional access policy evaluates grant controls. MFA is at the top of the list, followed by device validation and then Terms of Use.
That will help customers to understand how to read logs when grant control requires TOU or device ID and is pending MFA , TOU and device requirement will show as "failure"