Merge pull request #272559 from MicrosoftDocs/main

4/18 11:00 AM IST Publish

Author: Saisang

articles/ai-services/speech-service/includes/quickstarts/intent-recognition/javascript.md

@@ -51,7 +51,7 @@ Now we'll add some basic UI for input boxes, reference the Speech SDK's JavaScri
         <td><h1 style="font-weight:500;">Microsoft Azure AI Speech SDK JavaScript Quickstart</h1></td>
       </tr>
       <tr>
-        <td align="right"><a href="https://learn.microsoft.com~/articles/ai-services/speech-service/get-started" target="_blank">Subscription</a>:</td>
+        <td align="right"><a href="https://learn.microsoft.com/azure/ai-services/speech-service/overview" target="_blank">Subscription</a>:</td>
         <td><input id="subscriptionKey" type="text" size="40" value="subscription"></td>
       </tr>
       <tr>

articles/azure-monitor/agents/gateway.md

@@ -81,9 +81,9 @@ The Log Analytics gateway is available in these languages:
 
 ### Supported encryption protocols
 
-The Log Analytics gateway supports only Transport Layer Security (TLS) 1.0, 1.1, and 1.2.  It doesn't support Secure Sockets Layer (SSL).  To ensure the security of data in transit to Log Analytics, configure the gateway to use at least TLS 1.2. Older versions of TLS or SSL are vulnerable. Although they currently allow backward compatibility, avoid using them.  
+The Log Analytics gateway supports only Transport Layer Security (TLS) 1.0, 1.1, 1.2 and 1.3.  It doesn't support Secure Sockets Layer (SSL). To ensure the security of data in transit to Log Analytics, configure the gateway to use at least TLS 1.3. Although they currently allow for backward compatibility, avoid using older versions because they are vunerable.  
 
-For additional information, review [Sending data securely using TLS 1.2](../logs/data-security.md#sending-data-securely-using-tls-12). 
+For additional information, review [Sending data securely using TLS](../logs/data-security.md#sending-data-securely-using-tls-12). 
 
 >[!NOTE]
 >The gateway is a forwarding proxy that doesn’t store any data. Once the agent establishes connection with Azure Monitor, it follows the same encryption flow with or without the gateway. The data is encrypted between the client and the endpoint. Since the gateway is just a tunnel, it doesn’t have the ability the inspect what is being sent.

articles/azure-monitor/logs/restore.md

@@ -6,7 +6,7 @@ ms.date: 10/01/2022
 ---
 
 # Restore logs in Azure Monitor
-The restore operation makes a specific time range of data in a table available in the hot cache for high-performance queries. This article describes how to restore data, query that data, and then dismiss the data when you're done. 
+The restore operation makes a specific time range of data in a table available in the hot cache for high-performance queries. This article describes how to restore data, query that data, and then dismiss the data when you're done.  
 
 ## Permissions
 
@@ -21,7 +21,7 @@ Use the restore operation to query data in [Archived Logs](data-retention-archiv
 ## What does restore do?
 When you restore data, you specify the source table that contains the data you want to query and the name of the new destination table to be created. 
 
-The restore operation creates the restore table and allocates additional compute resources for querying the restored data using high-performance queries that support full KQL.
+The restore operation creates the restore table and allocates extra compute resources for querying the restored data using high-performance queries that support full KQL.
 
 The destination table provides a view of the underlying source data, but doesn't affect it in any way. The table has no retention setting, and you must explicitly [dismiss the restored data](#dismiss-restored-data) when you no longer need it. 
 
@@ -124,27 +124,36 @@ You can:
 
 - Restore up to 60 TB.
 - Run up to two restore processes in a workspace concurrently.
-- Run only one active restore on a specific table at a given time. Executing a second restore on a table that already has an active restore will fail. 
+- Run only one active restore on a specific table at a given time. Executing a second restore on a table that already has an active restore fails. 
 - Perform up to four restores per table per week. 
 
 ## Pricing model
 
-The charge for restored logs is based on the volume of data you restore, and the duration for which the restore is active. Data restores are billed on each UTC-day that the restore is active. 
+The charge for restored logs is based on the volume of data you restore, and the duration for which the restore is active. Thus, the units of price are *per GB per day*. Data restores are billed on each UTC-day that the restore is active. 
 
 - Charges are subject to a minimum restored data volume of 2 TB per restore. If you restore less data, you will be charged for the 2 TB minimum each day until the [restore is dismissed](#dismiss-restored-data).
-- On the first and last days that the restore is active, charges are prorated based on the period that the restore is active. 
+- On the first and last days that the restore is active, you're only billed for the part of the day the restore was active. 
 
-- The minimum charge will be for a 12-hour restore duration, even if the restore is active for less than 12-hours.
+- The minimum charge is for a 12-hour restore duration, even if the restore is active for less than 12-hours.
 
-- For more information, see [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/).
+- For more information on your data restore price, see [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/) on the Logs tab.
 
-For example, if your table holds 500 GB a day and you restore 10 days data from that table, you'll be charged for 5 TB of restored data each day until you [dismiss the restored data](#dismiss-restored-data).
+Here are some examples to illustrate data restore cost calculations:
+
+1. If your table holds 500 GB a day and you restore 10 days data from that table, your total restore size is 5 TB. You are charged for this 5 TB of restored data each day until you [dismiss the restored data](#dismiss-restored-data). Your daily cost is 5,000 GB multiplied by your data restore price (see [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/).) 
+
+1. If instead, only 700 GB of data is restored, each day that the restore is active is billed for the 2 TB minimum restore level. Your daily cost is 2,000 GB multiplied by your data restore price.
+
+1. If a 5 TB data restore is only kept active for 1 hour, it is billed for 12-hour minimum. The cost for this data restore is 5,000 GB multiplied by your data restore price multiplied by 0.5 days (the 12-hour minimum). 
+
+1. If a 700 GB data restore is only kept active for 1 hour, it is billed for 12-hour minimum. The cost for this data restore is 2,000 GB (the minimum billed restore size) multiplied by your data restore price multiplied by 0.5 days (the 12-hour minimum). 
 
 > [!NOTE]
 > There is no charge for querying restored logs since they are Analytics logs. 
 
 ## Next steps
 
 - [Learn more about data retention and archiving data.](data-retention-archive.md)
+
 - [Learn about Search jobs, which is another method for retrieving archived data.](search-jobs.md)
 

articles/communication-services/concepts/email/email-domain-configuration-troubleshooting.md

@@ -0,0 +1,127 @@
+---
+title: Troubleshooting Domain Configuration issues for Azure Email Communication Service
+titleSuffix: An Azure Communication Services concept document
+description: Learn about Troubleshooting domain configuration issues.
+author: raviverm
+manager: daysha-carter
+services: azure-communication-services
+ms.author: raviverm
+ms.date: 04/09/2024
+ms.topic: conceptual
+ms.service: azure-communication-services
+---
+# Troubleshooting Domain Configuration issues
+
+This guide describes how to resolve common problems with setting up and using custom domains for Azure Email Communication Service.
+
+## 1. Unable to verify Custom Domain Status
+
+You need to verify the ownership of your domain by adding a TXT record to your domain's registrar or Domain Name System (DNS) hosting provider. If the domain verification fails for any reason, complete the following steps in this section to identify and resolve the underlying issue.
+
+### Reasons  
+
+Once the verification process starts, Azure Email Communication Service attempts to read the TXT record from your custom domain. If Azure Email Communication Service fails to read the TXT record, it marks the verification status as failed.
+
+### Steps to resolve
+
+1. Copy the proposed TXT record by Email Service from [Azure portal](https://portal.azure.com). Your TXT record should be similar to this example:  
+
+    `ms-domain-verification=43d01b7e-996b-4e31-8159-f10119c2087a`
+
+2. If you haven’t added the TXT record, then you must add the TXT record to your domain's registrar or DNS hosting provider. For step-by-step instructions, see [Quickstart: How to add custom verified email domains](../../quickstarts/email/add-custom-verified-domains.md).   
+
+3. Once you add the TXT record, you can query the TXT records for your custom domain.  
+
+    1. Use the `nslookup` tool from Windows CMD terminal to read TXT records from your domain.
+    2. Use a third-party DNS lookup tool: 
+
+        https://www.bing.com/search?q=dns+lookup+tool
+
+    In this section, we continue using the `nslookup` method.
+
+4. Use the following `nslookup` command to query the TXT records: 
+
+    `nslookup -q=TXT YourCustomDomain.com` 
+
+    The `nslookup` query should return records like this: 
+
+    ![Results from an nslookup query to read the TXT records for your custom domain](../media/email-domain-nslookup-query.png "Screen capture of the example results from an nslookup query to read the TXT records for your custom domain.")
+
+5. Review the list of TXT records for your custom domain. If you don’t see your TXT record listed, Azure Email Communication Service can't verify the domain.
+
+## 2. Unable to verify SPF status
+
+Once you verify the domain status, you need to verify the Sender Policy Framework (SPF) and DomainKeys Identified Mail (DKIM), and DKIM2. If your SPF status is failing, follow these steps to resolve the issue.
+
+1.	Copy your SPF record from [Azure portal](https://portal.azure.com). Your SPF record should look like this:
+
+    `v=spf1 include:spf.protection.outlook.com -all`  
+
+2. Azure Email Communication Service requires you to add the SPF record to your domain's registrar or DNS hosting provider. For a list of providers, see [Add DNS records in popular domain registrars](../../quickstarts/email/add-custom-verified-domains.md#add-dns-records-in-popular-domain-registrars). 
+
+4. Once you add the SPF record, you can query the SPF records for your custom domain. Here are two methods:
+
+    1. Use `nslookup` tool from Windows CMD terminal to read SPF records from your domain.
+    2. Use a third-party DNS lookup tool:
+
+        https://www.bing.com/search?q=dns+lookup+tool
+
+    In this section, we continue using the `nslookup` method.
+
+5. Use the following `nslookup` command to query the SPF record: 
+
+    `nslookup -q=TXT  YourCustomDomain.com`
+
+    This query returns a list of TXT records for your custom domain. 
+
+    ![Results from an nslookup query to read the SPF records for your custom domain](../media/email-domain-nslookup-spf-query.png "Screen capture of the example results from an nslookup query to read the SPF records for your custom domain.")
+
+6. Review the list of TXT headers for your custom domain. If you don’t see your SPF record listed here, Azure Email Communication Service can't verify the SPF Status for your custom domain. 
+
+7. Check for `-all` in your SPF record.
+
+    If your SPF records contain `~all` the SPF verification fails.
+
+    Azure Communication Services requires `-all` instead of `~all` to validate your SPF record.
+
+
+## 3. Unable to verify DKIM or DKIM2 Status
+
+If Azure Email Communication Service fails to verify the DKIM or DKIM2 status, follow these steps to resolve the issue.
+
+1.	Open your command prompt and use `nslookup`:
+
+    `nslookup set q=TXT`
+
+2. If DKIM fails, then use `selector1`. If DKIM2 fails, then use `selector2`.
+
+    `selector1-azurecomm-prod-net._domainkey.contoso.com`
+
+    `selector2-azurecomm-prod-net._domainkey.contoso.com`
+
+3. This query returns the CNAME DKIM records for your custom domain.
+
+    ![Results from an nslookup query to read CNAME DKIM records for your custom domain](../media/email-domain-nslookup-cname-dkim.png "Screen capture of the example results from an nslookup query to read CNAME DKIM records for your custom domain.")
+
+4. If `nslookup` returns your CNAME DKIM or DKIM2 records, similar to the preceding image, then you can expect Azure Email Communication Service to verify the DKIM or DKIM2 status.
+
+    If the DKIM/DKIM2 CNAME records are missing from `nslookup` output, then Azure Email Communication Service can't verify the DKIM or DKIM2 status.
+
+    For a list of providers, see [CNAME records](../../quickstarts/email/add-custom-verified-domains.md#cname-records).
+
+
+
+## Next steps
+
+* [Email domains and sender authentication for Azure Communication Services](./email-domain-and-sender-authentication.md)
+
+* [Quickstart: Create and manage Email Communication Service resource in Azure Communication Services](../../quickstarts/email/create-email-communication-resource.md)
+
+* [Quickstart: How to connect a verified email domain with Azure Communication Services resource](../../quickstarts/email/connect-email-communication-resource.md)
+
+## Related articles
+
+- [Email client library](../email/sdk-features.md)
+- [Add custom verified domains](../../quickstarts/email/add-custom-verified-domains.md)
+- [Add Azure Managed domains](../../quickstarts/email/add-azure-managed-domains.md)
+- [Quota increase for email domains](./email-quota-increase.md)

articles/communication-services/concepts/email/email-quota-increase.md

@@ -0,0 +1,99 @@
+---
+title: Quota increase for Azure Email Communication Service
+titleSuffix: An Azure Communication Services concept document
+description: Learn about requesting an increase to the default limit.
+author: raviverm
+manager: daysha-carter
+services: azure-communication-services
+ms.author: raviverm
+ms.date: 04/09/2024
+ms.topic: conceptual
+ms.service: azure-communication-services
+---
+# Quota increase for email domains
+
+If you're using Azure Email Communication Service, you can raise your default email sending limit. To request an increase in your email sending limit, follow the steps outlined in this article.
+
+## 1. Understand domain reputation
+
+Email domain sender reputation is a measure of how trustworthy and legitimate recipients and email service providers perceive your emails. A good sender reputation means that your emails are less likely to be marked as spam or rejected by the email servers. A bad sender reputation means that your emails are more likely to be filtered out or blocked by email servers. The following factors can affect your domain reputation: 
+
+* The volume and frequency of your email campaigns.
+* The deliverability and bounce rate of your emails. A high bounce rate can damage your sender reputation and indicate that your email list is outdated or poorly maintained.
+* The feedback and complaints from your recipients. A high complaint rate can severely harm your sender reputation.
+
+## 2. Use a custom domain instead of an Azure Managed Domain
+
+Azure Email Communication service lets you try out the email sending feature using a domain that Azure manages. For your production workloads and higher sending limits, you should use your own domain to send emails.  
+
+You can set up your own domain by creating a custom domain resource under an Azure Email Communication Service resource. Azure Managed Domains are intended for testing purposes only. There are limits imposed on the number and frequency of emails you can send using the Azure Managed Domain. If you want to raise your email sending limit, you must configure a custom domain using Azure Email Communication Service.  
+
+For more information, see [Service limits for Azure Communication Services](../../concepts/service-limits.md#email).
+
+## 3. Configure a mail exchange record for your custom domain 
+
+A mail exchange (MX) record specifies the email server responsible for receiving email messages on behalf of a domain name. The MX record is a resource record in the Domain Name System (DNS). Essentially, an MX record signifies that the domain can receive emails.  
+
+Although Azure Communication Service only supports outbound emails, we recommend setting up an MX record to improve the reputation of your sender domain. An email from a custom domain that lacks an MX record might be labeled as spam by the recipient email service provider. This could damage your domain reputation. 
+
+## 4. Build your sender reputation  
+
+Once you complete the previous steps, you can start building your sender reputation by sending legitimate production workload emails. To improve your chances of receiving a rate limit increase, try to minimize email failures and spam rate before requesting for a limit increase.
+
+## 5. Request an email quota increase  
+
+To request an email quota increase, compile the following information:
+
+```
+Customer Information 
+Company name: 
+Company website: 
+Please provide a brief description of your business: 
+
+Email Service Information 
+Subscription ID: 
+Azure Communication Services Resource Name: 
+Is your custom domain already set up and currently used for sending messages:  
+Indicate the domain from which you are currently sending emails:  
+
+Usage Information
+1. What type of emails do you send? (such as Transactional, Marketing, Promotional) 
+2. Please specify the expected volume of emails you plan to send:  
+	- What is the maximum rate of messages per minute that you require? 
+	- What is the maximum rate of messages per hour that you require? 
+	- What is the maximum rate of messages per day that you require? 
+
+Additional Information 
+What is the source of the email addresses that you use for sending your messages?
+Note: The source of the email addresses that you send your messages to plays a crucial role in the 
+effectiveness and compliance of your email marketing campaigns. Providing details about the source 
+of your email addresses helps us understand how you acquire and maintain your subscriber list.
+
+How do you currently manage and remove email addresses that have unsubscribed or resulted in 
+bounce backs from your mailing list?
+Please explain if you have an automated process in place that handles unsubscribes when recipients 
+click on the 'unsubscribe' link in your emails. Additionally, if you receive bounce/undeliverable 
+notifications, can you include how you handle those and whether you have any mechanism to 
+automatically remove email addresses that result in consistent bounces.
+```
+
+You can copy this text to a file and add the requested information.
+
+Then submit the information in an incident report at [Create a support ticket](https://azure.microsoft.com/support/create-ticket/), requesting to raise your email sending limit.
+
+Email quota increase requests aren't automatically approved. The reviewing team considers your overall sender reputation when determining approval status. Sender reputation includes factors such as your email delivery failure rates, your domain reputation, and reports of spam and abuse. 
+
+## Next steps
+
+* [Email domains and sender authentication for Azure Communication Services](./email-domain-and-sender-authentication.md)
+
+* [Quickstart: Create and manage Email Communication Service resource in Azure Communication Services](../../quickstarts/email/create-email-communication-resource.md)
+
+* [Quickstart: How to connect a verified email domain with Azure Communication Services resource](../../quickstarts/email/connect-email-communication-resource.md)
+
+## Related articles
+
+- [Email client library](../email/sdk-features.md)
+- [Add custom verified domains](../../quickstarts/email/add-custom-verified-domains.md)
+- [Add Azure Managed domains](../../quickstarts/email/add-azure-managed-domains.md)
+- [Troubleshooting Domain Configuration issues](./email-domain-configuration-troubleshooting.md)