Overview – AAD Sync Cycle
Have you ever thought about Sync Cycle Amendment AAD, or ever wondered how to the AAD default sync cycle can be amended for Azure AD Connect? Since this is why you are mostly likely here keep reading the following article. Firstly we will cover how to amend the synchronize cycle from your on premises AD using a scheduler. Their are two sync schedules as default within Azure. These are the Delta sync which takes place and will synchronize object changes in scope of M365. Evidently this replicates them and keep the data consistent. Generally, this typically runs at a 30 minute interval. The second of the two which takes place is the Password syncorization, which can take place as frequent as every 2 minutes. (If using password hash syncorization.)
How to complete: AAD Sync Cycle Amendment
If you have any requirements where this is required the great news is Sync Cycle Amendment in AAD can be amended. The first way is via the default process built in by Microsoft. If you require to see the default and current schedule this can be see by the below.
- Firstly PowerShell (As Administrator) and run the below command before finally examining the image for more details
Set-ADSyncScheduler -CustomizedSyncCycleInterval 03:00:00
This would set the cycle cycle to every 3 hours you can rerun the first command to ensure this has set as required do not set this to more than 7 days. Specifically Microsoft do not recommended to set the time to more than 7 days in any of the documentation.
Additional Details: AAD Connect
If you want to find more details please visit the attached tech net article from Microsoft for more details.
Also, if you want to find more details out on how AAD Connect please check out my other blog posts. Furthermore being from a consultant in this area. Shortly, I am hoping to have numerous blog posts on the AAD Connect subject and Transformation rules.
Finally please feel free to drop a comment below or share this blog post if it has helped you.