Sender Integrity Logo

Practical DMARC guide

Setting up DMARC in Microsoft 365: from configuration to control

Written by Patrick

All articles

Your mailboxes run in Microsoft 365. That does not mean every message sent as your domain originates there. A useful DMARC setup starts with your full sending environment and the people responsible for it.

1. Inventory domains, services and ownership

For each domain, list employee email, billing, CRM, marketing and other sending processes. Record an internal owner and a provider contact for every service. Include subdomains.

Ask about processes that do not run every day. Monthly billing may fall outside a short test period. Use the inventory as a validation worklist, not as proof that every source is already configured correctly.

2. Check SPF for the actual sending sources

For a domain sending exclusively through Microsoft 365, the usual SPF configuration includes include:spf.protection.outlook.com. Other services may require a different setup. Do not publish a second SPF record at the same name: review the existing record and required authorizations together.

For each change, ask what problem the authorization addresses. A provider using its own Return-Path may need a different configuration from an extra include on your main domain.

3. Enable DKIM for your own domain

Use the two CNAME targets Microsoft provides for your domain. Retrieve them from your own environment rather than constructing values from an old example. Publish the records, then enable DKIM signing.

Check a received test message to confirm DKIM passes and identify the d= domain. Keep the result together with the date and sending route. This makes the configuration change traceable later.

4. Configure DMARC reporting

DMARC is published as a TXT record under _dmarc for the relevant domain. During an initial inventory, p=none with a working rua destination can support reporting without requesting quarantine or rejection through that policy.

Use a reporting destination you control and can process. Reporting to another domain may require additional authorization. Establish who reviews the reports and follows up on findings before you start.

Sender Integrity Managed combines available DMARC reporting with active RHEVOX analysis, actionable recommendations and guidance on follow-up. RHEVOX operates the platform and provides relevant findings and reporting. Technical implementation is agreed separately.

5. Validate mail streams before changing policy

Test a representative message from each service. Review SPF, DKIM and DMARC results in the Authentication-Results added by the receiving mail provider. Record deviations and ask the owner to confirm the associated source.

Then consider whether quarantine or reject fits your mail flows. Include forwarded messages and mailing lists in that decision. A successful Outlook test does not validate all your other services.

6. Record how you will retain control

Prepare a short handover: approved senders, open actions, owners and arrangements for new services. Validate a new sender before it begins sending production email.

A public DNS scan provides an initial configuration signal. Understanding observed mail streams requires reporting data; deciding on enforcement also requires analysis and validation.

Sources and next steps

Share

Share this insight

Found this useful? Share it with a colleague or your network.

DMARC configured. Who keeps track of what changes?

Sender Integrity Managed combines available DMARC reporting with active RHEVOX analysis, actionable recommendations and guidance on follow-up. RHEVOX operates the platform and provides relevant findings and reporting. Technical implementation is agreed separately.

Sender Integrity Logo