Exchange Connection Problems

Fix Exchange Hybrid Mail Flow to On-Premises Mailboxes

Emma BrownEmma Brown Nov 18, 2026 869 views

Question details

Restore mail flow from an Exchange Online mailbox to on-premises mailboxes in a hybrid deployment.

Fix Exchange Hybrid Mail Flow to On-Premises Mailboxes
Product
Exchange Online and Exchange Server 2010
Device & OS
not provided
Scenario
A test user was migrated from Exchange 2010 to Exchange Online and needs to send messages to recipients whose mailboxes remain on-premises.
Observed behavior
Messages to on-premises mailboxes failed with 550 5.1.10 RESOLVER.ADR.RecipientNotFound, and hybrid connectors were not initially visible.
Before you start

Confirm which accepted domain the affected recipients use and whether those recipients are represented in Exchange Online as mail-enabled objects with routing addresses. Sign in with an account that can manage Exchange mail flow settings and run the Hybrid Configuration Wizard.

Solution 1Recommended

Set the Exchange Online accepted domain to Internal Relay

Use this configuration when some on-premises recipients are not represented in Exchange Online and mail must be routed back on-premises.

An Authoritative domain can work when all on-premises recipients are represented in Exchange Online as mail-enabled objects with appropriate routing addresses. Internal Relay allows Exchange Online to relay messages for recipients it cannot resolve locally, provided the hybrid routing configuration is in place.

1
Open accepted domains

In the Exchange admin center, go to Mail flow > Accepted domains and select the domain used by the affected recipients.

2
Change the domain type

Edit the selected domain, choose Internal Relay as its domain type, and save the change.

3
Check routing and retest

Go to Mail flow > Connectors and verify that a connector routes messages from Exchange Online to your on-premises Exchange organization. Then send a test message from the migrated mailbox to an on-premises recipient.

Set the Exchange Online accepted domain to Internal Relay
Why the domain was Authoritative: A verified custom domain is Authoritative by default. The Hybrid Configuration Wizard does not determine whether every on-premises recipient is synchronized as a mail-enabled object.
Free Microsoft Office alternative

Work with Office Documents Alongside Your Exchange Migration

WPS Office is a free, lightweight alternative with a familiar interface and Microsoft Office format compatibility, making it easy to move your document work while you manage an Exchange migration. It does not change Exchange connectors or mail flow.

Edit migration checklists and troubleshooting notes in WPS WriterOpen and save Microsoft Word, Excel, and PowerPoint formats, including DOCX, XLSX, and PPTXUse a familiar interface for a smoother transition from Microsoft OfficeWork with a free, lightweight office suite
microsoft office alternative - wps office

Frequently Asked Questions

Why does Exchange Online return 550 5.1.10 for an on-premises recipient?

The recipient may not be represented in Exchange Online, while the shared accepted domain is set to Authoritative. Check Mail flow > Accepted domains and verify the recipient's synchronization and routing configuration.

When can I keep the domain set to Authoritative?

Authoritative can work when all on-premises recipients are represented in Exchange Online as mail-enabled objects with appropriate routing addresses and the hybrid connector is configured.

Will changing the domain to Internal Relay create the hybrid connector?

No. Internal Relay changes how Exchange Online handles unresolved recipients for the domain; a working route to the on-premises organization is still needed. Check Mail flow > Connectors and rerun the Hybrid Configuration Wizard if the expected connectors are missing.

Why did the wizard leave the domain as Authoritative?

A verified custom domain is Authoritative by default, and the Hybrid Configuration Wizard does not determine whether all on-premises recipients are synchronized as mail-enabled objects. Review the accepted domain type against your coexistence configuration.