For synchronization is only the need to install an local agent. The service is fully managed by Microsoft natively in the Azure portal. Azure AD Cloud sync is a Azure platform solution that syncs your existing identities to the Cloud without an on-premises installation. Microsoft released Azure AD Cloud Sync some months ago as a fully cloud managed solution for hybrid synchronization, Azure AD Connect always requires an existing server to install. The goal of Cloud migration is to minimize administrative overhead, automate existing workloads and get fully managed solutions from the provider.
Otherwise you get the the error message in the picture below.Īctivate TLS 1.2 for the selected server can be easily done with the Powershell script from the MS Docs site about TLS 1.2 enforcement for Azure AD Connect.Īfter TLS 1.2 is enabled, the upgrade process is straight forward and no different to Azure AD Connect version 1.
When you installing Azure AD connect v2 or update the existing installation, please check the Windows Server registry for TLS 1.2 enforcement. Check and activate for TLS 1.2 enforcement But remeber Azure AD Connect v2 is only supported on Windows Server 2016 or newer and the Server must have TLS 1.2 enabled. The installation or upgrade process is the same as in version 1 releases. The M365 Admin Center now report the AADConnect client version whenever there is export activity to Azure AD.Generic LDAP Connector and SQL Connector updated to latest version.release needs PowerShell version 5 or newer installed on the Windows Server (is installed per default on WS 2016 or newer).added new user properties to sync from ADDS to Azure AD.ADSyncTools are revamed with several improved and new cmdlets.release two new cmdlets to ADSyncTools module to enable or retrieve TLS 1.2 settins from Windows Server (Get-ADSycnToolsTls12 | Set-ADSycnToolsTls12).release use MSAL library for authentication, the older ADAL library was removed.Visual C++ runtime library use version 14 as prerequisite for SQL Server 2019.this relase avoid the need of a Global Admin account for authentication against AAD Connect setup.upgraded the LocalDB components to SQL 2019.this release enfore use of TLS 1.2 – if TLS 1.2 is not activated installation will fail.Inplace upgrades for servers with installed AAD Connect are not supported. Older Windows Server versions are not more supported and you can´t install AAD Connect on older WS versions. The biggest change is, that Azure AD Connect v2 is only supported on Windows Server 2016 or newer. Azure AD Connect v2 ImprovementsĪzure AD Connect v2 brings a tons of improvements and some big changes. For Azure AD Connect services with customized sync rules, I prefer to manually update the service, but this need additional overhead. Currently, versions older than 1.5.2.0 are no longer supported.įor small and medium business sizes, the auto update functionallity hold the Azure AD Connect server up to date. So it is really important to update regulary the Azure AD connect service. This means all Azure AD connect there where older then 18 months are out of support. We will begin implementing a deprecation process whereby versions of Azure AD Connect that were released more than 18 months ago will be deprecated. The team announced the following important notice
On November 2020 the Azure AD Connect team announced a new lifecycle for all Azure AD Connect versions.