Configure Microsoft 365 Mail Routing to an Internal Postmaster
Question details
Configure Microsoft 365 to route messages for users who have not migrated to an existing mail server.

- Product
- Microsoft 365 Exchange Online
- Device & OS
- not provided
- Scenario
- An organization is migrating selected mailboxes to Microsoft 365 while keeping other recipients on a third-party provider or internal postmaster server.
- Observed behavior
- Mail for migrated users should reach their Microsoft 365 mailboxes, while mail for other users should be routed to the existing mail server.
Identify the shared email domain and the public smart host name or IP address that accepts mail for unmigrated users. Confirm that the receiving server accepts inbound SMTP from Microsoft 365 and determine its TLS requirements.
Route Unmigrated Recipients Through an Exchange Online Connector
Use an internal relay domain and an outbound connector when Microsoft 365 and another mail system share an email domain.
With an internal relay domain, Exchange Online can route messages for recipients it does not resolve locally to another mail system. Make sure the downstream server does not send those messages back to Microsoft 365, which could create a mail loop.
In the Exchange admin center, go to Mail flow > Accepted domains, select the shared domain, and set its domain type to Internal relay.
Go to Mail flow > Connectors and select Add a connector. Set the connection from Microsoft 365 to your organization's email server, then follow the wizard to route messages for the shared domain through the connector.
In the connector wizard, choose routing through a smart host and enter the receiving server's public hostname or IP address. Configure TLS to match the receiving server's capabilities and certificate requirements.
Use the connector wizard's validation option, then send test messages to both a migrated mailbox and an unmigrated recipient. In Mail flow > Message trace, check the delivery path and investigate any failures.
Check the domain's MX record and Mail flow > Rules alongside the downstream server's routing configuration. Ensure the intended system receives incoming mail and that unresolved messages cannot loop between servers.

Use WPS Office for Documents During Your Microsoft 365 Migration
WPS Office is a free, lightweight alternative with a familiar interface for working with office files during a migration. It does not configure Exchange connectors or route email.

Frequently Asked Questions
Why should the shared domain be set to internal relay?
An internal relay domain allows Exchange Online to route mail for recipients it does not resolve locally to another mail system. Set it in Exchange admin center under Mail flow > Accepted domains, and configure a matching outbound connector.
What address should I enter as the smart host?
Enter the public hostname or IP address of the server that accepts SMTP mail for the unmigrated recipients. Confirm that it accepts connections from Microsoft 365 and supports the TLS settings selected in the connector.
Do I need to change my MX record?
Not necessarily. The MX record determines where external senders deliver mail first, so review it against your migration design before making changes. Ensure the first receiving system can route mail to both migrated and unmigrated users.
How can I check whether a message reached the downstream server?
Send a test message to an unmigrated recipient, then open Exchange admin center > Mail flow > Message trace. Review the trace for routing and delivery status, and check the downstream server's logs if needed.




