Merge pull request #313805 from spelluru/egridfreshness0326

Azure Event Grid - Freshness 2

Author: Stacyrch140

articles/event-grid/communication-services-email-events.md

@@ -1,18 +1,20 @@
 ---
 title: Azure Communication Services - Email events
-description: This article describes how to use Azure Communication Services as an Event Grid event source for Email Events.
+description: Azure Communication Services email events integrate with Event Grid for delivery and engagement tracking. Learn about supported event types, schemas, and responses.
+#customer intent: As a developer, I want to know which email events Azure Communication Services supports through Event Grid so that I can determine which events to subscribe to in my application.
 ms.topic: concept-article
-ms.date: 01/21/2025
+ms.date: 03/27/2026
 author: anmolbohra97
 ms.author: anmolbohra
+ms.reviewer: spelluru
 # Customer intent: I want to learn about what email events from Azure Communication Servics are supported through Azure Event Grid. 
 ---
 
 # Azure Communication Services - Email events
 
 This article provides the properties and schema for communication services email events. For an introduction to event schemas, see [Azure Event Grid event schema](event-schema.md).
 
-## Events types
+## Event types
 
 Azure Communication Services emits the following telephony and Short Message Service (SMS) event types:
 
@@ -25,7 +27,7 @@ Azure Communication Services emits the following telephony and Short Message Ser
 
 When an event is triggered, the Event Grid service sends data about that event to subscribing endpoints.
 
-This section contains an example of what that data would look like for each event.
+This section contains an example of what that data looks like for each event.
 
 ### Microsoft.Communication.EmailDeliveryReportReceived event
 
@@ -54,7 +56,7 @@ This section contains an example of what that data would look like for each even
 > [!NOTE]
 > Possible values for `Status` are:
 > - `Delivered`: The message was successfully handed over to the intended destination (recipient Mail Transfer Agent).
-> - `Suppressed`: The recipient email had hard bounced previously, and all subsequent emails to this recipient are being temporarily suppressed as a result.
+> - `Suppressed`: The recipient email previously hard bounced, so all subsequent emails to this recipient are temporarily suppressed.
 > - `Bounced`: The email hard bounced, which might happen because the email address doesn't exist or the domain is invalid.
 > - `Quarantined`: The message was quarantined (as spam, bulk mail, or phishing).
 > - `FilteredSpam`: The message was identified as spam, and was rejected or blocked (not quarantined).

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/end-point-validation-event-grid-events-schema.md

@@ -1,17 +1,20 @@
 ---
-title: Endpoint validation with Event Grid event schema
+title: Validate Webhook Endpoints with Event Grid Schema
 description: This article describes WebHook event delivery and endpoint validation when using webhooks and the Event Grid event schema.
 ms.topic: concept-article
-ms.date: 09/25/2024
+ms.date: 03/27/2026
+author: spelluru
+ms.author: spelluru
+ms.reviewer: spelluru
 ms.custom: FY25Q1-Linter
 #customer intent: As a developer, I want to know how to validate a Webhook endpoint using the Event Grid event schema.
 ---
 
 
 # Endpoint validation with Event Grid event schema
-Webhooks are one of the many ways to receive events from Azure Event Grid. When a new event is ready, Event Grid service POSTs an HTTP request to the configured endpoint with the event information in the request body.
+Webhooks are one of the many ways to receive events from Azure Event Grid. When a new event is ready, the Event Grid service POSTs an HTTP request to the configured endpoint with the event information in the request body.
 
-Like many other services that support webhooks, Event Grid requires you to prove ownership of your Webhook endpoint before it starts delivering events to that endpoint. This requirement prevents a malicious user from flooding your endpoint with events. 
+Like many other services that support webhooks, Event Grid requires you to prove ownership of your webhook endpoint before it starts delivering events to that endpoint. This requirement prevents a malicious user from flooding your endpoint with events. 
 
 ## Endpoint validation with Event Grid events
 When you use any of the following three Azure services, the Azure infrastructure automatically handles this validation:
@@ -37,16 +40,16 @@ If you're using any other type of endpoint, such as an HTTP trigger based Azure
 
 ### Validation details
 
-- At the time of event subscription creation/update, Event Grid posts a subscription validation event to the target endpoint.
-- The event contains a header value `aeg-event-type: SubscriptionValidation`.
-- The event body has the same schema as other Event Grid events.
+- When you create or update an event subscription, Event Grid sends a subscription validation event to the target endpoint.
+- The event includes a header with the value `aeg-event-type: SubscriptionValidation`.
+- The event body follows the same schema as other Event Grid events.
 - The `eventType` property of the event is `Microsoft.EventGrid.SubscriptionValidationEvent`.
-- The `data` property of the event includes a `validationCode` property with a randomly generated string. For example, `validationCode: acb13…`.
+- The `data` property of the event contains a `validationCode` property with a randomly generated string. For example, `validationCode: acb13…`.
 - The event data also includes a `validationUrl` property with a URL for manually validating the subscription.
 - The array contains only the validation event. Other events are sent in a separate request after you echo back the validation code.
-- The Event Grid data plane SDKs have classes corresponding to the subscription validation event data and subscription validation response.
+- The Event Grid data plane SDKs include classes that correspond to the subscription validation event data and subscription validation response.
 
-An example SubscriptionValidationEvent is shown in the following example:
+The following example shows a `SubscriptionValidationEvent`:
 
 ```json
 [
@@ -74,21 +77,21 @@ To prove endpoint ownership, echo back the validation code in the `validationRes
 }
 ```
 
-And, follow one of these steps: 
+Follow one of these steps: 
 
-- You must return an **HTTP 200 OK** response status code. **HTTP 202 Accepted** isn't recognized as a valid Event Grid subscription validation response. The HTTP request must complete within 30 seconds. If the operation doesn't finish within 30 seconds, then the operation will be canceled and it's reattempted after 5 seconds. If all the attempts fail, then it's treated as validation handshake error.
+- You must return an **HTTP 200 OK** response status code. **HTTP 202 Accepted** isn't recognized as a valid Event Grid subscription validation response. The HTTP request must complete within 30 seconds. If the operation doesn't finish within 30 seconds, the operation is canceled and reattempted after 5 seconds. If all the attempts fail, the operation is treated as a validation handshake error.
 
-    The fact that your application is prepared to handle and return the validation code indicates that you created the event subscription and expected to receive the event. Imagine the scenario that there's no handshake validation supported and a hacker gets to know your application URL. The hacker can create a topic and an event subscription with your application's URL, and start conducting a DoS attack to your application by sending a lot of events. The handshake validation prevents that to happen. 
+    The fact that your application is prepared to handle and return the validation code indicates that you created the event subscription and expected to receive the event. Imagine the scenario where there's no handshake validation supported and a bad actor gets to know your application URL. The bad actor can create a topic and an event subscription with your application's URL, and start conducting a DoS attack on your application by sending many events. The handshake validation prevents that to happen. 
 
-    Imagine that you already have the validation implemented in your app because you created your own event subscriptions. Even if a hacker creates an event subscription with your app URL, your correct implementation of the validation request event checks for the `aeg-subscription-name` header in the request to ascertain that it's an event subscription that you recognize. 
+    Imagine that you already have the validation implemented in your app because you created your own event subscriptions. Even if a bad actor creates an event subscription with your app URL, your correct implementation of the validation request event checks for the `aeg-subscription-name` header in the request to ascertain that it's an event subscription that you recognize. 
 
-    Even after that correct handshake implementation, a hacker can flood your app (it already validated the event subscription) by replicating a request that seems to be coming from Event Grid. To prevent that, you must secure your webhook with Microsoft Entra authentication. For more information, see [Deliver events to Microsoft Entra protected endpoints](secure-webhook-delivery.md). 
-- Or, you can manually validate the subscription by sending a GET request to the validation URL. The event subscription stays in a pending state until validated. The validation Url uses **port 553**. If your firewall rules block port 553, you need to update rules for a successful manual handshake.
+    Even after that correct handshake implementation, a bad actor can flood your app (it already validated the event subscription) by replicating a request that seems to be coming from Event Grid. To prevent that, you must secure your webhook with Microsoft Entra authentication. For more information, see [Deliver events to Microsoft Entra protected endpoints](secure-webhook-delivery.md). 
+- Or, you can manually validate the subscription by sending a GET request to the validation URL. The event subscription stays in a pending state until validated. The validation URL uses **port 553**. If your firewall rules block port 553, you need to update rules for a successful manual handshake.
 
-    In your validation of the subscription validation event, if you identify that it isn't an event subscription for which you're expecting events, you wouldn't return a 200 response or no response at all. Hence, the validation fails.    
+    In your validation of the subscription validation event, if you identify that it isn't an event subscription for which you're expecting events, don't return a 200 response or return no response at all. Hence, the validation fails.    
 
 For an example of handling the subscription validation handshake, see a [C# sample](https://github.com/Azure-Samples/event-grid-dotnet-publish-consume-events/blob/master/EventGridConsumer/EventGridConsumer/Function1.cs).
 
 
 ## Related content
-See the following article to learn how to troubleshoot event subscription validations: [Troubleshoot event subscription validations](troubleshoot-subscription-validation.md).
+To learn how to troubleshoot event subscription validations, see [Troubleshoot event subscription validations](troubleshoot-subscription-validation.md).