Android Enterprise Google Domain enrollment requires Google account on shared phonesSolved

Participant
Discussion
3 weeks ago Sep 14, 2026

We’re setting up shared Samsung Android phones that anyone should be able to pick up and use. During Android Enterprise enrollment, the device asks us to sign in with a managed Google Workspace account.

The enrollment profile in Hexnode is set to No authentication, so I expected the phone to enroll without tying it to a specific user.

Replies (3)

Marked SolutionPending Review
Hexnode Expert
3 weeks ago Sep 14, 2026
Marked SolutionPending Review

Hello @annemie ,

This behavior usually depends on how Android Enterprise is configured in the Hexnode UEM portal.

If Android Enterprise is set up using Google Domain integration, the enrollment flow is controlled by Google Workspace. In that setup, each Android Enterprise device must be associated with a managed Google Workspace user account that is synced with Hexnode.

The No authentication option in the Hexnode enrollment profile only controls Hexnode-side user authentication during enrollment. It does not bypass Google’s account requirement for Android Enterprise when the portal is configured with Google Domain.

So, for a Google Domain-based Android Enterprise setup, the device cannot be enrolled completely account-free. A managed Google Workspace account is required during enrollment.

Regards,
Simon Scott
Hexnode UEM

Marked SolutionPending Review
Participant
3 weeks ago Sep 14, 2026
Marked SolutionPending Review

Is there a way to enroll these as generic shared devices without getting Google Workspace account prompt during enrollment?

Marked SolutionPending Review
Hexnode Expert
3 weeks ago Sep 14, 2026
Marked SolutionPending Review

For shared devices where you do not want the Google Workspace account prompt during enrollment, the alternative is to configure Android Enterprise using Managed Google Play Accounts instead of Google Domain.

Note that switching from Google Domain to Managed Google Play Accounts requires unlinking the existing Android Enterprise setup. When this is done, Android Enterprise devices already enrolled under the Google Domain setup will be disenrolled and must be enrolled again using the new configuration.

Recommended approach:

  1. Plan a maintenance window for the migration.
  2. Unlink the existing Android Enterprise Google Domain setup.
  3. Configure Android Enterprise with Managed Google Play Accounts.
  4. Re-enroll the shared Android devices.
  5. If the devices had any policies or configurations assigned previously, reapply them to restore your original setup.

This is the supported path if the goal is to avoid binding each device enrollment to a managed Google Workspace user account.

Save