Subject: Unhealthy Identity synchronization Notification

As you can see below from the image, we haven’t had a directory sync for the last 54 hours.

Last directory sync Warning: last synced 54 hours ago

We will have to click on the link and see what the particular error is reporting with our Azure AD Connect Synchronization or use the link to troubleshoot our error.

Fixing problems with directory synchronization for Office 365 

Ok, time now to review the version of AD Connect we are running on our local Active Directory and do a in-place upgrade to solve this issue, often times upgrading the AD Connect Sync client will resolve issues with the synchronization.  Let see what’s the current version and what version we are running on our member server and see if we need to do the in-place upgrade.

The current version is 1.1.561.0 so there must be another issue going on, at this point we’ll try and run a few Power Shell Commands to push a sync.  We will run

Start-ADSyncSyncCycle -PolicyType Initial  - To push an initial sync over to office 365.

At this point when we ran the command we got a message back stating the sync was busy.

We also ran this command to see the health of the sync:

Get-ADSyncConnectorRunStatus

So we then opened to the Synchronization Scheduler to check the connectors, stopped them and ran a full synchronization, after that we restarted the member server.

This eventually cleared up our sync issue and from the portal we can see a healthy sync.

A great link you can use to troubleshoot your AD Connect Sync; also you may want to keep an eye on your syncs using the Azure AD Connect Health Dashboard that comes with Azure Active Directory Premium.

The post Azure: Fix Unhealthy Identity synchronization first appeared on Cloud Engineer - Everton Collins.