Merge pull request #259565 from spelluru/freshness1127

Freshness review

Author: v-dirichards

articles/event-grid/blob-event-quickstart-portal.md

@@ -1,7 +1,7 @@
 ---
 title: 'Use Azure Event Grid to send Blob storage events to web endpoint - portal'
 description: 'Quickstart: Use Azure Event Grid and Azure portal to create Blob storage account, and subscribe its events. Send the events to a Webhook.'
-ms.date: 10/27/2022
+ms.date: 11/27/2023
 ms.topic: quickstart
 ms.custom: mode-ui
 ---
@@ -20,7 +20,7 @@ In this article, you use the Azure portal to do the following tasks:
 
 When you're finished, you see that the event data has been sent to the web app.
 
-![View results.](./media/blob-event-quickstart-portal/view-results.png)
+:::image type="content" source="./media/blob-event-quickstart-portal/view-results.png" alt-text="Screenshot that shows the sample Azure Event Grid Viewer app with an event.":::
 
 ## Create a storage account
 
@@ -43,7 +43,7 @@ When you're finished, you see that the event data has been sent to the web app.
 
         >[!NOTE]
         > Only storage accounts of kind **StorageV2 (general purpose v2)** and **BlobStorage** support event integration. **Storage (general purpose v1)** does *not* support integration with Event Grid.
-1. The deployment may take a few minutes to complete. On the **Deployment** page, select **Go to resource**. 
+1. The deployment takes a few minutes to complete. On the **Deployment** page, select **Go to resource**. 
 
     :::image type="content" source="./media/blob-event-quickstart-portal/go-to-resource-link.png" alt-text="Screenshot showing the deployment succeeded page with a link to go to the resource.":::
 1. On the **Storage account** page, select **Events** on the left menu. 
@@ -52,7 +52,7 @@ When you're finished, you see that the event data has been sent to the web app.
 1. Keep this page in the web browser open. 
 
 ## Create a message endpoint
-Before subscribing to the events for the Blob storage, let's create the endpoint for the event message. Typically, the endpoint takes actions based on the event data. To simplify this quickstart, you deploy a [pre-built web app](https://github.com/Azure-Samples/azure-event-grid-viewer) that displays the event messages. The deployed solution includes an App Service plan, an App Service web app, and source code from GitHub.
+Before subscribing to the events for the Blob storage, let's create the endpoint for the event message. Typically, the endpoint takes actions based on the event data. To simplify this quickstart, you deploy a [prebuilt web app](https://github.com/Azure-Samples/azure-event-grid-viewer) that displays the event messages. The deployed solution includes an App Service plan, an App Service web app, and source code from GitHub.
 
 1. Select **Deploy to Azure** to deploy the solution to your subscription. 
 
@@ -65,7 +65,7 @@ Before subscribing to the events for the Blob storage, let's create the endpoint
 
         :::image type="content" source="./media/blob-event-quickstart-portal/template-deploy-parameters.png" alt-text="Screenshot showing the Custom deployment page.":::
 1. On the **Review + create** page, select **Create**. 
-1. The deployment may take a few minutes to complete. On the **Deployment** page, select **Go to resource group**. 
+1. The deployment takes a few minutes to complete. On the **Deployment** page, select **Go to resource group**. 
 
     :::image type="content" source="./media/blob-event-quickstart-portal/navigate-resource-group.png" alt-text="Screenshot showing the deployment succeeded page with a link to go to the resource group.":::
 4. On the **Resource group** page, in the list of resources, select the web app that you created. You also see the App Service plan and the storage account in this list. 
@@ -100,7 +100,7 @@ You subscribe to a topic to tell Event Grid which events you want to track, and
     2. Select **Web Hook** for **Endpoint type**. 
 
         :::image type="content" source="./media/blob-event-quickstart-portal/select-web-hook-end-point-type.png" alt-text="Screenshot showing the Create Event Subscription page with Web Hook selected as an endpoint.":::
-4. For **Endpoint**, click **Select an endpoint**, and enter the URL of your web app and add `api/updates` to the home page URL (for example: `https://spegridsite.azurewebsites.net/api/updates`), and then select **Confirm Selection**.
+4. For **Endpoint**, choose **Select an endpoint**, and enter the URL of your web app and add `api/updates` to the home page URL (for example: `https://spegridsite.azurewebsites.net/api/updates`), and then select **Confirm Selection**.
 
     :::image type="content" source="./media/blob-event-quickstart-portal/confirm-endpoint-selection.png" lightbox="./media/blob-event-quickstart-portal/confirm-endpoint-selection.png" alt-text="Screenshot showing the Select Web Hook page.":::
 5. Now, on the **Create Event Subscription** page, select **Create** to create the event subscription. 
@@ -114,7 +114,7 @@ Now, let's trigger an event to see how Event Grid distributes the message to you
 
 ## Send an event to your endpoint
 
-You trigger an event for the Blob storage by uploading a file. The file doesn't need any specific content. The articles assumes you have a file named testfile.txt, but you can use any file.
+You trigger an event for the Blob storage by uploading a file. The file doesn't need any specific content. 
 
 1. In the Azure portal, navigate to your Blob storage account, and select **Containers** on the let menu.
 1. Select **+ Container**. Give your container a name, and use any access level, and select **Create**. 
@@ -125,7 +125,7 @@ You trigger an event for the Blob storage by uploading a file. The file doesn't
       :::image type="content" source="./media/blob-event-quickstart-portal/select-container.png" alt-text="Screenshot showing the selection of the container.":::
 1. To upload a file, select **Upload**. On the **Upload blob** page, browse and select a file that you want to upload for testing, and then select **Upload** on that page. 
 
-      :::image type="content" source="./media/blob-event-quickstart-portal/upload-file.png" alt-text="Screenshot showing Upload blob page.":::
+      :::image type="content" source="./media/blob-event-quickstart-portal/upload-file.png" alt-text="Screenshot showing Upload blob page." lightbox="./media/blob-event-quickstart-portal/upload-file.png":::
 1. Browse to your test file and upload it.
 1. You've triggered the event, and Event Grid sent the message to the endpoint you configured when subscribing. The message is in the JSON format and it contains an array with one or more events. In the following example, the JSON message contains an array with one event. View your web app and notice that a **blob created** event was received. 
 

articles/event-grid/media/blob-event-quickstart-portal/blob-created-event.png

@@ -2,7 +2,7 @@
 title: Azure Event Grid security and authentication
 description: Describes Azure Event Grid and its concepts.
 ms.topic: conceptual
-ms.date: 10/25/2022
+ms.date: 11/27/2023
 ---
 
 # Authorizing access to Event Grid resources
@@ -25,10 +25,6 @@ The following operations return potentially secret information, which gets filte
 ## Built-in roles
 Event Grid provides the following three built-in roles. 
 
-The Event Grid Subscription Reader and Event Grid Subscription Contributor roles are for managing event subscriptions. They're important when implementing [event domains](event-domains.md) because they give users the permissions they need to subscribe to topics in your event domain. These roles are focused on event subscriptions and don't grant access for actions such as creating topics.
-
-The Event Grid Contributor role allows you to create and manage Event Grid resources. 
-
 
 | Role | Description |
 | ---- | ----------- | 
@@ -37,14 +33,19 @@ The Event Grid Contributor role allows you to create and manage Event Grid resou
 | [`EventGrid Contributor`](../role-based-access-control/built-in-roles.md#eventgrid-contributor) | Lets you create and manage Event Grid resources. |
 | [`EventGrid Data Sender`](../role-based-access-control/built-in-roles.md#eventgrid-data-sender) | Lets you send events to Event Grid topics. |
 
+The **Event Grid Subscription Reader** and **Event Grid Subscription Contributor** roles are for managing event subscriptions. They're important when implementing [event domains](event-domains.md) because they give users the permissions they need to subscribe to topics in your event domain. These roles are focused on event subscriptions and don't grant access for actions such as creating topics.
+
+The **Event Grid Contributor** role allows you to create and manage Event Grid resources. 
+
+
 
 > [!NOTE]
 > Select links in the first column to navigate to an article that provides more details about the role. For instructions on how to assign users or groups to RBAC roles, see [this article](../role-based-access-control/quickstart-assign-role-user-portal.md).
 
 
 ## Custom roles
 
-If you need to specify permissions that are different than the built-in roles, you can create custom roles.
+If you need to specify permissions that are different than the built-in roles, create custom roles.
 
 The following are sample Event Grid role definitions that allow users to take different actions. These custom roles are different from the built-in roles because they grant broader access than just event subscriptions.
 

articles/event-grid/media/blob-event-quickstart-portal/upload-file.png

@@ -2,8 +2,7 @@
 title: Azure Quickstart - Create an event hub using the Azure portal
 description: In this quickstart, you learn how to create an Azure event hub using Azure portal.
 ms.topic: quickstart
-ms.date: 10/10/2022
-ms.custom: ignite-fall-2021, mode-ui
+ms.date: 11/27/2023
 ---
 
 # Quickstart: Create an event hub using Azure portal
@@ -12,10 +11,7 @@ Azure Event Hubs is a Big Data streaming platform and event ingestion service th
 In this quickstart, you create an event hub using the [Azure portal](https://portal.azure.com).
 
 ## Prerequisites
-
-To complete this quickstart, make sure that you have:
-
-- Azure subscription. If you don't have one, [create a free account](https://azure.microsoft.com/free/) before you begin.
+To complete this quickstart, make sure that you have an Azure subscription. If you don't have one, [create a free account](https://azure.microsoft.com/free/) before you begin.
 
 ## Create a resource group
 
@@ -37,8 +33,7 @@ A resource group is a logical collection of Azure resources. All resources are d
 
 An Event Hubs namespace provides a unique scoping container, in which you create one or more event hubs. To create a namespace in your resource group using the portal, do the following actions:
 
-1. In the Azure portal, and select **Create a resource** at the top left of the screen.
-1. Select **All services** in the left menu, and select **star (`*`)** next to **Event Hubs** in the **Analytics** category. Confirm that **Event Hubs** is added to **FAVORITES** in the left navigational menu. 
+1. In the Azure portal, select **All services** in the left menu, and select **star (`*`)** next to **Event Hubs** in the **Analytics** category. Confirm that **Event Hubs** is added to **FAVORITES** in the left navigational menu. 
 
     :::image type="content" source="./media/event-hubs-quickstart-portal/select-event-hubs-menu.png" alt-text="Screenshot showing the selection of Event Hubs in the All services page.":::
 1. Select **Event Hubs** under **FAVORITES** in the left navigational menu, and select **Create** on the toolbar.

articles/event-grid/media/blob-event-quickstart-portal/view-subscription-event.png

@@ -2,25 +2,26 @@
 title: Scalability - Azure Event Hubs | Microsoft Docs
 description: This article provides information on how to scale Azure Event Hubs by using partitions and throughput units. 
 ms.topic: article
-ms.date: 10/25/2022
+ms.date: 11/23/2023
 ---
 
 # Scaling with Event Hubs
 
-There are two factors which influence scaling with Event Hubs.
-* Throughput units (standard tier) or processing units (premium tier) 
-* Partitions
+There are two factors that influence scaling with Event Hubs.
+
+- Throughput units (standard tier) or processing units (premium tier) 
+- Partitions
 
 ## Throughput units
 
-The throughput capacity of Event Hubs is controlled by *throughput units*. Throughput units are pre-purchased units of capacity. A single throughput unit lets you:
+The throughput capacity of event hubs is controlled by **throughput units**. Throughput units are prepurchased units of capacity. A single throughput unit lets you:
 
-* Ingress: Up to 1 MB per second or 1000 events per second (whichever comes first).
-* Egress: Up to 2 MB per second or 4096 events per second.
+* Ingress: Up to 1 MB per second or 1,000 events per second (whichever comes first).
+* Egress: Up to 2 MB per second or 4,096 events per second.
 
-Beyond the capacity of the purchased throughput units, ingress is throttled and a [ServerBusyException](/dotnet/api/microsoft.azure.eventhubs.serverbusyexception) is returned. Egress does not produce throttling exceptions, but is still limited to the capacity of the purchased throughput units. If you receive publishing rate exceptions or are expecting to see higher egress, be sure to check how many throughput units you have purchased for the namespace. You can manage throughput units on the **Scale** blade of the namespaces in the [Azure portal](https://portal.azure.com). You can also manage throughput units programmatically using the [Event Hubs APIs](./event-hubs-samples.md).
+Beyond the capacity of the purchased throughput units, ingress is throttled and Event Hubs throws a [ServerBusyException](/dotnet/api/microsoft.azure.eventhubs.serverbusyexception). Egress doesn't produce throttling exceptions, but is still limited to the capacity of the purchased throughput units. If you receive publishing rate exceptions or are expecting to see higher egress, be sure to check how many throughput units you have purchased for the namespace. You can manage throughput units on the **Scale** page of the namespaces in the [Azure portal](https://portal.azure.com). You can also manage throughput units programmatically using the [Event Hubs APIs](./event-hubs-samples.md).
 
-Throughput units are pre-purchased and are billed per hour. Once purchased, throughput units are billed for a minimum of one hour. Up to 40 throughput units can be purchased for an Event Hubs namespace and are shared across all event hubs in that namespace.
+Throughput units are prepurchased and are billed per hour. Once purchased, throughput units are billed for a minimum of one hour. Up to 40 throughput units can be purchased for an Event Hubs namespace and are shared across all event hubs in that namespace.
 
 The **Auto-inflate** feature of Event Hubs automatically scales up by increasing the number of throughput units, to meet usage needs. Increasing throughput units prevents throttling scenarios, in which:
 
@@ -29,15 +30,15 @@ The **Auto-inflate** feature of Event Hubs automatically scales up by increasing
 
 The Event Hubs service increases the throughput when load increases beyond the minimum threshold, without any requests failing with ServerBusy errors. 
 
-For more information about the auto-inflate feature, see [Automatically scale throughput units](event-hubs-auto-inflate.md).
+For more information about the autoinflate feature, see [Automatically scale throughput units](event-hubs-auto-inflate.md).
 
 ## Processing units
 
- [Event Hubs Premium](./event-hubs-premium-overview.md) provides superior performance and better isolation within a managed multitenant PaaS environment. The resources in a Premium tier are isolated at the CPU and memory level so that each tenant workload runs in isolation. This resource container is called a *Processing Unit* (PU). You can purchase 1, 2, 4, 8 or 16 processing Units for each Event Hubs Premium namespace. 
+ [Event Hubs Premium](./event-hubs-premium-overview.md) provides superior performance and better isolation within a managed multitenant PaaS environment. The resources in a Premium tier are isolated at the CPU and memory level so that each tenant workload runs in isolation. This resource container is called a **Processing Unit** (PU). You can purchase 1, 2, 4, 8 or 16 processing Units for each Event Hubs Premium namespace. 
 
 How much you can ingest and stream with a processing unit depends on various factors such as your producers, consumers, the rate at which you're ingesting and processing, and much more. 
 
-For example, Event Hubs Premium namespace with 1 PU and 1 event hub (100 partitions) can approximately offer core capacity of ~5-10 MB/s ingress and 10-20 MB/s egress for both AMQP or Kafka workloads.
+For example, Event Hubs Premium namespace with one PU and one event hub (100 partitions) can approximately offer core capacity of ~5-10 MB/s ingress and 10-20 MB/s egress for both AMQP or Kafka workloads.
 
 To learn about configuring PUs for a premium tier namespace, see [Configure processing units](configure-processing-units-premium-namespace.md).
 

articles/event-grid/security-authorization.md

@@ -5,7 +5,7 @@ services: event-hubs
 author: spelluru
 ms.service: event-hubs
 ms.topic: include
-ms.date: 04/11/2022
+ms.date: 11/27/2023
 ms.author: spelluru
 ms.custom: "include file"