Skip to content

Commit e00a6de

Browse files
authored
Merge pull request #109092 from smithre4/patch-1
Update concept-conditional-access-grant.md
2 parents 34377ca + 760b4b8 commit e00a6de

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

articles/active-directory/conditional-access/concept-conditional-access-grant.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: conditional-access
88
ms.topic: conceptual
9-
ms.date: 03/04/2020
9+
ms.date: 03/25/2020
1010

1111
ms.author: joflore
1212
author: MicrosoftGuyJFlo
@@ -64,6 +64,8 @@ Organizations can choose to use the device identity as part of their Conditional
6464

6565
Organizations can require that an access attempt to the selected cloud apps needs to be made from an approved client app. These approved client apps support [Intune app protection policies](/intune/app-protection-policy) independent of any mobile-device management (MDM) solution.
6666

67+
In order to leverage this grant control, Conditional Access requires that the device be registered in Azure Active Directory which requires the use of a broker app. The broker app can be either the Microsoft Authenticator for iOS, or the Microsoft Company portal for Android devices. If a broker app is not installed on the device when the user attempts to authenticate, the user gets redirected to the app store to install the broker app.
68+
6769
This setting applies to the following iOS and Android apps:
6870

6971
- Microsoft Azure Information Protection
@@ -101,6 +103,7 @@ This setting applies to the following iOS and Android apps:
101103
- The approved client apps support the Intune mobile application management feature.
102104
- The **Require approved client app** requirement:
103105
- Only supports the iOS and Android for device platform condition.
106+
- A broker app is required to register the device. On iOS, the broker app is Microsoft Authenticator and on Android, it is Intune Company Portal app.
104107
- Conditional Access cannot consider Microsoft Edge in InPrivate mode an approved client app.
105108

106109
See the article, [How to: Require approved client apps for cloud app access with Conditional Access](app-based-conditional-access.md) for configuration examples.
@@ -109,6 +112,8 @@ See the article, [How to: Require approved client apps for cloud app access with
109112

110113
In your Conditional Access policy, you can require an [Intune app protection policy](/intune/app-protection-policy) be present on the client app before access is available to the selected cloud apps.
111114

115+
In order to leverage this grant control, Conditional Access requires that the device be registered in Azure Active Directory which requires the use of a broker app. The broker app can be either the Microsoft Authenticator for iOS, or the Microsoft Company portal for Android devices. If a broker app is not installed on the device when the user attempts to authenticate, the user gets redirected to the app store to install the broker app.
116+
112117
This setting applies to the following client apps:
113118

114119
- Microsoft Cortana
@@ -121,6 +126,7 @@ This setting applies to the following client apps:
121126
- Apps for app protection policy support the Intune mobile application management feature with policy protection.
122127
- The **Require app protection policy** requirements:
123128
- Only supports the iOS and Android for device platform condition.
129+
- A broker app is required to register the device. On iOS, the broker app is Microsoft Authenticator and on Android, it is Intune Company Portal app.
124130

125131
See the article, [How to: Require app protection policy and an approved client app for cloud app access with Conditional Access](app-protection-based-conditional-access.md) for configuration examples.
126132

0 commit comments

Comments
 (0)