Google EMM (Managed Google Play) registered to inaccessible account: backend removal and re-registration
Android
When your Managed Google Play account is bound to a Google account you can no longer access — such as a former employee's account or a decommissioned test account — the Unregister button in the Esper Console appears greyed out and cannot be clicked.
Why this happens
Esper's Managed Google Play binding is tied to the specific Google account used during initial enrollment. If that account becomes inaccessible, Esper cannot verify ownership and disables the self-service unregister option. The orphaned binding must be removed from Esper's backend before a new Google account can be registered.
Before you begin
Determine whether any active devices are currently using Managed Google Play apps under the existing EMM binding. If they are, complete Steps 1 and 2 before contacting Esper Support. If no production devices use the current EMM account, skip to Step 3.
- Identify affected devices. In the Esper Console, navigate to Devices & Groups and review which devices have Managed Google Play apps installed or assigned. Note any Blueprints that have Managed Google Play enabled, as these will need to be updated before the binding is removed.
- Disable Managed Google Play in each affected Blueprint. In the Esper Console, navigate to Blueprints, open each Blueprint that has Managed Google Play enabled, and turn off the Managed Google Play option. This prevents devices from losing app access mid-transition when the EMM binding is removed.
- Converge all affected devices to the updated Blueprints. After saving each updated Blueprint, apply it and wait for all affected devices to reach a converged state. In the Esper Console, confirm the device status shows In Sync under Devices & Groups before proceeding. Do not proceed until convergence is complete — removing the EMM binding while devices are still syncing can leave apps in an unmanaged state.
-
Contact Esper Support to remove the orphaned EMM binding. Because you no longer have access to the original Google account, the binding cannot be removed through the Esper Console and must be cleared from the backend. Open a support ticket at support.esper.io and include:
- Your Esper tenant ID or enterprise ID
- Confirmation that you do not have access to the Google account currently registered
- Confirmation that all production devices have been converged off the existing EMM binding (or that no production devices were affected)
- Register the correct Google account. After Esper Support confirms the backend removal is complete, navigate to Apps & Configuration → Play Store in the Esper Console. Select Set up Managed Google Play and follow the on-screen prompts to enroll your correct Google account.
- Re-enable Managed Google Play in each affected Blueprint. Navigate to Blueprints, open each Blueprint that was updated in Step 2, and re-enable the Managed Google Play option. Apply each Blueprint and allow affected devices to converge.
Verify: Navigate to Apps & Configuration → Play Store in the Esper Console. The correct Google account should be displayed, and the Unregister button should be active and clickable. All affected devices should return to In Sync status under Devices & Groups within 15 minutes of Blueprint convergence completing.
If this doesn't resolve it
If the Unregister button remains greyed out after Esper Support confirms the backend removal is complete, or if devices do not return to In Sync after re-enabling Managed Google Play, contact Esper Support and provide your tenant ID, the email address of the new Google account you registered, and a screenshot of the Play Store screen showing the current registration state.
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.
Please sign in to leave a comment.
Comments
0 comments