SPF(supported) (dedicated subdomain) DKIM(recommended)
This article covers the SPF and DKIM authentication processes for Microsoft Dynamics 365 and how they are managed in Valimail Enforce. While only one of the two authentication methods is required for an email to pass DMARC, our recommendation is to configure both whenever possible.
Microsoft Dynamics 365 does not send SPF aligned emails by default.
TABLE OF CONTENTS
- Configuring DKIM authentication for your Microsoft Dynamics 365 emails
- Add a Microsoft Dynamics 365 DKIM key in Enforce
- Configuring SPF authentication for your Microsoft Dynamics 365 emails
Configuring DKIM authentication for your Microsoft Dynamics 365 emails
1. Go to Settings -> Email marketing -> Domain authentication. A list of existing authenticated domains opens.
2. Select New on the command bar to add a new domain. The wizard will guide you through the whole domain authentication process step by step. On the first step you will need to enter the domain name that you want to authenticate and select if it will be used for forms hosting and email sending capabilities.
3. On the next step you will be asked to add your first DNS record, which will check and confirm the ownership of your domain. Use “Copy” buttons to accurately copy the values of TXT record to avoid typos.
4. The next 2 steps will guide you through the setup process of CNAME records (CNAME1 and CNAME2) that stand for DKIM protection functionality. These 2 DKIM CNAME records must be published on your domain's Configuration page in Valimail Enforce.
5. The next step stands for the last required CNAME DNS record, which is for Envelope-From (Return-Path) domain alignment and SPF protection functionality. This last CNAME record needs to be added in your DNS.
6. On the last step you will be able to review and check your published DNS records. After your checkup is finished, select Verify. The system will check and validate all published DNS records and will show you the result summary on the dashboard. If there’s something wrong with your DNS records, you will see which exact record fails on the dashboard.
Here’s an example of an error message that states that TXT Ownership key was not found published in the DNS, which means either the record was not yet published, or it has some mistake/typo.
You can also find the instructions on how to set up DKIM and SPF for Microsoft Dynamics 365, here.
Add a Microsoft Dynamics 365 DKIM key in Enforce
Configuring SPF authentication for your Microsoft Dynamics 365 emails
We encourage you to use the comment section for any useful information about your sending service, such as the name of the service owner, change request ticket numbers, etc.