Azure Event Grid - Freshness 2

Author: spelluru

articles/event-grid/consume-private-endpoints.md

@@ -1,21 +1,23 @@
 ---
-title: Deliver events using private link service
-description: This article describes how to work around push delivery's limitation to deliver events using private link service.
+title: Secure Event Delivery with Private Links
+description: Private link event delivery in Azure Event Grid supports pull delivery but not push delivery. Learn how to configure private endpoints and explore secure alternatives.
+#customer intent: As a solutions architect, I want to know if Azure Event Grid push delivery supports private link so that I can determine the right event delivery approach for my secure network environment.
 ms.topic: how-to
-ms.date: 12/16/2024
+ms.date: 03/27/2026
+author: spelluru
+ms.author: spelluru
+ms.reviewer: spelluru
 # Customer intent: I would like to know if delivering events using private link service is supported in the Push model.
-ms.custom:
-  - build-2025
 ---
 
 # Deliver events securely over a private link
 This article describes how Azure Event Grid supports delivering events over a private link.
 
 ## Pull delivery
-**Pull** delivery supports consuming events using private links. Pull delivery is a feature of Event Grid namespaces. Once you add a private endpoint connection to a namespace, your consumer application can connect to Event Grid on a private endpoint to receive events. For more information, see [configure private endpoints for namespaces](configure-private-endpoints-pull.md) and [pull delivery overview](pull-delivery-overview.md).
+**Pull** delivery supports consuming events by using private links. Pull delivery is a feature of Event Grid namespaces. When you add a private endpoint connection to a namespace, your consumer application can connect to Event Grid on a private endpoint to receive events. For more information, see [configure private endpoints for namespaces](configure-private-endpoints-pull.md) and [pull delivery overview](pull-delivery-overview.md).
 
 ## Push delivery
-With **push** delivery isn't possible to deliver events using [private endpoints](../private-link/private-endpoint-overview.md). That is, with push delivery, either in Event Grid basic or Event Grid namespaces, your application can't receive events over private IP space. However, there's a secure alternative using managed identities with public endpoints. Use the link in the next section to navigate to the article that shows how to use managed identities to deliver events. 
+With **push** delivery, you can't deliver events by using [private endpoints](../private-link/private-endpoint-overview.md). That is, with push delivery, either in Event Grid basic or Event Grid namespaces, your application can't receive events over private IP space. However, there's a secure alternative that uses managed identities with public endpoints. Use the link in the next section to go to the article that shows how to use managed identities to deliver events. 
 
 ## Related content
-For more information about delivering events using a managed identity, see [Deliver events securely using managed identities](deliver-events-using-managed-identity.md).
+For more information about delivering events by using a managed identity, see [Deliver events securely using managed identities](deliver-events-using-managed-identity.md).

articles/event-grid/handler-webhooks.md

@@ -1,38 +1,42 @@
 ---
-title: Webhooks as event handlers for Azure Event Grid events
-description: Learn how to use webhooks as event handlers for Azure Event Grid events. Azure Automation runbooks and logic apps are supported as event handlers via webhooks. 
+title: Webhook Event Handlers for Azure Event Grid
+description: Learn how to use webhooks as event handlers for Azure Event Grid events. Azure Automation runbooks and logic apps are supported as event handlers via webhooks.
+#customer intent: As a developer, I want to configure a webhook as an event handler for Azure Event Grid so that I can process events at my own HTTP endpoint.
 ms.topic: concept-article
-ms.date: 02/12/2025
+ms.date: 03/27/2026
+author: spelluru
+ms.author: spelluru
+ms.reviewer: spelluru
 # Customer intent: As a developer or architect, I want to learn how to use Webhooks, Logic Apps, and Azure Automation runbooks as events handlers for Azure Event Grid events.
 ---
 
-# Webhooks, Automation runbooks, Logic Apps as event handlers for Azure Event Grid events
-An event handler receives events from an event source via Event Grid, and processes those events. You can use any WebHook as an event handler for events forwarded by Event Grid. The WebHook doesn't need to be hosted in Azure to handle events. Event Grid supports only HTTPS Webhook endpoints. You can also use an Azure Automation workbook or an Azure logic app as an event handler via webhooks. This article provides you links to conceptual, quickstart, and tutorial articles that provide you with more information. 
+# Webhooks, Automation runbooks, and Logic Apps as event handlers for Azure Event Grid events
+An event handler receives events from an event source through Event Grid and processes those events. You can use any webhook as an event handler for events that Event Grid forwards. The webhook doesn't need to be hosted in Azure to handle events. Event Grid supports only HTTPS webhook endpoints. You can also use an Azure Automation runbook or an Azure Logic App as an event handler through webhooks. This article provides links to conceptual, quickstart, and tutorial articles that give you more information. 
 
 > [!NOTE]
 > Even though you can use **Webhook** as an **endpoint type** to configure an Azure function as an event handler, use **Azure Function** as an endpoint type. For more information, see [Azure function as an event handler](handler-functions.md).
 
 ## Webhooks
-See the following articles for an overview and examples of using webhooks as event handlers. 
+For an overview and examples of using webhooks as event handlers, see the following articles. 
 
 |Title  |Description  |
 |---------|---------|
-| Quickstart: create and route custom events with - [Azure CLI](custom-event-quickstart.md), [PowerShell](custom-event-quickstart-powershell.md), and [portal](custom-event-quickstart-portal.md). | Shows how to send custom events to a WebHook. |
-| Quickstart: route Blob storage events to a custom web endpoint with - [Azure CLI](../storage/blobs/storage-blob-event-quickstart.md?toc=%2fazure%2fevent-grid%2ftoc.json), [PowerShell](../storage/blobs/storage-blob-event-quickstart-powershell.md?toc=%2fazure%2fevent-grid%2ftoc.json), and [portal](blob-event-quickstart-portal.md). | Shows how to send blob storage events to a WebHook. |
+| Quickstart: create and route custom events with - [Azure CLI](custom-event-quickstart.md), [PowerShell](custom-event-quickstart-powershell.md), and [portal](custom-event-quickstart-portal.md). | Shows how to send custom events to a webhook. |
+| Quickstart: route Blob storage events to a custom web endpoint with - [Azure CLI](../storage/blobs/storage-blob-event-quickstart.md?toc=%2fazure%2fevent-grid%2ftoc.json), [PowerShell](../storage/blobs/storage-blob-event-quickstart-powershell.md?toc=%2fazure%2fevent-grid%2ftoc.json), and [portal](blob-event-quickstart-portal.md). | Shows how to send blob storage events to a webhook. |
 | [Quickstart: send container registry events](/azure/container-registry/container-registry-event-grid-quickstart?toc=%2fazure%2fevent-grid%2ftoc.json) | Shows how to use Azure CLI to send Container Registry events. |
 | [Overview: receive events to an HTTP endpoint](receive-events.md) | Describes how to validate an HTTP endpoint to receive events from an event subscription, and receive and deserialize events. |
 
 
 ## Azure Automation
-You can process events by using Azure Automation runbooks. Processing of events by using automated runbooks is supported via webhooks. You create a webhook for the runbook and then use the webhook handler. See the following tutorial for an example: 
+You can process events by using Azure Automation runbooks. Event Grid supports processing of events by using automated runbooks through webhooks. You create a webhook for the runbook and then use the webhook handler. For an example, see the following tutorial: 
 
 |Title  |Description  |
 |---------|---------|
 |[Tutorial: Azure Automation with Event Grid and Microsoft Teams](ensure-tags-exists-on-new-virtual-machines.md) |Create a virtual machine, which sends an event. The event triggers an Automation runbook that tags the virtual machine, and triggers a message that is sent to a Microsoft Teams channel. |
 
 
 ## Logic Apps
-Use **Logic Apps** to implement business processes to process Event Grid events. You don't create a webhook explicitly in this scenario. The webhook is created for you automatically when you configure the logic app to handle events from Event Grid. See the following tutorials for examples: 
+Use **Logic Apps** to implement business processes that process Event Grid events. You don't create a webhook explicitly in this scenario. When you configure the logic app to handle events from Event Grid, the webhook is created automatically. For examples, see the following tutorials: 
 
 |Title  |Description  |
 |---------|---------|