MC258228 – (Updated) Reminder: Azure Active Directory – Enable support for TLS 1.2 protocol to avoid service impact (archived) Icon

check before: 2022-01-31


Azure Active Directory


World tenant, Online


Change type:

Admin impact, Retirement, Updated message



Updated June 22, 2021: We have extended the rollout timeline below. Thank you for your patience.
Note: If you have already transitioned to TLS 1.2, you can safely disregard this message.
As previously announced we will soon begin to retire support for following protocols and ciphers, in Azure Active Directory:

TLS 1.1, TLS 1.0 , 3DES cipher suite (TLS_RSA_WITH_3DES_EDE_CBC_SHA)
These protocols and ciphers are being retired to improve security when users/services interact with our cloud services.
Multiple announcements have been made via public articles "What's new in Azure Active Directory?" (Oct 2020, Nov 2020), emails to Azure subscription owners and Message center posts. This is a final reminder.
[Key points:]

TLS 1.0, 1.1 and 3DES cipher suite in U.S. government instances starting on March 31, 2021 – on going in phases.
TLS 1.0, 1.1 and 3DES cipher suite in public instances starting January 31, 2022. (This date has been postponed from 30th June 2021 to 31st Jan 2022, to give Administrators more time to remove the dependency on legacy TLS protocols and ciphers (TLS 1.0,1.1 and 3DES)).

Change Category:


Release Phase:



the free basic plan is required to see all details. Sign up here

A plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to please choose a plan.

Last updated 1 month ago

Share to MS Teams

Login to your account

Welcome Back, We Missed You!