Skip to content

Commit f0cdb93

Browse files
Merge pull request #301855 from asudbring/us444682-tm-faq-update
Added cipher suites for TLS to TM FAQ
2 parents 5f0523a + 7b35350 commit f0cdb93

File tree

1 file changed

+31
-1
lines changed

1 file changed

+31
-1
lines changed

articles/traffic-manager/traffic-manager-FAQs.md

Lines changed: 31 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: traffic-manager
55
author: asudbring
66
ms.service: azure-traffic-manager
77
ms.topic: concept-article
8-
ms.date: 01/28/2025
8+
ms.date: 06/25/2025
99
ms.author: allensu
1010
# Customer intent: As a Cloud Architect, I want to understand Azure Traffic Manager functionalities and limitations, so that I can effectively implement it for DNS-based traffic routing and ensure optimal performance of my distributed applications.
1111
---
@@ -104,6 +104,36 @@ To avoid service disruptions, resources that interact with Traffic Manager must
104104

105105
For information about migrating from TLS 1.0 and 1.1 to TLS 1.2, see [Solving the TLS 1.0 Problem](/security/engineering/solving-tls1-problem).
106106

107+
### What TLS cipher suites are supported by Azure Traffic Manager?
108+
109+
Azure Traffic Manager supports modern TLS cipher suites for TLS 1.2 and TLS 1.3 to ensure secure communications. The following cipher suites are supported:
110+
111+
**TLS 1.3 Cipher Suites**
112+
113+
These are associated with **Protocol 772** (which corresponds to TLS 1.3):
114+
115+
| Cipher Suite | Protocol |
116+
|--------------|----------|
117+
| TLS_AES_256_GCM_SHA384 | 772 |
118+
| TLS_AES_128_GCM_SHA256 | 772 |
119+
120+
**TLS 1.2 Cipher Suites**
121+
122+
These are associated with **Protocol 771** (TLS 1.2) and/or 65277 (used by some systems as an internal/custom code for TLS 1.2):
123+
124+
| Cipher Suite | Protocols |
125+
|--------------|-----------|
126+
| TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 | 771, 65277 |
127+
| TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 | 771, 65277 |
128+
| TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 | 771, 65277 |
129+
| TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 | 771, 65277 |
130+
| TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 | 771, 65277 |
131+
| TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 | 771, 65277 |
132+
| TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 | 771, 65277 |
133+
| TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 | 771, 65277 |
134+
135+
These cipher suites provide strong encryption and are compliant with modern security standards. Traffic Manager automatically negotiates the best available cipher suite during the TLS handshake process.
136+
107137
## Traffic Manager Geographic traffic routing method
108138

109139
### What are some use cases where geographic routing is useful?

0 commit comments

Comments
 (0)