search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.09k stars 21.14k forks source link

Need Clarification on Azure Communication Services Email Limits API Throttling and Timeouts #122097

Open makwanam opened 2 months ago

makwanam commented 2 months ago

Hello Team,

Need clarification on the ACS email service limits, (when used with SDK vs when used with SMTP client) This service limits page states the send email limits (for my use case, i am using custom domain and it falls into the 100 emails per hour category, which i find it very low for production use case scenarios since i am trying to setup email notifications using the ACS).

Now, I saw that there are two ways the ACS can be used to send email, first one is use the SDK - I am seeing the same limits stated on this page - Email client library overview for Azure Communication Services https://learn.microsoft.com/en-us/azure/communication-services/concepts/email/sdk-features#api-throttling-and-timeouts As per above page, this limit is applied when using the Azure Communication Email SDK (in C#) - How to send an email using Azure Communication Services

Second one here is to use the SMTP client with ACS, Does the same limit apply when using the Email SMTP support in Azure Communication Services? Also, the email smtp overview page mentions High-volume sending support for B2C communications.? What does that mean? Does it mean it supports sending emails in large quantities? (is it more than 100 per hour? if yes then what is the limit when ACS is used via SMTP client?) The page that shows ACS usage with SMTP client - Send email with SMTP

Basically, using the ACS email SDK vs using the ACS via SMTP client, is there is difference with how limits are applied with either of those? or do they both fall under same sending limit capacity since they use the ACS service internally?

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

PesalaPavan commented 2 months ago

@makwanam Thanks for your feedback! We will investigate and update as appropriate.

bashan-git commented 2 months ago

Hello @makwanam , Both SDKs and SMTP have the same mechanism for enforcing the service limits and you can request for additional quota as stated in the document.

makwanam commented 2 months ago

Hi @bashan-git, thanks for the clarification.

Still not clear on what it actually means by High-volume sending support for B2C communications. on this page - https://learn.microsoft.com/en-us/azure/communication-services/concepts/email/email-smtp-overview#key-principles

Few more questions, How is this service limit managed or who manages them? Which team handles or have control over them? How long does it take to increase the ACS email send limit capacity? (Is there a maximum limit? something like 1000 or 10000 emails per hour) Once we send in a request to increase the limit, What is the increment number that can be asked for? (for e.g., it starts with 100 emails per hour for custom domain. if I were to make a request to increase that quota, do I get to decide number or does the team who controls that number make the decision here?) How much time does it take for the review and approval process before the new quota is available to use?

makwanam commented 2 months ago

Hello Team,

Can someone help answer the questions I left in my above comment? Also, is Azure Communication Service the way to go for notifications purposes? For now, we just want to use the ACS to send out email notifications. Note - We are trying to implement email notifications within a customer facing project. The ACS aligns pretty well within the project setup since. The only issue is the limits since the amount of notifications will easily outgrow the email sending limit of ACS.

Feel free to add any other suggestions if there are other or better alternatives for sending email notifications!