Microsoft MS-700 Cheat Sheet: Teams Administrator

May 1, 2026

Review the Microsoft Teams Administrator (MS-700) scope, Teams governance, meetings, messaging, voice, apps, external access, lifecycle, compliance, and troubleshooting traps before practicing.

On this page

MS-700 is a Teams administration exam. Use this cheat sheet to separate collaboration governance, meeting policy, messaging, voice, apps, external access, lifecycle, compliance, and troubleshooting decisions.

Use this with practice. Review the Teams administration checkpoints, then return to the MS-700 exam page for sample questions and update tracking.

Open MS-700 practice page Compare Microsoft 365 routes

Exam snapshot

Field	Detail
Issuer	Microsoft
Certification lane	Microsoft Teams Administrator
Exam code	MS-700
Main scope	Teams collaboration, governance, meetings, voice, apps, lifecycle, compliance, and troubleshooting
IT Mastery status	Sample questions available

Teams administration map

Area	What to know	Common trap
Governance and lifecycle	Naming, ownership, expiration, archive, templates, sensitivity, and review	Letting unmanaged teams accumulate without owners
External collaboration	Guest access, external access, sharing settings, sensitivity, and channel membership	Confusing external access with guest membership
Meeting and messaging policies	Recording, transcription, lobby, chat, private chat, and user experience controls	Changing a tenant-wide setting when a scoped policy is needed
Voice and quality	Calling, phone system concepts, emergency calling, call analytics, network readiness, and devices	Treating call quality as only a user-device issue
App governance	Permission policies, setup policies, approved apps, custom apps, and app lifecycle	Allowing every app without risk review
Compliance and security	Retention, eDiscovery, audit, information barriers, labels, and communication controls	Assuming Teams compliance is separate from Microsoft Purview

Must-know distinctions

Distinction	How to decide
Guest access vs external access	Guest access adds external users to teams; external access allows communication across organizations.
Team vs channel	A team manages membership and broader workspace; channels organize work within that team.
Standard vs private channel	Standard channels follow team membership; private channels restrict membership inside the team.
Meeting policy vs messaging policy	Meeting policy controls meetings; messaging policy controls chat and message features.
App permission policy vs setup policy	Permission policy controls allowed apps; setup policy controls pinned and installed app experience.
Teams setting vs Purview setting	Teams controls collaboration behavior; Purview controls retention, eDiscovery, audit, and compliance.

High-yield checklist

Identify whether the issue is tenant-wide, policy-scoped, team-specific, or user-specific.
Check license, role, policy assignment, and group membership before deeper troubleshooting.
Use governance controls for naming, owners, expiration, templates, and lifecycle.
Use guest and external access settings carefully for partner collaboration.
Use meeting policies for recording, transcription, lobby, and meeting-feature scenarios.
Use messaging policies for chat and message-feature scenarios.
Use app policies for approved, blocked, pinned, or custom Teams apps.
Use call analytics, network readiness, and device evidence for quality issues.
Use Purview controls when retention, eDiscovery, or audit is the requirement.

Common traps

Treating private channels as a replacement for a separate team when governance needs differ.
Changing a global policy when only one group needs restriction.
Ignoring SharePoint and OneDrive behavior for Teams files.
Solving a compliance requirement only inside the Teams admin center.
Assuming every call-quality issue is caused by Microsoft service health.
Leaving inactive teams without lifecycle controls.

Practice strategy

For MS-700 misses, name the control plane first: team lifecycle, external collaboration, meeting policy, messaging policy, app policy, voice, files, or compliance. Then decide whether the fix belongs in Teams admin settings, Microsoft 365 administration, SharePoint, identity, or Purview.

Revised on Monday, May 25, 2026