This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 81%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMT%3C/text%3E%3C/svg%3E)
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.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(316.8, 68%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDT%3C/text%3E%3C/svg%3E)
Hi, What will happen after 31 August 2022 will versions 1.x still work but be unsupported or will they stop working ?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(131.20000000000002, 11%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERD%3C/text%3E%3C/svg%3E)
Hi Daniel - https://learn.microsoft.com/en-us/azure/active-directory/hybrid/whatis-azure-ad-connect-v2#what-else-do-i-need-to-know has more detailed information about AADConnect V2.0:
What happens if I do not upgrade?
Until one of the components that are being retired are actually deprecated, you will not see any impact. Azure AD Connect will keep on working.
We expect TLS 1.0/1.1 to be deprecated in January 2022, and you need to make sure you are not using these protocols by that date as your service may stop working unexpectedly. You can manually configure your server for TLS 1.2 though, and that does not require an update of Azure AD Connect to V2.0
In June 2022, ADAL will go out of support. When ADAL goes out of support authentication may stop working unexpectedly and this will block the Azure AD Connect server from working properly. We strongly advise you to upgrade to Azure AD Connect V2.0 before June 2022. You cannot upgrade to a supported authentication library with your current Azure AD Connect version.
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!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 16%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
Hi,
We have Azure AD connect 1.1.654.0 version on Windows 2008 R2 standard server. Issue is we are unable to login into Azure AD connect with global admin credentials.
Error as : unable to validate credentials. verify network connectivity and firewall or proxy settings.The remote server returned an error.(400) bad request.
We dont have any proxy servers. We are entering correct login credentials.
the sign-in assistant was retired.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(182.40000000000003, 13%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
Follow JediMaster12-7622 suggestion. I have almost the same setup. Running Windows Server 2008 R2 Standard with AzureADConnect 1.1.533.0 version. I started having the sync issues early this month. Seems like they enforced the use of TLS 1.2 or higher and caused my synchroinization issues.
I'm actually preparing to migrate my server to Windows Server 2019 and migrate our AD since AzureADConnect latest versions no longer support Windows 2008 R2.
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.
@Snakez S and @shravanthi Mortha would you be willing to vote for my answer. :) I'm glad it helped.
TIA