In April 2025, we introduced the Reject Direct Send setting in Public Preview to give Exchange Online admins a way to block unauthenticated Direct Send traffic that uses their own domains. Today, we’re pleased to announce that Reject Direct Send is now Generally Available for Exchange Online worldwide tenants.
Thank you to everyone who enabled the setting during Public Preview and shared feedback through the blog comments, the feedback mailbox, support and our MVP community. Your feedback shaped the improvements we made ahead of GA, including the Change Optics Report, which is now also Generally Available.
Customers have already embraced the setting: more than 70,000 organizations have enabled Reject Direct Send to add an extra layer of protection to the organizations.
What is Direct Send?
Direct Send is a method used to send email directly to an Exchange Online organization’s hosted mailboxes from on-premises devices, applications or third-party cloud services using the organization’s own accepted domain. It requires no authentication, as it mimics anonymous inbound mail from the internet apart from the sender domain. Many organizations have no need for it, which makes it an unnecessary avenue for spoofing their own domains. For more background, see Direct Send vs sending directly to an Exchange Online tenant.
What does Reject Direct Send do?
When enabled, Reject Direct Send blocks messages sent to your organization anonymously using an address in one of your accepted domains. Key points:
- Only the P1 MAIL FROM (envelope sender) address is evaluated. The P2 From header is not checked.
- “Anonymous” means the message is not attributed to any mail flow connector.
- Subdomains are included if the accepted domain has “Accept mail for all subdomains” enabled (MatchSubDomains = True).
- It works regardless of where your MX record points.
- It is one layer of protection. Spoofing of domains you don’t own is not Direct Send and continues to be handled by existing anti-spoofing protections.
Rejected messages receive the following response:
550 5.7.68 TenantInboundAttribution; Direct Send not allowed for this organization from unauthorized sources
What’s changed since Public Preview
- Visibility of Direct Send traffic: The Change Optics Report in the Exchange admin center (Reports > Mail flow > Change Optics Report) shows example Direct Send messages received by your organization in the DRS (Direct Send traffic) scenario, so you can identify legitimate senders before you enable the setting. The report is now Generally Available. See [Change Optics Report GA blog link].
- Azure Communication Services: The known issue affecting Azure Communication Services (ACS) Email has been resolved.
- Clarified documentation: FAQs covering subdomains, required permissions, connector attribution and third-party MX scenarios.
Secure by default for new tenants
As shared during Public Preview, we plan to enable Reject Direct Send by default for new Exchange Online tenants, without the option to disable it, as part of our commitment to making organizations secure by default. This is being rolled out at the time of publishing.
Before you enable Reject Direct Send as an existing tenant
- Review the DRS scenario in the Change Optics Report to find the devices, applications and services sending Direct Send traffic to your organization. Your domains’ SPF records are another good place to start.
- For each legitimate sender, create a partner inbound connector that matches its TLS certificate (recommended) or its sending IP addresses. See Configure mail flow using connectors in Exchange Online[https://learn.microsoft.com/en-us/exchange/mail-flow-best-practices/use-connectors-to-configure-mail-flow/use-connectors-to-configure-mail-flow].
- Confirm that messages from each partner are attributed to the connector, for example by running:
Get-MessageTraceV2 -MessageId "<message ID>" | Get-MessageTraceDetailV2 | Format-List
- If a vendor has neither static IPs nor a dedicated certificate, consider a mail flow rule with an exception (for example, a unique X-header) instead of the org-wide setting.
How to enable the setting
The setting remains opt-in and off by default for existing tenants. An admin with the Organization Configuration role can enable it with:
Set-OrganizationConfig -RejectDirectSend $true
Changes propagate across the service within 30 minutes. To check the current value:
Get-OrganizationConfig | Format-List RejectDirectSend
Known issue: third-party forwarding without SRS
If someone in your organization sends a message to a third party who forwards it back to your organization, and the third party’s email provider does not support Sender Rewriting Scheme (SRS), the message returns with your original sender address. These messages already fail SPF today; with Reject Direct Send enabled and no partner connector in place, they will be rejected.
Availability
Reject Direct Send is Generally Available for Exchange Online tenants in the worldwide environment. It is not currently available for GCC High and DoD environments.
Microsoft 365 Messaging Team