Skip to content
TrustList
News

Exchange Online can now reject spoofed Direct Send mail for good

Editorial

By TrustList Editorial

More than 70,000 organisations turned the setting on in preview; it stays off by default for existing tenants, while new ones get it with no way to switch it off.

About Exchange Online can now reject spoofed Direct Send mail for good

Exchange Online can now reject spoofed Direct Send mail for good

16 November 2026: Microsoft has made Reject Direct Send generally available for Exchange Online worldwide tenants, giving administrators a supported way to refuse mail that claims to come from their own domain but arrives without passing through any connector. Existing tenants must switch it on themselves, and Microsoft is making it permanent for new tenants, who will not be able to disable it.

Not yet independently verified. The details are from the Exchange Team's blog post of 16 November 2026. Microsoft says the forced default for new tenants was rolling out at the time of publishing, without a completion date, and the post speaks only of worldwide tenants, so government and sovereign clouds are not confirmed. We did not test the setting. We will update this when it can be confirmed, and remove this note.

The gap it closes

Direct Send lets a device or application deliver mail straight to a tenant's Exchange Online endpoint, using one of the tenant's own addresses as the sender, with no authentication. Printers and scanners rely on it. So do attackers, who use it to send phishing mail that appears to come from a colleague.

With the setting on, Exchange Online rejects messages that are sent anonymously, meaning they are not attributed to any mail flow connector, and that use an address in one of the tenant's accepted domains. The check is made on the envelope sender, the MAIL FROM address, and not on the From header a reader sees. Subdomains are included when the accepted domain is set to accept mail for all subdomains, and the rule applies wherever the domain's MX record points.

Rejected mail is returned with the error "550 5.7.68 TenantInboundAttribution; Direct Send not allowed for this organization from unauthorized sources".

The feature entered public preview in April 2025, and Microsoft says more than 70,000 organisations enabled it before general availability.

Switching it on without breaking the scanner

For existing tenants the setting "remains opt-in and off by default". An administrator with the Organization Configuration role enables it with one PowerShell command, Set-OrganizationConfig -RejectDirectSend $true, and the change takes effect within 30 minutes.

The work is in the preparation. Microsoft's post sets out the order:

  • Open the Change Optics Report, now also generally available in the Exchange admin centre under Reports and Mail flow, which shows examples of the Direct Send messages the tenant currently receives.
  • Review the domain's SPF record.
  • Create a partner inbound connector for each legitimate sender, such as a scanner, a line-of-business application or a third-party service, identified by TLS certificate where possible or by sending IP address.
  • Confirm with message trace that those senders are now attributed to their connector.

A forwarding case that still fails

Microsoft lists one known issue. When a user sends mail to an outside party whose system forwards it back without rewriting the sender address, the message returns bearing the tenant's own address and can be rejected. Such messages already fail SPF, so the cause lies with the forwarding service, but help desks will see the complaint. A problem with Azure Communication Services email seen during the preview has been resolved.

New tenants get no choice

Microsoft says it plans "to enable Reject Direct Send by default for new Exchange Online tenants, without the option to disable it", and that the rollout was under way when the post was published. A company setting up a new tenant, or a managed service provider creating them for clients, should assume from now on that devices need a connector from the first day.

Protection of this kind is otherwise bought from a gateway vendor: our email security software category lists 11 products. This one is a setting in a service the organisation already pays for, and Microsoft has given no date for making it the default in existing tenants.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in