Does Azure Communication Services prevent failed emails from being resent?

Karan Nanda 20 Reputation points
2024-05-02T07:53:42.97+00:00

hi Team,

We're implementing ACS for our company and I'm curious if there are any mechanisms which are present to prevent a previous failed email from being resent. One use case we've encountered is that an employee has left the org. Till the time their data is completely cleaned, if the emails continue to be fired, it results in "Azure.RequestFailedException: Message dropped because all recipients were suppressed" . Also, do these count as "failed emails" which are required by azure to be approximately 1% of total emails before our account limit is increased i.e. azure requires our company to have just 1% or less failure rate till our service limit is increased and I was curious if these emails will count just once towards the rate or as many times the API is triggered.

Azure Communication Services
Azure Communication Services
An Azure communication platform for deploying applications across devices and platforms.
702 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Gowtham CP 850 Reputation points
    2024-05-02T08:27:02.3166667+00:00

    Hi @Karan Nanda

    Azure Communication Services (ACS) doesn't automatically prevent resending failed emails. However, you can build in this functionality yourself. Here's how:

    • Track email deliveries: Maintain a record of email recipients and whether they've previously failed to receive an email.
    • Check before sending: Before sending a new email, check this record for any recipient with a failed delivery attempt in the past.
    • Skip failed recipients: If a recipient has a failed delivery, skip sending them the email again until the cause of the failure is addressed.

    Now, about failed email limits: Azure monitors the failure rate of your emails. These failures count towards your account's limit, potentially impacting future email deliverability. It's unclear whether a single failed email counts once or multiple times towards this limit. To ensure you stay within compliance, check Azure's documentation for clarification on their specific calculation method.

    0 comments No comments