A new version of Azure AD Connect is available since yesterday.
This release expands the scope of automatic upgrade to a wider scope, so there is an action needed if you don’t want that:
The scope expansion of the Automatic Upgrade feature affects customers with Azure AD Connect build 22.214.171.124 and after. If you do not want your Azure AD Connect server to be automatically upgraded, you must run following cmdlet on your Azure AD Connect server:
Set-ADSyncAutoUpgrade -AutoUpgradeState disabled.
You can download the new version from HERE.
Continue reading “Azure AD Connect: New version 1.1.561.0 available”
Yesterday a new smaller version update was made available for download. It contains one fix and two improvements/features:
New build number is: 1.1.557.0
See Azure AD Connect: Version release history and download the bits from here.
- Fixed an issue with the Initialize-ADSyncDomainJoinedComputerSync cmdlet that caused the verified domain configured on the existing service connection point object to be changed even if it is still a valid domain. This issue occurs when your Azure AD tenant has more than one verified domains that can be used for configuring the service connection point.
New features and improvements
- Password writeback is now available for preview with Microsoft Azure Government cloud and Microsoft Cloud Germany. For more information about Azure AD Connect support for the different service instances, refer to article Azure AD Connect: Special considerations for instances.
- The Initialize-ADSyncDomainJoinedComputerSync cmdlet now has a new optional parameter named AzureADDomain. This parameter lets you specify which verified domain to be used for configuring the service connection point.