Android Enterprise: “Work account creation failed!” during Managed Google Play provisioningSolved

Hi @grace_t,

The “Work account creation failed!” message usually appears when the Android Enterprise device cannot complete the server handshake required to provision the Managed Google Play work account.

For a device that was already enrolled and started showing this error suddenly, it can be caused by a temporary communication or synchronization issue between the device, Hexnode UEM, and Google’s services.

Try the following:

1. Restart the Android device.
2. In the Hexnode UEM portal, run the Scan Device action for the affected device.
3. Wait for the device status and action history to update.
4. Check whether the Managed Google Play work account is created successfully after the scan.

Restarting refreshes the device-side services, while Scan Device forces the device to sync with Hexnode again. In many cases, this re-establishes the provisioning flow without requiring re-enrollment.

Regards,
Isabel Lora
Hexnode UEM

For anyone else seeing this, it seems worth checking whether the device is newly enrolling or already enrolled. In my case, already enrolled devices sometimes recover after a restart and scan if the issue is just a temporary sync problem.

For anyone else seeing this, it seems worth checking whether the device is newly enrolling or already enrolled. In my case, already enrolled devices sometimes recover after a restart and scan if the issue is just a temporary sync problem.

Yes @ruthg_ , that distinction is important. If the device was previously enrolled and the error appears suddenly, a restart followed by Scan Device is a good first step.

If the same error continues after that, review the Android Enterprise/Managed Google Play configuration, device connectivity, and whether Google services are reachable from the device network.

Regards,
Isabel Lora
Hexnode UEM