Google Workspace Android EMM users disappeared from Hexnode after syncSolved

Hello @porter ,

Hexnode UEM does not delete users from Google Workspace. The Hexnode directory reflects the users returned by the configured Google Workspace sync.

If users are still active in Google Workspace but disappear from Hexnode after a sync, check the Google Workspace integration configuration in Hexnode UEM:

1. Go to Admin > Google Workspace.
2. Verify that the correct Google Workspace domain is selected.
3. Confirm whether the sync is configured for all users, selected groups, or filtered OUs.
4. Check whether the OU filter still includes the users expected to appear in Hexnode.
5. Verify the Google Workspace service account JSON credentials, client ID, and required API permissions.
6. Run a manual sync after correcting the configuration.

If the credentials or filter conditions are invalid, Hexnode may receive an empty or incomplete user list during sync. In that case, the users can appear as removed from Hexnode even though they still exist in Google Workspace.

Regards,
Simon Scott
Hexnode UEM

In my case, the users were still in the OU used for Android EMM, but the Hexnode directory showed zero users. I also noticed the sync configuration had sync all groups with an OU filter applied. I wasn’t sure whether saving that would unenroll devices or add/remove users unexpectedly.

When changing Google Workspace sync scope, review the filter carefully before saving. Hexnode UEM updates the directory based on the latest sync result. If the selected OU or group filter excludes existing users, those users may be removed from the Hexnode directory on the next sync.

For this scenario, the workaround would be:

1. Re-upload the Google Workspace JSON credentials in the Hexnode integration.
2. Update/verify the client ID used for domain-wide delegation.
3. Confirm that the required Google Workspace API scopes and permissions are granted.
4. Correct the OU/group filter so it includes the intended Android EMM users.
5. Change the sync frequency to daily or run a manual sync to confirm that users are returned correctly.

After the JSON credentials and client ID permissions were corrected, the Google Workspace sync communication would be restored and the users become visible again in Hexnode.

Can Hexnode limit Android EMM enrollment so only certain Google Workspace users can enroll, and can it reduce the number of devices a Google user is allowed to enroll?

To restrict which Google Workspace users are synced or allowed for enrollment, use the Google Workspace integration scope in Hexnode, such as selecting the appropriate OU or group-based filter. Ensure that the filter includes only the users intended for Hexnode management.

For the number of Android EMM devices a Google Workspace user can enroll, the default limit is controlled by Google Workspace. Google allows a user to enroll up to 15 devices through EMM. Hexnode cannot currently reduce this Google-enforced limit further from within the Hexnode portal.