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
+57-38Lines changed: 57 additions & 38 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ You can find more general guidance on how to set up your service architecture to
38
38
You can follow the documentation for [creating request to Azure Support](../../azure-portal/supportability/how-to-create-azure-support-request.md).
39
39
40
40
## Acquiring phone numbers
41
-
Before acquiring a phone number, make sure your subscription meets the [geographic and subscription](./telephony/plan-solution.md) requirements. Otherwise, you can't purchase a phone number. The below limitations apply to purchasing numbers through the [Phone Numbers SDK](./reference.md) and the [Azure portal](https://portal.azure.com/).
41
+
Before acquiring a phone number, make sure your subscription meets the [geographic and subscription](./telephony/plan-solution.md) requirements. Otherwise, you can't purchase a phone number. The following limitations apply to purchasing numbers through the [Phone Numbers SDK](./reference.md) and the [Azure portal](https://portal.azure.com/).
@@ -86,7 +86,7 @@ For more information on the SMS SDK and service, see the [SMS SDK overview](./sm
86
86
87
87
## Email
88
88
89
-
There is a limit on the number of email messages you can send for a given period of time. If you exceed the following limits on your subscription, your requests are rejected. You can attempt these requests again, when the Retry-After time has passed. You can make a request to raise the sending volume limits if needed.
89
+
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 reaching the limit by requesting to raise your sending volume limits if needed.
90
90
91
91
### Rate Limits
92
92
@@ -115,8 +115,25 @@ There is a limit on the number of email messages you can send for a given period
To email file attachments up to 30 MB, complete a [support request](../support.md).
121
+
122
+
If you need to send email file attachments larger than 30 MB, you can use this alternative solution. Store the files in an Azure Blob Storage account and include a link to the files in your email. You can secure the files with a Shared Access Signature (SAS). SAS provides secure delegated access to resources in your storage account. By using SAS, you have granular control over how clients can access your data.
123
+
124
+
Benefits of using an Azure Blob Storage account:
125
+
126
+
- You can handle large scale files.
127
+
- You can use SAS keys to precisely manage file access.
128
+
129
+
For more information, see:
130
+
131
+
-[Introduction to Azure Blob Storage](/azure/storage/blobs/storage-blobs-introduction)
132
+
-[Grant limited access to Azure Storage resources using shared access signatures (SAS)](/azure/storage/common/storage-sas-overview)
133
+
118
134
### Action to take
119
-
This sandbox setup is to help developers start building the application. Once you have established a sender reputation by sending mails, you can request to increase the sending volume limits. Submit a [support request](https://azure.microsoft.com/support/create-ticket/) to raise your desired email sending limit if you require sending a volume of messages exceeding the rate limits. Email quota increase requests aren't automatically approved. The reviewing team considers your overall sender reputation, which includes factors such as your email delivery failure rates, your domain reputation, and reports of spam and abuse when determining approval status.
135
+
136
+
To increase your email quota, follow the instructions at [Quota increase for email domains](./email/email-quota-increase.md).
120
137
121
138
> [!NOTE]
122
139
> Email quota increase requests may take up to 72 hours to be evaluated and approved, especially for requests that come in on Friday afternoon.
@@ -137,29 +154,30 @@ This sandbox setup is to help developers start building the application. Once yo
137
154
### Rate Limits
138
155
139
156
|**Operation**|**Scope**|**Limit per 10 seconds**|**Limit per minute**|
@@ -176,27 +194,28 @@ If you have strict compliance needs, we recommend that you delete chat threads u
176
194
177
195
### PSTN Call limitations
178
196
179
-
|**Name**|**Scope**|Limit|
180
-
|--|--|--|
181
-
|Default number of outbound* concurrent calls |per Number | 2
197
+
|**Name**|**Scope**| Limit |
198
+
| --- | --- | --- |
199
+
|Default number of outbound* concurrent calls |per Number | 2 |
182
200
183
-
*: no limits on inbound concurrent calls. You can also [submit a request to Azure Support](../../azure-portal/supportability/how-to-create-azure-support-request.md) to increase the outbound concurrent calls limit and it will be reviewed by our vetting team.
201
+
> [!NOTE]
202
+
> \* No limits on inbound concurrent calls. You can also [submit a request to Azure Support](../../azure-portal/supportability/how-to-create-azure-support-request.md) to increase the outbound concurrent calls limit, which is reviewed by our vetting team.
184
203
185
204
### Call maximum limitations
186
205
187
-
|**Name**| Limit|
188
-
|--|--|
189
-
|Number of participants | 350
206
+
|**Name**| Limit |
207
+
| --- | --- |
208
+
|Number of participants | 350 |
190
209
191
210
### Calling SDK streaming support
192
211
The Communication Services Calling SDK supports the following streaming configurations:
|**Maximum # of outgoing local streams that you can send simultaneously**| one video or one screen sharing | one video + one screen sharing |
197
-
|**Maximum # of incoming remote streams that you can render simultaneously**|9 videos + one screen sharing |9 videos + one screen sharing |
213
+
| Limit | Web | Windows/Android/iOS |
214
+
| --- | --- | --- |
215
+
|**Maximum # of outgoing local streams that you can send simultaneously**| one video or one screen sharing | one video + one screen sharing |
216
+
|**Maximum # of incoming remote streams that you can render simultaneously**|nine videos + one screen sharing |nine videos + one screen sharing |
198
217
199
-
While the Calling SDK won't enforce these limits, your users may experience performance degradation if they're exceeded.
218
+
The Calling SDK doesn't enforce these limits, but your users might experience performance degradation if you exceed these limits.
200
219
201
220
### Calling SDK timeouts
202
221
@@ -215,10 +234,10 @@ The following timeouts apply to the Communication Services Calling SDKs:
215
234
216
235
### Action to take
217
236
218
-
For more information about the voice and video calling SDK and service, see the [calling SDK overview](./voice-video-calling/calling-sdk-features.md) page or [known issues](./known-issues.md). You can also [submit a request to Azure Support](../../azure-portal/supportability/how-to-create-azure-support-request.md) to increase some of the limits and then it is reviewed by our vetting team.
237
+
For more information about the voice and video calling SDK and service, see the [calling SDK overview](./voice-video-calling/calling-sdk-features.md) page or [known issues](./known-issues.md). You can also [submit a request to Azure Support](../../azure-portal/supportability/how-to-create-azure-support-request.md) to increase some of the limits, pending review by our vetting team.
219
238
220
239
## Job Router
221
-
When sending or receiving a high volume of requests, you might receive a ```ThrottleLimitExceededException``` error. This error indicates you're hitting the service limitations, and your requests will be dropped until the token of bucket to handle requests is replenished after a certain time.
240
+
When sending or receiving a high volume of requests, you might receive a ```ThrottleLimitExceededException``` error. This error indicates you're hitting the service limitations, and your requests fail until the token of bucket to handle requests is replenished after a certain time.
222
241
223
242
Rate Limits for Job Router:
224
243
@@ -235,9 +254,9 @@ Using a Teams interoperability scenario, you'll likely use some Microsoft Graph
235
254
Each service offered through Microsoft Graph has different limitations; service-specific limits are [described here](/graph/throttling) in more detail.
236
255
237
256
### Action to take
238
-
When you implement error handling, use the HTTP error code 429 to detect throttling. The failed response includes the ```Retry-After``` response header. Backing off requests using the ```Retry-After``` delay is the fastest way to recover from throttling because Microsoft Graph continues to log resource usage while a client is being throttled.
257
+
When you implement error handling, use the HTTP error code 429 to detect throttling. The failed response includes the `Retry-After` response header. Backing off requests using the `Retry-After` delay is the fastest way to recover from throttling because Microsoft Graph continues to log resource usage while a client is being throttled.
239
258
240
259
You can find more information on Microsoft Graph [throttling](/graph/throttling) limits in the [Microsoft Graph](/graph/overview) documentation.
241
260
242
261
## Next steps
243
-
See the [help and support](../support.md) options.
262
+
See the [help and support](../support.md) options.
0 commit comments