Recently I had a customer who had implemented the latest version of Azure AD Connect (v. 1.1.119.0) which was available in February 2016. In this version Microsoft changed a lot the make it easier to administrate and convenient to use. They also added some great new features like!

  • Reduction in the sync interval to keep your Azure AD in sync with AD on-premises more quickly
  • Support for automatic upgrades
  • Ability to switch between sign-in methods through the wizard to enable faster pilots
  • Support for Domain and OU filtering within the wizard

Read more here: https://blogs.technet.microsoft.com/ad/2016/02/18/azure-ad-connect-1-1-is-now-ga-faster-sync-times-automatic-upgrades-and-more/ 

Well as it turned out, SyncCycle was not enabled. And the solution is quite simple! We found out by running this command:

Get-ADSyncScheduler

image

We quickly saw that SyncCycleEnabled was set to false. This is easily fixed with a new PowerShell command

Set-ADSyncScheduler -SyncCycleEnabled $True

Now, when running Get-ADSyncScheduler again we can se that SyncCycleEnabled is set to “True” and resources will by synchronized with Azure AD at a regular basis.

image

To kick of an initial Sync type the following command. This will trigger a full sync where as the next sync will be delta.

Start-ADSyncSyncCycle -PolicyType Initial

image

 

Do not forget to leave a comment if you have any questions! Smilefjes