Microsoft 365 Reject Direct Send is now generally available in Exchange Online. It adds protection against unauthorised email using your organisation’s domain, but legitimate scanners and business applications may need attention before you enable it. Existing organisations must opt in: this announcement does not mean every business’s scan-to-email service has suddenly changed.
Updated 17 November 2026
What has Microsoft changed?
Microsoft announced general availability on 16 November 2026. Reject Direct Send remains off by default for existing organisations. For newly created organisations, Microsoft is rolling out a default-on setting that cannot be disabled; the announcement does not give a completion date.
The control rejects anonymous messages using your own domain in the envelope sender address when they are not attributed to an approved mail-flow connector. That is different from simply checking the sender name displayed in Outlook. See Microsoft’s Reject Direct Send announcement for the scope and rollout details.
Will this stop my scanner or business app sending email?
It depends on how that device or application sends its messages. A scanner that emails documents to colleagues could use Direct Send, authenticated email submission or a connector-based relay. Those are different arrangements, even if they look identical to the person pressing “scan”.
Microsoft’s device and application email guidance distinguishes the main methods:
- Direct Send: unauthenticated delivery to recipients inside your Microsoft 365 organisation. It does not relay messages to external recipients.
- SMTP relay: uses a connector to identify the sending environment and can support internal and external delivery.
- Authenticated submission: sends through a mailbox. Where supported, Microsoft recommends modern authentication using OAuth.
Start by identifying the method in use. Buying a new printer or changing passwords is not a sensible first response to this announcement.
What should businesses check before enabling it?
Our recommendation is to treat this as a small, planned email change with a named owner and a test list. A useful review covers the following:
- List the systems that send email. Include multifunction printers, finance software, website forms, monitoring alerts and supplier-hosted applications. Record who owns each system and who should receive its messages.
- Review recent traffic. Microsoft’s Change Optics Report includes a Direct Send traffic scenario. It provides sample messages to help identify legitimate senders. Use it alongside your inventory; a sample report is not proof that you have found every monthly or occasional job.
- Agree the right sending arrangement. Where a connector is appropriate, have your IT provider check how it identifies the sending system. Microsoft documents certificate and IP-based controls in its mail-flow connector guidance. A connector should describe the intended mail flow, rather than becoming a broad exception for unidentified senders.
- Test real business tasks. Scan a document, trigger a sample application notification and check expected delivery. Include external recipients where the system normally supports them.
- Record and monitor the change. Keep the configuration owner, test results and recovery plan together. Check less frequent processes when they next run.
This is also a useful opportunity to tidy up undocumented accounts and settings as part of your Microsoft 365 governance.
What if scan-to-email has already stopped working?
Ask your IT provider to collect the failure message, sending address, recipient and time of the attempt. Compare a failed task with one that still works. That evidence is more useful than assuming the latest Microsoft announcement caused the fault.
If a change was recently made, check its timing and test results. Avoid making several unrelated changes at once: it makes the cause harder to establish and a successful fix harder to confirm.
Frequently asked questions
Does this block all phishing or spoofed email?
No. It targets this particular own-domain, anonymous sending route. It is one protective layer. Staff still need to recognise suspicious requests, including the kinds of messages discussed in our Microsoft 365 phishing warning.
Is this the same as the retirement of basic authentication?
No. Direct Send and authenticated SMTP submission are different sending methods. Establish which method your application uses before deciding which Microsoft change or migration guidance applies.
Should we enable it straight away?
Review your sending systems first, then agree a controlled change with your IT provider. For a business that depends on emailed invoices, scans or alerts, delivery testing belongs in the plan.
Need help checking Microsoft 365 email?
KES can help you review how your devices and applications use Microsoft 365 and plan the next steps. Explore our Microsoft 365 management support or contact the KES team to discuss your setup.