Merge pull request #253145 from IlanaWaitser/docs-editor/ingest-logs-event-hub-1695899171

Update ingest-logs-event-hub.md

Author: v-dirichards

articles/azure-monitor/logs/ingest-logs-event-hub.md

@@ -12,8 +12,7 @@ ms.custom: references_regions
 # customer-intent: As a DevOps engineer, I want to ingest data from an event hub into a Log Analytics workspace so that I can monitor logs that I send to Azure Event Hubs.
 ---
 
-
-# Tutorial: Ingest events from Azure Event Hubs into Azure Monitor Logs (Preview)
+# Tutorial: Ingest events from Azure Event Hubs into Azure Monitor Logs (Public Preview)
 
 [Azure Event Hubs](../../event-hubs/event-hubs-about.md) is a big data streaming platform that collects events from multiple sources to be ingested by Azure and external services. This article explains how to ingest data directly from an event hub into a Log Analytics workspace.
 
@@ -325,6 +324,7 @@ To ingest data into a [supported Azure table](../logs/logs-ingestion-api-overvie
     To: `"outputStream": "outputStream": "[concat(Microsoft-', parameters('tableName'))]"`
 
 1. In `transformKql`, [define a transformation](../essentials/data-collection-transformations-structure.md#transformation-structure) that sends the ingested data into the target columns in the destination Azure table.
+
 ## Grant the event hub permission to the data collection rule
 
 With [managed identity](../../active-directory/managed-identities-azure-resources/overview.md), you can give any event hub, or Event Hubs namespace, permission to send events to the data collection rule and data collection endpoint you created. When you grant the permissions to the Event Hubs namespace, all event hubs within the namespace inherit the permissions. 
@@ -337,16 +337,14 @@ With [managed identity](../../active-directory/managed-identities-azure-resource
 
     :::image type="content" source="media/ingest-logs-event-hub/event-hub-data-receiver-role-assignment.png" lightbox="media/ingest-logs-event-hub/event-hub-data-receiver-role-assignment.png" alt-text="Screenshot that shows the Add Role Assignment screen for the event hub with the Azure Event Hubs Data Receiver role highlighted.":::
 
-3. Select **User, group, or service principal** for **Assign access to** and click **Select members**. Select your DCR and click **Select**.
-
-    :::image type="content" source="media/ingest-logs-event-hub/event-hub-add-role-assignment-select-member.png" lightbox="media/ingest-logs-event-hub/event-hub-add-role-assignment-select-member.png" alt-text="Screenshot that shows the Members tab of the Add Role Assignment screen.":::
+1. Select **Managed identity** for **Assign access to** and click **Select members**. Select **Data collection rule**,  search your DCR by name and click **Select**.
 
+[ ![Screenshot of how to assign access to managed identity.](media/ingest-logs-event-hub/assign-access-to-managed-identity.png) ](media/ingest-logs-event-hub/assign-access-to-managed-identity.png#lightbox)
 
 4. Select **Review + assign** and verify the details before saving your role assignment.
 
     :::image type="content" source="media/ingest-logs-event-hub/event-hub-add-role-assignment-save.png" lightbox="media/ingest-logs-event-hub/event-hub-add-role-assignment-save.png" alt-text="Screenshot that shows the Review and Assign tab of the Add Role Assignment screen.":::
 
-
 ## Associate the data collection rule with the event hub
 
 The final step is to associate the data collection rule to the event hub from which you want to collect events. 
@@ -414,7 +412,6 @@ To create a data collection rule association in the Azure portal:
 
 1. Select **Review + create** and then **Create** when you review the details.
 
-
 ## Check your destination table for ingested events
 
 Now that you've associated the data collection rule with your event hub, Azure Monitor Logs will ingest all existing events whose [retention period](/azure/event-hubs/event-hubs-features#event-retention) hasn't expired and all new events.
@@ -429,9 +426,8 @@ To check your destination table for ingested events:
     ``` 
 
     You should see events from your event hub.
-`
-    :::image type="content" source="media/ingest-logs-event-hub/log-analytics-query-results-with-events.png" lightbox="media/ingest-logs-event-hub/log-analytics-query-results-with-events.png" alt-text="Screenshot showing the results of a simple query on a custom table. The results consist of events ingested from an event hub.":::
 
+:::image type="content" source="media/ingest-logs-event-hub/log-analytics-query-results-with-events.png" lightbox="media/ingest-logs-event-hub/log-analytics-query-results-with-events.png" alt-text="Screenshot showing the results of a simple query on a custom table. The results consist of events ingested from an event hub.":::
 ## Clean up resources
 
 In this tutorial, you created the following resources:
@@ -457,3 +453,5 @@ Learn more about to:
 - [Create a custom table](../logs/create-custom-table.md#create-a-custom-table).
 - [Create a data collection endpoint](../essentials/data-collection-endpoint-overview.md#create-a-data-collection-endpoint).
 - [Update an existing data collection rule](../essentials/data-collection-rule-edit.md).
+
+