Yesterday Microsoft released a new version of Azure AD Connect, which is the first new release since the Azure AD Connect was initially released to GA in August 2015.
Azure AD Connect is the main tool for integration of your on-premises identity system, like Active Directory, with Azure Active Directory.
Using Azure AD Connect you can perform synchronization of objects and identities between Active Directory and the Azure Active Directory, where services like Office 365, Azure and SaaS applications can authenticate using these synchronized identities.
This new version is: 1.0.9125.0
- Can reconfigure the ADFS to Azure AD trust.
- Can refresh the Active Directory schema and regenerate Sync Rules.
- Can disable a sync rule.
- Can define “AuthoritativeNull” as a new literal in a Sync Rule.
New preview features:
New supported scenario:
- Supports multiple on-premises Exchange organizations.
See Hybrid deployments with multiple Active Directory forests for more information.
- Password synchronization issues:
- An object moved from out-of-scope to in-scope will not have its password synchronized. This incudes both OU and attribute filtering.
- Selecting a new OU to include in sync does not require a full password sync.
- When a disabled user is enabled the password does not sync.
- The password retry queue is infinite and the previous limit of 5,000 objects to be retired has been removed.
- Improved troubleshooting.
- Not able to connect to Active Directory with Windows Server 2016 forest-functional level.
- Not able to change the group used for group filtering after initial install.
- Will no longer create a new user profile on the Azure AD Connect server for every user doing a password change with password writeback enabled.
- Not able to use Long Integer values in Sync Rules scopes.
- The checkbox “device writeback” remains disabled if there are unreachable domain controllers.
Go download the latest version of Azure AD Connect: https://goo.gl/sYoKXo