Retirement Announcement - Upgrade to the latest version of Azure AD Connect before 31 August 2022

Marilee Turscak-MSFT 35,621 Reputation points Microsoft Employee
2021-09-01T15:37:16.793+00:00

On 31 August 2022, all 1.x versions of Azure Active Directory (Azure AD) Connect will be retired because they include SQL Server 2012 components that will no longer be supported. Upgrade to the most recent version of Azure AD Connect by that date. If you have a question, please post it in this thread.

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
20,140 questions
{count} vote

Accepted answer
  1. JamesTran-MSFT 36,496 Reputation points Microsoft Employee
    2021-09-01T15:39:10.783+00:00

    Learn more from this migration document.

    If you have any additional queries regarding this retirement, please use comments on this thread to ask your specific queries and we will try our best to answer those queries.

    Thank you!


2 additional answers

Sort by: Most helpful
  1. Jonathan Roundy 81 Reputation points
    2022-08-15T13:10:31.533+00:00
    1. What TLS Version are you using on this server?
    2. Have you set it to force strong authentication in the .NET settings? https://johnlouros.com/blog/enabling-strong-cryptography-for-all-dot-net-applications
    1 person found this answer helpful.
    0 comments No comments

  2. Snakez S 1 Reputation point
    2022-08-26T16:58:57.35+00:00

    JediMaster12-7622 - Your suggestion hit the jackpot on my issue. In my case my AD server was already enabled to run TLS 1.2 but seems like my .Net Framework 4.8 install was trying to run under TLS 1.0/1.1. Seems like the change to accept only TLS 1.2 or higher on Azure servers became active recently and caused my synchronization issue. I restarted all Azure AD Connect services and run a full synchronization with no errors. Perfect.