Merge pull request #233048 from natekimball-msft/natekimball/last-minute-updates

American-Dipper · web-flow · commit 321a331497f9 · 2023-04-01T17:02:12.000-07:00
changes per discussion
diff --git a/articles/communication-services/concepts/email-pricing.md b/articles/communication-services/concepts/email-pricing.md
@@ -6,20 +6,17 @@ author: bashan-git
 manager: sphenry
 services: azure-communication-services
 ms.author: bashan
-ms.date: 04/15/2022
+ms.date: 03/31/2023
 ms.topic: conceptual
 ms.service: azure-communication-services
-ms.custom: private_preview, event-tier1-build-2022
 ---
 # Email pricing in Azure Communication Services
 
-[!INCLUDE [Public Preview Notice](../includes/public-preview-include.md)]
-
 Prices for Azure Communication Services are generally based on a pay-as-you-go model and Email offers pay-as-you-go pricing as well. The prices in the following examples are for illustrative purposes and may not reflect the latest Azure pricing.
 
 ## Email price
 
- The price is based on number of messages sent to the recipient and amount of data transferred to each recipient which includes headers, message content (including text and images), and attachments. Messages can be sent to one more recipients.
+ The price is based on number of messages sent to the recipient and amount of data transferred to each recipient which includes headers, message content (including text and images), and attachments. Messages can be sent to one or more recipients.
 
 
 |Email Send |Data Transferred|
diff --git a/articles/communication-services/concepts/email/email-attachment-allowed-mime-types.md b/articles/communication-services/concepts/email/email-attachment-allowed-mime-types.md
@@ -6,10 +6,9 @@ author: natekimball-msft
 manager: koagbakp
 services: azure-communication-services
 ms.author: natekimball
-ms.date: 03/24/2023
+ms.date: 03/31/2023
 ms.topic: conceptual
 ms.service: azure-communication-services
-ms.custom: private_preview, event-tier1-build-2022
 ---
 
 # Allowed attachment types for sending email in Azure Communication Services Email
diff --git a/articles/communication-services/concepts/email/email-authentication-best-practice.md b/articles/communication-services/concepts/email/email-authentication-best-practice.md
@@ -6,15 +6,12 @@ author: bashan-git
 manager: sphenry
 services: azure-communication-services
 ms.author: bashan
-ms.date: 04/15/2022
+ms.date: 03/31/2023
 ms.topic: conceptual
 ms.service: azure-communication-services
-ms.custom: private_preview, event-tier1-build-2022
 ---
 # Best practices for sender authentication support in Azure Communication Services Email
 
-[!INCLUDE [Public Preview Notice](../../includes/public-preview-include.md)]
-
 This article provides the Email Sending best practices on DNS records and  how to use the sender authentication methods that help prevent attackers from sending messages that look like they come from your domain.
 
 ## Email authentication and DNS setup
diff --git a/articles/communication-services/concepts/email/email-domain-and-sender-authentication.md b/articles/communication-services/concepts/email/email-domain-and-sender-authentication.md
@@ -6,15 +6,12 @@ author: bashan-git
 manager: sphenry
 services: azure-communication-services
 ms.author: bashan
-ms.date: 04/15/2022
+ms.date: 03/31/2023
 ms.topic: conceptual
 ms.service: azure-communication-services
-ms.custom: private_preview, event-tier1-build-2022
 ---
 # Email domains and sender authentication for Azure Communication Services
 
-[!INCLUDE [Public Preview Notice](../../includes/public-preview-include.md)]
-
 An email domain is a unique name that appears after the @ sign-in email addresses. It typically takes the form of your organization's name and brand that is recognized in public. Using your domain in email allows users to trust that this message isn't a phishing attempt, and that it is coming from a trusted source, thereby building credibility for your brand. If you prefer, you can utilize the email domains that is offered through the Azure Communication Services. We offer an email domain that can be used to send emails on behalf of your organization.
 
 ## Email domains and sender authentication
diff --git a/articles/communication-services/concepts/email/email-overview.md b/articles/communication-services/concepts/email/email-overview.md
@@ -6,15 +6,12 @@ author: bashan-git
 manager: sphenry
 services: azure-communication-services
 ms.author: bashan
-ms.date: 04/15/2022
+ms.date: 03/31/2023
 ms.topic: conceptual
 ms.service: azure-communication-services
-ms.custom: private_preview, event-tier1-build-2022
 ---
 # Email in Azure Communication Services
 
-[!INCLUDE [Public Preview Notice](../../includes/public-preview-include.md)]
-
 Azure Communication Services Email is a new primitive that facilitates high volume transactional, bulk and marketing emails on the Azure Communication Services platform and will enable Application-to-Person (A2P) use cases. Azure Communication Services Email is going to simplify the integration of email capabilities to your applications using production-ready email SDK options. Email enables rich collaboration in communication modalities combining with SMS and other communication channels to build collaborative applications to help reach your customers in their preferred communication channel.
 
 Azure Communication Services Email offers will improve your time-to-market with scalable, reliable email capabilities with your own SMTP domains. Like other communication modalities Email offering has the benefit of only paying for what you use.
diff --git a/articles/communication-services/concepts/email/prepare-email-communication-resource.md b/articles/communication-services/concepts/email/prepare-email-communication-resource.md
@@ -6,15 +6,12 @@ author: bashan-git
 manager: sphenry
 services: azure-communication-services
 ms.author: bashan
-ms.date: 04/15/2022
+ms.date: 03/31/2023
 ms.topic: conceptual
 ms.service: azure-communication-services
-ms.custom: private_preview, event-tier1-build-2022
 ---
 # Prepare Email Communication resource for Azure Communication Service 
 
-[!INCLUDE [Public Preview Notice](../../includes/public-preview-include.md)]
-
 Similar to Chat, VoIP and SMS modalities under the Azure Communication Services, you'll be able to send an email using Azure Communication Resource. However sending an email requires certain pre-configuration steps and you have to rely on your organization admins help setting that up. The administrator of your organization needs to,
 - Approve the domain that your organization allows you to send mail from 
 - Define the sender domain they'll  use as the P1 sender email address (also known as MailFrom email address) that shows up on the envelope of the email [RFC 5321](https://tools.ietf.org/html/rfc5321)
diff --git a/articles/communication-services/concepts/email/sdk-features.md b/articles/communication-services/concepts/email/sdk-features.md
@@ -6,15 +6,12 @@ author: bashan-git
 manager: sphenry
 services: azure-communication-services
 ms.author: bashan
-ms.date: 04/15/2022
+ms.date: 03/31/2023
 ms.topic: conceptual
 ms.service: azure-communication-services
-ms.custom: private_preview, event-tier1-build-2022
 ---
 # Email client library overview for Azure Communication Services
 
-[!INCLUDE [Public Preview Notice](../../includes/public-preview-include.md)]
-
 Azure Communication Services Email client libraries can be used to add transactional Email support to your applications.
 
 ## Client libraries
@@ -41,7 +38,7 @@ The following list presents the set of features that are currently available in
 
 ## API Throttling and Timeouts
 
-Your Azure account has a set of limitation on the number of email messages that you can send. For all the developers email sending is limited to 10 mails per minute, 25 mails in an hour and 100 mails in day. This sandbox setup is to help developers to start building the application and gradually you can request to increase the sending volume as soon as the application is ready to go live. Submit a support request to increase your sending limit.
+Your Azure account has a set of limitation on the number of email messages that you can send. For all the developers email sending is limited to 30 mails per minute, 100 mails in an hour. This sandbox setup is to help developers to start building the application and gradually you can request to increase the sending volume as soon as the application is ready to go live. Submit a support request to increase your sending limit.
 
 ## Next steps
 
diff --git a/articles/communication-services/concepts/service-limits.md b/articles/communication-services/concepts/service-limits.md
@@ -7,7 +7,7 @@ manager: shahen
 services: azure-communication-services
 
 ms.author: chpalm
-ms.date: 02/28/2023
+ms.date: 03/31/2023
 ms.topic: how-to
 ms.service: azure-communication-services
 ms.subservice: data
@@ -76,10 +76,10 @@ Sending a high volume of messages has a set of limitations on the number of emai
 
 |Operation|Scope|Timeframe (minutes)| Limit (number of emails) |
 |---------|-----|-------------|-------------------|
-|Send Email|Per Subscription|1|10|
-|Send Email|Per Subscription|60|25|
-|Get Email Status|Per Subscription|1|20|
-|Get Email Status|Per Subscription|60|50|
+|Send Email|Per Subscription|1|30|
+|Send Email|Per Subscription|60|100|
+|Get Email Status|Per Subscription|1|60|
+|Get Email Status|Per Subscription|60|200|
 
 ### Size Limits
 
diff --git a/articles/communication-services/concepts/troubleshooting-info.md b/articles/communication-services/concepts/troubleshooting-info.md
@@ -6,7 +6,7 @@ manager: chpalm
 services: azure-communication-services
 
 ms.author: prakulka
-ms.date: 11/30/2021
+ms.date: 03/31/2023
 ms.topic: conceptual
 ms.service: azure-communication-services
 ---
@@ -140,12 +140,20 @@ The program brief ID can be found on the [Azure portal](https://portal.azure.com
 
 ---
 
-## Access your email message ID
-When troubleshooting send email or email message status requests, you may be asked to provide a `message ID`. This can be accessed in the response:
+## Access your email operation ID
+When troubleshooting send email or email message status requests, you may be asked to provide an `operation ID`. This can be accessed in the response:
 
 # [.NET](#tab/dotnet)
 ```csharp
-Console.WriteLine($"MessageId = {emailResult.MessageId}");
+var emailSendOperation = await emailClient.SendAsync(
+    wait: WaitUntil.Completed,
+    senderAddress: sender,
+    recipientAddress: recipient,
+    subject: subject,
+    htmlContent: htmlContent);
+
+/// Get the OperationId so that it can be used for tracking the message for troubleshooting
+Console.WriteLine($"Email operation id = {emailSendOperation.Id}");
 ```
 ---
 
diff --git a/articles/communication-services/quickstarts/email/add-azure-managed-domains.md b/articles/communication-services/quickstarts/email/add-azure-managed-domains.md
@@ -6,15 +6,12 @@ author: bashan-git
 manager: sphenry
 services: azure-communication-services
 ms.author: bashan
-ms.date: 04/15/2022
+ms.date: 03/31/2023
 ms.topic: quickstart
 ms.service: azure-communication-services
-ms.custom: private_preview, event-tier1-build-2022
 ---
 # Quickstart: How to add Azure Managed Domains to Email Communication Service
 
-[!INCLUDE [Public Preview Notice](../../includes/public-preview-include.md)]
-
 In this quick start, you'll learn about how to provision the Azure Managed domain in Azure Communication Services to send email.
 
 ## Prerequisites
diff --git a/articles/communication-services/quickstarts/email/add-custom-verified-domains.md b/articles/communication-services/quickstarts/email/add-custom-verified-domains.md
@@ -6,15 +6,12 @@ author: bashan-git
 manager: sphenry
 services: azure-communication-services
 ms.author: bashan
-ms.date: 04/15/2022
+ms.date: 03/31/2023
 ms.topic: quickstart
 ms.service: azure-communication-services
-ms.custom: private_preview, event-tier1-build-2022
 ---
 # Quickstart: How to add custom verified domains to Email Communication Service
 
-[!INCLUDE [Public Preview Notice](../../includes/public-preview-include.md)]
-
 In this quick start, you'll learn about how to add a custom domain and verify in Azure Communication Services to send email.
 
 ## Prerequisites
@@ -76,7 +73,7 @@ To provision a custom domain you need to
     :::image type="content" source="./media/email-domains-custom-verify-progress.png" alt-text="Screenshot that shows the domain verification is in progress.":::
 15. Once your domain is verified, you can add your SPF and DKIM records to authenticate your domains. 
 
-    :::image type="content" source="./media/email-domains-custom-verified.png" alt-text="Screenshot that shows the the custom domain is verified." lightbox="media/email-domains-custom-verified-expanded.png":::
+    :::image type="content" source="./media/email-domains-custom-verified.png" alt-text="Screenshot that shows the custom domain is verified." lightbox="media/email-domains-custom-verified-expanded.png":::
 
 
 ### Configure sender authentication for custom domain
diff --git a/articles/communication-services/quickstarts/email/connect-email-communication-resource.md b/articles/communication-services/quickstarts/email/connect-email-communication-resource.md
@@ -6,15 +6,12 @@ author: bashan-git
 manager: sphenry
 services: azure-communication-services
 ms.author: bashan
-ms.date: 04/15/2022
+ms.date: 03/31/2023
 ms.topic: quickstart
 ms.service: azure-communication-services
-ms.custom: private_preview, event-tier1-build-2022
 ---
 # Quickstart: How to connect a verified email domain with Azure Communication Service resource
 
-[!INCLUDE [Public Preview Notice](../../includes/public-preview-include.md)]
-
 In this quick start, you'll learn about how to connect a verified domain in Azure Communication Services to send email.
 
 ## Connect an email domain to a Communication Service Resource
@@ -41,7 +38,7 @@ In this quick start, you'll learn about how to connect a verified domain in Azur
 
 5. Click Connect
  
-    :::image type="content" source="./media/email-domains-connected.png" alt-text="Screenshot that shows one of the verified email domain is now connected." lightbox="media/email-domains-connected-expanded.png":::
+    :::image type="content" source="./media/email-domains-connected.png" alt-text="Screenshot that shows one of the verified email domains is now connected." lightbox="media/email-domains-connected-expanded.png":::
 
 ## Disconnect an email domain from the Communication Service Resource
 
diff --git a/articles/communication-services/quickstarts/email/create-email-communication-resource.md b/articles/communication-services/quickstarts/email/create-email-communication-resource.md
@@ -6,15 +6,12 @@ author: bashan-git
 manager: sphenry
 services: azure-communication-services
 ms.author: bashan
-ms.date: 04/15/2022
+ms.date: 03/31/2023
 ms.topic: quickstart
 ms.service: azure-communication-services
-ms.custom: private_preview, event-tier1-build-2022
 ---
 # Quickstart - Create and manage Email Communication Service resource in Azure Communication Service
 
-[!INCLUDE [Public Preview Notice](../../includes/public-preview-include.md)]
-
  
 Get started with Email by provisioning your first Email Communication Services resource. Communication services resources can be provisioned through the [Azure portal](https://portal.azure.com/) or with the .NET management client library. The management client library and the Azure portal allow you to create, configure, update and delete your resources and interface with [Azure Resource Manager](../../../azure-resource-manager/management/overview.md), Azure's deployment and management service. All functionality available in the client libraries is available in the Azure portal. 
 
diff --git a/articles/communication-services/quickstarts/email/enable-user-engagement-tracking.md b/articles/communication-services/quickstarts/email/enable-user-engagement-tracking.md
@@ -6,14 +6,12 @@ author: bashan-git
 manager: sundraman
 services: azure-communication-services
 ms.author: bashan
-ms.date: 02/15/2023
+ms.date: 03/31/2023
 ms.topic: quickstart
 ms.service: azure-communication-services
 ---
 # Quickstart: How to enable user engagement tracking for the email domain with Azure Communication Service resource
 
-[!INCLUDE [Public Preview Notice](../../includes/public-preview-include.md)]
-
 Configuring email engagement enables the insights on your customers' engagement with emails to help build customer relationships. Only the emails that are sent from Azure Communication Services verified Email Domains that are enabled for user engagement analysis will get the engagement tracking metrics.
 
 > [!IMPORTANT]
diff --git a/articles/communication-services/quickstarts/email/handle-email-events.md b/articles/communication-services/quickstarts/email/handle-email-events.md
@@ -6,7 +6,7 @@ author: anmolbohra
 manager: komivi.agbakpem
 services: azure-communication-services
 ms.author: anmolbohra
-ms.date: 07/09/2022
+ms.date: 03/31/2023
 ms.topic: quickstart
 ms.service: azure-communication-services
 ms.subservice: email
@@ -15,8 +15,6 @@ ms.subservice: email
 
 Get started with Azure Communication Services by using Azure Event Grid to handle Communication Services Email events. After subscribing to Email events such as delivery reports and engagement reports, you generate and receive these events. Completing this quickstart incurs a small cost of a few USD cents or less in your Azure account.
 
-[!INCLUDE [Public Preview Notice](../../includes/public-preview-include.md)]
-
 ## Prerequisites
 
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
diff --git a/articles/communication-services/quickstarts/email/includes/create-email-resource-azp.md b/articles/communication-services/quickstarts/email/includes/create-email-resource-azp.md
@@ -3,10 +3,9 @@ author: author
 manager: author
 services: azure-communication-services
 ms.author: author
-ms.date: 04/15/2022
+ms.date: 03/31/2023
 ms.topic: include
 ms.service: azure-communication-services
-ms.custom: private_preview, event-tier1-build-2022
 ---
 
 ## Prerequisites
diff --git a/articles/communication-services/quickstarts/email/includes/email-operation-status.md b/articles/communication-services/quickstarts/email/includes/email-operation-status.md
@@ -5,10 +5,9 @@ author: natekimball-msft
 manager: koagbakp
 services: azure-communication-services
 ms.author: natekimball
-ms.date: 03/03/2023
+ms.date: 03/31/2023
 ms.topic: include
 ms.service: azure-communication-services
-ms.custom: private_preview, event-tier1-build-2022
 ---
 
 
diff --git a/articles/communication-services/quickstarts/email/includes/send-email-net.md b/articles/communication-services/quickstarts/email/includes/send-email-net.md
@@ -5,7 +5,7 @@ author: bashan-git
 manager: sundraman
 services: azure-communication-services
 ms.author: bashan
-ms.date: 03/24/2023
+ms.date: 03/31/2023
 ms.topic: include
 ms.service: azure-communication-services
 ---
@@ -77,7 +77,7 @@ dotnet build
 While still in the application directory, install the Azure Communication Services Email client library for .NET package by using the `dotnet add package` command.
 
 ```console
-dotnet add package Azure.Communication.Email --prerelease
+dotnet add package Azure.Communication.Email
 ```
 
 ## Creating the email client with authentication
@@ -397,7 +397,7 @@ You can download the sample app demonstrating this action from [GitHub](https://
 
 ### Throw an exception when email sending tier limit is reached
 
-The Email API has throttling with limitations on the number of email messages that you can send. Email sending has limits applied per minute and per hour as mentioned in [API Throttling and Timeouts](https://learn.microsoft.com/azure/communication-services/concepts/service-limits). When you have reached these limits, additional email sends with `SendAsync` calls will receive an error response of “429: Too Many Requests”. By default, the SDK is configured to retry these requests after waiting a certain period of time. We recommend you [set up logging with the Azure SDK](https://learn.microsoft.com/dotnet/azure/sdk/logging) to capture these response codes.
+The Email API has throttling with limitations on the number of email messages that you can send. Email sending has limits applied per minute and per hour as mentioned in [API Throttling and Timeouts](../../../concepts/service-limits.md). When you have reached these limits, additional email sends with `SendAsync` calls will receive an error response of “429: Too Many Requests”. By default, the SDK is configured to retry these requests after waiting a certain period of time. We recommend you [set up logging with the Azure SDK](/dotnet/azure/sdk/logging) to capture these response codes.
 
 Alternatively, you can manually define a custom policy as shown below.
 
diff --git a/articles/communication-services/quickstarts/email/send-email.md b/articles/communication-services/quickstarts/email/send-email.md
@@ -6,17 +6,14 @@ author: bashan-git
 manager: sphenry
 services: azure-communication-services
 ms.author: bashan
-ms.date: 04/15/2022
+ms.date: 03/31/2023
 ms.topic: quickstart
 ms.service: azure-communication-services
-ms.custom: private_preview, event-tier1-build-2022
 zone_pivot_groups: acs-azcli-js-csharp-java-python-power-platform
 ---
 
 # Quickstart: How to send an email using Azure Communication Service
 
-[!INCLUDE [Public Preview Notice](../../includes/public-preview-include.md)]
-
 In this quick start, you'll learn about how to send email using our Email SDKs.
 
 ::: zone pivot="platform-azcli"
