-
Notifications
You must be signed in to change notification settings - Fork 535
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Note to clarify Conditional Access behavior with Require app protection policy grant control #1243
base: main
Are you sure you want to change the base?
Conversation
…app protection policy" grant control or the "Require all the selected controls" option, where a managed device may be blocked from accessing an application, since it lacks an MAMenrollmentID. See https://msazure.visualstudio.com/One/_wiki/wikis/ESTS-Docs/338098/TrueMAMForWindows for clarification.
@pedroabsoares-ms : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Learn Build status updates of commit 2519585: ✅ 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" |
@@ -62,6 +62,9 @@ The following steps help create a Conditional Access policy requiring an app pro | |||
1. Confirm your settings and set **Enable policy** to **Report-only**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1. Confirm your settings and set **Enable policy** to **Report-only**. | |
> [!WARNING] | |
> Setting this to **Require all the selected controls**, or changing the grant controls might result in devices being blocked unintentionally. | |
1. Confirm your settings and set **Enable policy** to **Report-only**. |
>[!Note] | ||
>If you set to **Require all the selected controls** or just use the **Require app protection policy** control alone, you need to make sure that you only target unmanaged devices or that the devices are not MDM managed. Otherwise, the policy will block access to all applications since it cannot assess whether the application is compliant as per policy. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
>[!Note] | |
>If you set to **Require all the selected controls** or just use the **Require app protection policy** control alone, you need to make sure that you only target unmanaged devices or that the devices are not MDM managed. Otherwise, the policy will block access to all applications since it cannot assess whether the application is compliant as per policy. |
Added a note to clarify behavior when the there is only the "Require app protection policy" grant control or the "Require all the selected controls" option, where a managed device may be blocked from accessing an application, since it lacks an MAMenrollmentID.