How to Relay Mail Through Microsoft 365 from a Non-Accepted Domain
Question details
The user needs to route outbound emails from an on-premises source via Microsoft 365 when the sender domain is a delegated subdomain or foreign domain not accepted by the tenant.

- Product
- Microsoft 365 / Exchange Online
- Device & OS
- not provided
- Scenario
- Setting up outbound mail relay from an on-premises server through Microsoft 365 using a sender domain that is not verified as an accepted domain.
- Observed behavior
- Microsoft 365 blocks or fails to authenticate outbound relay attempts from non-accepted sender domains unless a supported hybrid or partner connector configuration is implemented.
Ensure you have global administrator or Exchange administrator privileges in Microsoft 365, as well as administrative access to your on-premises Exchange server and valid third-party SSL certificates.
Set Up Certificate-Based Relay in an Exchange Hybrid Environment
Use this method to authenticate an on-premises Exchange server with Microsoft 365 via a shared, verified parent domain using SSL certificates.
Microsoft 365 generally prevents outbound relay from non-accepted sender domains to protect against spam and unauthorized spoofing. To successfully route mail from these domains, you must establish a certificate-based relay.
This requires configuring an on-premises send connector and a corresponding Exchange Online inbound connector that securely authenticates your server's certificate.
Log in to the Microsoft 365 admin center and verify a parent domain that is actively shared between your on-premises Exchange server and the Microsoft 365 tenant.
Open the Exchange Admin Center on your local server. Create a new Send Connector configured to route mail to Exchange Online using TLS encryption and a valid third-party SSL certificate.
In the Microsoft 365 Exchange admin center, navigate to 'Mail flow' > 'Connectors'. Click 'Add a connector' and select the mail flow scenario from 'Your organization's email server' to 'Microsoft 365'.
Configure the new inbound connector to authenticate the connection by strictly matching the subject name or Subject Alternative Name (SAN) on the SSL certificate used by your on-premises Send Connector.

Configure Connectors for Secure Mail Flow with a Partner Organization
Apply this configuration if the mail flow originates from a trusted external partner organization rather than your own internal hybrid infrastructure.
Boost Your Productivity with WPS Office
While Microsoft 365 handles complex server configurations and hybrid mail routing, WPS Office provides a lightweight, highly compatible, and user-friendly alternative for your daily document, spreadsheet, and presentation tasks. Enjoy a familiar interface without the hefty subscription fees.
- 1. Download the Installer: Visit the official WPS website to download the free installation package for your operating system.
- 2. Install WPS Office: Run the downloaded installer and follow the quick on-screen instructions to complete the setup.
- 3. Open and Create: Launch WPS Office to instantly open Microsoft Office documents or start creating new files with ease.

Frequently Asked Questions
Why does Microsoft 365 reject emails sent from a non-accepted domain?
Microsoft 365 requires domains to be added and verified in the tenant as 'accepted domains' to prevent email spoofing and unauthorized relaying (spam). Emails from unverified domains are automatically rejected unless they are routed through a specifically configured, authenticated hybrid connector.
Can I relay mail to arbitrary external addresses like Gmail using a partner connector?
Generally, inbound connectors configured for partner organizations are designed to deliver mail securely to your own internal Microsoft 365 mailboxes. Relaying messages through Microsoft 365 to arbitrary external addresses using a non-accepted domain requires a strictly verified, certificate-based hybrid configuration to authorize the sender.
Do I need a third-party SSL certificate for Exchange Hybrid relay?
Yes. To properly authenticate the on-premises server's identity on the Microsoft 365 inbound connector, you must use a valid SSL certificate issued by a trusted third-party Certificate Authority (CA). Self-signed certificates are not supported for this scenario.




