Why are Communication Services Email Delivery Events not being displayed in Azure Event Grid

Simon Dix 80

I have created an Azure Communication Service to handle Voice, SMS & Email messaging and the sending of all message types is working as expected. I have also wired up the delivery status reporting for both SMS and Voice but when subscribing to the Microsoft.Communication.EmailDeliveryReportReceived event I am seeing no events being written to my Event Grid - I have a webhook endpoint and this is not being hit. To use the SMSDeliveryReportReceived event I had to add the following to each SMS message - new SmsSendOptions(enableDeliveryReport: true). Is something similar needed to enable the delivery report for emails?

SnehaAgrawal-MSFT 18,366

@Simon Dix Thanks for reaching here! Could you please double check if environment was step correctly-

To set up the environment that use to generate and receive events, double check for below steps-

To view event triggers, you need to generate some events.

Azure Communication Services emits the following telephony and SMS event types:

Event type	Description

Microsoft.Communication.SMSReceived	Published when an SMS is received by a phone number associated with the Communication Service.
Microsoft.Communication.SMSDeliveryReportReceived	Published when a delivery report is received for an SMS sent by the Communication Service.

The subject field of all Communication Services events identifies the user, phone number, or entity that is targeted by the event. Common prefixes are used to allow simple Event Grid filtering.

Check- https://learn.microsoft.com/en-us/azure/event-grid/event-schema-communication-services#event-subjects

See- the following example shows a filter for all SMS messages and delivery reports sent to all 555 area code phone numbers owned by a Communication Services resource:

"filter": {
  "includedEventTypes": [
    "Microsoft.Communication.SMSReceived",
    "Microsoft.Communication.SMSDeliveryReportReceived"
  ],
  "subjectBeginsWith": "phonenumber/1555",
}

Check this document to enable email delivery report

Let us know if issue remains.

Simon Dix 80 Reputation points

2024-02-12T09:12:48.0533333+00:00

I have successfully subscribed to the Microsoft.Communication.SMSDeliveryReportReceived event and the events are triggering as expected. The issue is with the Microsoft.Communication.EmailDeliveryReportReceived event - the events are being raised but there can be a delay of up to 6 hours after the email has been received by the recipient (in this case my yahoo mail inbox). Should the Microsoft.Communication.EmailDeliveryReportReceived event be raised faster than I am currently seeing?
Craig Ryan 0 Reputation points

2024-02-28T13:53:24.6266667+00:00
It's great to hear that you've successfully set up Azure Communication Service to handle Voice, SMS, and Email messaging, and that the sending of all message types is working as expected. However, it seems like you're encountering an issue with the delivery status reporting for Email messages. To enable delivery report for emails in Azure Communication Service, you may need to specify options similar to what you did for SMS messages. Specifically, you'll need to set up the enableDeliveryReport parameter to true when sending the email message. Here's an example of how you can do this in C#:

var emailMessage = new EmailMessage { Subject = "Your subject here", Content = "Your email content here", // Add email addresses to the recipients list To = { "recipient@example.com" }, // Enable delivery report for the email Options = new SendEmailOptions(enableDeliveryReport: true) }; // Send the email message await communicationClient.SendEmailAsync(fromEmailAddress, emailMessage);

By setting enableDeliveryReport to true in the SendEmailOptions when sending the email message, you should be able to receive delivery status reports for emails. If you've already tried this approach and are still not receiving events or hitting your webhook endpoint for email delivery reports, there may be other factors at play. Double-check your webhook endpoint configuration and ensure that it's correctly set up to receive and handle delivery status events for emails. I hope this helps! If you have any further questions or need additional assistance, please feel free to ask.
Simon Dix 80 Reputation points

2024-02-29T15:57:45.88+00:00

Thanks for the reply but I cannot see any class called SendEmailOptions in the Azure.Communication.Email package (I am using version 1.01). Also, there is no Options property on the EmailMessage class.
SnehaAgrawal-MSFT 18,366 Reputation points

2024-03-01T07:45:25.6566667+00:00

@Simon Dix Reached out to you internally for deeper investigation.

1 answer

SnehaAgrawal-MSFT 18,366 Reputation points

2024-02-13T15:20:40.7966667+00:00
@Simon Dix Sure,

As an endpoint experiences delivery failures, Event Grid begins to delay the delivery and retry of events to that endpoint.

For example, if the first 10 events published to an endpoint fail, Event Grid assumes that the endpoint is experiencing issues and will delay all subsequent retries and new deliveries for some time - in some cases up to several hours. The functional purpose of delayed delivery is to protect unhealthy endpoints and the Event Grid system.

Without back-off and delay of delivery to unhealthy endpoints, Event Grid's retry policy and volume capabilities can easily overwhelm a system.

So, suggestion here is to customize the retry policy when creating an event subscription by using the following two configurations. An event is dropped if either of the limits of the retry policy is reached.

Maximum number of attempts - The value must be an integer between 1 and 30. The default value is 30.

Event time-to-live (TTL) - The value must be an integer between 1 and 1440. The default value is 1440 minutes

Let us know.
Please sign in to rate this answer.
Simon Dix 80 Reputation points

2024-02-28T12:20:10.6366667+00:00

See comment below

Simon Dix 80 Reputation points

2024-02-28T12:30:13.58+00:00

I have deployed my web app as an App Service in Azure and have tested it with both SMS and Email. The Microsoft.Communication.SMSDeliveryReportReceived event was triggered as soon as the SMS was delivered but the Microsoft.Communication.EmailDeliveryReportReceived event has not triggered. Both endpoints have been available since the App was deployed and I have re-created the event subscriptions for both events with the new Azure endpoints (and with custom retry policies). The Email endpoint has been hit but this was for the Microsoft.EventGrid.SubscriptionValidationEvent, so the endpoint is healthy. Do you have any further suggestions as a delay of several hours receiving email delivery reports is not acceptable for my organisation to use in a production scenario?

Simon Dix 80 Reputation points

2024-02-29T16:37:25.8233333+00:00

I sent an email message on 28th February at 11:46am (GMT) and the email delivery report event was received at 13:22 on 29th February. I added some logging to the webhook endpoint and it has captured the following: "Got EmailDeliveryReportReceived event data, messageId: db6eb5b3-e41a-4538-9420-2544b2314cbf, recipient: #####@yahoo.co.uk, status: Failed". It is reporting the status as Failed but the email was successfully delivered to my yahoo email account. I have also sent an email to my work email address (at 08:29 GMT today) and have yet to receive the delivery report - based on previous experience I expect it to arrive at some point in the next 12-18 hours.
Sign in to comment