StrategyCore
Back to Resources
10/cybersecurity 2 min read

DMARC evaluation for organisations using Microsoft 365

Check the whole sending estate, including custom domains and applications outside the tenant.

An organisation’s Microsoft 365 subscription does not establish that every service sending as its domains is correctly authenticated. A useful evaluation covers the tenant, custom domains, third-party applications and indirect mail flows. It also distinguishes the organisation’s own controls from Microsoft’s separate requirements for senders to Outlook.com consumer accounts.

Microsoft 365 authentication review

SC-FL-04 · REV A · 2026.07

01Sender inventory

tenant and applications

02Domain configuration

SPF / DKIM

03Message tests

DMARC alignment

04Change monitoring

delivery and ownership

A tenant subscription is not evidence that every external sender is aligned.

Inventory sending services, configure custom-domain authentication, test messages and monitor changes.
01

Map domains and sending services

List the organisation’s custom domains, Microsoft 365 tenants, application relays, marketing systems and outsourced senders. Identify which system controls each DNS record and DKIM setting. Mail observed in a tenant is useful evidence, but it may not cover a separate service sending directly to external recipients.

02

Verify alignment in real messages

Follow Microsoft’s current guidance for SPF, DKIM and DMARC. Confirm that the domain in the visible From address aligns with an authenticated SPF or DKIM domain. A generic service signature is not evidence of alignment with the organisation’s custom domain. Test representative messages and inspect authentication results rather than relying on the presence of DNS records alone.

03

Check forwarding and receiver rules

Forwarding and mailing lists can affect authentication, so include them in testing before changing the domain’s DMARC policy. Microsoft’s May 2025 high-volume sender announcement concerns Outlook.com, Hotmail.com and Live.com consumer addresses. It is not a statement that every Microsoft 365 tenant must publish p=reject. Check current receiver guidance and the DMARC standard separately.

04

Review additional reporting integrations

A mailbox connector can add visibility, but it also creates an integration to administer. Valimail’s current Microsoft connector documentation describes a component running inside the organisation’s Azure tenant, with tenant-wide consent and an Azure subscription. Confirm the connector version, permissions, data flows, Azure cost owner and removal procedure. Do not reuse privacy claims from an older connector without checking the current design.

Sources and further reading

// Key Takeaways

What to remember

  • Test custom-domain alignment for every legitimate sending service.
  • Outlook.com consumer-sender rules have a specific scope.
  • Review the current connector’s permissions, architecture and operating costs.

// FAQ

Frequently asked questions

Q1

Does Microsoft 365 automatically cover third-party senders?

No. Applications and outsourced services sending as the customer’s domain need their own authentication and alignment checks. Inventory them alongside the tenant’s mail flows.

Q2

Is the current Valimail Microsoft connector just a read-only SaaS login?

Its current documentation describes deployment in the customer’s Azure tenant, tenant-wide administrator consent and Azure subscription requirements. Review the actual requested permissions, component version and cost before approving it.

Last updated:

Support Microsoft 365 authentication discussions in Japan.

Tell us how your product works with Microsoft 365, external senders and DNS. StrategyCore can coordinate technical questions with Japanese prospects and their Microsoft partners, then agree proposals, licensing and support responsibilities.