Email Migration

Fix Cached MX Routing After a Microsoft 365 Migration

Bushra ParveenBushra Parveen Nov 14, 2026 868 views

Question details

Determine why messages from some external senders do not arrive after a Microsoft 365 migration.

Fix Cached MX Routing After a Microsoft 365 Migration
Product
Microsoft 365 Exchange Online
Device & OS
not provided
Scenario
An organization has migrated its email to Microsoft 365 and needs to verify mail routing for affected external senders.
Observed behavior
Some external messages do not arrive, although messages sent to an alias may work. Cached DNS or MX records on external mail servers are a possible cause.
Before you start

Gather an affected recipient address, sender address, and approximate message time. Confirm which DNS provider hosts the recipient domain and that you have access to the Exchange admin center.

Solution 1Recommended

Check MX Records and Trace Missing Messages

Use DNS checks and a Microsoft 365 message trace to identify whether missing messages reached the tenant.

1
Check the published MX records

Use a public DNS lookup tool or run an MX lookup for the recipient domain. Confirm that its MX records point to the Microsoft 365 destination specified for the domain and that none point to the former mail server.

2
Review the DNS configuration

Sign in to your DNS provider and open the domain's DNS records. Correct any obsolete MX records, then check the publicly returned records again after the changes propagate.

3
Run a message trace

In the Exchange admin center, go to Mail flow > Message trace. Search using the affected sender, recipient, and message time, then review any matching delivery or failure details.

4
Contact affected senders

If the messages do not appear in the trace, ask the affected sender organizations to check their mail logs and DNS resolution, flush their DNS caches if appropriate, and investigate their outbound routing.

Check MX Records and Trace Missing Messages
External caches are outside your control: The recipient organization cannot clear DNS caches on external mail servers. An MX record's TTL controls normal cache expiration but does not guarantee that every external system refreshes immediately.
Free Microsoft Office alternative

Work With Office Documents in WPS Office

WPS Office is a free, lightweight alternative with a familiar interface for working with Office documents. Its format compatibility makes it easy to move existing files, although it does not resolve Microsoft 365 email routing or DNS issues.

Create and review migration notes and troubleshooting documentsCompatible with Microsoft Word, Excel, and PowerPoint formats, including DOCX, XLSX, and PPTXUse familiar document, spreadsheet, and presentation toolsMove existing Office files into a lightweight workspace
QA img-9

Frequently Asked Questions

How do I check whether a missing message reached Microsoft 365?

In the Exchange admin center, open Mail flow > Message trace and search for the sender, recipient, and approximate message time. Review any matching results for delivery or failure details.

Can I clear an external sender's DNS cache?

No. Ask the affected sender's organization to check its DNS resolution and mail logs and to flush its own DNS cache if appropriate.

Why might an alias receive mail when the primary address does not?

The alias may use a different domain or routing path. Check the domain in each address, compare their published MX records, and trace messages sent to both addresses.

Does a one-hour MX TTL guarantee that every sender updates within an hour?

No. The TTL sets the normal caching period, but external resolvers or mail systems may not refresh as expected. Ask affected senders to check the MX records their systems are using.