Email source7 min read · Updated Jun 2026

Configure SPF and DKIM for Microsoft 365

Microsoft 365 (Exchange Online) uses one SPF include and a pair of DKIM CNAMEs that point back into your tenant. Once they are published, you enable DKIM signing in the Defender portal.

Step 1: Authorise with SPF

Authorise Exchange Online with a single include in your SPF record:

TXT
Host@ (yourcompany.com)
Valuev=spf1 include:spf.protection.outlook.com -all
Provider note

If you also send from other services, add their includes to the same record. ClearSPF flattens all of them into one hosted record and keeps it under the 10-lookup limit.

Step 2: Sign with DKIM

Microsoft 365 DKIM uses two CNAME records that delegate signing back to your tenant. Replace yourcompany-com and yourtenant with your real values from the admin center.

  1. 1
    Publish the two CNAME records below at your DNS provider.
  2. 2
    In the Microsoft Defender portal → Email & collaboration → Policies → Email authentication → DKIM, select your domain.
  3. 3
    Toggle Sign messages for this domain with DKIM signatures to Enabled.
CNAME
Hostselector1._domainkey
Points toselector1-yourcompany-com._domainkey.yourtenant.onmicrosoft.com
CNAME
Hostselector2._domainkey
Points toselector2-yourcompany-com._domainkey.yourtenant.onmicrosoft.com
Provider note

Microsoft rotates between selector1 and selector2 automatically. Both CNAMEs must be present for rotation to work. The exact target hostnames are shown on the DKIM page in the Defender portal.

Step 3: Verify alignment in ClearDMARC

Once DNS has propagated, open the Sources view in ClearDMARC. Microsoft 365 should now show PASS · aligned for both SPF and DKIM. If it still shows a fail, the DKIM step usually needs more time or the provider’s wizard hasn’t been marked complete.

Running the full ClearAuth suite? ClearSPF and ClearDKIM host these records for you, so you add Microsoft 365 once in the console and never edit DNS by hand again.

Was this guide helpful?