Microsoft announced general availability of Reject Direct Send on 16 November 2026 for worldwide Exchange Online tenants. This guide revisits a real-world diagnostic problem through Microsoft's current supported control.
Why an internal-looking email is not necessarily from an internal account
During an October 2026 email investigation, the original message headers showed an anonymous external SMTP hop into Microsoft 365 and failed sender authentication checks. A subsequent gateway hop showed different authentication results. This illustrates why investigators need to distinguish original ingress from later forwarding. The observations were consistent with Direct Send-style spoofing; they did not independently prove mailbox compromise, successful exploitation of a particular configuration, or a completed remediation.
Microsoft introduced Reject Direct Send in public preview in April 2025 and announced general availability for worldwide Exchange Online tenants on 16 November 2026. This article revisits the historical investigation in light of that announcement. GCC High and DoD were not supported at the announcement date.
What Direct Send does
Direct Send allows devices and applications to deliver messages to internal Exchange Online recipients using the tenant's Microsoft 365 mail endpoint over TCP 25 without authenticating to a mailbox. It is not a general-purpose outbound relay. Legacy printers and monitoring applications are common dependencies. Normal inbound filtering still applies.
Distinguish the SMTP envelope sender (P1 MAIL FROM) from the visible message sender (P2 From). RejectDirectSend evaluates P1. It rejects anonymous messages when that domain belongs to the tenant's accepted domains and no qualifying inbound connector identifies the source by sending IP or certificate. It does not independently block every visible From spoof or every attempt to send directly to the Microsoft endpoint. Accepted subdomains are covered when MatchSubDomains is enabled.
Identify legitimate usage before enforcement
In the Exchange admin center, navigate to Reports > Mail flow > Change Optics Report and review the DRS scenario. The report provides example traffic, not a guarantee that every rare or intermittent sender is represented. Review a representative business cycle, including month-end workloads and emergency notifications. If the report is unavailable, record that visibility limitation, review trace samples and ask application owners for corroboration.
Use read-only Exchange Online PowerShell to inventory the current configuration:
Connect-ExchangeOnline
Get-OrganizationConfig | Format-List RejectDirectSend
Get-AcceptedDomain | Select-Object Name,DomainName,DomainType,MatchSubDomains
Get-InboundConnector | Select-Object Name,Enabled,ConnectorType,
SenderDomains,SenderIPAddresses,TlsSenderCertificateName,
RestrictDomainsToIPAddresses,RestrictDomainsToCertificate,RequireTlsAlso review SPF records, known relay hosts, printers, applications, monitoring alerts, third-party gateways and forwarding arrangements. SPF is a useful starting point, not a complete inventory or a substitute for connector attribution.
For each identified legitimate sender, record the business owner, source, envelope domain, frequency, recipient scope, existing connector, replacement option and verification evidence. Do not create broad IP allowlists or trust shared infrastructure without understanding who can send through it.
Choose an appropriate replacement
| Option | Appropriate use | Key dependency |
|---|---|---|
| SMTP submission using modern authentication | Application capable of authenticating | Supported OAuth implementation and authorised mailbox |
| Microsoft 365 SMTP relay | Approved relay/device infrastructure | Appropriate inbound connector and supported hosting scenario |
| Partner inbound connector | Known service sending into the organisation | Validating TLS certificate (preferred) or tightly scoped sending IPs |
| High Volume Email | Eligible internal application notifications | Verify current service support, authentication and limitations |
| Dedicated application email service | Workload cannot use supported Microsoft options | Separate security and delivery design |
Use Microsoft guidance for each option. A connector should assert a known source, not create a general anti-spam bypass. Review Enhanced Filtering for Connectors when a third-party gateway sits upstream.
Verify connector attribution
Collect a known legitimate message ID from a controlled test and inspect trace details:
Get-MessageTraceV2 -MessageId '<actual-test-message-id>' |
Get-MessageTraceDetailV2 | Format-ListCheck the actual routing and attribution details against the intended connector. A successful mailbox delivery alone is not sufficient evidence that the expected connector was used.
Enable rejection in an approved change window
The administrator needs the Organization Configuration role. Capture the existing value and the approved sender inventory before proceeding.
Set-OrganizationConfig -RejectDirectSend $true
Get-OrganizationConfig | Format-List RejectDirectSendAllow up to 30 minutes for propagation, as stated in the GA announcement. A matching rejected message receives SMTP error 550 5.7.68 TenantInboundAttribution. Coordinate verification with sending-system owners, since rejected SMTP transactions may not appear like successfully accepted messages in ordinary message trace results.
Test matrix and business impact
| Scenario | Expected result |
|---|---|
| Approved connector-attributed application | Continues through normal filtering |
| Authenticated user or supported submission flow | Continues, subject to applicable controls |
| Approved legacy device using unauthenticated Direct Send without a matching connector | Rejected if its envelope domain is accepted |
| Controlled negative test using an owned lab domain | Rejected when all control conditions match |
| External legitimate sender using a nonaccepted envelope domain | Not rejected solely by this control; normal filtering applies |
| Message with misleading visible From but a different envelope domain | Not blocked solely by Reject Direct Send; evaluate anti-spoofing controls |
| Message forwarded back from a service that preserves the original accepted envelope sender without SRS | Potential rejection without appropriate attribution |
Run negative tests only in a lab or explicitly authorised environment. Confirm scan-to-email, batch jobs, ticket notifications, mail gateway delivery, disaster-recovery alerts and external forwarding with business owners.
Rollback and ongoing monitoring
For existing tenants where changing the value back is supported, restore the recorded prior setting only if the agreed rollback criteria are met:
Set-OrganizationConfig -RejectDirectSend $false
Get-OrganizationConfig | Format-List RejectDirectSendThis reopens the unauthorised Direct Send path, so treat it as temporary and explicitly risk-accepted. Microsoft is rolling out mandatory rejection for new tenants; do not promise this rollback is always possible. Prefer remediating the specific legitimate sender via a supported method.
Investigation lessons
Review original trusted Received hops, Authentication-Results at the correct boundary, connector attribution, envelope sender and visible From independently. Later SPF or DMARC outcomes do not necessarily establish original sender legitimacy. Correlate with Exchange and Entra audit evidence before asserting account compromise. Keep SPF, DKIM, DMARC, impersonation protection and third-party gateway routing controls in place: Reject Direct Send is complementary.
References
- Exchange Team: Reject Direct Send generally available, 16 November 2026
- Exchange Team: original public preview announcement
- Set-OrganizationConfig
- Microsoft 365 application and device email options
First published 21 November 2026. This article discusses a historical, anonymised scenario. The procedures are intended for authorised review and testing; no specific production change or successful lab test is asserted.