What you'll learn in this article
- DMARC for Office 365 is configured in your domain’s DNS by publishing a DMARC TXT record.
- Starting with a p=none policy lets you monitor mail flow before moving to stricter enforcement.
- The rua tag allows you to receive aggregate reports that show who is sending mail on your behalf.
- Reviewing reports before moving to quarantine or reject helps protect legitimate mail from disruption.
- Mimecast helps simplify DMARC setup, monitoring, and policy enforcement with better visibility and guided tools.
What is DMARC for Office 365?
DMARC, or Domain-based Message Authentication, Reporting & Conformance, is a protocol for ensuring that email is
sent from legitimate domains. DMARC is one of the most effective ways of protecting against phishing attacks, domain
spoofing and other email-based threats.
DMARC builds on the widely used SPF and
DKIM
protocols for authenticating email. To pass a
DMARC check
, an email must authenticate with SPF and/or DKIM. Additionally, DMARC requires that all the information about the
sender within the message is aligned, which helps to block email where attackers spoof the "From" header of trusted
organizations. Finally, the
DMARC record
stipulates what the recipient of an email should do with the message if authentication fails.
DMARC is an essential tool for organizations using Microsoft Office 365. While DMARC in Office 365 is enabled for
inbound emails by default, organizations that use their own domain must manage DMARC monitoring on their own and
configure their own DMARC records.
How to Configure DMARC in Office 365
Setting up DMARC in Office 365 starts in your domain’s DNS, not inside the Microsoft 365 admin center. The goal is to
publish a DMARC TXT record that tells receiving mail servers how to handle messages that fail authentication and where
to send reporting data.
1. Go to your DNS manager
Open your domain registrar or DNS hosting provider and navigate to the DNS management area for the domain you want to
protect. Create a new TXT record and use:
-
Host/Name: _dmarc.yourdomain.com (or just _dmarc, depending on your provider)
-
TTL: 1 hour (may appear as 3600 seconds)
-
Value: Your DMARC policy string
2. Choose your DMARC policy
The policy is set in the required p= tag and tells receiving servers how to handle messages that fail DMARC. You can
choose from:
-
p=none – monitors email activity without changing delivery behavior
-
p=quarantine – sends failing messages to spam or junk
-
p=reject – blocks failing messages from reaching inboxes
If you are setting up DMARC for the first time, start with p=none. This gives you visibility into your email traffic
before moving to stricter enforcement.
3. Add a reporting address
Use the rua= tag to receive an aggregate DMARC report. These reports show which servers are sending mail on your
behalf and whether
SPF
and DKIM are passing. Example:
-
rua=mailto:reports@yourdomain.com;
You can also send reports to more than one address by separating them with commas.
4. Build and publish the full DMARC record
Combine the required version tag, your policy, and your reporting address in the TXT value field. A simple starting
record looks like this:
-
v=DMARC1; p=none; rua=mailto:reports@yourdomain.com;
Once saved, DNS changes can take time to propagate, and reports may begin arriving within the next few days.
If you want to speed up setup and reduce formatting errors, a
DMARC record generator can help you create a properly structured TXT value before you publish it.
5. Review reports before moving to enforcement
After publishing your record, monitor aggregate reports to confirm that legitimate Microsoft 365 mail and any
third-party senders are authenticating correctly. Once you’ve verified alignment and fixed any issues, you can move
from:
-
p=none → p=quarantine → p=reject
This phased approach helps reduce the chance of legitimate mail being flagged while you strengthen protection against
spoofing.
Regularly reviewing aggregate reports also helps support
DMARC compliance by showing whether your legitimate senders are properly aligned before you move to stricter enforcement.
DMARC tells receiving servers what action you request, but the receiving system still decides how to handle failed
mail. In Microsoft environments, some failed messages may still be treated as spoofed or spam based on Exchange Online
Protection and other filtering logic.
Challenges in Configuring DMARC for Office 365
Unfortunately, implementing and managing DMARC in Office 365 is just as complicated as configuring it for any other
email provider. Because DMARC builds on SPF and DKIM, email administrators must ensure that their
SPF record
and
DKIM record
are up-to-date and properly authorized.
Before establishing and enforcing a
DMARC policy , administrators must identify all the email senders using their domains, including third-parties legitimately sending
email on their behalf. Many organizations have hundreds of domains, including many they aren't aware of. To avoid a
situation where legitimate emails fail the
DMARC test, organizations often spend months monitoring activity and digesting voluminous and complex DMARC reports before
enabling a DMARC reject policy.
There is no native tool for monitoring or managing DMARC in Office 365. For organizations that want to simplify
deployment and streamline management of DMARC, Mimecast offers an easy-to-use solution that integrates easily with
Office 365.
Office 365 and DMARC Analyzer
Mimecast
DMARC Analyzer
is a SaaS-based solution that reduces the cost, complexity and time required to implement and manage DMARC in Office
365. DMARC Analyzer acts as an expert guide, providing step-by-step instructions that help you move toward a reject
policy as quickly as possible.
In contrast to other DMARC solutions, DMARC Analyzer offers simple and effective self-service tools that eliminate the
need for expensive ongoing professional services. DMARC Analyzer enables email administrators to:
- Enjoy 360° visibility and governance across all email channels, providing a more efficient way to shut down
spoofing attempts and monitor the Office 365 environment.
- Easily publish
DMARC records on the gateway with self-service email intelligence tools.
-
Simplify enforcement and monitor ongoing performance with user-friendly alerts, reports and charts.
- Receive personalized DMARC records and reports on spoofing within an Office 365 instance.
Benefits of DMARC Analyzer for Office 365
With DMARC Analyzer, you can monitor and manage DMARC in Office 365 with:
-
SPF, DKIM, and DMARC record check services that help to uncover potential errors in syntax and content that could affect mail delivery.
-
Forensic reports that help to identify and track down the sources of malicious email.
-
A DMARC record setup wizard to create DMARC records.
-
Unlimited users, domains and domain groups to ensure coverage of DMARC authentication.
-
Summary reports for tracking progress that are issued daily, weekly and monthly.
-
Two-factor authentication to improve security.
-
Tools to monitor DNS changes and to receive proactive alerts when a DNS record is altered.
-
Easy-to-read aggregate reports and charts for faster analysis of DMARC performance and enforcement of DMARC
policy.
-
Optional managed services offered by Mimecast specialists with expertise in deployment and project management that
can help to minimize risk and provide the fastest path to DMARC enforcement.
Additional Mimecast solutions for Office 365
Mimecast's solution for managing DMARC in Office 365 is part of a suite of services that help to achieve cyber
resilience for Office 365 by maximizing security, simplifying archiving and ensuring continuity.
Mimecast offers integrated service bundles for Office 365 that are designed for and delivered 100% in the cloud. This
Mimecast Office 365 solution includes:
-
Best-in-breed email and web security for known and advanced threats, including spear-phishing attacks, ransomware,
zero-day attacks, malware, spam and many others.
-
A compliant archive for enterprise information that provides lightning fast search and easy case management for
e-discovery.
-
Perpetual mail storage for instant recoverability.
-
Mail continuity that provides access to live email and archives even during outages.
-
Migration tools that reduce the risk and effort of moving to Office 365.
Conclusion
Configuring DMARC for Office 365 helps reduce spoofing risk and gives you more control over how unauthenticated email
is handled. Starting with monitoring and moving toward stricter enforcement can help you protect your domain without
disrupting legitimate mail.
Mimecast helps simplify DMARC deployment and management with tools that improve visibility, support enforcement, and
make it easier to protect your brand.