Fix Microsoft 365 External Email Delivery to a Migrated Hybrid Mailbox
Question details
Restore external email delivery to one migrated Microsoft 365 user in an Exchange hybrid environment while preserving working internal and outbound email.

- Product
- Microsoft 365 Exchange Online and on-premises Microsoft Exchange Server
- Device & OS
- not provided
- Scenario
- After a hybrid mailbox migration, one user cannot receive messages from outside the organization, although other users are unaffected.
- Observed behavior
- The user can send and receive internal email and send external email. The on-premises Exchange server still identifies the recipient as a User Mailbox rather than a Remote Mailbox, and no external non-delivery reports are available.
Have an Exchange administrator confirm the affected user's primary SMTP address, Exchange Online mailbox, and migration batch status. Obtain access to the on-premises Exchange management tools and directory synchronization server, and ask an external sender for a test message timestamp and any full non-delivery report.
Verify that the migration completed and the recipient is a remote mailbox
Start here when only one migrated user is affected and on-premises Exchange still lists that user as a local mailbox.
Open the Exchange admin center used to manage the migration and select Migration. Review the user's migration batch and individual migration report to confirm that finalization completed successfully, rather than relying only on the migration team's initial status.
In the Exchange Online admin center, go to Recipients > Mailboxes and locate the user. Check that the mailbox exists and that its primary email address and aliases match the intended recipient.
In the on-premises Exchange admin center, open Recipients > Mailboxes and inspect the user's mailbox type. You can also run Get-Recipient -Identity user@contoso.com | Format-List RecipientTypeDetails,PrimarySmtpAddress in the on-premises Exchange Management Shell. A successfully migrated standard user mailbox should normally appear as RemoteUserMailbox, not UserMailbox.
If the batch is incomplete, review its errors before attempting recipient changes. If the cloud mailbox is confirmed but the on-premises object remains UserMailbox, have the hybrid Exchange administrator investigate and use a supported recipient repair procedure; do not simply disable or delete the local mailbox.

Correct the remote routing address and synchronize the recipient
Use this after confirming the migration and the intended recipient state, especially when the user's targetAddress is missing or incorrect.
Trace an external test message and verify hybrid mail routing
Use this if recipient corrections do not restore delivery or if the point of failure is still unclear.
Use WPS Office for Documents While Exchange Email Is Being Repaired
WPS Office does not repair Exchange hybrid routing or replace Exchange Online email service. It provides a free, lightweight alternative for document work, with a familiar interface and Microsoft Office format compatibility that makes migration straightforward.

Frequently Asked Questions
Why can this user receive internal email but not external email?
Internal and external messages can take different delivery paths in a hybrid deployment. External messages may enter through on-premises Exchange, where a stale UserMailbox object routes them locally. Check the recipient type in the on-premises Exchange admin center and trace a fresh external test message to confirm the actual path.
Should a migrated mailbox appear as UserMailbox on-premises?
After a completed hybrid migration, a standard user mailbox should normally appear on-premises as RemoteUserMailbox. Run Get-Recipient -Identity user@contoso.com | Format-List RecipientTypeDetails in the on-premises Exchange Management Shell and verify the migration report if it still shows UserMailbox.
What address belongs in the targetAddress attribute?
For the migrated user, it should normally be the verified remote routing address, such as user@tenant.mail.onmicrosoft.com. For an existing remote mailbox, set it through Set-RemoteMailbox -RemoteRoutingAddress using the actual tenant routing domain. Do not assume that editing this attribute alone repairs an incorrect local mailbox type.
Do I need to change the MX record if only one user is affected?
Usually, an isolated recipient problem calls for recipient and migration checks first. Inspect the MX record to understand the inbound route, but do not change it unless message tracing and the intended hybrid design show that domain-wide routing is incorrect.
Will messages sent before the fix arrive automatically?
Only messages still being retried by a sending server or held in a deliverable queue may arrive later. Messages already rejected, expired, or delivered to an unintended local mailbox will not automatically reappear in Exchange Online. Check message traces, on-premises logs, queues, and any remaining local mailbox, then request resends when necessary.




