1
Open Outlook on the web
Sign in with the user's intended work account and verify the mailbox opens.
Everyday IT · Outlook
Use the web version to prove which layer is broken.
When Outlook is failing, Outlook on the web is one of the fastest comparison tests available.If the mailbox works in the browser, stop treating the first symptom like a Microsoft 365 outage.
The two-minute isolation test
Test the same user and same mailbox through two different clients.
2
Check the exact symptom
Look for the missing message, folder, calendar item, or send/receive behavior that is failing in desktop Outlook.
3
Compare results
If the browser is current and desktop Outlook is stale or broken, move toward the workstation, Outlook profile, cache, saved credentials, or local connectivity.
4
If both fail, move upstream
When the same symptom exists in the browser, investigate the mailbox, permissions, licensing, service health, transport, or identity layer instead of rebuilding the client.
What the comparison does and does not prove
Browser success is strong evidence, but it does not explain every local failure by itself.
Browser good
Cloud access is functioning
The user can authenticate and reach the mailbox. That makes local Outlook state a much stronger suspect.
Desktop bad
Check the client deliberately
Review connection state, cached mode, add-ins, saved credentials, Office sign-in, profile health, and whether the workstation itself has network problems.
Still unclear
Use a fresh profile as a test
If the mailbox is healthy but Classic Outlook remains broken, the Outlook profile rebuild guide is the next controlled test.
Browser success tells you where not to spend the next hour.
Use comparison to narrow the layer before repairing, reinstalling, or changing tenant settings.