Email Migration

Prevent NDRs During an Exchange 2010 Cutover Migration to Microsoft 365

Steven ParkerSteven Parker Nov 20, 2026 868 views

Question details

Prevent non-delivery reports when cloud users send mail to on-premises recipients during an Exchange 2010 cutover migration.

Prevent NDRs During an Exchange 2010 Cutover Migration to Microsoft 365
Product
Exchange 2010 and Exchange Online in Microsoft 365
Device & OS
not provided
Scenario
A migration batch creates cloud recipient objects while some recipients still need to receive mail on-premises.
Observed behavior
Cloud users may receive non-delivery reports when sending messages to on-premises recipients after the migration batch starts.
Before you start

Identify which recipients are hosted on-premises and which have Exchange Online mailboxes. Have Exchange admin access and the details of any non-delivery report available so you can check recipient routing and message traces.

Solution 1Recommended

Check accepted domains, recipients, and mail-flow routing

Use this approach to find routing mismatches that can cause non-delivery reports during the transition.

1
Review the migration batch

In the Exchange admin center, open Migration and check the batch status and any reported errors. Confirm which mailboxes have been created or migrated.

2
Verify recipient objects

In the Exchange admin center, open Recipients and check the affected addresses and recipient types. A cloud mailbox created by the batch can receive mail locally in Exchange Online, so verify where the intended mailbox is active.

3
Check the accepted-domain type

In the Exchange admin center, go to Mail flow > Accepted domains and select the affected domain. Use Authoritative when Exchange Online is responsible for the domain's recipients; consider Internal relay when some recipients remain on-premises and the routing design requires Exchange Online to relay mail to them.

4
Verify relay routing

If using Internal relay, go to Mail flow > Connectors and verify that an appropriate outbound connector routes unresolved recipients to the on-premises mail system. Check its destination and security settings against your mail-flow design.

5
Trace a failed message

In the Exchange admin center, open Mail flow > Message trace and search for a failed message. Compare the trace and non-delivery report with the recipient and connector settings, then send a test message after making any correction.

Check accepted domains, recipients, and mail-flow routing
Internal relay does not override a cloud mailbox: If the recipient already has a cloud mailbox, Exchange Online can deliver there rather than relay the message on-premises. Check the recipient object and migration state before changing the domain type.
Free Microsoft Office alternative

Work With Migration Documents in WPS Office

WPS Office is a free, lightweight alternative for working with migration plans and checklists. Its familiar interface and Microsoft Office format compatibility make it easy to move existing documents into your workflow. It does not configure Exchange mail flow.

Organize migration plans and recipient checklistsOpen and edit Microsoft Word, Excel, and PowerPoint formatsUse a familiar interface for everyday document tasksMove existing Office files into a lightweight workspace
microsoft office alternative - wps office

Frequently Asked Questions

Should the accepted domain be Authoritative or Internal relay during migration?

In the Exchange admin center, check Mail flow > Accepted domains. Use Authoritative when Exchange Online is responsible for the domain's recipients. Internal relay may be appropriate when some recipients remain on-premises and an outbound connector is configured to route unresolved recipients there.

Why can a cloud mailbox receive mail instead of the on-premises mailbox?

A migration batch can create a cloud mailbox for the address, allowing Exchange Online to resolve and deliver the message locally. Check the recipient object under Recipients and review the batch status under Migration.

Can I enable directory synchronization after a cutover migration?

Yes. You can deploy Microsoft Entra Connect after the cutover to synchronize on-premises identities. First review Microsoft's account-matching guidance and verify that on-premises users match the intended Microsoft 365 accounts.

Do I have to change the accepted-domain type after migration or synchronization?

Not automatically. Review Mail flow > Accepted domains and choose the type that matches the final recipient hosting and routing design.