Article
Service limits for Azure Communication Services
learn.microsoft.com
Quoted on this wiki
Every place a page here uses this source, in the order the words come in it.
Custom Domains “Send Email Per Subscription 1 30 Yes” The following table lists limits for Azure managed domains.
Custom Domains “Send Email Per Subscription 60 100 Yes” The following table lists limits for Azure managed domains.
The following table lists limits for Azure managed domains. “Send Email Per Subscription 60 10 No” Size limits for email
Email “Take action before reaching the limit by requesting to raise your sending volume limits if needed.” The Azure Communication Services email service is designed to support high throughput. However, the service imposes initial rate limits to help customers onboard smoothly and avoid some of the issues that can occur when switching to a new email service.
The Azure Communication Services email service is designed to support high throughput. However, the service imposes initial rate limits to help customers onboard smoothly and avoid some of the issues that can occur when switching to a new email service. “This gradual increase enables third-party email service providers to adapt to the change in IP for your domain's email traffic.” Azure Communication Services email service supports high volume up to 1-2 million messages per hour. High throughput can be enabled based on several factors, including:
The Azure Communication Services email service is designed to support high throughput. However, the service imposes initial rate limits to help customers onboard smoothly and avoid some of the issues that can occur when switching to a new email service. “The gradual change gives you time to protect your sender reputation and maintain the reliability of your email delivery.” Azure Communication Services email service supports high volume up to 1-2 million messages per hour. High throughput can be enabled based on several factors, including:
The Azure Communication Services email service is designed to support high throughput. However, the service imposes initial rate limits to help customers onboard smoothly and avoid some of the issues that can occur when switching to a new email service. “We recommend gradually increasing your email volume using Azure Communication Services Email over a period of two to four weeks, while closely monitoring the delivery status of your emails.” Azure Communication Services email service supports high volume up to 1-2 million messages per hour. High throughput can be enabled based on several factors, including:
The Azure Communication Services email service is designed to support high throughput. However, the service imposes initial rate limits to help customers onboard smoothly and avoid some of the issues that can occur when switching to a new email service. “The gradual change gives you time to protect your sender reputation and maintain the reliability of your email delivery.” Azure Communication Services email service supports high volume up to 1-2 million messages per hour. High throughput can be enabled based on several factors, including:
When you reach service limitations, you receive an HTTP status code 429 (too many requests). In general, follow these best practices for throttling: “Reduce the number of operations per request.” Reduce the frequency of calls.
Reduce the number of operations per request. “Reduce the frequency of calls.” Avoid immediate retries because all requests accrue against your usage limits.
Reduce the frequency of calls. “Avoid immediate retries because all requests accrue against your usage limits.” Find more general guidance on how to set up your service architecture to handle throttling and limitations in the Azure architecture documentation for throttling patterns. To increase throttling limits, make a request to Azure Support.
Avoid immediate retries because all requests accrue against your usage limits. “To increase throttling limits, make a request to Azure Support.” Open the Azure portal and sign in.