Today a new version of Azure AD Connect was released – v220.127.116.11 (even though the site says 2/16/2016, but wasn’t there yesterday!)
The download link is here: https://www.microsoft.com/en-us/download/details.aspx?id=47594
If you want a reminder on what Azure AD Connect is, Microsoft have a great article here. It replaced Dirsync and AADSync
It’s worth the upgrade, full release notes are here but the big change in my opinion is:
New preview features:
- The new default sync cycle interval is 30 minutes. Used to be 3 hours for all earlier releases. Adds support to change the scheduler behavior.
30 minutes is much nicer to wait for a change (this doesn’t include passwords) than 3 hours.
Note that this used to be controlled from a scheduled task in DirSync and AADSync, but now runs as the Microsoft Azure AD Sync service. If you want to check that your sync has now changed to 30 minutes, run the PowerShell command “Get-ADSyncScheduler” and you should see the values of AllowedSyncCycleInterval and CurrentlyEffectivSyncCycleInterval both as 30 minutes:
If you’ve already got the connector installed, it will just install over the top using your existing settings. It just requires re-entry of your Azure AD credentials for syncing, and took me about two minutes to run.
Update: 1st March 2016
Due to a bug with the time, version 18.104.22.168 has been released. Please use that instead of 22.214.171.124
4 thoughts on “Azure AD Connect 126.96.36.199”
The next cycle is at 1-1-0001. Do you know a solution for this to be at a more present date?
I have the same problem. Although MS claims each setting is configurable, I don’t see a switch for that. Someone has already asked the question and I’ve backed it up here https://azure.microsoft.com/en-us/documentation/articles/active-directory-aadconnectsync-feature-scheduler/ so hopefully we’ll know soon.
I can confirm that despite this, I’m still getting changes through, which is probably due to the delta setting.
Just letting you know I managed to work with Microsoft on this, and it’s now fixed in a new release. Blog post updated. Thank you for alerting me to this!
Thanks for the update!