Merge pull request #279110 from ccompy/patch-1

Update transport-layer-security-enforce-minimum-version.md

Author: prmerger-automator[bot]

articles/event-hubs/transport-layer-security-enforce-minimum-version.md

@@ -5,7 +5,7 @@ description: Configure a service bus namespace to require a minimum version of T
 author: EldertGrootenboer
 ms.service: event-hubs
 ms.topic: article
-ms.date: 04/25/2022
+ms.date: 06/24/2024
 ms.author: egrootenboer
 ---
 
@@ -17,6 +17,12 @@ Azure Event Hubs supports choosing a specific TLS version for namespaces. Curren
 
 Azure Event Hubs namespaces permit clients to send and receive data with TLS 1.0 and above. To enforce stricter security measures, you can configure your Event Hubs namespace to require that clients send and receive data with a newer version of TLS. If an Event Hubs namespace requires a minimum version of TLS, then any requests made with an older version will fail.
 
+> [!WARNING]
+> As of 31 October 2024, TLS 1.0 and TLS 1.1 will no longer be supported on Azure. [TLS 1.0 and TLS 1.1 end of support announcement](https://azure.microsoft.com/updates/azure-support-tls-will-end-by-31-october-2024-2/) The minimum TLS version will be 1.2 for all Event Hubs deployments.
+
+> [!IMPORTANT]
+> On 31 October 2024, TLS 1.3 will be enabled for AMQP traffic. TLS 1.3 is already enabled for Kafka and HTTPS traffic. Java clients may have a problem with TLS 1.3 due to a dependency on an older version of Proton-J. For more details, read [Java client changes to support TLS 1.3 with Azure Service Bus and Azure Event Hubs](https://techcommunity.microsoft.com/t5/messaging-on-azure-blog/java-client-changes-to-support-tls-1-3-with-azure-service-bus/ba-p/4089355) 
+
 > [!IMPORTANT]
 > If you are using a service that connects to Azure Event Hubs, make sure that service is using the appropriate version of TLS to send requests to Azure Event Hubs before you set the required minimum version for an Event Hubs namespace.