Email senders
Microsoft Dynamics 365 DMARC setup: DKIM and Return-Path
How Customer Insights - Journeys authenticates your domain with one TXT and three CNAME records, and what breaks DMARC alignment in Dynamics 365.
SPF include for Microsoft Dynamics 365
Microsoft Dynamics 365 does not need an SPF include on your domain.
DKIM for Microsoft Dynamics 365
- Selectors
- Microsoft Dynamics 365 does not document this.
- How to enable it
- Two CNAME records on each sending domain, created in the Customer Insights - Journeys domain authentication wizard. Copy the values the wizard shows for your domain.
Microsoft Dynamics 365 signs with your domain
Envelope-from and SPF alignment
SPF counts for DMARC only when this domain matches the domain in your From address. If it is Microsoft Dynamics 365’s own domain, SPF can pass without aligning, and DMARC then depends on an aligned DKIM signature.
- Envelope-from (Return-Path)
- A CNAME on your domain. Copy the target the domain authentication wizard shows.
Sending ranges of Microsoft Dynamics 365
Use these to recognize Microsoft Dynamics 365 in your reports. They change over time, so do not copy them into your SPF record.
Microsoft Dynamics 365 does not document this.
Does your domain authorize Microsoft Dynamics 365?
Enter your domain. The SPF Checker reads your record and names the senders it authorizes.
Microsoft Dynamics 365 documentation
- Microsoft Learn: Authenticate your domains
- checked 2026-11-09
- Microsoft Learn: Best practices for email marketing
- checked 2026-11-09
- Microsoft Learn: Set the sender, receiver, language and legal designation for a message
- checked 2026-11-09
- Microsoft Learn: Server-side synchronization between customer engagement apps and email servers
- checked 2026-11-09
- Microsoft Learn: Connect to Exchange Online
- checked 2026-11-09
How it authenticates
Microsoft Dynamics 365 DMARC alignment starts in Customer Insights - Journeys, the marketing app, under Settings > Email marketing > Domain authentication. The wizard gives you four DNS records for each domain you send from.
One TXT proves domain ownership. Two CNAMEs point to DKIM public keys for signature verification. The third CNAME sets the bounce Return-Path so SPF aligns with From.
Copy both DKIM CNAME names and values from your domain authentication wizard; selectors shown for another domain are examples. Microsoft calls DKIM extra important when your domain uses DMARC.
The wizard does not create DMARC. Preserve existing policy and report addresses; only if absent, publish a monitoring TXT at _dmarc:
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Dynamics 365 Sales and Customer Service work differently. When a mailbox uses server-side synchronization, their mail is submitted to the email service set for that mailbox, such as Exchange Online, so check authentication there. The Microsoft 365 guide covers that path.
What to watch for
New environments include a domain ending in dyn365mktg.com, meant for testing only. If a user's address is on a domain you have not authenticated, Dynamics rewrites the From address to an authenticated domain. Microsoft warns the result probably isn't a valid return address.
Authenticate the exact domain in your From address. The wizard treats example.com and www.example.com as separate domains.
Your root SPF record usually needs no change. Microsoft offers an optional include for the few receivers that check SPF against the From address. Use the envelope-from value from your own registration and merge it into your one SPF record, because two records make SPF fail. Microsoft's article prints a space after include:, but SPF syntax has none.
If a CNAME already sits on the domain, the ownership TXT record cannot be added there. Microsoft's alternative is a TXT record on dynmktown.example.com.