"Error Enrolling your endpoint to Google EMM" resolves after retrying Managed Google Play enrollment

Android

Title: "Error Enrolling your endpoint to Google EMM" — retry to resolve

When binding Esper to Managed Google Play, some Google Workspace accounts return an Error Enrolling your endpoint to Google EMM message immediately after authorization completes.

Why this happens

Google's EMM registration API occasionally fails to confirm the binding on the first attempt due to a transient server-side error. The authorization itself succeeds, but the final registration handshake does not complete. Retrying the flow reuses the valid authorization and allows the handshake to finish.

Before you start

• Confirm you are signed in to a Google Workspace admin account with permission to bind an EMM provider — personal Gmail accounts cannot be used.
• Confirm no other EMM provider is already bound to your Google domain. Only one EMM provider can be registered per Google Workspace domain at a time. To check, go to the Google Admin Console and navigate to Devices → Mobile & endpoints → Settings → Third-party integrations. If another provider is listed and you want to use Esper, remove it before continuing.

Steps

1. Open the Esper Console and navigate to Apps & Configuration → Managed Google Play.
2. Begin the enrollment flow and complete the Google authorization prompt using your Google Workspace admin account. Do not switch accounts or change any settings mid-flow — doing so creates a mismatched session that prevents the binding from completing.
3. If the Error Enrolling your endpoint to Google EMM message appears after authorization, do not close the browser tab. Return to Apps & Configuration → Managed Google Play to restart the enrollment flow from the beginning.
4. Repeat the authorization steps using the same Google Workspace admin account.
5. Retry up to three times if needed. Most enrollments succeed on the second or third attempt.

Verify: Enrollment is complete when the Managed Google Play iframe loads inside the Esper Console and your Google Workspace domain name is displayed without any error banner. No further action is needed — devices can now be enrolled against your bound domain.

If this doesn't resolve it

If the error persists after three attempts, contact Esper Support and include the following:

• A screen recording of the full authorization flow, including the error message
• Your Google Workspace domain name
• Your Esper organization name or ID
• The date and approximate time (with timezone) when the error occurred

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.