[ Blog ]

Microsoft 365 Direct Send: Check Readiness Before You Block

6 min readBy Team EA

Before switching on Reject Direct Send, find out which legitimate applications depend on it. DMARC reports help identify senders, but Microsoft 365 evidence is needed to assess their readiness.

The short answer: Microsoft 365 can block anonymous messages that use your own domain to email your employees. Review the sending systems and their approved connections first. A healthy DMARC dashboard alone does not prove those messages will keep arriving.

What is Microsoft 365 Direct Send in plain English?

Think of an office scanner emailing a document to an employee. The scanner may send directly to the company's Microsoft 365 mailboxes without signing in to a mailbox. Applications can use this approach too. Microsoft calls it Direct Send. Its device guidance describes Direct Send as an option for sending to recipients inside the organization, rather than relaying mail to external recipients. [1]

The security concern is that a sender outside your organization can attempt to use your domain in a similar way. Reject Direct Send lets administrators block the relevant anonymous traffic. Legitimate senders need an approved route before the change is made. [2]

For a founder, the decision is practical: identify the systems that send important business email before changing the way Microsoft accepts it. Ask who owns each system, how often it sends, and how the team will notice if delivery stops.

What changed in November 2026?

Microsoft announced general availability of Reject Direct Send on 16 November 2026. This is a Microsoft 365 configuration control, rather than a new DMARC DNS tag. [3]

EnvironmentPublished status
Existing Exchange Online worldwide tenantsAvailable; opt-in and off by default.
New tenantsMicrosoft says default-on deployment, without the option to disable, is rolling out. No completion date is specified.
GCC High and DoDNot currently available.

Status reflects Microsoft's 16 November announcement. Confirm the actual setting in your tenant. [3]

What does RejectDirectSend actually check?

The setting evaluates the envelope sender domain, also called the P1 or MAIL FROM domain. It does not use the visible From address as its test. Under the documented conditions, Exchange rejects anonymous incoming messages whose envelope sender uses an accepted domain and whose connection does not match an inbound connector by IP or certificate. [4]

This explains a common troubleshooting mistake: adding an IP to SPF does not create or authenticate a Microsoft connector. Microsoft describes certificate- or IP-based partner connectors as the way to attribute legitimate sources for this control. [2]

Keep your SPF, DKIM and DMARC work in place. Treat connector readiness as a separate question in the change review.

Can DMARC reports show Direct Send traffic?

They can supply clues, but they cannot establish complete Direct Send readiness. Standard DMARC aggregate reports summarize connecting IPs, message counts, authentication results, alignment and DMARC policy outcomes. They do not have dedicated standard fields for the tenant's RejectDirectSend setting, Microsoft connector attribution or error 550 5.7.68. [5]

QuestionWhat a DMARC report establishes
Which sources use our domain?Reported connecting IPs and authentication identities, for traffic covered by reporting receivers.
Does that traffic authenticate?Reported SPF/DKIM results and DMARC alignment.
Is this our scanner or payroll application?Evidence for investigation; business ownership still needs confirmation.
Will Microsoft accept it after we enable blocking?Not established by standard DMARC fields. Check the tenant and sending route.

A DMARC disposition is not a complete inbox-delivery result. Do not label every reported rejection as a Direct Send block or interpret missing report traffic as proof that an attack was stopped. The documentation cited here does not guarantee that every Direct Send rejection appears in aggregate reports. [5]

A practical Direct Send readiness workflow

Use the following workflow to combine domain evidence with a Microsoft 365 investigation. The ownership, approval and monitoring steps are EmailAuth's recommended operating process.

1. Create a sending-system inventory

Start with your DMARC source list and documented applications. Include systems that run infrequently: month-end finance reports, backup alerts and occasional scan-to-email jobs. Record each system's purpose, owner, expected recipients and test contact. An unfamiliar IP is a lead to investigate, not automatic proof of abuse.

2. Collect Microsoft 365 evidence

Review the tenant setting, accepted domains and connectors. In the Exchange admin center, open Reports → Mail flow → Change Optics Report and select the DRS scenario. Use its examples to investigate Direct Send usage. [6]

The report is sampled. Its export currently contains the rows loaded into the table, not necessarily every row for the selected period. Microsoft recommends using Message Trace for additional message details. Avoid declaring a tenant ready simply because one export is empty. [6]

3. Confirm legitimate senders and choose their route

Have the business owner confirm whether each application is still needed. For a legitimate source, review an appropriate certificate- or IP-based connector with the mail administrator. Microsoft's connector guidance explains how connectors secure and control mail flow. Choose the narrowest configuration appropriate to the actual service; a shared infrastructure address is not, by itself, evidence of ownership. [7]

4. Test before approval

Use representative messages from the actual application. Record the message ID, timestamp and intended recipient. Microsoft recommends verifying connector attribution with trace details before enabling the control. Also review forwarding paths: a third party that forwards your mail back without sender rewriting can cause rejection. [3]

5. Enable blocking and monitor business delivery

Agree a change window, named approver and recovery procedure. After activation, ask owners to confirm successful delivery from their systems. Include critical scheduled jobs in follow-up testing. Keep any unresolved sender visible as an open item rather than hiding it behind an overall readiness score.

For MSPs, keep a separate assessment for each tenant. One customer's connector configuration or successful test does not establish another customer's readiness.

How to enable Reject Direct Send in Exchange Online

After preparing the senders, an authorized administrator can connect through Exchange Online PowerShell using modern authentication. With the module installed, load it and sign in: [8]

Import-Module ExchangeOnlineManagement
Connect-ExchangeOnline -UserPrincipalName admin@example.com

Replace the example account with your administrator's account. Check the setting before changing it:

Get-OrganizationConfig | Format-List RejectDirectSend

Enable blocking only after the readiness review:

Set-OrganizationConfig -RejectDirectSend $true

The change requires the Organization Configuration role and can take up to 30 minutes to propagate. Check the setting again afterward. [3]

For an existing tenant where disabling is permitted, the administrator can restore the off setting:

Set-OrganizationConfig -RejectDirectSend $false

Microsoft documents $true as blocking and $false as not blocking. Confirm tenant restrictions before treating this as your recovery plan. [4]

What does error 550 5.7.68 mean?

The relevant rejection includes:

550 5.7.68 TenantInboundAttribution;
Direct Send not allowed for this organization from unauthorized sources

Microsoft documents this response for blocked Direct Send. Investigate the actual sending route and connector attribution before changing DNS records. [2]

Illustrative example: a finance application stops emailing employees after the administrator enables blocking. The team should capture the rejection, identify the application's sending infrastructure, confirm its owner and test the agreed route. Adding unrelated senders to SPF would make the inventory harder to manage without proving that this connection is approved.

Keep the rejection separate from DMARC alignment failures in your incident record. This helps the next administrator understand which control caused the problem and which change restored delivery.

Frequently asked questions

Can we complete the assessment using only DMARC reports?

No. They support source discovery. Tenant settings, connector evidence and delivery testing are needed to complete the assessment. [5]

Is a Direct Send assessment the same as reaching DMARC reject?

No. Track domain authentication and Microsoft connection readiness as separate workstreams. A single green status should not conceal an unfinished review of either.

What if the Microsoft report shows no examples?

Check the period, data availability and the application's actual sending schedule. The Change Optics report is a sample, so an empty view is not a complete mail-flow audit. [6]

Should we give a provider administrator credentials?

Use an agreed authorization process and scoped access appropriate to the work. Begin with a read-only evidence review; approve configuration changes separately. Do not share administrator passwords to obtain an assessment.

Can EmailAuth assess this without a Microsoft connection?

Start a discussion with our team about the evidence available for your environment. Domain reports can support the conversation; a Microsoft readiness conclusion requires additional tenant evidence. A report upload and an authorized tenant connection are different collection methods, and the assessment scope should state which is being used.

Plan your Microsoft 365 readiness review

Before enabling Reject Direct Send, bring your sending-system inventory and available Microsoft reports to an EmailAuth architect discussion. Ask how to assess the evidence, resolve unknown senders and plan approved changes alongside your DMARC enforcement work.

Discuss Microsoft 365 readiness

Request an architect call. Scope and access requirements are agreed before any tenant changes.

[ Email authentication guide ]

Enterprise provenance

Why top financial institutions and governments retired their email security dashboards.

Traditional email authentication platforms sell you a dashboard and ask your engineers to do the labour. In high-stakes environments, manual oversight means delayed enforcement, configuration drift and unmonitored shadow domains.

EmailAuth is the agentic email provenance platform. Our agents enforce p=reject, keep third-party senders aligned and move your domains to full RFC 9989 compliance, the new DMARC standard, with human-in-the-loop auditability.

Governments Large enterprises Tier-1 financial institutions

SaaS · Dedicated tenancy · Air-gapped on-prem · BYOK encryption

[ Keep reading ]

All posts