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!
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
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!
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.