Send & Receive Issues

Troubleshoot Office 365 Email Delays to One Domain

Natalie TaylorNatalie Taylor Nov 22, 2026 868 views

Question details

Identify why Office 365 emails to a specific domain are delayed before delivery to its private mail server.

Troubleshoot Office 365 Email Delays to One Domain
Product
Microsoft 365 Exchange Online
Device & OS
not provided
Scenario
An Office 365 sender emails recipients hosted on a specific private mail server.
Observed behavior
Messages are delayed for hours or days, while the receiving server records no connection attempts during the delay.
Before you start

Collect the sender and recipient addresses, approximate send times with time zones, and message IDs for delayed emails. An Exchange administrator may need to run the message trace, and the receiving server administrator can check connection logs.

Solution 1Recommended

Trace Delayed Messages and Escalate to Microsoft

Use message traces, headers, and server logs to determine the scope of the delay and provide evidence for investigation.

1
Run a message trace

In the Exchange admin center, go to Mail flow > Message trace. Search using the sender, recipient, and relevant time range, then open the delayed message's trace details.

2
Review the delivery events

Compare the timestamps and status of the trace events with the receiving server's connection logs for the same period. Record any pending, deferred, or failed events and their details.

3
Compare test messages

Send test messages from another Microsoft 365 sender to the affected domain and to a recipient at a different domain. Compare their trace results to see whether the delay is limited to a sender, message, or destination.

4
Collect full headers

Ask recipients for the full headers of delayed and promptly delivered messages. In classic Outlook for Windows, open a received message, select File > Properties, and copy the Internet headers.

5
Contact Microsoft support

In the Microsoft 365 admin center, open Help & support and submit a support request. Provide the trace results, full headers, message IDs, timestamps, and relevant receiving-server logs privately.

Trace Delayed Messages and Escalate to Microsoft
What the logs can show: A lack of receiving-server connection attempts suggests the delay may occur before the final delivery attempt, but it does not by itself establish the cause.
Free Microsoft Office alternative

Work With Office Files in WPS Office

WPS Office is a free, lightweight alternative for working with familiar Office files. Its familiar interface and format compatibility make it easy to move your document work to WPS. It does not fix Exchange Online email delivery delays.

Review email troubleshooting notes and trace reports in a familiar workspaceOpen and edit Microsoft Word, Excel, and PowerPoint formats, including DOCX, XLSX, and PPTXUse a familiar interface to ease the transition from Microsoft OfficeWork with a free, lightweight office suite
microsoft office alternative - wps office

Frequently Asked Questions

Where can I trace a delayed Office 365 email?

An authorized administrator can open the Exchange admin center and go to Mail flow > Message trace. Search by sender, recipient, and the relevant time range, then review the message's events.

Does an empty receiving-server log prove Microsoft caused the delay?

No. It suggests that the recipient server may not have received a connection attempt during that period. Compare the server logs with the message trace and headers, and ask Microsoft support to investigate.

How can I tell whether the delay affects only one domain?

Send comparable test messages to the affected domain and to another external domain. Also test with a different Microsoft 365 sender, then compare message trace results and delivery times.

What should I send Microsoft support?

Submit the message trace, full headers, message IDs, sender and recipient addresses, timestamps with time zones, and relevant receiving-server logs through a private support request in the Microsoft 365 admin center.