Merge pull request #291174 from jaesoni/old-tls-deprecation

TLS 1 and 1.1 deprecation note

Author: prmerger-automator[bot]

articles/application-gateway/application-gateway-ssl-policy-overview.md

@@ -5,7 +5,7 @@ services: application gateway
 author: greg-lindsay
 ms.service: azure-application-gateway
 ms.topic: concept-article
-ms.date: 06/06/2023
+ms.date: 11/28/2024
 ms.author: greglin
 ---
 
@@ -17,6 +17,9 @@ The TLS policy includes control of the TLS protocol version as well as the ciphe
 
 ## Usage and version details
 
+> [!IMPORTANT]
+> Starting **August 31, 2025**, all clients and backend servers interacting with Azure Application Gateway must use Transport Layer Security (TLS) 1.2 or higher, as [support for TLS 1.0 and 1.1 will be discontinued](https://azure.microsoft.com/updates/azure-application-gateway-support-for-tls-10-and-tls-11-will-end-by-31-august-2025).
+
 - SSL 2.0 and 3.0 are disabled for all application gateways and are not configurable.
 - A custom TLS policy allows you to select any TLS protocol as the minimum protocol version for your gateway: TLSv1_0, TLSv1_1, TLSv1_2, or TLSv1_3.
 - If no TLS policy is chosen, a [default TLS policy](application-gateway-ssl-policy-overview.md#default-tls-policy) gets applied based on the API version used to create that resource.