MS-700 preparation connects a broad Teams administration syllabus with practical tenant administration, so the challenge is making study sessions useful for both exam readiness and real-world work.
MS-700 is the Microsoft exam for administrators who manage Microsoft Teams across chat, meetings, calling, collaboration, governance, security, compliance, and troubleshooting. A useful cheat sheet therefore needs to do more than repeat topic names; it should connect exam objectives to the portals, policies, PowerShell cmdlets, and operational decisions a Teams administrator is expected to recognise.
Last updated: 2026. This guide reflects the current Teams admin model and uses Microsoft Entra terminology rather than older Azure AD naming. Product features can change faster than exam pages, so the exam scope should always be checked against the official Microsoft Learn page before booking the exam, while day-to-day configuration should be validated in a test tenant before being used in production.
How to use this MS-700 cheat sheet
The most efficient way to study MS-700 is to pair each exam domain with a small administrative task. Reading about meeting policies is helpful, but creating one, assigning it to a test user, joining a meeting, and checking the effect in the Teams client builds the kind of recognition that matters during troubleshooting and exam questions.
This cheat sheet is organised around practical administration areas rather than a long catalogue of features. It highlights where an administrator normally works, what the decision is, which policies or cmdlets are worth knowing, and what to practise in a lab tenant. Readers who want guided labs aligned to the same exam can use the MS-700 instructor-led course as a structured path after reviewing the quick reference.
Teams administration foundation
The core administration surface is the Microsoft Teams admin center. Teams administrators also move between the Microsoft 365 admin center, Microsoft Entra admin center, SharePoint admin center, Exchange admin center, and Microsoft Purview depending on the task. This is an important exam point because Teams rarely owns every part of a setting by itself; identity, group lifecycle, files, messages, recordings, retention, and compliance controls often live outside the Teams admin center.
A common mistake is treating the Teams Administrator role as though it has unlimited control over Microsoft 365. In practice, role boundaries matter. A Teams administrator may manage Teams policies and meeting configuration, but SharePoint permissions, Exchange mailboxes, Microsoft Entra conditional access, and Purview compliance policies may require other roles or coordination with other administrators. The article on Microsoft 365 admin roles explained is useful background when revising these boundaries.
Governance starts with the Microsoft 365 Group behind a team. Naming policies, expiration policies, sensitivity labels, templates, and lifecycle reviews reduce the risk of uncontrolled team creation and abandoned workspaces. Exam questions often frame this as a technical setting, but the real administrative issue is ownership: every team should have accountable owners, a clear purpose, and a lifecycle plan before sprawl becomes difficult to reverse.
Objective-mapped quick reference
The MS-700 blueprint expects administrators to plan, configure, manage, secure, and troubleshoot Teams. The following quick reference keeps those areas tied to practical administration rather than abstract revision headings.
- Teams and channels: use the Teams admin center to manage teams, private channels, shared channels, templates, archive settings, and policies that control creation and discovery.
- Users and access: use Microsoft Entra and the Teams admin center for licensing, roles, guest access, external access, and cross-tenant collaboration settings.
- Meetings and events: manage meeting policies, live event policies, webinar and town hall settings where available, meeting templates, recording options, transcription, lobby behaviour, and content sharing.
- Calling: manage phone number assignment, emergency addresses, dial plans, voice routing policies, auto attendants, call queues, and Direct Routing configuration where required.
- Security and compliance: use Microsoft Purview for retention, eDiscovery, DLP, sensitivity labels, communication compliance, and information barriers, while using Teams policies to shape user behaviour.
- Monitoring and troubleshooting: use Call Analytics for user-level call investigation, Call Quality Dashboard for tenant-wide trends, usage reports for adoption, and network tests for readiness validation.
PowerShell remains high value because many administration tasks are easier to audit, repeat, or bulk assign from the command line. For MS-700, administrators should recognise policy assignment cmdlets such as Grant-CsTeamsMeetingPolicy, tenant federation configuration such as Set-CsTenantFederationConfiguration, voice objects such as New-CsAutoAttendant, and voice routing cmdlets such as New-CsOnlineVoiceRoutingPolicy, Get-CsOnlineVoiceRoutingPolicy, and Grant-CsOnlineVoiceRoutingPolicy. A separate reference on Essential Teams PowerShell commands can help turn those names into repeatable practice.
Collaboration: guest access, external access, and shared channels
External collaboration is one of the easiest areas to misconfigure because several features sound similar but solve different problems. External access, also called federation, allows users to find, chat, and call people in external domains without adding them to a team. Guest access adds an external person as a guest in the tenant so they can participate in teams and channels according to guest settings. Shared channels are different again: they support collaboration across organisations through Microsoft Entra cross-tenant access settings and B2B direct connect, without the same guest membership model.
The decision framework is straightforward. Use external access when the requirement is simple cross-organisation chat or calling. Use guest access when the external person needs access to a team, channel conversations, and files governed by the host tenant. Use shared channels when two organisations need longer-running collaboration in a specific channel while keeping users working from their own tenant context.
The main admin paths are Teams admin center > Users > External access for federation-style controls and Teams admin center > Users > Guest access for guest capabilities. Shared channels additionally depend on Microsoft Entra cross-tenant access settings, so a Teams-only change may not be enough. In lab practice, administrators should configure one allowed external domain, invite one guest user to a test team, and then configure a shared channel scenario to see how the user experience and governance model differ.
Meetings, recordings, and compliance controls
Meeting administration is more than switching features on and off. Meeting policies influence who can record, present, bypass the lobby, share content, use transcription, or allow anonymous participants. These settings become operationally important when organisations need different controls for executives, regulated departments, external sessions, or classroom-style meetings.
Compliance depends on where Teams data is stored. Meeting recordings are stored in OneDrive or SharePoint depending on the meeting context, while chat and channel messages are governed through Microsoft 365 compliance capabilities. Microsoft Purview policies such as retention, eDiscovery, DLP, communication compliance, and sensitivity labels can therefore affect Teams content even when the setting is not configured inside the Teams admin center.
The practical exam insight is the interplay between Teams policies and Purview. A meeting policy may allow recording, but retention settings determine how long that recording remains. DLP may restrict sensitive information in chats or files. Sensitivity labels can influence container-level controls for the underlying Microsoft 365 Group and SharePoint site. Administrators who revise these topics together are less likely to choose a Teams-only answer when the scenario is really about information governance.
Voice and telephony decisions
MS-700 candidates should be comfortable with the core voice choices because Teams Phone configuration quickly becomes operational rather than theoretical. Calling Plans use Microsoft as the calling provider where available. Operator Connect uses a participating operator integrated into Teams. Direct Routing connects Teams Phone to a customer-managed or provider-managed session border controller, often abbreviated as SBC.
The choice is usually driven by operational responsibility. Calling Plans reduce telecom infrastructure management but may not fit every regional or carrier requirement. Operator Connect keeps number management and provider connectivity more integrated while still using a carrier relationship. Direct Routing offers the most control for complex routing, existing carrier contracts, contact centre integration, or migration scenarios, but it introduces SBC design, certificate, routing, and monitoring responsibilities.
Exam preparation should include the objects behind the design. Phone number assignment, emergency addresses, dial plans, voice routing policies, call queues, and auto attendants are all part of the administrator’s vocabulary. A small test scenario might assign a number to a user, create an auto attendant for a reception flow, add a call queue for a support group, and review which voice routing policy applies to each test user.
Network readiness, monitoring, and troubleshooting
Teams performance issues often look like application problems when the root cause is network quality, device configuration, or policy mismatch. Poor audio, frozen video, failed screen sharing, or intermittent meeting joins should lead an administrator to examine client health, network path, device drivers, meeting policy, and service health rather than assuming a single cause.
Call Analytics is useful for investigating an individual user’s call or meeting experience. Call Quality Dashboard is better for spotting patterns across buildings, networks, subnets, devices, or time periods. Usage reports show adoption and activity, but they do not replace quality telemetry. In practice, these tools answer different questions: what happened to this user, whether the issue is widespread, and whether Teams is being used as expected.
A minimal readiness check should include media network paths, firewall and proxy behaviour, QoS planning for Teams media traffic, DSCP marking where supported by the network, trusted IPs and network sites for location-aware features, and emergency calling configuration. Location-based routing may also matter in regulated or complex voice environments. Lab work should include reviewing a poor-quality call in Call Analytics, comparing it with CQD trends, and checking whether the issue appears to be device-specific, network-specific, or tenant-wide.
Practical labs for exam preparation
The most useful MS-700 labs are small, repeatable, and easy to reset. A test tenant, a few licensed users, and a deliberate naming convention are enough for most revision tasks. The goal is not to build a production-grade Teams environment; it is to make the administrative cause and effect visible.
Start with collaboration. Create a team from a template, add standard and private channels, configure external access for one domain, add a guest user, and compare that with a shared channel scenario. Then move to meetings by creating two meeting policies, assigning them to different users, and testing recording, lobby, presenter, and content sharing behaviour.
Security and compliance practice should connect Teams with Microsoft Purview. Apply a retention policy to Teams messages in a test scope, review how DLP affects chat or files, and confirm how recordings appear in OneDrive or SharePoint. For voice, build a simple call flow with an auto attendant and call queue, then review which policies and numbers are assigned to each user.
Troubleshooting labs should be equally direct. Create a scenario where a user cannot chat externally because federation is restricted, a guest cannot access a team because guest settings or sharing permissions block access, or a meeting participant cannot record because policy prevents it. These exercises help administrators recognise whether the fix belongs in Teams admin center, Microsoft Entra, SharePoint, Exchange, or Microsoft Purview.
Study priorities that map to real administration
MS-700 preparation works best when candidates avoid memorising isolated feature names. The exam frequently describes an administrative outcome, such as controlling external collaboration or improving meeting quality, and expects the candidate to identify the right policy, portal, role, or reporting tool. That makes scenario-based study more valuable than reading long lists of settings.
Good revision should include official Microsoft Learn exam objectives, hands-on testing in a non-production tenant, and selective PowerShell practice. It should also include awareness of feature movement between portals, because Microsoft 365 administration changes over time. The stable skill is knowing how identity, collaboration, compliance, voice, and monitoring fit together.
Administrators planning several Microsoft certifications may also want to consider how Teams administration connects with broader Microsoft 365 administration, security, and endpoint management. Readynez includes MS-700 and other Microsoft training within Unlimited Microsoft Training, which can make sense for learners building a wider certification plan rather than preparing for one exam in isolation.
Using this cheat sheet in practice
A strong MS-700 study plan should produce an administrator who can explain a setting, find it in the correct portal, apply it to the right users, validate the result, and troubleshoot the outcome. That is the difference between recognising a term and being able to manage Teams in a real Microsoft 365 tenant.
The most practical next step is to turn each section into a short lab and keep notes on the portal path, policy name, cmdlet, and validation method. Readynez can support that process through structured MS-700 training, and readers who want help choosing a suitable route can contact the team with questions about the Microsoft 365 Teams Administrator certification.
FAQ
What is an MS-700 cheat sheet?
An MS-700 cheat sheet is a concise study reference for Microsoft Exam MS-700: Managing Microsoft Teams. A useful version maps exam topics to real administration tasks such as configuring Teams policies, managing external collaboration, setting up meetings, reviewing compliance controls, and troubleshooting call quality.
Can a cheat sheet help with the MS-700 exam?
A cheat sheet can help by organising key concepts and reminding candidates which portal, policy, or cmdlet applies to a scenario. It should not be treated as a complete substitute for Microsoft Learn, hands-on lab work, and review of the current exam skills outline.
What should MS-700 candidates practise in a lab tenant?
Good lab scenarios include configuring guest access and external access, creating meeting policies, testing recording and lobby settings, reviewing retention or DLP effects in Microsoft Purview, assigning Teams Phone settings where licensing allows, and investigating call quality in Call Analytics or CQD.
Which PowerShell cmdlets are useful for MS-700 revision?
High-yield examples include Grant-CsTeamsMeetingPolicy, Set-CsTenantFederationConfiguration, New-CsAutoAttendant, New-CsOnlineVoiceRoutingPolicy, Get-CsOnlineVoiceRoutingPolicy, and Grant-CsOnlineVoiceRoutingPolicy. Candidates should understand what each cmdlet is used for rather than memorising syntax alone.
What is the difference between guest access and external access in Teams?
External access allows users to communicate with people in other domains without adding them as members of the tenant. Guest access adds an external user as a guest so they can participate in teams and channels, subject to tenant settings, team membership, and sharing controls.
