AgenorIT
AgenorIT
Cloud Engineering & Security•10 min read

DMARC Setup & Staged Rollout Guide for Microsoft 365 in Australia

GS
Gurinder Singh
Principal Cloud & Software Architect
Published: 2026-11-03
Last Reviewed: 2026-11-03
Rolling out DMARC on Microsoft 365 without blocking legitimate invoices or marketing emails requires a staged four-phase progression: configuring Exchange Online SPF and dual-selector DKIM signing first, publishing DMARC in monitoring mode (p=none), aligning third-party senders like Xero, Mailchimp, and Resend via DKIM or delegated subdomains, and stepping enforcement up to p=quarantine and p=reject.

Every week, Australian small and mid-sized businesses discover that either their outbound invoices are landing in customer junk folders, or external scammers are spoofing their .com.au domain to send fraudulent payment-redirection emails. While Microsoft 365 includes enterprise-grade email authentication capabilities natively in Exchange Online, most tenants only have a basic SPF record configured—leaving DKIM disabled and DMARC either missing entirely or permanently stuck at p=none.

Before editing any live DNS records, run your domain through our free Microsoft 365 Email Security Checker to inspect your current SPF lookup count, Exchange Online DKIM selectors, and DMARC policy, or engage our team for managed Microsoft 365 security hardening.

Key Takeaways

  • Follow a Staged Enforcement Path: Always progress through p=none (monitoring) → p=quarantine → p=reject only after verifying zero legitimate sender failures in your DMARC aggregate (rua) reports.
  • Prioritise DKIM Alignment Over Bloated SPF: Microsoft 365, Xero, Mailchimp, and Resend all support custom DKIM signing (via CNAME records for Microsoft 365, Xero, and Mailchimp, and a TXT record for Resend), which survives email forwarding and avoids breaking the strict RFC 7208 10-DNS-lookup limit on your root SPF record.
  • Isolate Bulk & Transactional Streams on Subdomains: Sending marketing campaigns or application notifications from dedicated subdomains (e.g. news.company.com.au or app.company.com.au) protects your primary corporate domain reputation and gives each service its own independent SPF allowance.
  • Close the Inbound Spoofing Loop: Once p=reject is active, pair it with Exchange Online anti-spoofing policies and impersonation protection as part of your broader Essential Eight in Microsoft 365 & Intune baseline.

1. How SPF, DKIM, and DMARC Alignment Works in Microsoft 365

To pass DMARC, an email must not only pass SPF or DKIM verification—it must pass identifier alignment. That means the domain visible to the recipient in the From: header must match either the Return-Path (envelope sender) domain validated by SPF, or the d= signing domain in the cryptographic DKIM header.

ProtocolDNS Record TypeRole in Microsoft 365Common Failure Mode
SPF (Sender Policy Framework)TXT on @ (root or subdomain)Lists IP ranges and cloud hosts authorised to send mail for the envelope Return-Path domain.Exceeding 10 DNS lookups (PermError), using multiple v=spf1 TXT records, or ending with +all / ?all.
DKIM (DomainKeys Identified Mail)Two CNAME records (selector1._domainkey & selector2._domainkey)Attaches a cryptographic RSA signature (d=yourdomain.com.au) to outbound headers and body content.CNAMEs published in DNS, but DKIM signing never toggled On inside the Microsoft Defender portal.
DMARC (Domain-based Message Authentication)TXT on _dmarcEnforces alignment between the visible From: header and SPF/DKIM, and instructs receivers how to handle failures (none, quarantine, reject).Leaving p=none indefinitely with no rua= mailbox monitoring aggregate XML reports.

2. Phase 1: Establish Your Microsoft 365 SPF and DKIM Baseline

Before turning on DMARC enforcement, confirm that every legitimate email sent directly from Exchange Online passes both SPF and 2048-bit DKIM alignment.

Step 1A: Clean Up Your Root SPF Record

Ensure your root domain has exactly one v=spf1 TXT record. For a domain whose only root-domain sender is Microsoft 365 Exchange Online, the canonical record is:

v=spf1 include:spf.protection.outlook.com -all

Keep your total DNS-querying mechanisms (include, a, mx, ptr, exists, redirect) strictly below 10—ideally at 7 or fewer—so future vendor nested includes never trigger an RFC 7208 PermError.

Step 1B: Publish and Enable Exchange Online DKIM Selectors

New Microsoft 365 domains provisioned since May 2025 use CNAME targets ending in dkim.mail.microsoft rather than the legacy *.onmicrosoft.com format. Because target values vary depending on when your domain was added to the tenant, always copy the exact selector1 and selector2 CNAME values generated for your domain directly from the Microsoft Defender portal (Email authentication settings > DKIM):

Host:  selector1._domainkey.example.com.au
Value: selector1-example-com-au._domainkey.<tenant-guid>.<region>.dkim.mail.microsoft

Host:  selector2._domainkey.example.com.au
Value: selector2-example-com-au._domainkey.<tenant-guid>.<region>.dkim.mail.microsoft

Publish both CNAME records in your DNS provider (with Cloudflare proxy disabled / DNS-only). Once DNS propagates, return to the Microsoft Defender portal (Email authentication settings > DKIM), select your custom domain, and toggle Sign messages for this domain with DKIM signatures to Enabled.


3. Phase 2: Align Third-Party Senders (Xero, Mailchimp, and Resend)

The number-one reason Australian SMBs hesitate to move past p=none is fear of breaking automated invoices from Xero, newsletters from Mailchimp, or transactional website emails from Resend. Here is how to align each platform cleanly:

Xero (Invoices, Statements, and Payroll)

Xero sends emails using its own bounce return-path domain, which means adding Xero to your SPF record does not achieve DMARC SPF alignment. Instead:

  1. Follow the provider's domain authentication guide in Xero to register your sending domain for authenticated email delivery.
  2. Publish the unique DKIM CNAME records provided by Xero in your DNS zone.
  3. Verify the domain inside Xero so every outbound invoice is cryptographically signed with d=yourdomain.com.au, satisfying DMARC via DKIM alignment with zero impact on your SPF lookup budget.

Mailchimp (Marketing & Newsletters)

  1. Follow the provider's domain authentication guide in Mailchimp to authenticate your domain (or preferably a dedicated marketing subdomain such as news.yourdomain.com.au) by publishing the DKIM CNAME records (k2._domainkey and k3._domainkey) supplied in your Mailchimp account.
  2. Do not add include:servers.mcsv.net to your root SPF record unless explicitly required; Mailchimp's domain authentication satisfies DMARC alignment via DKIM signing without consuming root SPF lookups.

Resend (Website Forms & Transactional Notifications)

  1. Configure Resend on a dedicated transactional subdomain (for example, notify.yourdomain.com.au or mail.yourdomain.com.au) rather than your root @ domain.
  2. Publish the resend._domainkey TXT record alongside the dedicated send subdomain MX and SPF TXT records. Because Resend's DKIM key is a TXT record and its SPF record lives on the send subdomain, it uses zero lookups from your root @ SPF budget while achieving full SPF and DKIM alignment.

4. Phase 3: The Staged DMARC Rollout (p=none → quarantine → reject)

Never jump directly to p=reject. Follow this structured progression across four to six weeks:

Note on the pct Tag: While some legacy guides use pct=25 or pct=50 to sample enforcement, the pct tag is being retired in the updated DMARC specification (DMARCbis) and shouldn't be relied on as a primary safeguard. Instead, rely on thorough p=none aggregate report auditing before stepping up to p=quarantine and p=reject.

Stage 1: Monitoring Mode (p=none) — Weeks 1 to 2

Publish a monitoring DMARC record on _dmarc.yourdomain.com.au pointing aggregate reports (rua) to a dedicated DMARC reporting parser or monitoring mailbox:

v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com.au; fo=1; adkim=r; aspf=r;

During these two weeks, zero emails are blocked. Review the daily XML aggregate reports to confirm that Exchange Online, Xero, Mailchimp, Resend, and any scanner/copier or CRM relays are passing DKIM or SPF alignment at 100%.

Stage 2: Partial Quarantine (p=quarantine; pct=25) — Week 3

Once all known legitimate senders pass alignment, step the policy up to quarantine unauthenticated messages into recipient junk folders (bearing in mind that pct is being retired in the updated DMARC spec and shouldn't be relied on):

v=DMARC1; p=quarantine; pct=25; rua=mailto:dmarc-reports@yourdomain.com.au; fo=1; adkim=r; aspf=r;

Stage 3: Full Quarantine (p=quarantine) — Week 4

After seven days with zero false positives in your aggregate reports, enforce full quarantine across all unauthenticated messages:

v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@yourdomain.com.au; fo=1; adkim=r; aspf=r;

Stage 4: Hard Enforcement (p=reject) — Week 5 Onwards

When your aggregate reports confirm that only unauthorised spoofing attempts are failing DMARC, transition to full enforcement:

v=DMARC1; p=reject; rua=mailto:dmarc-reports@yourdomain.com.au; fo=1; adkim=r; aspf=r;

With p=reject active, receiving mail servers reject (bounce) failing mail during the SMTP transaction before spoofed messages can reach a customer, supplier, or employee inbox.


Conclusion & Next Steps

Enforcing DMARC p=reject across Microsoft 365 is one of the highest-leverage security controls an Australian business can implement to prevent brand impersonation and invoice fraud—and when planned properly, it causes zero disruption to your finance or marketing workflows.

Technical FAQ

Frequently Asked Questions

Direct engineering answers to key technical and migration considerations.

Enabling p=reject before auditing DMARC aggregate (rua) reports instructs receiving mail servers to reject (bounce) any email sent on behalf of your domain that fails SPF and DKIM alignment—including legitimate invoices from Xero, CRM notifications, or payroll slips if those platforms have not been cryptographically aligned first.
Modern Xero email authentication uses custom DKIM CNAME records added to your DNS zone rather than a root SPF include, because Xero sends from its own envelope return-path domain. Signing outbound invoices with your domain's DKIM key satisfies DMARC identifier alignment without consuming your 10-lookup SPF limit.
Under RFC 7208 Section 4.6.4, any SPF evaluation requiring more than 10 DNS-querying mechanisms (such as include, a, mx, or ptr) immediately fails with a PermError. To prevent PermError, delegate bulk marketing and transactional senders like Mailchimp or Resend to dedicated subdomains (such as mail.yourdomain.com.au or notify.yourdomain.com.au) and authenticate via DKIM.
Exchange Online uses two CNAME selectors—selector1 and selector2—to perform zero-downtime cryptographic key rotation (including upgrading from 1024-bit to 2048-bit RSA keys). While one selector actively signs outbound mail, the standby selector holds the next key in DNS.
GS

Written by Gurinder Singh

Author

Principal Cloud & Software Architect at AgenorIT. Specialising in Microsoft Azure Landing Zones, Microsoft Entra identity architectures, Microsoft Fabric lakehouses, and high-performance digital products for Australian organisations.

Direct Technical Consultation

Need Senior Architecture Guidance on Your Platform?

Speak directly with an experienced engineer about cloud infrastructure, data pipelines, or software development.

Senior Azure architect & vetted specialistsStrict confidentialityDirect technical scoping