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
+6-8Lines changed: 6 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ When you hit service limitations, you receive an HTTP status code 429 (Too many
23
23
- Reduce the frequency of calls.
24
24
- Avoid immediate retries because all requests accrue against your usage limits.
25
25
26
-
You can find more general guidance on how to set up your service architecture to handle throttling and limitations in the [Azure Architecture](/azure/architecture) documentation for [throttling patterns](/azure/architecture/patterns/throttling). Throttling limits can be increased through a request to Azure Support.
26
+
You can find more general guidance on how to set up your service architecture to handle throttling and limitations in the [Azure Architecture](/azure/architecture) documentation for [throttling patterns](/azure/architecture/patterns/throttling). To increase throttling limits you need to make a request to [Azure Support](../support.md).
27
27
28
28
1. Open the [Azure portal](https://ms.portal.azure.com/) and sign in.
@@ -104,9 +102,9 @@ You can send a limited number of email messages. If you exceed the following lim
104
102
105
103
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. 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
104
107
-
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 only available for verified custom domains, not Azure-managed domains.
105
+
### Rate Limits for Email
108
106
109
-
### Rate Limits
107
+
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 only available for verified custom domains, not Azure-managed domains.
### Create the Text Analytics client with authentication
123
121
124
-
Create a new function with a Text Analytics client that also retrieves your connection information. Add the following code into the `AnalyzeSensitiveData` function to retrieve the connection key and endpoint for the resource from environment variables named `LANGUAGE_KEY` and `LANGUAGE_ENDPOINT`. It also creates the new `TextAnalyticsClient`**??? function or variable or ???**. For more information about managing your Text Analytics connection information, see [Quickstart: Detect Personally Identifiable Information \(PII\) > Get your key and endpoint](/azure/ai-services/language-service/personally-identifiable-information/quickstart#get-your-key-and-endpoint).
122
+
Create a new function with a Text Analytics client that also retrieves your connection information. Add the following code into the `AnalyzeSensitiveData` function to retrieve the connection key and endpoint for the resource from environment variables named `LANGUAGE_KEY` and `LANGUAGE_ENDPOINT`. It also creates the new `TextAnalyticsClient`and `AzureKeyCredential` variables. For more information about managing your Text Analytics connection information, see [Quickstart: Detect Personally Identifiable Information \(PII\) > Get your key and endpoint](/azure/ai-services/language-service/personally-identifiable-information/quickstart#get-your-key-and-endpoint).
125
123
126
124
```csharp
127
125
// This example requires environment variables named "LANGUAGE_KEY" and "LANGUAGE_ENDPOINT"
@@ -135,7 +133,7 @@ var client = new TextAnalyticsClient(new Uri(languageEndpoint), new AzureKeyCred
135
133
136
134
Loop through the content to check for any sensitive data. Start the sensitivity check with a baseline of `false`. If sensitive data is found, return `true`.
137
135
138
-
Add the following code into the `AnalyzeSensitiveData` function following the line that creates the `TextAnalyticsClient`**???variable???**.
136
+
Add the following code into the `AnalyzeSensitiveData` function following the line that creates the `TextAnalyticsClient` variable.
139
137
140
138
```csharp
141
139
boolsenstiveDataDetected=false; // we start with a baseline that of no sensitive data
### Create the Content Safety client with authentication
193
191
194
-
Create a new function with a Content Safety client that also retrieves your connection information. Add the following code into the `AnalyzeInappropriateContent` function to retrieve the connection key and endpoint for the resource from environment variables named `CONTENT_LANGUAGE_KEY` and `CONTENT_LANGUAGE_ENDPOINT`. It also creates a new `ContentSafetyClient`**???variable???**. If you're using the same Azure AI instance for Text Analytics, these values remain the same. For more information about managing your Content Safety connection information, see [Quickstart: Detect Personally Identifiable Information (PII) > Create environment variables](/azure/ai-services/language-service/personally-identifiable-information/quickstart#create-environment-variables).
192
+
Create a new function with a Content Safety client that also retrieves your connection information. Add the following code into the `AnalyzeInappropriateContent` function to retrieve the connection key and endpoint for the resource from environment variables named `CONTENT_LANGUAGE_KEY` and `CONTENT_LANGUAGE_ENDPOINT`. It also creates a new `ContentSafetyClient` variable. If you're using the same Azure AI instance for Text Analytics, these values remain the same. For more information about managing your Content Safety connection information, see [Quickstart: Detect Personally Identifiable Information (PII) > Create environment variables](/azure/ai-services/language-service/personally-identifiable-information/quickstart#create-environment-variables).
195
193
196
194
```csharp
197
195
// This example requires environment variables named "CONTENT_LANGUAGE_KEY" and "CONTENT_LANGUAGE_ENDPOINT"
@@ -204,7 +202,7 @@ var client = new ContentSafetyClient(new Uri(contentSafetyEndpoint), new AzureKe
204
202
205
203
Loop through the content to check for inappropriate content. Start the inappropriate content detection with a baseline of `false`. If inappropriate content is found, return `true`.
206
204
207
-
Add the following code into the `AnalyzeInappropriateContent` function after the line that creates the `ContentSafetyClient`**???variable???**.
205
+
Add the following code into the `AnalyzeInappropriateContent` function after the line that creates the `ContentSafetyClient` variable.
208
206
209
207
```csharp
210
208
boolinappropriateTextDetected=false;
@@ -254,7 +252,7 @@ Add the sample email content into the Main function, following the lines that cr
254
252
255
253
You need to get the sender email address. For more information about Azure Communication Services email domains, see [Quickstart: How to add Azure Managed Domains to Email Communication Service](../quickstarts/email/add-custom-verified-domains.md).
256
254
257
-
Modify the recipient email address. **??? Is this enough information ???**
255
+
Modify the recipient email address variable.
258
256
259
257
Put both the subject and the message body into a `List<string>` which can be used by the two content checking functions.
260
258
@@ -327,8 +325,5 @@ else
327
325
328
326
## Next steps
329
327
330
-
**???Any???**
331
-
332
-
## Related articles
333
-
334
-
**???Any???**
328
+
- Learn more about [Azure Communication Services](../overview.md).
329
+
- Learn more about [Azure AI Studio](/azure/ai-studio/).
0 commit comments