Skip to content

Commit 9a7c383

Browse files
authored
Update application-gateway-tls-version-retirement.md
1 parent e0e3fd2 commit 9a7c383

File tree

1 file changed

+20
-1
lines changed

1 file changed

+20
-1
lines changed

articles/application-gateway/application-gateway-tls-version-retirement.md

Lines changed: 20 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: application gateway
55
author: jaesoni
66
ms.service: azure-application-gateway
77
ms.topic: concept-article
8-
ms.date: 05/15/2025
8+
ms.date: 07/18/2025
99
ms.author: mbender
1010
ms.custom:
1111
- build-2025
@@ -86,6 +86,25 @@ You don't need to configure anything on your Application Gateway for the backend
8686

8787
You must ensure that your servers in the backend pools are compatible with these updated protocol versions. This compatibility avoids any disruptions when establishing a TLS/HTTPS connection with those backend servers.
8888

89+
## Identification methods
90+
91+
### Metrics
92+
To determine whether clients connecting to your Application Gateway resource are utilising TLS 1.0 or 1.1, use the `Client TLS protocol` metric provided by Application Gateway. For further details, see the [metrics documentation](monitor-application-gateway-reference.md#metrics). You can view it from the Portal by following these steps.
93+
94+
1. Go to the Application Gateway resource in the Azure portal.
95+
2. In the left menu pane, open the "Metrics" blade in Monitoring section.
96+
3. Select metric as `Client TLS protocol` from the dropdown.
97+
4. To view granular protocol version information, select "Apply splitting" and choose "TLS protocol".
98+
99+
![A diagram showing metrics page with TLS version split for application gateway traffic.](media/application-gateway-tls-version-retirement/metric-tls-version.png)
100+
101+
### Logs
102+
You can also refer to the [Application Gateway Access logs](monitor-application-gateway-reference.md#access-log-category) to view this information in the logs format.
103+
104+
### Error information
105+
Once support for TLS versions 1.0 and 1.1 is discontinued, clients may encounter errors such as `curl: (35) error:0A000410:SSL routines::sslv3 alert handshake failure`. Depending on the browser being used, various messages indicating TLS handshake failures may be displayed.
106+
107+
89108
## Next steps
90109

91110
Learn about [TLS policy types and configurations](application-gateway-ssl-policy-overview.md)

0 commit comments

Comments
 (0)