What's changed: Created MS-700 Chapter 5 (domain: Monitor, report on, and troubleshoot Teams). Monitoring/reporting (Call Quality Dashboard CQD quality trends, per-call details, alert rules, Teams usage reports, network connectivity test, feedback), client troubleshooting (client-side logs, clear Teams client cache, self-help diagnostics, install/update, client health), and sign-in/meeting troubleshooting (sign-in issues identity layer, join meeting issues meeting/client layer, Microsoft 365 Copilot/AI experiences, feedback policies). This completes the MS-700 textbook: all 5 chapters / 13 sections.
5.2Troubleshoot clients
Understand collecting client-side logs, clearing the Teams client cache, self-help diagnostics, client install/update issues, and checking client health in the Teams admin center.
For client issues, escalate from "light fixes (cache)" to "detailed diagnostics (logs)".
5.2.1Cache and logs
For display glitches, stale data, or load issues, first try clearing the Teams client cache (the standard fix for corrupt cache). For deeper investigation that this does not resolve, collect client-side logs (detailed diagnostic logs). Self-help diagnostics for Teams automatically checks common issues and guides you. Distinguish "standard fix for light glitches" = cache clear from "detailed diagnostics" = log collection.
5.2.2Install, update, and health
Resolve Teams client install/update issues by checking distribution method and version. The Teams admin center shows each user/device’s client health (version, connection state) to help isolate widespread issues. Note that client-side problems have different causes from sign-in issues (next section).
Cues: "standard fix for display glitches/stale data" = clear the Teams client cache. "detailed diagnostic logs" = collect client-side logs. "auto-check common issues" = self-help diagnostics. "check client version/connection state" = client health in the Teams admin center. Install/update issues: check distribution method and version.
Watch the mix-ups: (1) Cache clear (standard light fix) vs log collection (detailed diagnostics). (2) Self-help diagnostics (auto-check) vs manual log collection. (3) Client health (Teams admin center) checks version/connection. (4) Client problems vs sign-in issues (auth-caused) have different causes.
5.2.3Section summary
- Display glitches/stale data = clear the Teams client cache; detailed diagnostics = collect client-side logs
- Self-help diagnostics auto-checks; the Teams admin center shows client health
- Client problems and sign-in issues have different causes
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. A user’s Teams shows display glitches or stale data. What is the standard first fix to try?
Q2. For a complex client issue not fixed by clearing cache, you want detailed information to investigate. Best?
Q3. You want users to auto-check common Teams issues and follow guidance to resolve them. Best?
Q4. You want to check Teams client version and connection state across many users to isolate a widespread issue. Best?
Q5. What correctly distinguishes clearing the cache from collecting client-side logs?
Keep track of your progress
The full study guide is free to read. Sign up free to practice with the question bank, track what you have read, review your mistakes, and highlight passages.