"This device is not managed by Google Play Services" during provisioning: clear stale EMM binding and re-bind Android Enterprise account

Android

Title: "This device is not managed by Google Play Services" — clear stale EMM binding

When provisioning a device or installing managed apps, the error This device is not managed by Google Play Services appears on-device and enrollment fails or apps do not install from Google Play.

Why this happens

Esper connects to Google Play through an Android Enterprise binding tied to a specific Google account. If that binding becomes outdated, was set up incorrectly, or the underlying Google account changed, Android can no longer verify that the device is managed — blocking provisioning and app delivery.

Before you start

Confirm that Control Managed Google Play Services is enabled in your blueprint. Go to Blueprints → [Blueprint Name] → Platform Services → Google Services and verify the toggle is ON. If it is off, enable it, save the blueprint, and re-apply before continuing.

Step 1: Upgrade the existing Google account binding

1. Navigate to Apps & Configuration → Play Store in the Esper Console.
2. Select Upgrade for free to convert the existing Google account to a full Managed Google Play enterprise enrollment. This upgrades the account type without requiring a new Google account or clearing existing device enrollments.
3. Follow the on-screen prompts until the upgrade is confirmed.
4. Go to Settings → Android Enterprise and confirm the binding status shows as active.
5. Re-apply the affected blueprint by navigating to Devices & Groups → [Group Name] → Blueprint → Apply. This pushes the refreshed Managed Google Play configuration to enrolled devices.
6. Provision a test device using your normal method (QR code, Zero-Touch, or KME).

Verify: The test device completes enrollment without the error, and managed apps install successfully from Google Play. Enrolled devices that were already active should not require re-enrollment, but may take up to 15 minutes to reflect the updated configuration in the Activity Feed.

Step 2: Clear the stale binding and re-bind a new account

If Step 1 does not resolve the error, or if you need to bind a different Google account, the existing binding must be reset at the backend before a new one can be created.

1. Contact Esper Support and request a backend Android Enterprise binding reset for your tenant. Provide the Google account email currently bound and, if switching accounts, the new target Google account email.
2. Once Esper Support confirms the existing binding has been cleared, navigate to Settings → Android Enterprise in the Esper Console.
3. Follow the on-screen enterprise enrollment flow to bind the Google account (new or existing). Complete all steps until the binding status shows as active.
4. Re-apply all affected blueprints by navigating to Devices & Groups → [Group Name] → Blueprint → Apply for each group.
5. Factory reset a test device and provision it end-to-end using your normal provisioning method.

Verify: Provisioning completes without the error, managed apps appear in Google Play, and the device shows as enrolled in Devices & Groups. Already-enrolled devices do not need to be re-enrolled, but re-applying the blueprint ensures Managed Google Play configurations propagate correctly.

If this doesn't resolve it

If the error persists after completing both steps, contact Esper Support and include the following:

• A screenshot of the exact on-device error, including any secondary message text
• The Google account email address currently bound under Settings → Android Enterprise
• The device make, model, and Android version
• The provisioning method used (QR code, Zero-Touch, or KME)

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.