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.1Monitor and report
Understand quality trend analysis with the Call Quality Dashboard (CQD), per-call quality, alert rules, Teams usage reports, the Microsoft 365 network connectivity test, and feedback management.
Operations look separately at "call/meeting quality" and "usage". Understand trends and set up alerts to stay aware.
5.1.1Quality monitoring
The Call Quality Dashboard (CQD) aggregates quality data across many calls/meetings to analyze trends and identify which sites/networks/subnets have concentrated quality problems. Drill into specific issues with per-call details (quality metrics for a specific call). Alert rules notify when quality/incident thresholds are crossed. CQD’s role is "quality trend analysis"—separate from usage reporting (usage reports).
5.1.2Usage and reports
Teams usage reports aggregate usage—team activity, app usage, active users, per-meeting metrics, storage usage (used to understand adoption). Monitor site connectivity with the Microsoft 365 network connectivity test, and manage collection of user feedback. Distinguish "quality trends (CQD)" from "usage (usage reports)" from "notification (alert rules)."
Cues: "aggregate call/meeting quality, analyze trends, find problem sites" = Call Quality Dashboard (CQD). "per-call quality metrics" = per-call details. "team activity/app usage/active users/storage totals" = Teams usage reports. "notify on threshold breach" = alert rules. "monitor site connectivity" = network connectivity test.
Watch the mix-ups: (1) CQD (quality trends) vs Teams usage reports (usage totals). (2) Alert rules (notification) are a separate feature on monitoring data. (3) Per-call details (one call) vs CQD aggregation (overall trends) differ in granularity. (4) The network connectivity test is about connectivity, not quality metrics per se.
5.1.3Section summary
- The Call Quality Dashboard (CQD) aggregates quality data, analyzes trends, finds problem sites
- Teams usage reports aggregate usage—team activity/apps/active users/storage
- Alert rules notify on threshold breach; the network connectivity test monitors site connectivity
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. Reports of poor meeting quality are rising across sites. You want to analyze trends to find which sites/subnets have concentrated quality issues. Best?
Q2. You want to understand usage—team activity, app usage, active users, storage. Best?
Q3. You want automatic notifications when call quality or incident metrics cross a threshold. Best?
Q4. What correctly distinguishes CQD from Teams usage reports?
Q5. You want to inspect the quality metrics (packet loss, jitter) of one specific call in detail. Best?
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.