Sender Identity

Home · Guides · Microsoft 365

ESP · Microsoft 365

Microsoft 365: selector1, selector2, and Outlook SPF.

22 October 2026

This guide covers Microsoft 365: where to copy SPF and DKIM values, how to publish them at your DNS provider, and how to point DMARC aggregate reports at a mailbox you control—or at Hosted DMARC on Sender Identity.

Before you change DNS

  1. Run the free static audit and keep a copy of the current SPF and DMARC text.
  2. List every system that already sends as this domain (office mail, billing, marketing, tickets).
  3. Prefer one organizational-domain DMARC record. Subdomain records override the org policy when present.

Where to copy the values

  1. Microsoft 365 Defender / Exchange admin → Email authentication / DKIM.
  2. Enable DKIM for the domain. Microsoft gives two CNAMEs: selector1 and selector2 under ._domainkey.
  3. Publish both CNAMEs, then enable signing.
  4. SPF should include include:spf.protection.outlook.com.

Typical DNS shape

TypeName / hostValue / points toNote
TXT@v=spf1 include:spf.protection.outlook.com -allMerge with existing includes; stay under 10 DNS lookups.
CNAMEselector1._domainkeyselector1-brand-example._domainkey.domain.onmicrosoft.comExact target is shown in the admin center.
CNAMEselector2._domainkeyselector2-brand-example._domainkey.domain.onmicrosoft.comKeep both for key rotation.

DMARC aggregate reports

Two workable patterns:

The free audit suggests a starter p=none record for your own mailbox. It never writes p=reject and never points rua at reports.senderidentity.com—that only happens on the paid hosted path.

Verify

  1. Wait for DNS, then run the free audit. Add any unusual DKIM selector under “DKIM selectors” if the default probe list misses it.
  2. Sender Identity’s vendor catalog can label known includes and selectors in paid monitoring; labels never publish DNS for you.
  3. Keep p=none until aggregate reports show only senders you recognize, then stage quarantine and reject in Account.