While Microsoft was steadily rolling out Azure AD Connect throughout the first half of March to organizations with automatically upgrading Azure AD Connect installations, an issue was discovered.
The issue was fixed in Azure AD Connect version 1.1.750.0 and put through the same rollout pace as version 1.1.749.0 to land at automatically upgrading organizations.
As promised, Microsoft has released Azure AD Connect version 1.1.750.0 for download, now that, apparently, all automatically upgrading Azure AD Connect installations at organizations have actually been upgraded.
What’s fixed
AutoUpgrade
The AutoUpgrade functionality was incorrectly disabled for some Azure AD tenants who deployed Azure AD Connect version 1.1.524.0, or up.
To ensure that your Azure AD Connect instance is still eligible for AutoUpgrade, run the following Windows PowerShell Cmdlet:
Set-ADSyncAutoUpgrade -AutoUpgradeState AutoUpgradeConfigurationState.Enabled
The Set-ADSyncAutoUpgrade Windows PowerShell Cmdlet would previously block Autoupgrade if auto-upgrade state is set to Suspended. This is now changed so it does not block AutoUpgrade of future builds.
Taxonomy
The team changed the User Sign-in page option "Password Synchronization" to "Password Hash Synchronization". Azure AD Connect synchronizes password hashes, not passwords, so this aligns with what is actually occurring.
Version information
This is version 1.1.750.0 of Azure AD Connect.
It was signed off on on March 22, 2018.
Download information
You can download Azure AD Connect here.
The download weighs 80,7 MB.
Note
After the upgrade to Azure AD Connect version 1.1.750.0 completes, a Full Synchronization cycle is automatically triggered, followed by a full import for the Azure AD connector and a full sync for the AD connector. Since this may take some time, depending on the size of your Azure AD Connect environment, make sure that you have taken the necessary steps to support this or hold off on upgrading until you have found a convenient moment to do so.
Doh! Just installed AD Connect yesterday at customer in multi-forest. Well time to check version and upgrade.
Anyone else seeing this as only doing imports as "Stage Only"even though staging mode is not enabled?