You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/communication-services/concepts/service-limits.md
+44-18Lines changed: 44 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -101,31 +101,57 @@ For more information on the SMS SDK and service, see [SMS SDK overview](./sms/sd
101
101
102
102
## Email
103
103
104
-
You can send a limited number of email messages. If you exceed the following limits for your subscription, your requests are rejected. You can attempt these requests again, after the `Retry-After` time passes. Take action before you reach the limit. Request to raise your sending volume limits, if needed.
104
+
You can send a limited number of email messages. If you exceed the [email rate limits](#rate-limits-for-email) for your subscription, your requests are rejected. You can attempt these requests again, after the Retry-After time passes. Take action before reaching the limit by requesting to raise your sending volume limits if needed.
105
105
106
-
The Azure Communication Services email service is designed to support high throughput. 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 that you use Azure Communication Services email over a period of two to four weeks to gradually increase your email volume. During this time, closely monitor the delivery status of your emails. This gradual increase enables third-party email service providers to adapt to the change in IP for your domain's email traffic. The gradual change gives you time to protect your sender reputation and maintain the reliability of your email delivery.
106
+
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.
107
107
108
-
### Rate limits for email
108
+
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. This gradual increase enables third-party email service providers to adapt to the change in IP for your domain's email traffic. The gradual change gives you time to protect your sender reputation and maintain the reliability of your email delivery.
109
109
110
-
We approve higher limits for customers based on use case requirements, domain reputation, traffic patterns, and failure rates. To request higher limits, follow the instructions at [Quota increase for email domains](./email/email-quota-increase.md). Higher quotas are available only for verified custom domains, not Azure managed domains.
110
+
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:
111
+
- Customer peak traffic
112
+
- Business needs
113
+
- Ability to manage failure rates
114
+
- Domain reputation
111
115
112
-
The following table lists limits for [Custom domains](../quickstarts/email/add-custom-verified-domains.md).
116
+
### Failure Rate Requirements
113
117
114
-
| Operation | Scope | Time frame (minutes) | Limit (number of emails) |
To enable a high email quota, your email failure rate must be less than one percent (1%). If your failure rate is high, you must resolve the issues before requesting a quota increase.
119
+
Customers are expected to actively monitor their failure rates.
120
+
121
+
If the failure rate increases after a quota increase, Azure Communication Services will contact the customer for immediate action and a resolution timeline. In extreme cases, if the failure rate isn't managed within the specified timeline, Azure Communication Services may reduce or suspend service until the issue is resolved.
122
+
123
+
#### Related articles
124
+
125
+
Azure Communication Services provides rich logs and analytics to help monitor and manage failure rates. For more information, see the following articles:
126
+
127
+
-[Improve sender reputation in Azure Communication Services email](./email/sender-reputation-managed-suppression-list.md)
-[Quickstart: Manage domain suppression lists in Azure Communication Services using the management client libraries](../quickstarts/email/manage-suppression-list-management-sdks.md)
132
+
133
+
> [!NOTE]
134
+
> To request higher limits, follow the instructions at [Quota increase for email domains](./email/email-quota-increase.md). Higher quotas are only available for verified custom domains, not Azure-managed domains.
@@ -43,6 +43,9 @@ Before provisioning an Azure Managed Domain, review the following table to decid
43
43
|**Pros:**| - Setup is quick & easy<br/>- No domain verification required<br /> | - Emails are sent from your own domain |
44
44
|**Cons:**| - Sender domain is not personalized and cannot be changed<br/>- Sender usernames can't be personalized<br/>- Very limited sending volume<br />- User Engagement Tracking can't be enabled <br /> | - Requires verification of domain records <br /> - Longer setup for verification |
45
45
46
+
### Service limits
47
+
48
+
Both Azure managed domains and Custom domains are subject to service limits. Service limits include failure, rate, and size limits. For more informations, see [Service limits for Azure Communication Services > Email](../../concepts/service-limits.md#email).
46
49
47
50
## Sender authentication for Azure Managed Domain
48
51
@@ -58,5 +61,6 @@ Azure Communication Services automatically configures the required email authent
58
61
59
62
## Related articles
60
63
61
-
* Familiarize yourself with the [Email client library](../../concepts/email/sdk-features.md)
62
-
* Learn how to send emails with custom verified domains in [Quickstart: How to add custom verified email domains](../../quickstarts/email/add-custom-verified-domains.md)
64
+
* Familiarize yourself with the [Email client library](../../concepts/email/sdk-features.md).
65
+
* Review email failure limits, rate limits, and size limits in [Service limits for Azure Communication Services > Email](../../concepts/service-limits.md#email).
66
+
* Learn how to send emails with custom verified domains in [Quickstart: How to add custom verified email domains](../../quickstarts/email/add-custom-verified-domains.md).
Copy file name to clipboardExpand all lines: articles/communication-services/quickstarts/email/add-custom-verified-domains.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,6 +42,10 @@ Before provisioning a custom email domain, review the following table to decide
42
42
|**Pros:**| - Setup is quick & easy<br/>- No domain verification required<br /> | - Emails are sent from your own domain |
43
43
|**Cons:**| - Sender domain isn't personalized and can't be changed<br/>- Sender usernames can't be personalized<br/>- Limited sending volume<br />- User Engagement Tracking can't be enabled<br /> | - Requires verification of domain records<br /> - Longer setup for verification |
44
44
45
+
### Service limits
46
+
47
+
Both Azure managed domains and Custom domains are subject to service limits. Service limits include failure, rate, and size limits. For more informations, see [Service limits for Azure Communication Services > Email](../../concepts/service-limits.md#email).
48
+
45
49
## Change MailFrom and FROM display names for custom domains
46
50
47
51
You can optionally configure your `MailFrom` address to be something other than the default `DoNotReply` and add more than one sender username to your domain. For more information about how to configure your sender address, see [Quickstart: How to add multiple sender addresses](add-multiple-senders.md).
@@ -96,3 +100,5 @@ The following links provide more information about how to add a CNAME record usi
96
100
## Related articles
97
101
98
102
* Familiarize yourself with the [Email client library](../../concepts/email/sdk-features.md)
103
+
* Review email failure limits, rate limits, and size limits in [Service limits for Azure Communication Services > Email](../../concepts/service-limits.md#email).
104
+
* Learn how to send emails with Azure Managed Domains in [Quickstart: How to add Azure Managed Domains to Email Communication Service](../../quickstarts/email/add-azure-managed-domains.md).
0 commit comments