Skip to main content
Level 1.6: Donut
November 21, 2025
Solved

Enable third party EMM (Intune)

  • November 21, 2025
  • 3 replies
  • 0 views

So I am trying to enable Managed Google Play in Intune to use for Android device management.
We already have a managed Google domain, but we have device management turned off. To my knowledge we only use it for Workplace.

 

When I try to enable managed google play in Intune I get two different error messages

 

Any ideas or tips of what we need to enable or open up in the Google admin console to enable third party EMM? 
Does the account I am using to enable managed google play have to be a google super admin or something?

Best answer by markolisica

Hey @matsm,

I learned that you need an account with the "Super Admin" role to bind Android Enterprise to EMM (Intune in your case).

 

3 replies

Level 1.5: Cupcake
December 4, 2025

Hey @matsm,

I learned that you need an account with the "Super Admin" role to bind Android Enterprise to EMM (Intune in your case).

 

Emilie_B
Community Manager
December 16, 2025

Hello @matsm - hope you're well! 


I've checked with our internal team and they said that having "Google Mobile Management" turned off in the Google Admin console is actually the correct configuration when you want to use InTune - as it prevents conflicts. 


However, you still need to perform the Android Enterprise Binding so Intune has permission to talk to your Google Play Store.


And, as mentioned by @markolisica, the account you use to authorise the connection must be a "Google Super Admin".


You can see more information regarding binding here: https://support.google.com/work/android/answer/14319210?hl=en#zippy=%2Cmanage-emm-bindings 

 

Please let me know if this is useful or if you need anything else :)

Emilie 

matsmAuthor
Level 1.6: Donut
December 17, 2025

Thanks for the follow-up.
For some reason it didn't work with a service account even if it had the Super Admin role.
Had to use my own account.

Emilie_B
Community Manager
December 17, 2025

Thanks for the update @matsm - I'm glad it's been resolved!