You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/event-grid/communication-services-email-events.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,18 +1,20 @@
1
1
---
2
2
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.
4
5
ms.topic: concept-article
5
-
ms.date: 01/21/2025
6
+
ms.date: 03/27/2026
6
7
author: anmolbohra97
7
8
ms.author: anmolbohra
9
+
ms.reviewer: spelluru
8
10
# Customer intent: I want to learn about what email events from Azure Communication Servics are supported through Azure Event Grid.
9
11
---
10
12
11
13
# Azure Communication Services - Email events
12
14
13
15
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).
14
16
15
-
## Events types
17
+
## Event types
16
18
17
19
Azure Communication Services emits the following telephony and Short Message Service (SMS) event types:
18
20
@@ -25,7 +27,7 @@ Azure Communication Services emits the following telephony and Short Message Ser
25
27
26
28
When an event is triggered, the Event Grid service sends data about that event to subscribing endpoints.
27
29
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.
@@ -54,7 +56,7 @@ This section contains an example of what that data would look like for each even
54
56
> [!NOTE]
55
57
> Possible values for `Status` are:
56
58
> -`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.
58
60
> -`Bounced`: The email hard bounced, which might happen because the email address doesn't exist or the domain is invalid.
59
61
> -`Quarantined`: The message was quarantined (as spam, bulk mail, or phishing).
60
62
> -`FilteredSpam`: The message was identified as spam, and was rejected or blocked (not quarantined).
0 commit comments