Addressing TLS Version Support Changes in Azure Traffic Manager

Question

What actions are required due to the upcoming end of support for TLS 1.0 and 1.1 in Azure Traffic Manager?

PS - Based on common issues that we have seen from customers and other sources, we are posting these questions to help the Azure community.

Answer 1

Starting on October 31, 2024, Azure Traffic Manager will no longer support TLS 1.0 and 1.1. To avoid potential service disruptions and enhance security, all interactions with Azure services must be secured using TLS 1.2 or later. The older TLS versions are not known to be vulnerable, but TLS 1.2 and later provide improved security features such as perfect forward secrecy and stronger cipher suites.

To prepare for this change: 1. Confirm that your resources interacting with Azure services are using TLS 1.2 or later. 2. If you are already using TLS 1.2 or later exclusively, no further action is needed. 3. If you still rely on TLS 1.0 or 1.1, ensure you upgrade to TLS 1.2 or later by October 31, 2024.

Additionally, validate that your backend supports TLS 1.2 if you are using HTTPS probes. No backend changes are necessary other than ensuring TLS 1.2 support.

Resources:

• Azure support for TLS 1.0 and TLS 1.1 will end by 31 October 2024
• Transport Layer Security (TLS) best practices with the .NET Framework
• Update to TLS 1.2
• Azure Traffic Manager documentation

Hope this helps. If you have any follow-up questions, please let me know. I would be happy to help.

Please do not forget to "Accept the answer" and "up-vote" wherever the information provided helps you, as this can be beneficial to other community members.