Lesson 11 of 60 beginner

Office / M365 User Issues

The everyday pain recruiters expect you to know

Open interactive version (quiz + challenge)

Real-world analogy

Email and Teams are like the plumbing of a modern office. Nobody notices them until they stop — then every single person becomes an emergency ticket at the same time. A good junior fixes the right pipe; a weak one reboots the whole building.

What is it?

M365/Office support is the bulk of daily corporate helpdesk work. Mastering the mental model (profile vs mailbox, permission vs delegation, layered mail flow, Teams cache, OneDrive sync, Conditional Access) eliminates most wasted reboots.

Real-world relevance

CEO: ‘I sent an important email, customer didn’t get it.’ Junior runs Exchange message trace, sees the message was rejected by the recipient’s server (‘mailbox full’). Responds with evidence in 10 minutes. No blame, no blind reboot, clean resolution.

Key points

Outlook profile is not the mailbox — Outlook stores a local profile (connection settings) + an OST file (cached mail). Many ‘Outlook is broken’ tickets are profile/OST corruption, not mailbox-side. A new Outlook profile often fixes things that reinstalling never would.
Mail flow layers — User → Outlook → Exchange Online → recipient server → destination. Look at message trace / delivery reports in admin center. Don’t guess where a message died.
Permissions vs delegation — Folder permissions (Inbox, Calendar) = another user sees your data. Delegation = another user can act on your behalf (send-as, send-on-behalf). Know the difference; they cause very different support tickets.
Shared mailbox vs distribution list vs M365 group — Shared mailbox: everyone sees the same inbox. DL: routes mail to multiple inboxes. M365 group: mailbox + Teams + SharePoint + Planner bundle. The wrong choice creates years of confusion.
Teams failures — Usually one of: sign-in/token, camera/mic/permissions, network (UDP/SIP ports), or cache. `%appdata%\Microsoft\Teams` cache clearing is a classic fix.
OneDrive / SharePoint sync — Long paths, reserved characters, large files, locked files, and shadow-copy quotas are common. Users blame ‘OneDrive broken’ for file-name issues that are really their own. Read the sync icon and logs.
MFA and Conditional Access friction — Users get blocked by conditional access on new devices/locations. Don’t disable policies to ‘fix’ it — investigate sign-in logs in Entra and let the user complete registration properly.
Licensing and mailbox size — ‘Mail won’t send’ may simply be: license was removed, mailbox quota full, or sending limits hit. Check license + mailbox size before anything else.

Code example

// M365 triage checklist (admin + user side)

User side:
  - Close Outlook -> Control Panel -> Mail -> Profiles
  - Create a NEW Outlook profile as a test
  - Clear Teams cache:  %appdata%\Microsoft\Teams
  - Check OneDrive sync icon and pending/blocked files
  - Verify MFA and device-registration state

Admin side (Microsoft 365 / Exchange Online):
  - Message Trace for failed deliveries
  - Mailbox size + quotas
  - License assignment state
  - Sign-in logs (Entra)  -> Conditional Access blocks?
  - Shared mailbox / delegation / send-as audit

Line-by-line walkthrough

1. M365 triage checklist
2. User-side header
3. Recreate Outlook profile as a test
4. Blank separator
5. Clear Teams cache path
6. Check OneDrive sync status
7. Verify MFA/device state
8. Blank separator
9. Admin-side header
10. Message trace for mail flow
11. Mailbox size and quotas
12. License assignment
13. Sign-in logs in Entra
14. Conditional Access investigation
15. Shared mailbox / delegation audit

Spot the bug

Ticket: 'I cannot send mail to external customer.'
Junior removes the user's MFA to 'test', then reassigns a license, then asks the user to resend.
Audit later flags MFA removal as a policy violation.

Need a hint?

Which evidence should have been gathered BEFORE any policy change?

Show answer

Run Message Trace first to see WHERE the message failed: rejected by recipient? quota? policy? Check mailbox size and license. Never remove MFA as a troubleshooting shortcut — this is a policy violation in most regulated environments. Document, escalate with evidence.

Explain like I'm 5

Email and Teams are two different highways. When a car doesn’t arrive, you don’t rebuild the car — you check: did it leave the garage, reach the first intersection, make it through the tunnel, get to the destination city? That map is called ‘message trace.’

Fun fact

A surprising number of ‘Outlook broken’ tickets are caused by users deleting the OST file thinking it’s a virus. Outlook simply rebuilds it on next sign-in — the pain is just the cache resync, not an actual outage.

Hands-on challenge

Open your own Outlook and Teams. Find the profile settings (Outlook: Control Panel → Mail → Profiles). Locate the Teams cache folder (%appdata%\Microsoft\Teams). Do NOT delete anything. Just note the paths in your lab journal.

More resources

Message Trace in Exchange Online (Microsoft Learn)
Conditional Access overview (Microsoft Learn)
OneDrive sync troubleshooting (Microsoft Learn)

Open interactive version (quiz + challenge) ← Back to course: IT Jobs Bootcamp