mail-flow-trace

Mail flow trace checks the recipient mailbox via Microsoft Graph and falls back to Exchange PowerShell Get-MessageTrace to identify routing delays, spam filtering, or delivery failures. It reconstructs the email journey to pinpoint exactly where transport stopped.

An email bounces with an NDR due to transport routing failures, policy blocks, or invalid recipients. A mail flow trace identifies the exact delivery failure point by analyzing Exchange Online service health advisories and detailed message trace logs.

Check for quarantine by running a mail flow trace that detects quarantine-related notices and classifies message placement across Inbox, Junk, or Deleted Items. It guides you to a dedicated quarantine inspection workflow when filtering policies intercept the message.

Yes, you can use Exchange PowerShell as a fallback when Microsoft Graph cannot resolve full transport routing. The trace provides exact Get-MessageTrace and Get-MessageTraceDetail commands to query Exchange Online logs for delayed or missing messages.

The best way to troubleshoot missing emails after a policy update is running a post-change validation mail flow trace. It verifies recipient inbox search placement, correlates Microsoft 365 service health advisories, and checks Defender filtering actions to explain the delivery outcome.

Yes, mail flow trace works for helpdesk troubleshooting of delayed messages by verifying inbox search placement and correlating Microsoft 365 mail-flow service advisories. It identifies whether delays stem from systemic incidents, spam handling, or transport routing issues.