Hi @boris,
Thank you for reaching out.
I understand why this can be confusing, especially since the sync process itself does not always surface clear error messages.
In most scenarios where newly, created users are not added to Hexnode, the issue is related to consent permissions configured in Microsoft Entra ID rather than the synchronization mechanism itself.
For Microsoft Entra ID users to successfully sync and enroll their devices in Hexnode UEM, the Hexnode Azure Directory Services integration requires the following consent permissions:
- profile – View users’ basic profile
- offline_access – Maintain access to granted data
- email – View users’ email address
- openid – Sign users in
- User.ReadBasic.All – Sign in and read user profile
If the Microsoft Entra ID administrator has configured User consent settings to “Do not allow user consent”, users will be unable to grant these required permissions during enrollment. In such cases, admin consent is mandatory, and users without administrative privileges will fail to enroll or sync into Hexnode, even though the directory integration may appear to be configured correctly.
To resolve this, please review the following setting:
- Microsoft Entra ID > Enterprise applications > Consent and permissions
Configure User consent to one of the following options:
- Allow user consent for apps, or
- Allow user consent for apps from verified publishers, for selected permissions
If the “Allow user consent for apps from verified publishers, for selected permissions” option is selected, additional configuration is required. The administrator must explicitly enable the necessary permissions so that users are allowed to consent on behalf of the organization.
To do this:
- Navigate to Microsoft Entra ID > Enterprise applications > Consent and permissions > Permission classifications (preview).
- Select + Add permissions.
- Choose Microsoft APIs > Microsoft Graph.
- Enable the required permissions listed above.
Once the appropriate consent permissions are configured, user synchronization and enrollment should proceed as expected without requiring further changes on the Hexnode side.
Please feel free to reach out if you have any additional questions or need further clarification.
Best regards,
Eden Pierce
Hexnode
21 Views
