Skip to content

Commit e8e4e75

Browse files
committed
Communication Services - Events
1 parent f234d8b commit e8e4e75

1 file changed

Lines changed: 7 additions & 5 deletions

File tree

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

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,20 @@
11
---
22
title: Azure Communication Services - Email events
3-
description: This article describes how to use Azure Communication Services as an Event Grid event source for Email Events.
3+
description: Azure Communication Services email events integrate with Event Grid for delivery and engagement tracking. Learn about supported event types, schemas, and responses.
4+
#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.
45
ms.topic: concept-article
5-
ms.date: 01/21/2025
6+
ms.date: 03/27/2026
67
author: anmolbohra97
78
ms.author: anmolbohra
9+
ms.reviewer: spelluru
810
# Customer intent: I want to learn about what email events from Azure Communication Servics are supported through Azure Event Grid.
911
---
1012

1113
# Azure Communication Services - Email events
1214

1315
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).
1416

15-
## Events types
17+
## Event types
1618

1719
Azure Communication Services emits the following telephony and Short Message Service (SMS) event types:
1820

@@ -25,7 +27,7 @@ Azure Communication Services emits the following telephony and Short Message Ser
2527

2628
When an event is triggered, the Event Grid service sends data about that event to subscribing endpoints.
2729

28-
This section contains an example of what that data would look like for each event.
30+
This section contains an example of what that data looks like for each event.
2931

3032
### Microsoft.Communication.EmailDeliveryReportReceived event
3133

@@ -54,7 +56,7 @@ This section contains an example of what that data would look like for each even
5456
> [!NOTE]
5557
> Possible values for `Status` are:
5658
> - `Delivered`: The message was successfully handed over to the intended destination (recipient Mail Transfer Agent).
57-
> - `Suppressed`: The recipient email had hard bounced previously, and all subsequent emails to this recipient are being temporarily suppressed as a result.
59+
> - `Suppressed`: The recipient email previously hard bounced, so all subsequent emails to this recipient are temporarily suppressed.
5860
> - `Bounced`: The email hard bounced, which might happen because the email address doesn't exist or the domain is invalid.
5961
> - `Quarantined`: The message was quarantined (as spam, bulk mail, or phishing).
6062
> - `FilteredSpam`: The message was identified as spam, and was rejected or blocked (not quarantined).

0 commit comments

Comments
 (0)