Monitor, Report on, and Troubleshoot Teams
Reports and analytics
Teams admin center reports cover usage (active users, teams and channels, messages), app usage, PSTN and calling activity, and device health. The exam expects you to separate the two quality tools clearly. Call Quality Dashboard (CQD) is an aggregate, organization-wide view with roughly 30 days of data plus near-real-time slices, and it is the right tool for spotting patterns such as a bad building or subnet. Call Analytics is per-user and per-call detail, including media stream metrics, and is used to investigate one person's poor call or a specific session. Both retain about 30 days of history.
Troubleshooting workflow
Establish scope first: one user, one location, or one meeting? Then work outward. The Microsoft 365 network connectivity test validates required endpoints, UDP ports, and latency from a location, and QoS with DSCP tagging protects media. Server-side, check service health, confirm the user's assigned policies and licenses, and review audit logs in Purview for recent administrative changes such as policy edits or license removals. Client-side self-help diagnostics and Teams logs surface signaling and media details for a single user.
Worked example. Ten users in one office report poor call quality while everyone else is fine. Open CQD, filter by building or subnet, and compare. If that subnet shows high jitter and packet loss across many users, the cause is the network path, not a policy. Per-user Call Analytics would only confirm individual bad calls, not reveal the pattern.