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).
Cues: "cannot sign in (credentials/token/MFA/Conditional Access)" = sign-in issues (identity layer). "signed in but cannot join/use features" = join meeting issues (meeting/client layer). "in-meeting Copilot not working" = check licensing/prerequisites/policies. "control feedback collection" = feedback policies.
Watch the mix-ups: (1) Sign-in issues (identity layer) vs join meeting issues (meeting/client layer). (2) A Conditional Access block can cause sign-in problems. (3) Copilot issues also depend on licensing/prerequisites (recording/transcription). (4) Feedback policies control feedback collection, separate from quality monitoring (CQD).
5.3.3Section summary
- Sign-in issues are the identity layer—auth/token/MFA/Conditional Access
- Join meeting issues are signed-in but cannot join/use features (meeting/client layer)
- Copilot issues: check licensing/prerequisites/policies; feedback policies control feedback collection
Sign in to track progress — Log in.
Quick check
(just a quick review)Q1. A user cannot sign in to Teams, with credentials, MFA, or Conditional Access suspected. What kind of issue is this?
Q2. A user is signed in but cannot join a specific meeting or use in-meeting features. What kind of issue is this?
Q3. Microsoft 365 Copilot is not working in a meeting. What is the appropriate first thing to check?
Q4. You want to enable/disable collection of feedback/surveys users send to Microsoft. Best?
Q5. What is a correct way to isolate sign-in issues from join meeting issues?
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.