Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into mdb-rdp-split

Author: RoseHJM

articles/event-grid/add-identity-roles.md

@@ -3,7 +3,7 @@ title: Add managed identity to a role on Azure Event Grid destination
 description: This article describes how to add managed identity to Azure roles on destinations such as Azure Service Bus and Azure Event Hubs. 
 ms.topic: how-to
 ms.custom: devx-track-azurecli
-ms.date: 03/25/2021
+ms.date: 01/31/2024
 ---
 
 # Grant managed identity the access to Event Grid destination
@@ -16,9 +16,9 @@ Assign a system-assigned managed identity by using instructions from the followi
 - [System topics](enable-identity-system-topics.md)
 
 ## Supported destinations and Azure roles
-After you enable identity for your event grid custom topic or domain, Azure automatically creates an identity in Microsoft Entra ID. Add this identity to appropriate Azure roles so that the custom topic or domain can forward events to supported destinations. For example, add the identity to the **Azure Event Hubs Data Sender** role for an Azure Event Hubs namespace so that the event grid custom topic can forward events to event hubs in that namespace. 
+After you enable identity for your Event Grid custom topic or domain, Azure automatically creates an identity in Microsoft Entra ID. Add this identity to appropriate Azure roles so that the custom topic or domain can forward events to supported destinations. For example, add the identity to the **Azure Event Hubs Data Sender** role for an Azure Event Hubs namespace so that the Event Grid custom topic can forward events to event hubs in that namespace. 
 
-Currently, Azure event grid supports custom topics or domains configured with a system-assigned managed identity to forward events to the following destinations. This table also gives you the roles that the identity should be in so that the custom topic can forward the events.
+Currently, Azure Event Grid supports custom topics or domains configured with a system-assigned managed identity to forward events to the following destinations. This table also gives you the roles that the identity should be in so that the custom topic can forward the events.
 
 | Destination | Azure role | 
 | ----------- | --------- | 
@@ -30,7 +30,7 @@ Currently, Azure event grid supports custom topics or domains configured with a
 ## Use the Azure portal
 You can use the Azure portal to assign the custom topic or domain identity to an appropriate role so that the custom topic or domain can forward events to the destination. 
 
-The following example adds a managed identity for an event grid custom topic named **msitesttopic** to the **Azure Service Bus Data Sender** role for a Service Bus namespace that contains a queue or topic resource. When you add to the role at the namespace level, the event grid custom topic can forward events to all entities within the namespace. 
+The following example adds a managed identity for an Event Grid custom topic named **msitesttopic** to the **Azure Service Bus Data Sender** role for a Service Bus namespace that contains a queue or topic resource. When you add to the role at the namespace level, the Event Grid custom topic can forward events to all entities within the namespace. 
 
 1. Go to your **Service Bus namespace** in the [Azure portal](https://portal.azure.com). 
 1. Select **Access Control** in the left pane. 
@@ -56,7 +56,7 @@ The following example adds a managed identity for an event grid custom topic nam
 The steps are similar for adding an identity to other roles mentioned in the table. 
 
 ## Use the Azure CLI
-The example in this section shows you how to use the Azure CLI to add an identity to an Azure role. The sample commands are for event grid custom topics. The commands for event grid domains are similar. 
+The example in this section shows you how to use the Azure CLI to add an identity to an Azure role. The sample commands are for Event Grid custom topics. The commands for Event Grid domains are similar. 
 
 ### Get the principal ID for the custom topic's system identity 
 First, get the principal ID of the custom topic's system-managed identity and assign the identity to appropriate roles.
@@ -82,7 +82,7 @@ az role assignment create --role "$role" --assignee "$topic_pid" --scope "$event
 ```
 
 ### Create a role assignment for a Service Bus topic at various scopes 
-The following CLI example shows how to add an event grid custom topic's identity to the **Azure Service Bus Data Sender** role at the namespace level or at the Service Bus topic level. If you create the role assignment at the namespace level, the event grid topic can forward events to all entities (Service Bus queues or topics) within that namespace. If you create a role assignment at the Service Bus queue or topic level, the event grid custom topic can forward events only to that specific Service Bus queue or topic. 
+The following CLI example shows how to add an Event Grid custom topic's identity to the **Azure Service Bus Data Sender** role at the namespace level or at the Service Bus topic level. If you create the role assignment at the namespace level, the Event Grid topic can forward events to all entities (Service Bus queues or topics) within that namespace. If you create a role assignment at the Service Bus queue or topic level, the Event Grid custom topic can forward events only to that specific Service Bus queue or topic. 
 
 ```azurecli-interactive
 role="Azure Service Bus Data Sender" 

articles/event-grid/create-custom-topic.md

@@ -1,7 +1,7 @@
 ---
 title: Create an Azure Event Grid topic or a domain
 description: This article shows how to create an Event Grid topic or domain.
-ms.date: 07/21/2022
+ms.date: 01/31/2024
 ms.topic: how-to
 ms.custom: mode-ui
 ---
@@ -18,9 +18,9 @@ If you're new to Azure Event Grid, read through [Event Grid overview](overview.m
 An Event Grid topic provides a user-defined endpoint that you post your events to. 
 
 1. Sign in to [Azure portal](https://portal.azure.com/).
-2. In the search bar at the top, type **Event Grid Topics**, and then select **Event Grid Topics** from the drop-down list. If you are create a domain, search for **Event Grid Domains**.
+2. In the search bar at the top, type **Event Grid Topics**, and then select **Event Grid Topics** from the drop-down list. To create a domain, search for **Event Grid Domains**.
 
-    :::image type="content" source="./media/custom-event-quickstart-portal/select-topics.png" alt-text="Screenshot showing the Azure port search bar to search for Event Grid topics.":::
+    :::image type="content" source="./media/custom-event-quickstart-portal/select-topics.png" lightbox="./media/custom-event-quickstart-portal/select-topics.png" alt-text="Screenshot showing the Azure port search bar to search for Event Grid topics.":::
 3. On the **Event Grid Topics** or **Event Grid Domains** page, select **+ Create** on the toolbar. 
 
     :::image type="content" source="./media/custom-event-quickstart-portal/create-topic-button.png" alt-text="Screenshot showing the Create Topic button on Event Grid topics page.":::
@@ -30,7 +30,7 @@ On the **Basics** page of **Create Topic** or **Create Event Grid Domain** wizar
 
 1. Select your Azure **subscription**.
 2. Select an existing resource group or select **Create new**, and enter a **name** for the **resource group**.
-3. Provide a unique **name** for the custom topic or domain. The name must be unique because it's represented by a DNS entry. Don't use the name shown in the image. Instead, create your own name - it must be between 3-50 characters and contain only values a-z, A-Z, 0-9, and "-".
+3. Provide a unique **name** for the custom topic or domain. The name must be unique because it's represented by a Domain Name System (DNS) entry. Don't use the name shown in the image. Instead, create your own name - it must be between 3-50 characters and contain only values a-z, A-Z, 0-9, and "-".
 4. Select a **location** for the Event Grid topic or domain.
 1. Select **Next: Networking** at the bottom of the page to switch to the **Networking** page.  
 
@@ -39,7 +39,7 @@ On the **Basics** page of **Create Topic** or **Create Event Grid Domain** wizar
 ## Networking page
 On the **Networking** page of the **Create Topic** or **Create Event Grid Domain** wizard, follow these steps:
 
-1. If you want to allow clients to connect to the topic or domain endpoint via a public IP address, keep the **Public access** option selected. 
+1. If you want to allow clients to connect to the topic or domain endpoint via a public IP address, keep the **Public access** option selected. You can restrict the access to specific IP addresses or IP address range. 
 
     :::image type="content" source="./media/configure-firewall/networking-page-public-access.png" alt-text="Screenshot showing the selection of Public access option on the Networking page of the Create topic wizard.":::
 1. To allow access to the topic or domain via a private endpoint, select the **Private access** option. 
@@ -62,6 +62,9 @@ On the **Security** page of the **Create Topic**  or **Create Event Grid Domain*
 1. To disable local authentication, select **Disabled**. When you do it, the topic or domain can't be accessed using accesskey and SAS authentication, but only via Microsoft Entra authentication.
 
     :::image type="content" source="./media/authenticate-with-microsoft-entra-id/create-topic-disable-local-auth.png" alt-text="Screenshot showing the Advanced tab of Create Topic page when you can disable local authentication.":::
+1. Configure the minimum required Transport Layer Security (TLS) version. For more information, see [Configure minimum TLS version](transport-layer-security-configure-minimum-version.md).
+
+    :::image type="content" source="./media/create-custom-topic/configure-transport-layer-security-version.png" alt-text="Screenshot showing the Advanced tab of Create Topic page when you can select the minimum TLS version.":::
 1. Select **Advanced** at the bottom of the page to switch to the **Advanced** page. 
 
 ## Advanced page
@@ -72,13 +75,13 @@ On the **Security** page of the **Create Topic**  or **Create Event Grid Domain*
 
     :::image type="content" source="./media/create-custom-topic/data-residency.png" alt-text="Screenshot showing the Data residency section of the Advanced page in the Create Topic wizard.":::
 
-    The **Cross-Geo** option allows Microsoft-initiated failover to the paired region in case of a region failure. For more information, see [Server-side geo disaster recovery in Azure Event Grid](geo-disaster-recovery.md). Microsoft-initiated failover is exercised by Microsoft in rare situations to fail over Event Grid resources from an affected region to the corresponding geo-paired region. This process doesn't require an intervention from user. Microsoft reserves right to make a determination of when this path will be taken. The mechanism doesn't involve a user consent before the user's topic or domain is failed over. For more information, see [How do I recover from a failover?](./faq.yml).
+    The **Cross-Geo** option allows Microsoft-initiated failover to the paired region when there's a region failure. For more information, see [Server-side geo disaster recovery in Azure Event Grid](geo-disaster-recovery.md). Microsoft-initiated failover is exercised by Microsoft in rare situations to fail over Event Grid resources from an affected region to the corresponding geo-paired region. This process doesn't require an intervention from user. Microsoft reserves right to make a determination of when this path will be taken. The mechanism doesn't involve a user consent before the user's topic or domain is failed over. For more information, see [How do I recover from a failover?](./faq.yml).
 
-    If you select the **Regional** option, you may define your own disaster recovery plan. 
+    If you select the **Regional** option, you can define your own disaster recovery plan. 
 3. Select **Next: Tags** to move to the **Tags** page. 
 
 ## Tags page
-The **Tags** page has no fields that are specific to Event Grid. You can assign a tag (name-value pair) as you do for any other Azure resource.  Select **Next: Review + create** to switch to the **Review + create** page. 
+The **Tags** page has no fields that are specific to Event Grid. You can assign a tag (name-value pair) as you do for any other Azure resource. Select **Next: Review + create** to switch to the **Review + create** page. 
 
 ## Review + create page
 On the **Review + create** page, review all your settings, confirm the validation succeeded, and then select **Create** to create the topic or the domain.

articles/event-grid/custom-event-to-eventhub.md

@@ -1,14 +1,14 @@
 ---
 title: 'Quickstart: Send custom events to Event Hubs - Event Grid, Azure CLI'
 description: 'Quickstart: Use Azure Event Grid and Azure CLI to publish a topic, and subscribe to that event. An event hub is used for the endpoint.'
-ms.date: 11/18/2022
+ms.date: 01/31/2024
 ms.topic: quickstart
 ms.custom: devx-track-azurecli, mode-api
 ---
 
 # Quickstart: Route custom events to Azure Event Hubs with Azure CLI and Event Grid
 
-[Azure Event Grid](overview.md) is a highly scalable and serverless event broker that you can use to integrate applications using events. Events are delivered by Event Grid to  [supported event handlers](event-handlers.md) and Azure Event Hubs is one of them. In this article, you use  Azure CLI for the following steps:
+[Azure Event Grid](overview.md) is a highly scalable and serverless event broker that you can use to integrate applications using events. Event Grid delivers events to  [supported event handlers](event-handlers.md) and Azure Event Hubs is one of them. In this article, you use  Azure CLI for the following steps:
 
 1. Create an Event Grid custom topic.
 1. Create an Azure Event Hubs subscription for the custom topic.
@@ -34,7 +34,7 @@ az group create --name gridResourceGroup --location westus2
 
 ## Create a custom topic
 
-An Event Grid topic provides a user-defined endpoint that you post your events to. The following example creates the custom topic in your resource group. Replace `<topic_name>` with a unique name for your custom topic. The Event Grid topic name must be unique because it's represented by a DNS entry.
+An Event Grid topic provides a user-defined endpoint that you post your events to. The following example creates the custom topic in your resource group. Replace `<topic_name>` with a unique name for your custom topic. The Event Grid topic name must be unique because it's represented by a Domain Name System (DNS) entry.
 
 1. Specify a name for the topic. 
 
@@ -96,7 +96,7 @@ endpoint=$(az eventgrid topic show --name $topicname -g gridResourceGroup --quer
 key=$(az eventgrid topic key list --name $topicname -g gridResourceGroup --query "key1" --output tsv)
 ```
 
-To simplify this article, you use sample event data to send to the custom topic. Typically, an application or Azure service would send the event data. CURL is a utility that sends HTTP requests. In this article, use CURL to send the event to the custom topic.  The following example sends three events to the Event Grid topic:
+To simplify this article, you use sample event data to send to the custom topic. Typically, an application or Azure service would send the event data. CURL is a utility that sends HTTP requests. In this article, use CURL to send the event to the custom topic. The following example sends three events to the Event Grid topic:
 
 ```azurecli-interactive
 for i in 1 2 3
@@ -106,7 +106,7 @@ do
 done
 ```
 
-On the **Overview** page for your Event Hubs namespace in the Azure portal, notice that Event Grid sent those three events to the event hub. You'll see the same chart on the **Overview** page for the `demohub` Event Hubs instance page. 
+On the **Overview** page for your Event Hubs namespace in the Azure portal, notice that Event Grid sent those three events to the event hub. You see the same chart on the **Overview** page for the `demohub` Event Hubs instance page. 
 
 :::image type="content" source="./media/custom-event-to-eventhub/show-result.png" lightbox="./media/custom-event-to-eventhub/show-result.png" alt-text="Image showing the portal page with incoming message count as 3.":::
 

articles/event-grid/custom-event-to-queue-storage.md

@@ -1,14 +1,14 @@
 ---
 title: 'Quickstart: Send custom events to storage queue - Event Grid, Azure CLI'
 description: 'Quickstart: Use Azure Event Grid and Azure CLI to publish a topic, and subscribe to that event. A storage queue is used for the endpoint.'
-ms.date: 12/20/2022
+ms.date: 01/31/2024
 ms.topic: quickstart
 ms.custom: devx-track-azurecli, mode-api
 ---
 
 # Quickstart: Route custom events to Azure Queue storage via Event Grid using Azure CLI
 
-[Azure Event Grid](overview.md) is a highly scalable and serverless event broker that you can use to integrate applications using events. Events are delivered by Event Grid to  [supported event handlers](event-handlers.md) and Azure Queue storage is one of them. In this article, you use  Azure CLI for the following steps:
+[Azure Event Grid](overview.md) is a highly scalable and serverless event broker that you can use to integrate applications using events. Event Grid delivers events to  [supported event handlers](event-handlers.md) and Azure Queue storage is one of them. In this article, you use  Azure CLI for the following steps:
 
 1. Create an Event Grid custom topic.
 1. Create an Azure Queue subscription for the custom topic.
@@ -34,7 +34,7 @@ az group create --name gridResourceGroup --location westus2
 
 ## Create a custom topic
 
-An Event Grid topic provides a user-defined endpoint that you post your events to. The following example creates the custom topic in your resource group. Replace `<topic_name>` with a unique name for your custom topic. The Event Grid topic name must be unique because it's represented by a DNS entry.
+An Event Grid topic provides a user-defined endpoint that you post your events to. The following example creates the custom topic in your resource group. Replace `<topic_name>` with a unique name for your custom topic. The Event Grid topic name must be unique because it's represented by a Domain Name System (DNS) entry.
 
 1. Specify a name for the topic. 
 
@@ -114,7 +114,7 @@ endpoint=$(az eventgrid topic show --name $topicname -g gridResourceGroup --quer
 key=$(az eventgrid topic key list --name $topicname -g gridResourceGroup --query "key1" --output tsv)
 ```
 
-To simplify this article, you use sample event data to send to the custom topic. Typically, an application or Azure service would send the event data. CURL is a utility that sends HTTP requests. In this article, you use CURL to send the event to the custom topic.  The following example sends three events to the Event Grid topic:
+To simplify this article, you use sample event data to send to the custom topic. Typically, an application or Azure service would send the event data. CURL is a utility that sends HTTP requests. In this article, you use CURL to send the event to the custom topic. The following example sends three events to the Event Grid topic:
 
 ```azurecli-interactive
 for i in 1 2 3