Skip to content

Commit 5499ae2

Browse files
committed
Resolved questions
Resolved all questions and removed question marks, added next steps and moved paragraph about email rate limits.
1 parent 5fbd98c commit 5499ae2

File tree

2 files changed

+13
-20
lines changed

2 files changed

+13
-20
lines changed

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

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ When you hit service limitations, you receive an HTTP status code 429 (Too many
2323
- Reduce the frequency of calls.
2424
- Avoid immediate retries because all requests accrue against your usage limits.
2525

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

2828
1. Open the [Azure portal](https://ms.portal.azure.com/) and sign in.
2929
2. Select [Help+Support](https://ms.portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/overview).
@@ -61,8 +61,6 @@ Number purchase limits can be increased through a request to Azure Support.
6161
8. Add **Additional details** as needed, then click **Next**.
6262
9. At **Review + create** check the information, make changes as needed, then click **Create**.
6363

64-
65-
6664
## Identity
6765

6866
| Operation | Timeframes (seconds) | Limit (number of requests) |
@@ -104,9 +102,9 @@ You can send a limited number of email messages. If you exceed the following lim
104102

105103
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.
106104

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
108106

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

111109
[Custom Domains](../quickstarts/email/add-custom-verified-domains.md)
112110

@@ -126,7 +124,7 @@ We approve higher limits for customers based on use case requirements, domain re
126124
|Get Email Status|Per Subscription|1|10|
127125
|Get Email Status|Per Subscription|60|20|
128126

129-
### Size Limits
127+
### Size Limits for Email
130128

131129
| **Name** | Limit |
132130
| --- | --- |
@@ -161,7 +159,7 @@ To increase your email quota, follow the instructions at [Quota increase for ema
161159
162160
## Chat
163161

164-
### Size Limits
162+
### Size Limits for Chat
165163

166164
| **Name** | Limit |
167165
| --- | --- |
@@ -172,7 +170,7 @@ To increase your email quota, follow the instructions at [Quota increase for ema
172170
|Message Size|28 KB |
173171
|Number of Azure Communication Services resources per Azure Bot|1000 |
174172

175-
### Rate Limits
173+
### Rate Limits for Chat
176174

177175
| **Operation** | **Scope** | **Limit per 10 seconds** | **Limit per minute** |
178176
| --- | --- | --- | --- |

articles/communication-services/samples/email-detect-sensitive-content.md

Lines changed: 7 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -106,8 +106,6 @@ namespace SendEmail
106106

107107
Create a new function to analyze the email subject and body for sensitive data such as social security numbers and credit card numbers.
108108

109-
**??? Where does this go? After *Pre-check sensitive data and inappropriate content* ???**
110-
111109
```csharp
112110
private static async Task<bool> AnalyzeSensitiveData(List<string> documents)
113111
{
@@ -121,7 +119,7 @@ private static async Task<bool> AnalyzeSensitiveData(List<string> documents)
121119

122120
### Create the Text Analytics client with authentication
123121

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

126124
```csharp
127125
// This example requires environment variables named "LANGUAGE_KEY" and "LANGUAGE_ENDPOINT"
@@ -135,7 +133,7 @@ var client = new TextAnalyticsClient(new Uri(languageEndpoint), new AzureKeyCred
135133

136134
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`.
137135

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

140138
```csharp
141139
bool senstiveDataDetected = false; // we start with a baseline that of no sensitive data
@@ -191,7 +189,7 @@ static async Task<bool> AnalyzeInappropriateContent(List<string> documents)
191189

192190
### Create the Content Safety client with authentication
193191

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

196194
```csharp
197195
// 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
204202

205203
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`.
206204

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

209207
```csharp
210208
bool inappropriateTextDetected = false;
@@ -254,7 +252,7 @@ Add the sample email content into the Main function, following the lines that cr
254252

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

257-
Modify the recipient email address. **??? Is this enough information ???**
255+
Modify the recipient email address variable.
258256

259257
Put both the subject and the message body into a `List<string>` which can be used by the two content checking functions.
260258

@@ -327,8 +325,5 @@ else
327325

328326
## Next steps
329327

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

Comments
 (0)