Microsoft sends DMARC aggregate reports from two services: Outlook.com — the consumer mail of hotmail.com, live.com and outlook.com — and Microsoft 365, which appears in reports as “Enterprise Outlook”. Both arrive from dmarcreport@microsoft.com, typically once a day. Microsoft 365 reports only for organisations whose MX points straight at it, and neither service sends failure reports.
| Reports come from | dmarcreport@microsoft.com |
| Named in the report as | Outlook.com, Enterprise Outlook |
| Covers | Outlook.com (Hotmail, Live) and Microsoft 365 mailboxes |
| Sent | Typically once a day, covering the previous day |
| Attachment | XML, “likely GZIP compressed”, Microsoft says |
| Failure reports | No — aggregate reports only |
| Where these details come from | Microsoft documents what it sends and when. The address and the two org_names are what the reports themselves show; Microsoft’s own sample uses microsoft.com and dmarceng@microsoft.com. |
Read one of its reports
Choose the attachment as it arrived — .zip, .gz or .xml — or paste its XML. It is read here in your browser and sent nowhere: we name the reporter and list every address that sent mail as your domain.
Why Microsoft sends you reports
Because your domain’s DMARC record asks for them. Its rua= tag names an address, and Microsoft sends a report there for each period in which it received mail that used your domain in the From address — your own mail, a service sending for you, and anything forged in your name. Nobody has signed you up to anything: remove rua= and the reports stop.
What is in them
For each sending address, the number of messages, the SPF and DKIM results and whether DMARC passed. “The Subject line contains the destination domain that sent the report (Submitter) and the source domain for the DMARC results (Report Domain).”
The org_name tells you which service saw the mail: Outlook.com for the consumer addresses, Enterprise Outlook for mail received by Microsoft 365 organisations. In the reports we receive, both cover one day from midnight UTC.
Worth knowing
- Microsoft 365 sends reports “as long as the MX record for the Microsoft 365 domain points directly to Microsoft 365” — an organisation behind another gateway, or a hybrid set-up delivering on-premises first, sends none.
- No failure reports from either: “Microsoft 365 doesn’t send DMARC Forensic reports … even if a valid ruf=mailto: address exists”, and for Outlook.com, “We don’t have plans to send RUF.”
- A report arrives only if the service received mail from your domain that day.
Microsoft’s own page for senders →
Questions
What is “Enterprise Outlook” in a DMARC report?
Microsoft 365 — the org_name its reports carry for mail received by business and school mailboxes on Exchange Online. Outlook.com reports cover the consumer addresses.
Why do I get no reports from Microsoft?
Either no Microsoft mailbox received mail from your domain that day, or the recipients’ organisations route mail through another gateway first — Microsoft 365 then sends no reports for them.
Sources
Checked on 26 September 2026 against these official sources:
- Set up DMARC to validate email in Microsoft 365 — learn.microsoft.com
- Strengthening Email Ecosystem: Outlook’s New Requirements for High‐Volume Senders — techcommunity.microsoft.com