Skip to content

Commit 9e9400e

Browse files
authored
Merge pull request #2491 from msbemba/patch-10
Update end-user-mam-apps-ios.md
2 parents 1f6e313 + 151457a commit 9e9400e

1 file changed

Lines changed: 8 additions & 0 deletions

File tree

memdocs/intune/fundamentals/end-user-mam-apps-ios.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,14 @@ If the device is **not enrolled in Intune**, the user is asked to restart the ap
4242

4343
For devices that are **enrolled for management in Intune**, the user sees a message that their app is now managed.
4444

45+
46+
### Approved client app requirement
47+
48+
Organizations might 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.
49+
50+
In order to apply this grant control, Conditional Access requires that the device is registered in Azure Active Directory, which requires the use of a broker app. The broker app could be the Microsoft Authenticator for iOS. If a broker app isn’t installed on the device when the user attempts to authenticate, the user gets redirected to the appropriate app store to install the required broker app.
51+
52+
4553
## Use apps with multi-identity support
4654

4755
Apps that support multi-identity let you use different work and personal accounts to access the same apps. App protection policies, like entering a device PIN, are activated when users access these apps in a work or school context.

0 commit comments

Comments
 (0)