Run a message trace for the affected mailbox and a recent Gmail test message; with no NDR and only one mailbox affected, the trace result is the required next step to determine whether Microsoft 365 received, filtered, delayed, or delivered it.
1. Trace a new external test message
An Exchange or Global Administrator should:
- Send a uniquely titled test message from Gmail, such as
External test 2026-11-14 14:30.
- Open Exchange admin center → Mail flow → Message trace → Start a trace.
- Set:
- Sender: the Gmail address
- Recipient: the affected mailbox
- Time range: include the test time and select the correct time zone
- Delivery status: All
- Run the trace, open the matching result, and inspect its events and final status. Message trace records whether Exchange Online received, rejected, deferred, quarantined, filtered, or delivered the message.^1^
Allow approximately 5–10 minutes for the reported status to update.
2. Act on the trace result
- Quarantined: Open Microsoft Defender portal → Email & collaboration → Review → Quarantine → Email, filter by the recipient and sender, select the message, and choose Release email. If it is a false positive, an authorized administrator can also submit it to Microsoft during release.^2^
- Filtered as spam or Failed: Open the trace details and identify the policy, connector, malware, TLS, or mail-flow-rule event responsible. Exchange Online can reject or divert mail because of filtering, rules, connectors, moderation, or delivery failures.^3^
- Pending or Getting status: Exchange Online is still processing or retrying delivery. Recheck shortly and compare the timestamp with Microsoft 365 admin center → Health → Service health → Exchange Online. The Service health page provides tenant-specific incidents, advisories, user impact, and updates.^4^
- Delivered: Check the mailbox in Outlook on the web, including Junk Email, Deleted Items, Archive, and the Other tab. Also inspect Inbox rules because a rule can move or delete a message after delivery. Message trace showing Delivered means Exchange delivered it to the intended destination; it does not prove that it remained visible in the Inbox.^1^
- No result: Microsoft 365 has no matching record for the sender, recipient, and time range. Repeat with the exact addresses and a wider range. If it remains absent, obtain the Gmail message details—especially the full recipient, send time/time zone, and Message-ID—and have the sender inspect its delivery logs. A sender’s Sent folder alone does not establish that Exchange Online received the message.
3. Check mailbox delivery restrictions only if trace indicates authentication rejection
If trace details—or a later NDR—show that anonymous/external senders are not permitted, open:
Exchange admin center → Recipients → Mailboxes → affected mailbox → Manage message delivery restriction
Under Accept messages from, clear Require senders to be authenticated, select the appropriate permitted senders, and save. This setting should be changed only when the trace or NDR identifies that restriction; Microsoft documents it specifically for external delivery rejection such as 550 5.7.134.^5^
Because a broad Microsoft 365/Exchange-related incident was reported around November 13–14, check the tenant’s Service health entry in parallel. Public status information does not establish that this particular mailbox is affected, especially when the symptom is isolated to one mailbox. If trace remains Pending, shows an unexplained failure, or contains no actionable event, use Health → Service health → Report an issue and attach the sender, recipient, UTC timestamp, Message-ID, and trace details.
References
- Message trace in the Exchange admin center in Exchange Online
- Manage quarantined messages and files as an admin
- Message Trace FAQ in Exchange Online
- How to check Microsoft 365 service health
- Fix NDR error "550 5.7.134" in Exchange Online