Fix Microsoft 365 NDRs for an On-Premises Mail Domain
Question details
Configure mail flow from Microsoft 365 to recipients hosted on an on-premises mail server.

- Product
- Exchange Online in Microsoft 365
- Device & OS
- not provided
- Scenario
- A domain is used for recipients in Exchange Online and on an on-premises mail server.
- Observed behavior
- Exchange Online rejects recipients that are not present in the cloud directory when the accepted domain is authoritative, resulting in a non-delivery report.
Sign in to the Exchange admin center with an account that can manage accepted domains and mail flow connectors. Confirm the affected domain and identify how Exchange Online should route mail to the on-premises server.
Set the Accepted Domain to Internal Relay and Verify Routing
Use this configuration when some recipients for the domain are hosted on an on-premises mail server rather than in Exchange Online.
An internal relay domain allows Exchange Online to relay messages for recipients it cannot resolve locally. A correctly configured route to the on-premises mail server is still required.
Sign in to the Exchange admin center and go to Mail flow > Accepted domains.
Select the affected domain, such as Fabricam.com, edit its settings, and change the domain type from Authoritative to Internal relay. Save the change.
Go to Mail flow > Connectors and verify that an enabled connector routes mail for the domain from Microsoft 365 to the on-premises mail server. Check its destination and security settings against the server configuration.
Check the domain's DNS and MX records against your intended mail flow, then send a test message to an on-premises recipient. If delivery fails, review the new non-delivery report and use Mail flow > Message trace to investigate.

Work With Office Files in WPS Office
WPS Office is a free, lightweight alternative for working with documents, spreadsheets, and presentations. Its familiar interface and Microsoft Office format compatibility make it easy to move existing files. Exchange Online mail routing must still be configured in Microsoft 365.

Frequently Asked Questions
Why does an authoritative domain cause an NDR for an on-premises recipient?
Exchange Online treats an authoritative domain as hosting its recipients in the cloud. If the recipient is not present in the cloud directory, Exchange Online can reject the message instead of relaying it to the on-premises server.
Is changing the domain to Internal relay enough to deliver mail?
Not necessarily. Go to Mail flow > Connectors in the Exchange admin center and verify that an enabled connector provides the correct route and security settings for the on-premises server.
Do I need to change the MX records before testing?
Not necessarily for a message sent from Exchange Online to an on-premises recipient. MX records affect how inbound mail is directed, so check them against your intended mail flow and migration plan.
What should I do if the test message is delivered but marked as spam?
Review the receiving server's spam-filtering logs and check the domain's email authentication settings. Internal relay controls routing; it does not bypass spam filtering.




