Skip to content

Commit 8dd354a

Browse files
Merge pull request #271702 from vac0224/vc_email_quota_tsg_2024-04-10
Email Quota and Domain Troubleshooting
2 parents 9f51560 + aab7115 commit 8dd354a

File tree

6 files changed

+230
-0
lines changed

6 files changed

+230
-0
lines changed
Lines changed: 127 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,127 @@
1+
---
2+
title: Troubleshooting Domain Configuration issues for Azure Email Communication Service
3+
titleSuffix: An Azure Communication Services concept document
4+
description: Learn about Troubleshooting domain configuration issues.
5+
author: raviverm
6+
manager: daysha-carter
7+
services: azure-communication-services
8+
ms.author: raviverm
9+
ms.date: 04/09/2024
10+
ms.topic: conceptual
11+
ms.service: azure-communication-services
12+
---
13+
# Troubleshooting Domain Configuration issues
14+
15+
This guide describes how to resolve common problems with setting up and using custom domains for Azure Email Communication Service.
16+
17+
## 1. Unable to verify Custom Domain Status
18+
19+
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.
20+
21+
### Reasons
22+
23+
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.
24+
25+
### Steps to resolve
26+
27+
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:
28+
29+
`ms-domain-verification=43d01b7e-996b-4e31-8159-f10119c2087a`
30+
31+
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).
32+
33+
3. Once you add the TXT record, you can query the TXT records for your custom domain.
34+
35+
1. Use the `nslookup` tool from Windows CMD terminal to read TXT records from your domain.
36+
2. Use a third-party DNS lookup tool:
37+
38+
https://www.bing.com/search?q=dns+lookup+tool
39+
40+
In this section, we continue using the `nslookup` method.
41+
42+
4. Use the following `nslookup` command to query the TXT records:
43+
44+
`nslookup -q=TXT YourCustomDomain.com`
45+
46+
The `nslookup` query should return records like this:
47+
48+
![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.")
49+
50+
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.
51+
52+
## 2. Unable to verify SPF status
53+
54+
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.
55+
56+
1. Copy your SPF record from [Azure portal](https://portal.azure.com). Your SPF record should look like this:
57+
58+
`v=spf1 include:spf.protection.outlook.com -all`
59+
60+
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).
61+
62+
4. Once you add the SPF record, you can query the SPF records for your custom domain. Here are two methods:
63+
64+
1. Use `nslookup` tool from Windows CMD terminal to read SPF records from your domain.
65+
2. Use a third-party DNS lookup tool:
66+
67+
https://www.bing.com/search?q=dns+lookup+tool
68+
69+
In this section, we continue using the `nslookup` method.
70+
71+
5. Use the following `nslookup` command to query the SPF record:
72+
73+
`nslookup -q=TXT YourCustomDomain.com`
74+
75+
This query returns a list of TXT records for your custom domain.
76+
77+
![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.")
78+
79+
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.
80+
81+
7. Check for `-all` in your SPF record.
82+
83+
If your SPF records contain `~all` the SPF verification fails.
84+
85+
Azure Communication Services requires `-all` instead of `~all` to validate your SPF record.
86+
87+
88+
## 3. Unable to verify DKIM or DKIM2 Status
89+
90+
If Azure Email Communication Service fails to verify the DKIM or DKIM2 status, follow these steps to resolve the issue.
91+
92+
1. Open your command prompt and use `nslookup`:
93+
94+
`nslookup set q=TXT`
95+
96+
2. If DKIM fails, then use `selector1`. If DKIM2 fails, then use `selector2`.
97+
98+
`selector1-azurecomm-prod-net._domainkey.contoso.com`
99+
100+
`selector2-azurecomm-prod-net._domainkey.contoso.com`
101+
102+
3. This query returns the CNAME DKIM records for your custom domain.
103+
104+
![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.")
105+
106+
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.
107+
108+
If the DKIM/DKIM2 CNAME records are missing from `nslookup` output, then Azure Email Communication Service can't verify the DKIM or DKIM2 status.
109+
110+
For a list of providers, see [CNAME records](../../quickstarts/email/add-custom-verified-domains.md#cname-records).
111+
112+
113+
114+
## Next steps
115+
116+
* [Email domains and sender authentication for Azure Communication Services](./email-domain-and-sender-authentication.md)
117+
118+
* [Quickstart: Create and manage Email Communication Service resource in Azure Communication Services](../../quickstarts/email/create-email-communication-resource.md)
119+
120+
* [Quickstart: How to connect a verified email domain with Azure Communication Services resource](../../quickstarts/email/connect-email-communication-resource.md)
121+
122+
## Related articles
123+
124+
- [Email client library](../email/sdk-features.md)
125+
- [Add custom verified domains](../../quickstarts/email/add-custom-verified-domains.md)
126+
- [Add Azure Managed domains](../../quickstarts/email/add-azure-managed-domains.md)
127+
- [Quota increase for email domains](./email-quota-increase.md)
Lines changed: 99 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,99 @@
1+
---
2+
title: Quota increase for Azure Email Communication Service
3+
titleSuffix: An Azure Communication Services concept document
4+
description: Learn about requesting an increase to the default limit.
5+
author: raviverm
6+
manager: daysha-carter
7+
services: azure-communication-services
8+
ms.author: raviverm
9+
ms.date: 04/09/2024
10+
ms.topic: conceptual
11+
ms.service: azure-communication-services
12+
---
13+
# Quota increase for email domains
14+
15+
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.
16+
17+
## 1. Understand domain reputation
18+
19+
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:
20+
21+
* The volume and frequency of your email campaigns.
22+
* 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.
23+
* The feedback and complaints from your recipients. A high complaint rate can severely harm your sender reputation.
24+
25+
## 2. Use a custom domain instead of an Azure Managed Domain
26+
27+
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.
28+
29+
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.
30+
31+
For more information, see [Service limits for Azure Communication Services](../../concepts/service-limits.md#email).
32+
33+
## 3. Configure a mail exchange record for your custom domain
34+
35+
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.
36+
37+
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.
38+
39+
## 4. Build your sender reputation
40+
41+
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.
42+
43+
## 5. Request an email quota increase
44+
45+
To request an email quota increase, compile the following information:
46+
47+
```
48+
Customer Information
49+
Company name:
50+
Company website:
51+
Please provide a brief description of your business:
52+
53+
Email Service Information
54+
Subscription ID:
55+
Azure Communication Services Resource Name:
56+
Is your custom domain already set up and currently used for sending messages:
57+
Indicate the domain from which you are currently sending emails:
58+
59+
Usage Information
60+
1. What type of emails do you send? (such as Transactional, Marketing, Promotional)
61+
2. Please specify the expected volume of emails you plan to send:
62+
- What is the maximum rate of messages per minute that you require?
63+
- What is the maximum rate of messages per hour that you require?
64+
- What is the maximum rate of messages per day that you require?
65+
66+
Additional Information
67+
What is the source of the email addresses that you use for sending your messages?
68+
Note: The source of the email addresses that you send your messages to plays a crucial role in the
69+
effectiveness and compliance of your email marketing campaigns. Providing details about the source
70+
of your email addresses helps us understand how you acquire and maintain your subscriber list.
71+
72+
How do you currently manage and remove email addresses that have unsubscribed or resulted in
73+
bounce backs from your mailing list?
74+
Please explain if you have an automated process in place that handles unsubscribes when recipients
75+
click on the 'unsubscribe' link in your emails. Additionally, if you receive bounce/undeliverable
76+
notifications, can you include how you handle those and whether you have any mechanism to
77+
automatically remove email addresses that result in consistent bounces.
78+
```
79+
80+
You can copy this text to a file and add the requested information.
81+
82+
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.
83+
84+
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.
85+
86+
## Next steps
87+
88+
* [Email domains and sender authentication for Azure Communication Services](./email-domain-and-sender-authentication.md)
89+
90+
* [Quickstart: Create and manage Email Communication Service resource in Azure Communication Services](../../quickstarts/email/create-email-communication-resource.md)
91+
92+
* [Quickstart: How to connect a verified email domain with Azure Communication Services resource](../../quickstarts/email/connect-email-communication-resource.md)
93+
94+
## Related articles
95+
96+
- [Email client library](../email/sdk-features.md)
97+
- [Add custom verified domains](../../quickstarts/email/add-custom-verified-domains.md)
98+
- [Add Azure Managed domains](../../quickstarts/email/add-azure-managed-domains.md)
99+
- [Troubleshooting Domain Configuration issues](./email-domain-configuration-troubleshooting.md)
86.1 KB
Loading
38.7 KB
Loading
66.7 KB
Loading

articles/communication-services/toc.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -961,6 +961,8 @@ items:
961961
href: concepts/email/email-optout-management.md
962962
- name: Understanding sender reputation
963963
href: concepts/email/sender-reputation-managed-suppression-list.md
964+
- name: Quota increase for email domains
965+
href: concepts/email/email-quota-increase.md
964966
- name: Pricing
965967
href: https://azure.microsoft.com/pricing/details/communication-services/
966968
- name: Domains
@@ -969,6 +971,8 @@ items:
969971
href: concepts/email/email-domain-and-sender-authentication.md
970972
- name: Best practices for sender authentication support
971973
href: concepts/email/email-authentication-best-practice.md
974+
- name: Troubleshooting Domain Configuration issues
975+
href: concepts/email/email-domain-configuration-troubleshooting.md
972976
- name: Messaging policy
973977
href: concepts/sms/messaging-policy.md
974978
- name: Events

0 commit comments

Comments
 (0)