Skip to content

Commit 93a200e

Browse files
Merge pull request #289809 from vac0224/vc-service-limit-links-2024-11-15
ASK MODE: Email service limit links
2 parents 16f9a6f + 3aef0e2 commit 93a200e

File tree

3 files changed

+57
-21
lines changed

3 files changed

+57
-21
lines changed

articles/communication-services/concepts/service-limits.md

Lines changed: 44 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -101,31 +101,57 @@ For more information on the SMS SDK and service, see [SMS SDK overview](./sms/sd
101101

102102
## Email
103103

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.
105105

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.
107107

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.
109109

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
111115

112-
The following table lists limits for [Custom domains](../quickstarts/email/add-custom-verified-domains.md).
116+
### Failure Rate Requirements
113117

114-
| Operation | Scope | Time frame (minutes) | Limit (number of emails) |
115-
|---------|-----|-------------|-------------------|
116-
|Send email|Per subscription|1|30|
117-
|Send email|Per subscription|60|100|
118-
|Get email status|Per subscription|1|60|
119-
|Get email status|Per subscription|60|200|
118+
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)
128+
- [Email Insights](./analytics/insights/email-insights.md)
129+
- [Enable logs via Diagnostic Settings in Azure Monitor](./analytics/enable-logging.md)
130+
- [Quickstart: Handle Email events](../quickstarts/email/handle-email-events.md)
131+
- [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.
135+
136+
### Rate Limits for Email
137+
138+
[Custom Domains](../quickstarts/email/add-custom-verified-domains.md)
139+
140+
| Operation | Scope | Timeframe (minutes) | Limit (number of emails) | Higher limits available |
141+
| --- | --- | --- | --- | --- |
142+
| Send Email | Per Subscription | 1 | 30 | Yes |
143+
| Send Email | Per Subscription | 60 | 100 | Yes |
144+
| Get Email Status | Per Subscription | 1 | 60 | Yes |
145+
| Get Email Status | Per Subscription | 60 | 200 | Yes |
120146

121147
The following table lists limits for [Azure managed domains](../quickstarts/email/add-azure-managed-domains.md).
122148

123-
| Operation | Scope | Time frame (minutes) | Limit (number of emails) |
124-
|---------|-----|-------------|-------------------|
125-
|Send email|Per subscription|1|5|
126-
|Send email|Per subscription|60|10|
127-
|Get email status|Per subscription|1|10|
128-
|Get email status|Per subscription|60|20|
149+
| Operation | Scope | Timeframe (minutes) | Limit (number of emails) | Higher limits available |
150+
| --- | --- | --- | --- | --- |
151+
| Send Email | Per Subscription | 1 | 5 | No |
152+
| Send Email | Per Subscription | 60 | 10 | No |
153+
| Get Email Status | Per Subscription | 1 |10 | No |
154+
| Get Email Status | Per Subscription | 60 |20 | No |
129155

130156
### Size limits for email
131157

@@ -289,4 +315,4 @@ You can find more information about Microsoft Graph [throttling](/graph/throttli
289315

290316
## Related content
291317

292-
See the [help and support](../support.md) options.
318+
- [Help and support options](../support.md)

articles/communication-services/quickstarts/email/add-azure-managed-domains.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.devlang: azurecli
1616

1717
# Quickstart: How to add Azure Managed Domains to Email Communication Service
1818

19-
In this quick start, you learn how to provision the Azure Managed Domain to Email Communication Service in Azure Communication Services.
19+
This article describes how to provision an Azure Managed Domain for Email Communication Service in Azure Communication Services.
2020

2121
::: zone pivot="platform-azp"
2222
[!INCLUDE [Azure portal](./includes/create-azure-managed-domain-resource-az-portal.md)]
@@ -43,6 +43,9 @@ Before provisioning an Azure Managed Domain, review the following table to decid
4343
|**Pros:** | - Setup is quick & easy<br/>- No domain verification required<br /> | - Emails are sent from your own domain |
4444
|**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 |
4545

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).
4649

4750
## Sender authentication for Azure Managed Domain
4851

@@ -58,5 +61,6 @@ Azure Communication Services automatically configures the required email authent
5861

5962
## Related articles
6063

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).

articles/communication-services/quickstarts/email/add-custom-verified-domains.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,10 @@ Before provisioning a custom email domain, review the following table to decide
4242
|**Pros:** | - Setup is quick & easy<br/>- No domain verification required<br /> | - Emails are sent from your own domain |
4343
|**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 |
4444

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+
4549
## Change MailFrom and FROM display names for custom domains
4650

4751
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
96100
## Related articles
97101

98102
* 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

Comments
 (0)