Android Enterprise enrollment asks for Google Workspace login even when Hexnode authentication is set to No AuthenticationSolved

Hi @raelynn,

Yes, this can happen with Android Enterprise enrollment. The No Authentication option in the Hexnode enrollment profile controls whether Hexnode asks for user authentication during enrollment. It does not bypass the Google authentication step required by Android Enterprise.

If Android Enterprise was originally configured using a Google Workspace account, Google may require that account during device setup to bind and register the device with the enterprise domain. Signing in with the Google Workspace account allows the device to complete Android Enterprise Device Owner enrollment.

After enrollment, the managed Google account may be visible on the device, including in the Play Store and under Google account settings.

Regards,
Sienna Carter
Hexnode UEM

That makes sense. Signing in with the Workspace account did let the enrollment finish. The remaining concern is that these are shared devices, so I don’t want users removing that work account or adding their own Google accounts.

Hi @raelynn,

For Android devices enrolled as Device Owner, you can prevent users from modifying accounts through the Android restrictions policy in Hexnode.

Configure the Android Advanced restriction for Modify Accounts/Users, so users cannot remove the existing work account or add other internet accounts on the device. After saving the policy, associate it with the shared devices or the relevant device group.

This does not necessarily hide the managed Google account from every system screen, but it prevents end users from removing it or adding personal accounts, which is usually the recommended setup for shared Android Enterprise devices.

Regards,
Sienna Carter
Hexnode UEM