Last week, Microsoft released a new version of Azure AD Connect, its free Hybrid Identity bridge product to synchronize objects and their attributes from on-premises Active Directory Domain Services (AD DS) environments and LDAP v3-compatible directories to Azure Active Directory.
Write-back of msExchUcVoicemailSettings
The Azure AD Connect team changed the functionality of attribute write-back to ensure hosted voice-mail is working as expected. Under certain scenarios, Azure AD was overwriting the msExchUcVoicemailSettings attribute during write-back with a $null value. Azure AD Connect will now no longer clear the on-premises value of this attribute if the cloud value is not set.
Notifications and remediation of non-default rules
The Azure AD Connect team enhanced the handling of changed default rules. You are now notified if you have made changes to the default rules and are offered options to repair the default rules.
Test Azure AD Connectivity
The Azure AD Connect team added diagnostics in the Azure AD Connect Wizard to investigate and identify connectivity issues to Azure AD. These same diagnostics can also be run directly through Windows PowerShell using the Test- AdSyncAzureServiceConnectivity Cmdlet.
Test AD Connectivity
The Azure AD Connect team added diagnostics in the Azure AD Connect Wizard to investigate and identify connectivity issues to AD. These same diagnostics can also be run directly through Windows PowerShell using the Start-ConnectivityValidation function in the ADConnectivityTools PowerShell module.
Hybrid Azure AD Join and Device Write-back Schema Pre-Check
The Azure AD Connect team added an Active Directory schema version pre-check for Hybrid Azure Active Directory Join and device write-back.
Easier attribute search for directory extensions
The Azure AD Connect team changed the Directory Extension page attribute search functionality to be non-case sensitive.
Full TLS 1.2 Support
The Azure AD Connect team added full support for TLS 1.2. This release supports all other protocols being disabled and only TLS 1.2 being enabled on the machine where Azure AD Connect is installed.
Upgrades when using SQL Always On
The Azure AD Connect team fixed a bug where Azure AD Connect Upgrade would fail if SQL Always On was being used. This fix was part of Azure AD Connect 1.1.882.0.
Display of OUs with forward slahes in their names
The Azure AD Connect team fixed a bug to correctly parse names of Organizational Units (OUs) that contain a forward slash.
PTA disabled in Staging Mode
The Azure AD Connect team fixed an issue where Pass-Through Authentication would be disabled for a clean install in staging mode.
Loading of Troubleshooting PowerShell Module
The Azure AD Connect team fixed a bug that prevented the PowerShell module to be loaded when running the Troubleshooting tools.
Hostname issues for Servers running Azure AD Connect
The Azure AD Connect team fixed a bug that would block customers from using numeric values in the first character of a host name.
Integrity for partition and container selections
The Azure AD Connect team fixed a bug where Azure AD Connect would allow invalid partitions and container selection.
Invalid Pasword errors with Desktop SSO
The Azure AD Connect team fixed the “Invalid Password” error message when Desktop Single Sign-On (SSO) is enabled.
AD FS Trust Management
The Azure AD Connect team fixed various bugs for managing the ‘Office 365 Identity Platform’ Relying Party Trust (RPT) for Active Directory Federation Services (AD FS).
Schema Check for Device Write-back
The Azure AD Connect team fixed the schema check to look for the msDs-DeviceContainer object class (introduced with Active Directory Domain Servives on Windoes Server 2012 R2) when you configure Device Write-back.
This is version 184.108.40.206 of Azure AD Connect.
It was signed off on on October 25th, 2018 and available for download since October 27th, 2018..
You can download Azure AD Connect here.
The download weighs 83,7 MB
This is the first release of Azure AD Connect in the 1.2 branch of releases. Coincidentally, it aligns with the TLS 1.2 enforcement in Azure AD Connect towards Azure AD.
The new connectivity tests to Active Directory Domain Services (especially in multi-forest scenarios) and Azure AD are a most welcome treat!