Forum Discussion
Conditional Access Policy compliant devices on Android devices
Hello everybody,
has anyone ever set up a Conditional Access Policy that ensures, that only managed devices (marked as compliant) can access Exchange Online?
I tried that and basically it also works for Windows, iOS and Android devices.
Unfortunately there is a problem with managed e-mail profiles on Android devices.
We have configuration profiles that create an exchange online account with Oauth login on the devices. To check the emails, the Gmail app is rolled out on the devices and the Gmail app accesses the managed Exchange Online profile.
This works well, but as soon as I activate the Conditional Access Policy and an Android user has to authenticate again, e.g. because of a password change or on a new device, the login mask reports that the device is not registered and that the Microsoft company portal app should be downloaded first.
This message is wrong, the device is registered and everything else works. It occurs on different devices. As a temporary solution, I deactivated the policy for Android devices.
Has anyone ever had this problem?
Kind regards
Marco
8 Replies
- MrT81Copper ContributorI'm seeing the same thing in our Intune setup. However it doesn't appear to just be Gmail. Any android apps that are azure sign-in integrated are having this issue for us.
marcosiefert You might get some info when you have a look in Azure AD at the Sign-ins. If you have a look at the client app which is used, you should be able to see if Gmail is a legacy auth app. Only browser and Mobile apps and desktop is modern, all others are legacy.
- marcosiefertCopper Contributor
Please excuse the late reply.
I checked it in Azure at the sign-ins.
Gmail is shown as "Mobile Apps and Desktop clients", so it should work.
When Gmail connects to Exchange Online, a Modern Authentication login mask is shown. Multi-factor authentication also shows up, but after confirmation the login process stops with the message that the device is not registered, although it is registered. The problem doesn't occur with any other app, just Gmail.
Seems to be a bug, doesn't it?- Online Ronald FoppenCopper Contributor
marcosiefert Bit of a longshot on this older thread, but did you manage to get this resolved? I am running into exactly the same issue.
Android device is marked a compliant but the config process does not seem to honor it.
- Moe_KinaniBronze ContributorI think the issue is Legacy vs Modern auth, Gmail may use Legacy auth to login, you can confirm by going to sign in logs from Azure AD->Add Filter->Client App->Check all the boxes.
I know you have CA enabled to allow ActiveSync but you also have Android Profile to use Modern Auth. I suspect the the test will work as expected if you use Outlook app not Gmail.
Hope this helps!
Moe