Managing Synchronization with AAD Connect

Share this:

Using AAD Connect synchronization settings to validate, trigger synchronization and check the status.


For those administrators that are coming from previous versions the synchronization process was changed on this new release. For starters there is no more Task on the Task Scheduler to trigger the replication process, the synchronization frequency also changed, nowadays the default is 30 minutes.

In order to verify the replication settings  in place the following cmdlet can be used. In order change any of those parameters the cmdlet Set-ADSyncScheduler can be used.



Forcing the synchronization…

Using any PowerShell session on the server, the administrator can trigger a delta synchronization (Delta import, Delta Sync and Export)  which only performs the updates. Here is the cmdlet required to start the delta synchronization.

Start-ADSyncSyncCycle –PolicyType Delta


To force a complete synchronization the following cmdlet can be used.

Start-ADSyncSyncCycle –PolicyType Initial


Checking the replication status…

The client can be used to force replication as well, but on a daily basis it is not used. Another useful task that can be performed with the client is  the process to track replication and what is going on the background is the same than previous versions. We can use the miisclient which is located on C:\Program Files\Microsoft Azure AD Sync\UIShell.


In the Operations tab, the administrator will be able to see existent and past synchronization attempts and their status, that is a good start for any troubleshooting related to AAD Connect synchronization.


Written by Anderson Patricio

Anderson Patricio is a Canadian Exchange Server MVP and MCSM (Solutions Master) and he contributes to the Microsoft Community with articles, tutorials, blog posts, forums and book reviews. He is a regular contributor at, and (Portuguese).