Fix Microsoft 365 Mail Delivery to On-Premises Addresses in the Same Domain
Question details
The user needs Microsoft 365 to deliver messages to on-premises addresses that share a custom domain with Exchange Online mailboxes.

- Product
- Microsoft 365 Exchange Online
- Device & OS
- not provided
- Scenario
- Some addresses in a custom domain are hosted in Exchange Online, while the remaining addresses are hosted on an on-premises mail server.
- Observed behavior
- Messages sent from Exchange Online to on-premises addresses may fail with an address-not-found error when split-domain mail flow is not configured.
Confirm that the custom domain is verified in Microsoft 365 and identify the on-premises mail server's publicly reachable mail endpoint. You need an administrator account with permission to manage accepted domains and connectors in the Exchange admin center.
Configure an Internal Relay Domain and an Outbound Connector
Use this setup when Exchange Online and an on-premises mail server host different recipients in the same domain.
An internal relay domain allows Exchange Online to route mail for recipients it cannot resolve locally through an appropriate connector. The on-premises server must be able to accept mail for the remaining recipients.
Open the Exchange admin center, go to Mail flow > Accepted domains, select the shared domain, and change its domain type to Internal relay. Save the change.
Go to Mail flow > Connectors and add a connector from Office 365 to your organization's email server. Choose to use it for messages sent to the shared domain and add that domain to the connector's recipient domains.
In the connector setup, route messages through a smart host and enter the public hostname or IP address of the on-premises mail server. Configure the TLS settings to match the server's certificate and capabilities, then validate and save the connector.
On the on-premises mail server and firewall, allow the required SMTP traffic and confirm that the server accepts the shared domain and recognizes its local recipients. Check the routing configuration to avoid sending unresolved messages back to Exchange Online in a loop.
Send a message from an Exchange Online mailbox to a known on-premises recipient. If it fails, open Mail flow > Message trace in the Exchange admin center and inspect the delivery details and error.

Document Your Exchange Mail Flow with WPS Office
WPS Office is a free, lightweight Office alternative with a familiar interface and support for common Microsoft Office formats, making it easy to move existing documents. Use it to document your split-domain configuration; Exchange mail routing must still be configured in Microsoft 365.

Frequently Asked Questions
Why does Exchange Online say an on-premises address does not exist?
If the shared domain is authoritative in Exchange Online, an unresolved recipient can be rejected rather than routed to the on-premises server. Check the domain type under Mail flow > Accepted domains and review the delivery error.
Is changing the domain to internal relay enough?
No. Exchange Online also needs an appropriate outbound connector to route unresolved recipients to the on-premises mail server, and that server must accept the domain and recognize its recipients.
How can I see why a test message failed?
Open the Exchange admin center and go to Mail flow > Message trace. Search for the test message and review its delivery status and error details.
Can WPS Office fix an Exchange Online connector?
No. Configure and troubleshoot Exchange connectors in the Exchange admin center. WPS Office can help you document the settings and test results.




