1
Get one exact example
Record sender, recipient, subject, and approximate send or expected-arrival time. Vague complaints like “mail is delayed” are not enough.
Everyday IT · Microsoft 365 Mail Flow
Do not guess where the message went.
A single exact message can tell you whether the problem is before Microsoft 365, inside mail flow, in security processing, or only in the user's Outlook client.Sender, recipient, subject, exact time, then trace.
The evidence-first path
2
Check first receipt by Microsoft 365
If Exchange first receives the message long after the sender says it was sent, the delay happened before Microsoft 365.
3
Read the result, not just the headline
Delivered, rejected, redirected, quarantined, and security-processing events point to different next steps. Expand suspicious events and read the reason.
4
If delivery is prompt, move to the client
If Microsoft 365 received and delivered the message on time but Outlook shows it late, investigate client sync, profile, cache, rules, add-ins, or connectivity instead of rewriting mail flow.
What not to do
Avoid
Changing connectors or transport rules first
Organization-wide mail-flow changes should follow evidence, not one user's symptom.
Avoid
Assuming quarantine explains every delay
Prove when Exchange first received the message and when it was delivered or quarantined. Similar-looking events can represent different problems.
Avoid
Weakening security controls casually
Do not create broad bypasses simply to make one message pass. Understand the authentication, reputation, or policy reason first.
The trace tells you which team, layer, or client deserves your next five minutes.