This guide outlines the process for enabling Reject Direct Send in Exchange Online. Since the source excerpt is unavailable, specific configuration steps and PowerShell commands cannot be provided here. Administrators should refer to official Microsoft documentation for accurate implementation details to secure their tenant.
Applies to: Reject Direct Send Exchange Online. Checked: 18 November 2026.
Before you start
Before you begin, confirm that your tenant is eligible for the Reject Direct Send feature. Eligibility details are typically outlined in Microsoft’s official documentation, so review those resources first.
Make sure you have the appropriate administrative permissions in Exchange Online. You’ll need to be a member of the Exchange Administrator role or have equivalent rights to modify mail flow settings.
Because the source excerpt is not available, the exact list of prerequisites is not included here. Refer to Microsoft’s guidance for a complete set of requirements.
Understanding the Feature
You can see that Reject Direct Send is designed to block unauthenticated email traffic.
It helps protect against email spoofing and unauthorized access, which strengthens your organization’s security posture.
When enabled, the feature rejects email messages that lack proper authentication, preventing spoofed senders from reaching your inboxes.
This adds a layer of defense against phishing and other email‑based attacks.
You should review the official Microsoft documentation to understand the exact configuration steps and any prerequisites before enabling the feature.
This will ensure your tenant is properly secured.
Configuration Steps
Begin by opening the Exchange Admin Center (EAC) or launching a PowerShell session connected to your Exchange Online tenant.
Because the exact command syntax is not included in the source, you will need to follow the step‑by‑step instructions provided in Microsoft’s official documentation.
Typical actions include locating the setting for Reject Direct Send and toggling it on, then saving the changes. If you prefer PowerShell, you would run the appropriate cmdlet after connecting to Exchange Online.
After applying the configuration, confirm the change by sending a test message from an unauthenticated source and verifying that it is rejected.
Verification
After enabling Reject Direct Send, you should test the setting by sending unauthenticated emails. Use a non‑licensed test account or a mailbox without proper authentication to send a message without credentials. Review the mail flow logs to confirm that direct send attempts are being rejected. Look for log entries that indicate a rejection of unauthenticated send attempts. [SCREENSHOT: verification dashboard] If the expected rejections are not seen, consult the official documentation for detailed verification steps and additional troubleshooting guidance.
If that didn’t work
If you are still receiving unauthenticated emails after enabling the feature, you should investigate your current mail flow configuration. Start by checking for any conflicting email flow rules or connectors that might be bypassing the security settings.
Next, review the Exchange Online logs to identify specific error messages associated with rejected or accepted emails. These logs provide the necessary data to determine why the Reject Direct Send setting is not behaving as expected.
Because the source documentation is currently unavailable, specific troubleshooting commands or step-by-step recovery procedures cannot be provided at this time. You should verify your settings against the official guidance at Microsoft Tech Community.
FAQ
What is Reject Direct Send?
It is an Exchange Online feature that blocks unauthenticated email traffic, helping to prevent spoofing and unauthorized access to your tenant.
Who should enable this feature?
Exchange Online administrators and IT security teams looking to enhance their tenant’s security posture against unauthenticated email attempts.
Is the source excerpt available?
No, the source excerpt is not available. Therefore, specific details from the provided data cannot be included in this guide.
Sources
- https://techcommunity.microsoft.com/t5/exchange-team-blog/reject-direct-send-now-generally-available-in-exchange-online/ba-p/4573787 (official page, listed in the topic evidence, not fetched)
