If you use Microsoft’s AD Connect, also known as DirSync, you may have received an email like this:
It’s bad news: your Active Directory is not syncing with Office 365. “Azure Active Directory did not register a synchronization attempt from the Identity synchronization tool in the last 24 hours.”
I got this after upgrading AD Connect to the latest version, currently 1.1.553.
The email recommends you run a troubleshooting tool on the AD Connect server. I did that. Nothing wrong. I rebooted, it synced once, then I got another warning.
This is only a test system but I still wanted to find out what was wrong. I tweaked the sync configuration, again without fixing the issue.
Finally I found this post. Somehow, AD Connect had configured itself not to sync. You can get the current setting in PowerShell, using get-adsyncscheduler:
As you can see, SyncCycleEnabled is set to false. The fix is trivial, just type:
set-adsyncscheduler –SyncCycleEnabled $true
Well, I am glad to fix it, but should not Microsoft’s troubleshooting tool find this simple configuration problem?