Merge pull request #289327 from spelluru/note1028

TLS Note for Event Grid

Author: JamesJBarnett

articles/event-grid/includes/tls-note.md

@@ -0,0 +1,12 @@
+---
+ title: Deprecation of Transport Layer Security (TLS) 1.0 and 1.1
+ description: The include file contains a note about deprecation of TLS 1.0 and 1.1.
+ author: robece
+ ms.service: azure-event-grid
+ ms.topic: include
+ ms.date: 10/28/2024
+ ms.author: robece
+---
+
+> [!NOTE]
+> **Regarding TLS 1.0 / 1.1 deprecation**: For system topics, you need to take action only for the event delivery to webhook destinations. If the destination supports TLS 1.2, the event delivery happens using 1.2. If the destination doesn't support TLS 1.2, the event delivery automatically falls back to 1.0 and 1.1. Post March 1st, 2025, event delivery using 1.0 and 1.1 won't be supported. Ensure that your webhook destinations support TLS 1.2. One easy way to check for TLS 1.2 support is to use [Qualys SSL Labs](https://www.ssllabs.com/ssltest/). If the report shows that TLS 1.2 is supported, no action is required. For more information, see the following blog post: [Retirement: Upcoming TLS changes for Azure Event Grid](https://azure.microsoft.com/updates/v2/TLS-changes-for-Azure-Event-Grid)

articles/event-grid/overview.md

@@ -62,8 +62,7 @@ Event Grid offers a rich mixture of features. These features include:
 - **High throughput** - Build high-volume integrated solutions with Event Grid.
 - **Custom domain names** - Allows users to assign their own domain names to Event Grid namespace's HTTP endpoints, enhancing security and simplifying client configuration.
 
-> [!NOTE]
-> **Regarding TLS 1.0 / 1.1 deprecation**: For system topics, you need to take action only for the event delivery to webhook destinations. If the destination supports TLS 1.2, the event delivery happens using 1.2. If the destination doesn't support TLS 1.2, the event delivery automatically falls back to 1.0 and 1.1. Post Oct 31st 2024, event delivery using 1.0 and 1.1 won't be supported. Ensure that your webhook destinations support TLS 1.2. One easy way to check for TLS 1.2 support is to use [Qualys SSL Labs](https://www.ssllabs.com/ssltest/). If the report shows that TLS 1.2 is supported, no action is required. For more information, see the following blog post: [Retirement: Upcoming TLS changes for Azure Event Grid](https://azure.microsoft.com/updates/v2/TLS-changes-for-Azure-Event-Grid)
+[!INCLUDE [tls-note.md](./includes/tls-note.md)]
 
 ## Use cases
 
@@ -163,7 +162,7 @@ You can configure **private links** to connect to Azure Event Grid to **publish
 
 Here's the list of regions where the new MQTT broker and namespace topics features are available:
 
-| | | | |
+| Region | Region | Region | Region |
 | -- | -- | -- | -- | 
 | Australia East | Australia South East | Australia Central |Australia Central 2 |
 | Brazil South | Brazil Southeast | Canada Central | Canada East |

articles/event-grid/sdk-overview.md

@@ -11,8 +11,7 @@ ms.devlang: csharp
 
 Event Grid provides SDKs that enable you to programmatically manage your resources and post events.
 
-> [!NOTE]
-> **Regarding TLS 1.0 / 1.1 deprecation**: For system topics, you need to take action only for the event delivery to webhook destinations. If the destination supports TLS 1.2, the event delivery happens using 1.2. If the destination doesn't support TLS 1.2, the event delivery automatically falls back to 1.0 and 1.1. Post Oct 31st 2024, event delivery using 1.0 and 1.1 won't be supported. Ensure that your webhook destinations support TLS 1.2. One easy way to check for TLS 1.2 support is to use [Qualys SSL Labs](https://www.ssllabs.com/ssltest/). If the report shows that TLS 1.2 is supported, no action is required. For more information, see the following blog post: [Retirement: Upcoming TLS changes for Azure Event Grid](https://azure.microsoft.com/updates/v2/TLS-changes-for-Azure-Event-Grid)
+[!INCLUDE [tls-note.md](./includes/tls-note.md)]
 
 ## Management SDKs