Investigate Delayed External Email in Exchange Online Message Trace
Question details
Determine where external email is delayed using Exchange Online message trace.

- Product
- Exchange Online
- Device & OS
- not provided
- Scenario
- Users receive messages from external senders several hours after they were sent.
- Observed behavior
- A message trace reports a TLS 1.2 receipt event and a 607-minute delay before Office 365 received the message.
Gather an affected recipient address, sender address, approximate send time, and the complete trace for at least one delayed message. Confirm when the issue began and whether it affects multiple users or external domains.
Review the complete Exchange Online message trace
Use the event timeline to determine whether the delay occurred before or after Exchange Online received the message.
In the Exchange admin center, go to Mail flow > Message trace.
Start a trace using the affected sender, recipient, and time range, then open the matching message in the results.
Review the complete event details and compare the receipt and delivery times. Check the displayed time zone and identify which systems the events refer to before assigning the delay.
Repeat the trace for other affected recipients and external domains. Record when the delays started and whether they affect one user or the organization.
If the delay occurred before Exchange Online received the message, ask the sender's mail administrator to check their server, outbound queue, DNS, and delivery logs. If the delay occurred after receipt or remains unclear, share the full trace and affected recipient details with your mail administrator or Microsoft Support through a secure channel.

Use WPS Office for everyday document work
WPS Office is a free, lightweight alternative with a familiar interface and Microsoft Office format support for a smooth transition. It does not fix Exchange Online email delivery delays.

Frequently Asked Questions
Where can I find the full message trace?
In the Exchange admin center, go to Mail flow > Message trace, search for the message, and open the matching result to review its event details.
Does a TLS 1.2 event mean TLS caused the delay?
No. TLS 1.2 identifies the connection security used for an event. Compare the full sequence and timestamps to determine where the delay occurred.
Who should investigate a delay before Exchange Online received the message?
Ask the sender's mail administrator to review their outbound queue, server logs, DNS, and delivery attempts. Provide the sender, recipient, and message timing so they can find the relevant records.
What should I provide to Microsoft Support?
Share the complete message-trace results, affected recipient, approximate send time, when the issue began, and whether multiple users or external domains are affected. Use a secure support channel for account details.




