Skip to content
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

Require approved client app incorrectly implies 'Microsoft Authenticator' can be used as a broker app on Android #105756

Closed
Borgquite opened this issue Feb 24, 2023 · 3 comments

Comments

@Borgquite
Copy link

Borgquite commented Feb 24, 2023

According to this page, under 'Require approved client app':

The broker app can be Microsoft Authenticator for iOS, or either Microsoft Authenticator or Microsoft Company Portal for Android devices.

And later:

Requires a broker app to register the device. The broker app can be Microsoft Authenticator for iOS, or either Microsoft Authenticator or Microsoft Company Portal for Android devices.

However under 'Require app protection policy' we are told that on iOS, the broker app is Microsoft Authenticator, and on Android, the broker app is Intune Company Portal. This is in line with user testing, and the Microsoft support case [Case #:32525687] as described here: https://techcommunity.microsoft.com/t5/microsoft-intune/why-different-broker-apps-for-ios-and-android-not-enrolled-when/m-p/3614640/highlight/true#M11896

Please update this page to reflect that Microsoft Company Portal is the only supported broker app on Android.


Document Details

Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

@YashikaTyagii
Copy link
Contributor

@Borgquite
Thanks for your feedback! We will investigate and update as appropriate.

@Borgquite
Copy link
Author

Borgquite commented Feb 27, 2023

@YashikaTyagii Please ignore this feedback. I have found the cause of the confusion:

  • The 'Require approved client app' Conditional Access policy requires a broker app to perform device registration.
  • The 'Require app protection policy' and the general Intune App Protection Policy feature on Android require app protection functionality built into the Company Portal app.

In my testing, it seems that the 'Require approved client app' setting on itself can work on an Android device with Microsoft Authenticator installed. However the 'Require app protection policy' setting does in fact require the Company Portal app. This is slightly confusing since often the 'Require approved client app' setting (which can use Microsoft Authenticator or Company Portal) is setup along with app protection policies (which can only use Company Portal). But the current text in the article is actually correct, once you realise that a 'broker app' is not the same as 'app protection functionality'.

Thanks for considering this - it appears the article is correct as it stands. Perhaps the 'Require app protection policy' section could be clearer:

'The broker app can be Microsoft Authenticator for iOS. On Android the broker app must additionally support app protection functionality, so the only supported broker app for this policy is Microsoft Company Portal for Android devices.'

https://learn.microsoft.com/en-gb/azure/active-directory/conditional-access/concept-conditional-access-grant#require-approved-client-app
https://learn.microsoft.com/en-us/mem/intune/apps/app-protection-policy#company-portal-app-and-intune-app-protection

@YashikaTyagii
Copy link
Contributor

@Borgquite
We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants