A new version of Azure AD Connect was released some days ago, the current build is 220.127.116.11.
This update mainly add some additional diagnostic options and full support of TLS 1.2
See the announcement here: https://docs.microsoft.com/en-us/azure/active-directory/hybrid/reference-connect-version-history#12650
You can always get the newest version from the AADConnect Download Page
New features and improvements
- 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 will now no longer clear the on-premises value of this attribute if the cloud value is not set.
- 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 Powershell using the Test- AdSyncAzureServiceConnectivity Cmdlet.
- 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 Powershell using the Start-ConnectivityValidation function in the ADConnectivityTools Powershell module. For more information see What is the ADConnectivityTool PowerShell Module?
- Added an AD schema version pre-check for Hybrid Azure Active Directory Join and device write-back
- Changed the Directory Extension page attribute search to be non-case sensitive.
- 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. For more information see TLS 1.2 enforcement for Azure AD Connect
- Fixed a bug where Azure AD Connect Upgrade would fail if SQL Always On was being used.
- Fixed a bug to correctly parse OU names that contain a forward slash.
- Fixed an issue where Pass-Through Authentication would be disabled for a clean install in staging mode.
- Fixed a bug that prevented the PowerShell module to be loaded when running the Troubleshooting tools
- Fixed a bug that would block customers from using numeric values in the first character of a host name.
- Fixed a bug where Azure AD Connect would allow invalid partitions and container selection
- Fixed the “Invalid Password” error message when Desktop SSO is enabled.
- Various Bug fixes for AD FS Trust Management
- When configuring Device Writeback – fixed the schema check to look for the msDs-DeviceContainer object class (introduced on WS2012 R2)