Fix Microsoft 365 Mail Delivery to the Wrong Hybrid Exchange Mailbox
Question details
Direct messages from migrated Microsoft 365 users to the intended on-premises Exchange mailbox.

- Product
- Microsoft 365 and hybrid Exchange 2010
- Device & OS
- not provided
- Scenario
- A migrated Exchange Online user sends a message to a recipient whose mailbox remains on an on-premises Exchange server.
- Observed behavior
- The message is delivered to an inactive or unintended Exchange Online mailbox instead of the recipient's on-premises mailbox.
Confirm which mailbox should receive the recipient's mail and check whether the recipient has an Exchange Online mailbox. You will need Exchange administrator access and access to the server running Microsoft Entra Connect, formerly Azure AD Connect.
Correct the recipient representation in Exchange Online
Use this approach when an unintended cloud mailbox is receiving mail for a user whose active mailbox is on-premises.
In a hybrid deployment, an on-premises mailbox should normally be represented in Exchange Online as a mail user, not as an active cloud mailbox. An incorrectly provisioned cloud mailbox can cause Exchange Online to deliver messages locally rather than route them on-premises.
In the Exchange admin center, open Recipients and look up the affected user. Check whether the Exchange Online recipient is listed as a mailbox rather than a mail user.
In the on-premises Exchange Management Console, open Recipient Configuration and inspect the user's mailbox and email addresses. Confirm that it is the intended mailbox and that the recipient information is synchronized to Microsoft 365.
After confirming the cloud mailbox is not needed, review its contents, retention requirements, and recovery options with your Exchange administrator. Use the Microsoft 365 admin center's Users > Active users page to review the user's license; in the reported case, removing the Exchange Online license and waiting for mailbox removal restored delivery. Do not delete the synchronized user account as a substitute for removing the mailbox.
Run a synchronization cycle from the Microsoft Entra Connect server, or wait for the scheduled cycle. Then return to Recipients in the Exchange admin center and confirm that the cloud recipient is a mail user with the intended on-premises routing address.
Send a test message from a migrated cloud mailbox to the affected recipient. In the Exchange admin center, open Mail flow > Message trace, find the test message, and check its delivery details; also confirm receipt in the on-premises mailbox.

Check hybrid mail flow if delivery still fails
Use this check if the recipient is correctly represented as a mail user but messages still do not reach the on-premises mailbox.
Work with Office files using WPS Office
WPS Office is a free, lightweight alternative for everyday document work, with a familiar interface and support for common Microsoft Office formats to help you move between suites. It does not change Exchange mail routing or repair hybrid mailboxes.

Frequently Asked Questions
Why is mail going to a cloud mailbox before the user is migrated?
An unintended Exchange Online mailbox may have been provisioned for the recipient. Check Recipients in the Exchange admin center to see whether the user appears as a mailbox rather than a mail user.
Do I need to create an outbound connector to fix this?
Not necessarily. First check whether Exchange Online recognizes the on-premises recipient as a mail user. If that is correct and delivery still fails, inspect Mail flow > Message trace and review the existing hybrid connectors.
Will removing the Exchange Online license delete mailbox data?
Removing the license can disconnect or remove access to the cloud mailbox, and recovery depends on the applicable retention and hold settings. Review the mailbox contents and recovery options before changing the license under Users > Active users in the Microsoft 365 admin center.
How can I confirm that the fix worked?
Send a test message from a migrated mailbox, then search for it under Mail flow > Message trace in the Exchange admin center. Confirm that the message also appears in the intended on-premises mailbox.




