When using Azure Logic App connector for Azure Communication Service, you no longer can have multiple email addresses in the TO parameter. That action has been deprecated. See https://learn.microsoft.com/en-us/connectors/acsemail/#send-email-(preview)---deprecated-%5bdeprecated%5d. Instead, use the additional CC and BCC parameters. See https://learn.microsoft.com/en-us/connectors/acsemail/#send-email.
Aileron Consulting LLC is a technology consulting firm. Feel free to contact us at blog@aileronconsulting.com to send any questions, comments, free pizzas, t-shirts etc.
Tuesday, March 26, 2024
Monday, March 18, 2024
Azure Email Communication Service error - "Requested message could not be located. Couldn't find a record with the messageID"
When using Azure Email Communication service, you may run into this error - "Requested message could not be located. Couldn't find a record with the messageID". This generally is not an issue. What seems to be happening is that a getstatus call is being made almost about the same time a send call is being made. The recommendation is to write your own polling logic. See https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/email/send-email-advanced/manually-poll-for-email-status?tabs=connection-string
Friday, March 8, 2024
Azure Email communication service - EmailDroppedAllRecipientsSuppressed
When using Email communication service, if you receive this error most likely a previous email to the recipient bounced back and the Email Communication Service will not send an email for another x number of hours & days. See https://learn.microsoft.com/en-us/azure/communication-services/concepts/email/sender-reputation-managed-suppression-list .
{'id':'xxxxxxxxx','status':'Failed','error':{'code':'EmailDroppedAllRecipientsSuppressed','message':'Message dropped because all recipients were suppressed','target':null,'details':null,'innererror':null}}