- Resource exclusions for a custom enterprise application and Exchange Online
- MFA is configured as the grant control
#### Example scenario 1
| Example scenario | User impact (before → after) | Conditional Access evaluation change |
|---|---|---|
| A user signs into VSCode desktop client, which requests openid and profile scopes. | **Before**: User not prompted for MFA</br>**After**: User is prompted for MFA | Conditional Access is now evaluated using Windows Azure Active Directory as the enforcement audience. |
| A user signs in using Azure CLI, which requests only User.Read. | **Before**: User not prompted for MFA</br>**After**: User is prompted for MFA | Conditional Access is now evaluated using Windows Azure Active Directory as the enforcement audience. |
| A user signs in through a custom enterprise application (excluded from the policy) that requests only User.Read and People.Read. | **Before**: User not prompted for MFA</br>**After**: User is prompted for MFA | Conditional Access is now evaluated using Windows Azure Active Directory as the enforcement audience. |
There is no change in behavior when an application requests a scope beyond those listed previously.
In the following example, Conditional Access is not enforced because Exchange Online is excluded from the policy.
#### Example scenario 2
| Example scenario | User impact | Conditional Access evaluation |
|---|---|---|
| A user signs in to a custom enterprise application (excluded from the policy) that requests offline_access and SharePoint access (Files.Read). | No change in behavior | Conditional Access continues to be enforced based on the SharePoint resource. |
- Resource exclusions for a custom enterprise application and Exchange Online
- MFA is configured as the grant control
#### Example scenarios
| Example scenario | User impact (before → after) | Conditional Access evaluation |
|---|---|---|
| A user signs into VSCode desktop client, which requests openid and profile scopes. | **Before**: User not prompted for MFA</br>**After**: User is prompted for MFA | Conditional Access is now evaluated using Windows Azure Active Directory as the enforcement audience. |
| A user signs in using Azure CLI, which requests only `User.Read`. | **Before**: User not prompted for MFA</br>**After**: User is prompted for MFA | Conditional Access is now evaluated using Windows Azure Active Directory as the enforcement audience. |
| A user signs in through a custom enterprise application (excluded from the policy) that requests only `User.Read` and `People.Read`. | **Before**: User not prompted for MFA</br>**After**: User is prompted for MFA | Conditional Access is now evaluated using Windows Azure Active Directory as the enforcement audience. |
There is no change in behavior when an application requests a scope beyond those listed previously, as illustrated in the following examples.
#### Example scenarios
| Example scenario | User impact | Conditional Access evaluation |
|---|---|---|
| A user signs in to a custom enterprise application (excluded from the policy) that requests offline_access and SharePoint access (`Files.Read`). | No change in behavior | Conditional Access continues to be enforced based on the SharePoint resource. |
| A user signs in to the OneDrive desktop sync client. OneDrive requests offline_access and Exchange Online access (`Mail.Read`). | No change in behavior | Conditional Access is not enforced because Exchange Online is excluded from the policy. |