Google Enterprise Binding Expired – Recovery and Migration Process
Summary
Related SOTI ONE Platform Products
Related Device OS
Situation
Customers may experience one or more of the following issues:
- Managed Google Play is no longer accessible or functioning correctly.
- The existing Google Enterprise binding cannot be accessed.
- Android Enterprise enrollment or configuration fails.
- Previously approved Managed Google Play applications are no longer available after reconfiguration.
This is typically caused by the expiration of the Google Enterprise binding due to inactivity. See https://support.google.com/accounts/answer/12418290?hl=en for more information.
Environment
- Android Enterprise
- Managed Google Play
- Google Enterprise Binding
- SOTI MobiControl (if applicable)
Process Description
1. Confirm Binding Expiration
Verify that:
- The existing enterprise binding is inaccessible or inactive
- Google Play Enterprise management is no longer available
- Android Enterprise features are failing due to a missing binding
2. Create a New Enterprise Binding
The customer must:
- Create a new managed Google Play / Android Enterprise binding
- Use a new email address during setup
Note:
- The original email may no longer be reusable if tied to the expired enterprise
3. Raise a Google Support Case
Once the new binding is created, the customer should contact Google to request migration of the old enterprise to the new one.
Use the following links:
- https://support.google.com/accounts (to open a support request/ticket)
- http://g.co/recover (to attempt account recovery if access to the old account is still required)
Google will assess whether the migration of apps and enterprise data is possible.
4. Information Required by Google
Advise the customer to provide:
- Old enterprise/binding details
- New enterprise ID
- Old email address
- New email address
- Reason for migration request (enterprise expired due to inactivity)
Verification and Validation
Verify:
- A new enterprise binding has been successfully created
- Android Enterprise enrollment functions correctly
- Managed Google Play is accessible
- Required applications appear after Google's migration process (if completed)
If migration is successful, confirm:
- Applications are visible
- Existing configurations function as expected
- Device enrollment and app deployment operate normally
Was this helpful?
Thanks for your feedback