How to Fix Hybrid Exchange Mail Not Reaching On-Premises Mailboxes
Question details
Incoming emails fail to reach on-premises Exchange users after configuring Microsoft 365 hybrid mail flow, despite message traces reporting successful delivery.
- Product
- Microsoft Exchange
- Device & OS
- not provided
- Scenario
- Configuring a Microsoft 365 hybrid mail flow while user mailboxes are still retained on-premises.
- Observed behavior
- Incoming emails stop reaching the on-premises mailboxes, even though the Microsoft 365 message trace indicates the messages were delivered successfully.
Ensure you have administrative access to both your Microsoft 365 Exchange Admin Center and your on-premises Exchange Server, and ask affected senders to forward any Non-Delivery Reports (NDRs).
Verify and Update Domain MX Records
Ensure the MX record for your routing domain correctly points to the on-premises Exchange server when your user mailboxes have not yet been migrated to the cloud.
When mailboxes reside entirely on-premises during the initial stages of a hybrid deployment, routing your primary MX record directly to Microsoft 365 can cause delivery failures. The MX record should reflect the actual location of the active mailboxes.
Log into the management console of your public DNS hosting provider and navigate to the DNS records section for your email domain.
Find the primary Mail Exchanger (MX) record responsible for routing inbound emails for your organization.
Verify that the MX record points to the public IP address or public hostname of your on-premises Exchange server, rather than pointing to Exchange Online (Microsoft 365).
Save your DNS changes and allow up to 24-48 hours for global DNS propagation, though local routing improvements may be noticed sooner.
Review Centralized Mail Transport Configuration
Inspect your Exchange connectors to ensure that centralized mail flow is properly routing messages back to your on-premises environment.
Analyze Non-Delivery Reports (NDRs)
Use the bounce messages received by senders to identify specific routing failures between the cloud and on-premises servers.
Looking for a Lightweight Alternative to Microsoft Office?
While troubleshooting complex Exchange hybrid server configurations, you might also be looking for ways to streamline your desktop productivity. WPS Office offers a free, lightweight, and highly compatible alternative to Microsoft Office suites.
Frequently Asked Questions
What is centralized mail transport in an Exchange hybrid setup?
Centralized mail transport is a configuration that forces all outbound mail from Microsoft 365 to route through your on-premises Exchange servers before being delivered to the internet. This ensures all messages are subject to your existing on-premises compliance, archiving, and routing rules.
Why does a message trace show as 'delivered' when the on-premises user hasn't received the email?
In a hybrid deployment, Microsoft 365 might successfully hand off the email to the on-premises connector. The cloud message trace marks this handoff as a successful 'delivery' to the next hop, but a subsequent local on-premises routing issue may prevent the message from reaching the actual mailbox.
Should my MX record point to Office 365 or my on-premises Exchange server?
If all your user mailboxes are still on-premises and you are just beginning your hybrid setup, your MX record should typically point to your on-premises Exchange server. Once all mailboxes are completely migrated to Microsoft 365, you should update the MX record to point to Exchange Online.
