Merge pull request #300109 from spelluru/egridupdates0519

Freshness review - top 50 - June expiry

Author: prmerger-automator[bot]

articles/event-grid/system-topics.md

@@ -2,12 +2,11 @@
 title: System topics in Azure Event Grid
 description: Describes system topics in Azure Event Grid. 
 ms.topic: conceptual
-ms.custom: build-2023
-ms.date: 06/14/2024
+ms.date: 05/20/2025
 ---
 
 # System topics in Azure Event Grid
-A system topic in Event Grid represents one or more **events published by Azure services** such as Azure Storage and Azure Event Hubs. For example, a system topic may represent **all blob events** or only **blob created** and **blob deleted** events published for a **specific storage account**. In this example, when a blob is uploaded to the storage account, the Azure Storage service publishes a **blob created** event to the system topic in Event Grid, which then forwards the event to topic's [subscribers](event-handlers.md) that receive and process the event. 
+A system topic in Event Grid represents one or more **events published by Azure services** such as Azure Storage and Azure Event Hubs. For example, a system topic can represent **all blob events** or only **blob created** and **blob deleted** events published for a **specific storage account**. In this example, when a blob is uploaded to the storage account, the Azure Storage service publishes a **blob created** event to the system topic in Event Grid, which then forwards the event to topic's [subscribers](event-handlers.md) that receive and process the event. 
 
 > [!NOTE] 
 > Only Azure services can publish events to system topics. Therefore, you don't get an endpoint or access keys that you can use to publish events like you do for [custom topics](custom-topics.md) or [event domains](event-domains.md).
@@ -45,7 +44,7 @@ When you use [CLI](create-view-manage-system-topics-cli.md), [REST](/rest/api/ev
 > We recommend that you create a system topic first and then create a subscription on the topic, as it's the latest way of creating system topics.
 
 ### Failure to create system topics
-The system topic creation fails if you have set up Azure policies in such a way that the Event Grid service can't create it. For example, you may have a policy that allows creation of only certain types of resources (for example: Azure Storage, Azure Event Hubs, and so on.) in the subscription. 
+The system topic creation fails if you set up Azure policies in such a way that the Event Grid service can't create it. For example, you can have a policy that allows creation of only certain types of resources (for example: Azure Storage, Azure Event Hubs, and so on) in the subscription. 
 
 In such cases, event flow functionality is preserved. However, metrics and diagnostic functionalities of system topics are unavailable.
 

articles/event-hubs/event-hubs-capture-overview.md

@@ -1,8 +1,8 @@
 ---
-title: Capture streaming events
+title: Capture Streaming Events
 description: This article provides an overview of the Capture feature that allows you to capture events streaming through Azure Event Hubs. 
 ms.topic: concept-article
-ms.date: 06/25/2024
+ms.date: 05/20/2025
 #customer intent: As a developer, I want to know how capture events flowing through an event hub in an Azure Blob Storage or an Azure Data Lake Storage. 
 ---
 
@@ -11,15 +11,12 @@ Azure Event Hubs enables you to automatically capture the data streaming through
 
 :::image type="content" source="./media/event-hubs-features/capture.png" alt-text="Image showing capturing of Event Hubs data into Azure Storage or Azure Data Lake Storage":::
 
-> [!NOTE]
-> Configuring Event Hubs Capture to use Azure Data Lake Storage **Gen 2** is same as configuring it to use an Azure Blob Storage. For details, see [Configure Event Hubs Capture](event-hubs-capture-enable-through-portal.md). 
-
 Event Hubs Capture enables you to process real-time and batch-based pipelines on the same stream. This means you can build solutions that grow with your needs over time. Whether you're building batch-based systems today with an eye towards future real-time processing, or you want to add an efficient cold path to an existing real-time solution, Event Hubs Capture makes working with streaming data easier.
 
-> [!IMPORTANT]
-> - The destination storage (Azure Storage or Azure Data Lake Storage) account  must be in the same subscription as the event hub when not using managed identity for authentication.
-> - Event Hubs doesn't support capturing events in a premium storage account.
-> - Event Hubs Capture supports any non-premium Azure storage account with support for block blobs.
+## Important points to consider
+- The destination storage (Azure Storage or Azure Data Lake Storage) account must be in the same subscription as the event hub when not using managed identity for authentication.
+- Event Hubs doesn't support capturing events in a premium storage account.
+- Event Hubs Capture supports any non-premium Azure storage account with support for block blobs.
 
 ## How Event Hubs Capture works
 
@@ -30,7 +27,10 @@ Event Hubs Capture enables you to specify your own Azure Blob storage account an
 Captured data is written in [Apache Avro][Apache Avro] format: a compact, fast, binary format that provides rich data structures with inline schema. This format is widely used in the Hadoop ecosystem, Stream Analytics, and Azure Data Factory. More information about working with Avro is available later in this article.
 
 > [!NOTE]
-> When you use no code editor in the Azure portal, you can capture streaming data in Event Hubs in an Azure Data Lake Storage Gen2 account in the **Parquet** format. For more information, see [How to: capture data from Event Hubs in Parquet format](../stream-analytics/capture-event-hub-data-parquet.md?toc=%2Fazure%2Fevent-hubs%2Ftoc.json) and [Tutorial: capture Event Hubs data in Parquet format and analyze with Azure Synapse Analytics](../stream-analytics/event-hubs-parquet-capture-tutorial.md?toc=%2Fazure%2Fevent-hubs%2Ftoc.json).
+> - When you use no code editor in the Azure portal, you can capture streaming data in Event Hubs in an Azure Data Lake Storage Gen2 account in the **Parquet** format. For more information, see [How to: capture data from Event Hubs in Parquet format](../stream-analytics/capture-event-hub-data-parquet.md?toc=%2Fazure%2Fevent-hubs%2Ftoc.json) and [Tutorial: capture Event Hubs data in Parquet format and analyze with Azure Synapse Analytics](../stream-analytics/event-hubs-parquet-capture-tutorial.md?toc=%2Fazure%2Fevent-hubs%2Ftoc.json).
+> - Configuring Event Hubs Capture to use Azure Data Lake Storage **Gen 2** is same as configuring it to use an Azure Blob Storage. For details, see [Configure Event Hubs Capture](event-hubs-capture-enable-through-portal.md). 
+
+
 
 ### Capture windowing
 

articles/event-hubs/monitor-event-hubs.md

@@ -1,7 +1,7 @@
 ---
 title: Monitor Azure Event Hubs
 description: Learn how to use Azure Monitor to view, analyze, and create alerts on metrics from Azure Event Hubs. 
-ms.date: 06/20/2024
+ms.date: 05/20/2025
 ms.custom: horz-monitor, subject-monitoring
 ms.topic: conceptual
 ---
@@ -44,7 +44,7 @@ For more information about the resource types for Event Hubs, see [Azure Event H
 > Enabling these settings requires additional Azure services: storage account, event hub, or Log Analytics. These services might increase your cost. To calculate an estimated cost, visit the [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator).
 
 > [!NOTE]
-> When you enable metrics in a diagnostic setting, dimension information is not currently included as part of the information sent to a storage account, event hub, or log analytics.
+> When you enable metrics in a diagnostic setting, dimension information isn't currently included as part of the information sent to a storage account, event hub, or log analytics.
 
 [!INCLUDE [horz-monitor-platform-metrics](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-platform-metrics.md)]
 
@@ -81,7 +81,7 @@ For the available resource log categories, their associated Log Analytics tables
 Using Azure Monitor Log Analytics requires you to create a diagnostic configuration and enable **Send information to Log Analytics**. For more information, see the [Metrics](#azure-monitor-platform-metrics) section. Data in Azure Monitor Logs is stored in tables, with each table having its own set of unique properties. Azure Event Hubs has the capability to dispatch logs to either of two destination tables: Azure Diagnostic or Resource specific tables in Log Analytics. For a detailed reference of the logs and metrics, see [Azure Event Hubs monitoring data reference](monitor-event-hubs-reference.md).
 
 > [!IMPORTANT]
-> When you select **Logs** from the Azure Event Hubs menu, Log Analytics is opened with the query scope set to the current workspace. This means that log queries will only include data from that resource. If you want to run a query that includes data from other databases or data from other Azure services, select **Logs** from the **Azure Monitor** menu. See [Log query scope and time range in Azure Monitor Log Analytics](/azure/azure-monitor/logs/scope) for details.
+> When you select **Logs** from the Azure Event Hubs menu, Log Analytics is opened with the query scope set to the current workspace. It means that log queries include only data from that resource. If you want to run a query that includes data from other databases or data from other Azure services, select **Logs** from the **Azure Monitor** menu. See [Log query scope and time range in Azure Monitor Log Analytics](/azure/azure-monitor/logs/scope) for details.
 
 ### Use runtime logs
 
@@ -255,9 +255,9 @@ The following table lists some suggested alert rules for Event Hubs. These alert
 
 | Alert type | Condition | Description  |
 |:---|:---|:---|
-| Metric | CPU              | When CPU utilization exceeds a set value.       |
-| Metric | Available Memory | When Available Memory drops below a set value. |
-| Metric | Capture Backlog  | When Capture Backlog is above a certain value. |
+| Metric | CPU              | When CPU utilization exceeds a set value       |
+| Metric | Available Memory | When Available Memory drops below a set value |
+| Metric | Capture Backlog  | When Capture Backlog is above a certain value |
 
 [!INCLUDE [horz-monitor-advisor-recommendations](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-advisor-recommendations.md)]