Email Quota and Domain Troubleshooting

Added Email Quota and Domain Configuration Troubleshooting articles

Author: vac0224

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: dacarte
+services: azure-communication-services
+ms.author: ravi.verma
+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: 
+
+    ![alt text](../media/email-domain-nslookup-query.png "Screen capture of the example results from an nslookup query to return 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. 
+
+    ![alt text](../media/email-domain-nslookup-spf-query.png "Screen capture of the example results from an nslookup query to return 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.
+
+    ![alt text](../media/email-domain-nslookup-cname-dkim.png "Screen capture of the example results from an nslookup query to return 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,62 @@
+---
+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: dacarte
+services: azure-communication-services
+ms.author: ravi.verma
+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 information outlined in the [Email quota increase request form](https://microsoft-my.sharepoint.com/:w:/p/raviverm/ETwbXkxMGlVBosTGBjnIF-YBxo8YQ8Eb8uI4T7fT44LNzQ?e=oBfQYw). Then submit the information in an incident report at [Create a support ticket](https://azure.microsoft.com/en-us/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)

articles/communication-services/concepts/media/email-domain-nslookup-cname-dkim.png

@@ -921,6 +921,8 @@ items:
       href: concepts/email/email-attachment-allowed-mime-types.md
     - name: Understanding sender reputation
       href: concepts/email/sender-reputation-managed-suppression-list.md      
+    - name: Quota increase for email domains
+      href: concepts/email/.md  
     - name: Pricing
       href: https://azure.microsoft.com/pricing/details/communication-services/
     - name: Domains
@@ -929,6 +931,8 @@ items:
         href: concepts/email/email-domain-and-sender-authentication.md
       - name: Best practices for sender authentication support 
         href: concepts/email/email-authentication-best-practice.md
+      - name: Troubleshooting Domain Configuration issues 
+        href: concepts/email/email-domain-configuration-troubleshooting.md
     - name: Messaging policy
       href: concepts/sms/messaging-policy.md
     - name: Events