Trace Id is missing
Skip to main content
Azure

RETIREMENT

Retirement: Update on retirement of TLS 1.0 and TLS 1.1 versions for Azure Services 

Published date: Oct 24, 2024

Following the announcement on November 10, 2023, we are continuing our transition to requiring TLS 1.2 or later for all connections to Azure services. To minimize disruption to customer workloads, several services will continue supporting TLS 1.0 and TLS 1.1 versions and complete their transitions by August 31, 2025 when TLS 1.2 or later will be required for all connections to Azure services (unless explicitly indicated in service documentation). The list of remaining services will be updated as transitions to TLS 1.2 or later complete.

While the Microsoft implementation of TLS 1.0 and TLS 1.1 versions is not known to have vulnerabilities, TLS 1.2 or later versions provide improved security features, including perfect forward secrecy and stronger cipher suites. 

Customers still using TLS 1.0 or 1.1 should transition their workloads to TLS 1.2 or later versions to ensure uninterrupted connectivity to Azure services. 

Recommended action

To avoid potential service disruptions, confirm that your resources that interact with Azure services are using TLS 1.2 or later. Then:

  • If they're already exclusively using TLS 1.2 or later, you don't need to take further action.
  • If they still have a dependency on TLS 1.0 or 1.1, transition them to TLS 1.2 or later. 

Help and support 

Read more about the update to TLS 1.2. If you have questions, get answers from community experts in Microsoft Q&A. If you have a support plan and you need technical help, please create a support request. 

Previously Published on November 10, 2023: Azure support for TLS 1.0 and TLS 1.1 will end by October 31, 2024

To enhance security and provide best-in-class encryption for your data, we'll require interactions with Azure services to be secured using Transport Layer Security (TLS) 1.2 or later beginning October 31, 2024, when support for TLS 1.0 and 1.1 will end. 

The Microsoft implementation of older TLS versions is not known to be vulnerable, however, TLS 1.2 or later offer improved security with features such as perfect forward secrecy and stronger cipher suites. 

Recommended action

To avoid potential service disruptions, confirm that your resources that interact with Azure services are using TLS 1.2 or later. Then:

  • If they're already exclusively using TLS 1.2 or later, you don't need to take further action. 
  • If they still have a dependency on TLS 1.0 or 1.1, transition them to TLS 1.2 or later by October 31, 2024. 

Help and support 

Read more about the update to TLS 1.2. If you have questions, get answers from community experts in Microsoft Q&A. If you have a support plan and you need technical help, please create a support request.