Practical troubleshooting guide · The business scenario is illustrative, not a client case study. Administrative changes require authorised access.

A transport business in the QEW corridor sends an update from dispatch, but a customer says it never arrived. The message may have been rejected, filtered or sent to an outdated address. A structured trace helps separate those possibilities while dispatch maintains its normal operational communication process.

Capture the actual sending route

Record the sender, recipient, time zone and subject of a safe example. Was the update sent from Outlook, a shared mailbox or transport software? A platform may use its own sending service rather than Exchange Online. Collect the failure notice if one exists, and do not assume an Outlook sent copy proves the receiving organisation accepted the email.

Run a focused trace

An authorised administrator can use Exchange admin center, Mail flow, Message trace. Search the relevant sender, recipient and time range, then open the matching message details. Review events rather than only the headline status. Record the identifier and diagnostic response for escalation. Trace visibility and available reports depend on age and permissions, so start with a recent example.

Follow the evidence to the responsible system

A failed event may identify an address, policy or receiving-server issue. A delivered result calls for checking mailbox location, quarantine or recipient handling; it does not prove a human read the update. If Exchange has no matching record, verify the search and obtain the transport platform’s sending logs. Avoid broad allow-listing or disabling filtering to solve one unconfirmed complaint.

Retest without creating duplicate operational work

Use a clearly marked test update with a staff-controlled recipient first. Then agree a confirmation method for the affected customer through the business’s established process. Verify replies return to a monitored inbox. Keep the diagnosis and any changed rule in your support record, so a later delivery complaint can be compared against an actual baseline rather than memory.

MAKE IT ACTIONABLE

Your next steps

  • Identify Outlook versus platform-generated mail.
  • Save trace events and error details.
  • Confirm reply handling after the fix.

Official reference

Microsoft: Message trace in Exchange Online

Technical guidance checked October 1, 2026. Product features and requirements can change. The business checklists above are practical suggestions from Cyber Bounds.

PUT THE NEXT STEP INTO PRACTICE

Help with microsoft 365.

Make Outlook, Teams, and shared files work together for your business. Tell us about your situation and we’ll discuss a suitable scope and quote.

Explore Microsoft 365