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.3Troubleshoot sign-in and meetings
Understand sign-in issues (auth/token/MFA/Conditional Access), join meeting/feature-access issues, troubleshooting Microsoft 365 Copilot/AI experiences, and feedback policies.
Problems where users cannot get into Teams have different causes for "sign-in (authentication)" vs "joining a meeting". Isolation is key.
5.3.1Sign-in and join meeting
Sign-in issues stem from the identity layer (auth, tokens, MFA, Conditional Access)—check credentials, cached tokens, and Conditional Access blocks. Join meeting issues are when the user is signed in but cannot join a meeting or use features, often due to meeting policies, the client, or the network. Isolate "cannot sign in" = identity layer from "cannot join" = meeting/client layer.
5.3.2Copilot and feedback
If Microsoft 365 Copilot / AI experiences do not work in a meeting, check licensing, prerequisite features (recording/transcription), and policies. Feedback policies control collection of feedback/surveys users send to Microsoft (enable/disable, survey display). This is a user-experience management setting, separate from quality monitoring (CQD).
Continue reading — free sign-up
You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.