After upgrading my labs to Azure Active Directory Synchronization Services (AAD Sync), the install completed successfully and I was able to use the new process to manually initiate a full sync cycle. Excellent!
Since all went swimmingly, I was a little bit surprised a day later to find that newly created objects were not being created in the cloud nor were changes propagated to office 365. Hmm. Weird. It is not meant to sync every three hours? So what is up? AAD Sync uses a scheduled task, so we start by checking that.
We can see that the scheduled task which is used to initiate the sync is disabled. Why is this disabled?
If you clear the synchronize now option at the end of configuration, this disables the scheduled task. It is upon you to then manually enable the task. The below screenshot shows the default settings when the configuration has been finished. The synchronize now option is selected by default – this will enable the scheduled task.
This is all covered in the AAFD Sync FAQ. For the above item, specifically this section — How often are changes synchronized.
Beware the synchronize now option. If you chose to not synchronise at that point, for example to ensure that OUs are excluded from synchronising, then enable the task afterwards.