SPF, DKIM, and DMARC for Microsoft 365
Configure Microsoft 365 authentication.
Microsoft 365 domains typically use SPF plus two DKIM CNAME records from the Microsoft Defender or Exchange admin experience.
What this helps you do
Microsoft 365 domains typically use SPF plus two DKIM CNAME records from the Microsoft Defender or Exchange admin experience.
Recommended workflow in Outlio
Add or merge SPF with include:spf.protection.outlook.com.
Open the Microsoft DKIM settings for your domain.
Create the two DKIM CNAME records Microsoft provides.
Enable DKIM signing after records resolve.
Add DMARC at _dmarc and run Outlio Test Domain Setup.
Quality checks
- Microsoft DKIM often fails until both selectors resolve.
- Use the exact domain-specific CNAME targets from Microsoft.
- If the domain was recently added to Microsoft 365, give provisioning time to finish.
Common mistakes to avoid
- Using TXT records when Microsoft asked for CNAME records.
- Forgetting to enable DKIM after DNS is added.
Done well, this should leave you with
A cleaner Outlio setup, fewer avoidable campaign issues, and a more reliable path from setup to replies.
Related articles
Why do I need DNS records?
Understand SPF, DKIM, DMARC, MX, and tracking records.
How to setup MX, SPF, DKIM, DMARC
Step-by-step DNS setup for sending domains.
SPF, DKIM, and DMARC for Google Workspace
Configure Google Workspace authentication for outreach.
Namecheap DNS with Google Workspace
Add Google Workspace records in Namecheap.
Namecheap DNS with Microsoft 365
Add Microsoft 365 records in Namecheap.
GoDaddy DNS with Google Workspace
Set up Google authentication records in GoDaddy.
Was this article helpful?
Need more help? Contact Support