Why different broker apps for iOS and Android (not enrolled) when using app protection policies?

Hi Jonas,

yes I can explain why, but I can't explain if it will change in future. Here is the reason for this:

Android has a way to share data between apps which the Intune product uses on the Android platform. Which data actually is shared I don't know, but there are various opportunities for which you can use this. For example to deliver new SDK versions to other apps on the Android platform. The Company Portal is maintained by the Intune product group where the Authenticator app is maintained by the Azure AD product group.

The sharing is officially documented here: https://docs.microsoft.com/en-us/intune/end-user-mam-apps-android

The Company Portal app is a way for Intune to share data in a secure location. Therefore, the Company Portal app is a requirement for all apps that are associated with app protection policies, even if the device is not enrolled in Intune.

For iOS this is not possible because Apple does not allow such a scenario due to his app model and containerization. So, for iOS there is absolutely no reason then to force usage of the Company Portal but the Authenticator as a broker makes totally sense.

So why does not Android switch to Authenticator as well? I think that's because of the different teams, Intune does not own the Authenticator and maybe the publishing of new versions then is not that fast as they would like it to have (that's the way how big companies and product ownership works).

You can use Microsoft Intune UserVoice to make a Design Change Request or support a maybe already existing one here:

https://microsoftintune.uservoice.com/forums/291681-ideas

best,

Oliver