Merge pull request #288273 from vac0224/vc-email-multiple-domain-2024-10-18

Add multiple custom domain note

Author: v-ccolin

articles/communication-services/quickstarts/email/connect-email-communication-resource.md

@@ -12,9 +12,10 @@ ms.service: azure-communication-services
 ms.custom: devx-track-extended-java, devx-track-js, devx-track-python
 zone_pivot_groups: acs-js-csharp-java-python-portal-rest
 ---
+
 # Quickstart: How to connect a verified email domain
 
-In this quick start, you learn how to connect a verified domain in Azure Communication Services to send email.
+This quickstart describes how to connect a verified domain in Azure Communication Services to send email.
 
 ::: zone pivot="azure-portal"
 [!INCLUDE [connect-domain-portal](./includes/connect-domain-portal.md)]

articles/communication-services/quickstarts/email/includes/connect-domain-js.md

@@ -13,11 +13,11 @@ ms.custom: mode-other
 
 ## Prerequisites
 
-- An Azure account with an active subscription. [Create an account for free.](https://azure.microsoft.com/free/dotnet/).
+- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/dotnet/).
 - An Azure Email Communication Services Resource ready to provision domains. [Get started creating an Email Communication Resource](../create-email-communication-resource.md).
 - An [Azure Managed Domain](../add-azure-managed-domains.md) or [Custom Domain](../add-custom-verified-domains.md) provisioned and ready to send emails. This domain must be fully verified before attempting to link it to the Communication Service resource.
-- An Azure Communication Services Resource. [Create a Communication Services Resources.](../../create-communication-resource.md)
-- We're using a [service principal for authentication](/entra/identity-platform/howto-create-service-principal-portal). Set the values of the client ID, tenant ID and client secret of the Microsoft Entra application as the following environment variables: `AZURE_CLIENT_ID`, `AZURE_TENANT_ID`, and `AZURE_CLIENT_SECRET`.
+- An Azure Communication Services Resource. [Create a Communication Services Resources](../../create-communication-resource.md).
+- We're using a [service principal for authentication](/entra/identity-platform/howto-create-service-principal-portal). Set the values of the client ID, tenant ID, and client secret of the Microsoft Entra application as the following environment variables: `AZURE_CLIENT_ID`, `AZURE_TENANT_ID`, and `AZURE_CLIENT_SECRET`.
 
 ## Install the required packages
 
@@ -44,13 +44,13 @@ client = new CommunicationServiceManagementClient(credential, subscriptionId);
 
 Replace the `<resource-group-name>`, `<azure-communication-services-resource-name>`, and `<linked-domain-resource-id>` in the sample code.
 
-The linked domain resource ID should be in the following format. 
+Format the linked domain resource ID as follows: 
 
 ```
 /subscriptions/<subscription-id>/resourceGroups/<resource-group-name>/providers/Microsoft.Communication/emailServices/<email-service-name>/domains/<domain-name>
 ```
 
-If you are using an Azure Managed Domain, the `domain-name` is "AzureManagedDomain". The `email-service-name` should be the same email service that you used to provision the domain.
+If you're using an Azure Managed Domain, the `domain-name` is "AzureManagedDomain". The `email-service-name` should be the same email service that you used to provision the domain.
 
 Once these values are populated, run the sample code.
 
@@ -74,7 +74,7 @@ const result = await client.communicationServices.beginCreateOrUpdateAndWait(
 
 Replace the `<resource-group-name>`, and `<azure-communication-services-resource-name>` in the sample code. 
 
-Once these values are populated run the sample code.
+Once these values are populated, run the sample code.
 
 ```javascript
 const parameters = {

articles/communication-services/quickstarts/email/includes/connect-domain-net.md

@@ -13,10 +13,10 @@ ms.custom: mode-other
 
 ## Prerequisites
 
-- An Azure account with an active subscription. [Create an account for free.](https://azure.microsoft.com/free/dotnet/).
+- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/dotnet/).
 - An Azure Email Communication Services Resource ready to provision domains. [Get started creating an Email Communication Resource](../create-email-communication-resource.md).
 - An [Azure Managed Domain](../add-azure-managed-domains.md) or [Custom Domain](../add-custom-verified-domains.md) provisioned and ready to send emails. This domain must be fully verified before attempting to link it to the Communication Service resource.
-- An Azure Communication Services Resource. [Create a Communication Services Resources.](../../create-communication-resource.md)
+- An Azure Communication Services Resource. [Create a Communication Services Resources](../../create-communication-resource.md).
 - We're using a [service principal for authentication](/entra/identity-platform/howto-create-service-principal-portal). Set the values of the client ID, tenant ID, and client secret of the Microsoft Entra application as the following environment variables: `AZURE_CLIENT_ID`, `AZURE_TENANT_ID`, and `AZURE_CLIENT_SECRET`.
 
 ## Install the required packages
@@ -45,7 +45,7 @@ ArmClient client = new ArmClient(new DefaultAzureCredential());
 
 Replace the `<subscription-id>`, `<resource-group-name>`, `<azure-communication-services-resource-name>`, and `<linked-domain-resource-id>` in the sample code.
 
-The linked domain resource ID should be in the following format. 
+Format the linked domain resource ID as follows: 
 
 ```
 /subscriptions/<subscription-id>/resourceGroups/<resource-group-name>/providers/Microsoft.Communication/emailServices/<email-service-name>/domains/<domain-name>

articles/communication-services/quickstarts/email/includes/connect-domain-portal.md

@@ -20,32 +20,40 @@ ms.custom: mode-other
 
 ## Connect an email domain to a Communication Service Resource
 
-1. In the Azure Communication Service Resource overview page, click **Domains** on the left navigation panel under Email.
+1. In the Azure Communication Service Resource overview page, in the left navigation panel under Email, click **Domains**.
 
     :::image type="content" source="../media/email-domains.png" alt-text="Screenshot that shows the left navigation panel for linking Email Domains." lightbox="../media/email-domains.png":::
 
-2. Select one of the options below
-    - Click **Connect domain** in the upper navigation bar.
-    - Click **Connect domain** in the splash screen.
+2. Select one of the following options:
+
+    - From the upper navigation bar, click **Connect domain**.
+    - From the splash screen, click **Connect domain**.
 
         :::image type="content" source="../media/email-domains-connect.png" alt-text="Screenshot that shows how to connect one of your verified email domains." lightbox="../media/email-domains-connect.png":::
-3. Select a one of the verified domains by filtering 
-    - Subscription
-    - Resource Group
-    - Email Service
-    - Verified Domain
+
+3. Select one of the verified domains by filtering:
+
+    - **Subscription**
+    - **Resource Group**
+    - **Email Service**
+    - **Verified Domain**
 
     :::image type="content" source="../media/email-domains-connect-select.png" alt-text="Screenshot that shows how to filter and select one of the verified email domains to connect." lightbox="../media/email-domains-connect-select.png":::
+
 > [!Note]
-> We allow only connecting the domains in the same geography. Please ensure that Data location for Communication Resource and Email Communication Resource that was selected during resource creation are the same.
+> You can only connect domains in the same geography. Please ensure that the Data location for Communication Resource and Email Communication Resource you selected during resource creation are in the same geography.
 
-4. Click Connect
+4. Click **Connect**.
 
     :::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.png":::
 
+> [!Note]
+> We enable customers to link up to 100 custom domains to a single communication service resource. All Mail-From addresses configured under these custom domains are accessible for the communication service resource. You can only link verified custom domains.
+
 ## Disconnect an email domain from the Communication Service Resource
 
-1. In the Azure Communication Service Resource overview page, click **Domains** on the left navigation panel under Email.
-2. Select the Connected Domains click the ... and click Disconnect.  
+1. In the Azure Communication Services Resource overview page, from the left navigation panel under Email, click **Domains**.
+
+1. Select the Connected Domains, then click **...** and select **Disconnect**.
 
     :::image type="content" source="../media/email-domains-connect-disconnect.png" alt-text="Screenshot that shows how to disconnect the connected domain." lightbox="../media/email-domains-connect-disconnect.png":::

articles/communication-services/quickstarts/email/includes/connect-domain-rest.md

@@ -13,24 +13,24 @@ ms.custom: mode-other
 
 ## Prerequisites
 
-- An Azure account with an active subscription. [Create an account for free.](https://azure.microsoft.com/free/dotnet/).
+- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free/dotnet/).
 - An Azure Email Communication Services Resource ready to provision domains. [Get started creating an Email Communication Resource](../create-email-communication-resource.md).
 - An [Azure Managed Domain](../add-azure-managed-domains.md) or [Custom Domain](../add-custom-verified-domains.md) provisioned and ready to send emails. This domain must be fully verified before attempting to link it to the Communication Service resource.
-- An Azure Communication Services Resource. [Create a Communication Services Resources.](../../create-communication-resource.md)
+- An Azure Communication Services Resource. [Create a Communication Services Resources](../../create-communication-resource.md).
 
 ## Connect an email domain to a Communication Service Resource
 
 Replace the `{subscription-id}`, `{resource-group-name}`, `{communication-services-resource-name}`, and `{linked-domain-resource-id}` in the sample request.
 
-The linked domain resource ID should be in the following format. 
+Format the linked domain resource ID as follows:
 
 ```
 /subscriptions/{subscription-id}/resourceGroups/{resource-group-name}/providers/Microsoft.Communication/emailServices/{email-service-name}/domains/{domain-name}
 ```
 
-If you are using an Azure Managed Domain, the `domain-name` is "AzureManagedDomain". The `email-service-name` should be the same email service that you used to provision the domain.
+If you're using an Azure Managed Domain, the `domain-name` is "AzureManagedDomain". The `email-service-name` should be the same email service that you used to provision the domain.
 
-Once these values are populated make a PATCH request to the using the following Request URL and Body. 
+Once these values are populated, make a PATCH request using the following Request URL and body. 
 
 ```
 https://management.azure.com/subscriptions/{subscription-id}/resourceGroups/{resource-group-name}/providers/Microsoft.Communication/CommunicationServices/{communication-services-resource-name}?api-version=2023-03-31
@@ -48,7 +48,7 @@ https://management.azure.com/subscriptions/{subscription-id}/resourceGroups/{res
 
 Replace the `{subscription-id}`, `{resource-group-name}`, and `{communication-services-resource-name}` in the sample request.
 
-Once these values are populated, make a PATCH request to the using the following Request URL and Body. 
+Once these values are populated, make a PATCH request using the following Request URL and body. 
 
 ```
 https://management.azure.com/subscriptions/{subscription-id}/resourceGroups/{resource-group-name}/providers/Microsoft.Communication/CommunicationServices/{communication-services-resource-name}?api-version=2023-03-31