Microsoft Entra ID sync not updating in Hexnode after last successful syncSolved

This can happen if the OAuth token used by the Microsoft Entra ID integration becomes invalid or if admin consent for the Hexnode Directory Service enterprise application is no longer valid.

To restore the sync, re-authenticate the Entra ID connection in Hexnode:

1. In the Hexnode portal, go to Admin > Microsoft Entra ID.
2. Open the configured domain.
3. Go to the Directory Services tab.
4. Click Configure and complete the Microsoft OAuth consent flow again.
5. Use an Entra ID account with the required admin privileges, such as Global Administrator or Privileged Role Administrator.
6. In the Microsoft Entra admin center, open Enterprise applications and verify that admin consent is granted for the Hexnode Directory Service app.
7. Return to Hexnode and click Sync Now.

After re-authentication, the directory sync should resume. If the sync remains stuck in In Progress for an extended time, wait for the current sync attempt to clear before trying again.

Re-authenticating the Directory Services connection and then running Sync Now fixed it for us. The Entra sync completed successfully after that.

Good to know. So the fix was not to delete and recreate the Entra integration, just re-run the configuration and consent flow?

Correct. You do not need to recreate the entire Microsoft Entra ID integration if the domain is already configured. Re-running the Directory Services configuration refreshes the authorization used for syncing. This is especially useful if the admin account used during the original setup had its password changed, access policies were updated, or enterprise application consent was modified in Entra ID. Any of these can interrupt the existing sync authorization.