Why do this

Occasionally, the local cache of Entra Connect will become corrupted, resulting in specific users not syncing certain changes to AAD (some attributes may still sync, others may not).


You can usually resolve this by clearing the Entra Connect Cache on the DC running it.


How to do it

  1. Stop the sync scheduler:

    In a non-admin Powershell window, run Set-ADSyncScheduler -SyncCycleEnabled $False
  2. Launch the Synchronization Service Manager from the start menu.

  3. Flush the AAD connector:
    Click Connectors, right-click the AAD connector and choose Delete. Make sure to select the Delete connector space only option!

    • Repeat this step with the local AD connector.

  4. Re-start the Sync scheduler:

    In a non-admin Powershell window, run Set-ADSyncScheduler -SyncCycleEnabled $True
  5. Perform a full sync with the command Start-ADSyncSyncCycle -PolicyType Initial


That's it! Remember, if you're working on a specific user, you can view their Audit Logs in Entra to see the changes made by Entra Connect. Note that it may take a few minutes for the logs there to update after a successful sync. You can also see what the sync did on the server's end by looking at the runs in the Synchronization Service Manager.


Reference