HomeSetup guides › Connect Intune to Managed Google Play (Android Enterprise binding)
Setup guide · from scratch

Connect Intune to Managed Google Play (Android Enterprise binding)

One-time, effectively permanent binding that unlocks Android Enterprise. Sign in with an organisational Entra account that has a working mailbox (NOT personal Gmail). Path is Devices > Enrollment > Android > Prerequisites, NOT Connectors and tokens.

one-time human step · Google enterprise registration (launched from Intune)assisted guide — Decolla walks you through this
This is a one-time human step. It runs through Google enterprise registration (launched from Intune), which requires an interactive sign-in no MDM or API can perform for you. Decolla keeps it frictionless: the wizard shows these exact steps at the moment you need them, and flags what to bring back (a token, a file, an ID).
Step 1. Open Edge or Chrome and put portal.azure.com, play.google.com and enterprise.google.com in the same browser security zone, or the pop-ups get blocked mid-flow.
Screenshot: Browser security-zone / trusted-sites settings (captured during a live customer build — coming to this page)
Step 2. Go to https://intune.microsoft.com and sign in with an Intune Administrator organisational account (e.g. admin@example-company.co.uk, never a @gmail.com address).
Screenshot: Intune signed in with the org account (captured during a live customer build — coming to this page)
Step 3. Confirm that account has a working mailbox — Google runs an email validation during registration.
Screenshot: Test email received in the account's mailbox (captured during a live customer build — coming to this page)
Step 4. Click Devices > Enrollment > Android tab. (Do NOT use Tenant administration for this step.)
Screenshot: Devices > Enrollment > Android tab (captured during a live customer build — coming to this page)
Step 5. Under 'Prerequisites' click 'Managed Google Play'.
Screenshot: Prerequisites list with Managed Google Play (captured during a live customer build — coming to this page)
Step 6. Tick 'I agree' (grants Microsoft permission to send user and device info to Google).
Screenshot: 'I agree' consent screen (captured during a live customer build — coming to this page)
Step 7. Click 'Launch Google to connect now' — a new Google tab opens.
Screenshot: 'Launch Google to connect now' button (captured during a live customer build — coming to this page)
Step 8. On Google's page confirm the pre-filled Entra account and choose 'Sign in with Microsoft' if offered — do not switch to a personal Google account.
Screenshot: Google sign-in showing the pre-filled Entra account (redact) (captured during a live customer build — coming to this page)
Step 9. Enter the organisation name (e.g. 'Example Company Ltd') and business contact, then accept the Android Enterprise agreement.
Screenshot: Google org-details / agreement screen (captured during a live customer build — coming to this page)
Step 10. Click 'Allow and create account'.
Screenshot: 'Allow and create account' confirmation (captured during a live customer build — coming to this page)
Step 11. Back in Intune confirm a green 'connected' status showing your organisation name; refresh if it still says not-configured.
Screenshot: Intune Managed Google Play 'Connected' status with org name (captured during a live customer build — coming to this page)
Step 12. (Recommended) In Google add a second enterprise owner for redundancy.
Screenshot: Google enterprise owners list (captured during a live customer build — coming to this page)

See it on a real device.

Decolla is in private build — early-access members see a build defined, deployed and rolled back first.

Get early access