I recently tested the behavior of broker apps for MAM policies in both Android and iOS.

Android:

Initially, I started with no policy applied to the user, installed Outlook, and logged in with my corp credentials. after some time I deployed the policy to the user profile and waited for it to sync so that it would prompt to install the company portal as expected behavior, but it didn’t then I installed Teams and logged in as soon as I did that policy kicks in and prompted me to Install company portal and policy deployed to the device.

iOS:

I followed the same steps as Android, however as soon as I installed Teams policy started to kick in but it didn’t prompt me to install Microsoft Authenticator as a broker app.

Is this an ideal scenario? MS Authenticator is not required to push MAM policies to iOS Devices.

In both cases, The device didn’t get registered and the device entry was not shown under the user’s devices.

​I recently tested the behavior of broker apps for MAM policies in both Android and iOS. Android:Initially, I started with no policy applied to the user, installed Outlook, and logged in with my corp credentials. after some time I deployed the policy to the user profile and waited for it to sync so that it would prompt to install the company portal as expected behavior, but it didn’t then I installed Teams and logged in as soon as I did that policy kicks in and prompted me to Install company portal and policy deployed to the device. iOS:I followed the same steps as Android, however as soon as I installed Teams policy started to kick in but it didn’t prompt me to install Microsoft Authenticator as a broker app. Is this an ideal scenario? MS Authenticator is not required to push MAM policies to iOS Devices. In both cases, The device didn’t get registered and the device entry was not shown under the user’s devices.    Read More

​