MS-700 study materials
MS-700 study resources

MS-700 study plan

MS-700 · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Configure and manage a Teams environment

  • Inventory every tenant-wide Teams setting that governs external collaboration (external access, guest access, federation, unmanaged/anonymous join) and set each to a defined target value in a test tenant

  • Differentiate guest access from external access by walking through a request flow for each and recording where each control lives in the admin center

  • Configure the coexistence and upgrade mode between legacy Skype for Business and Teams and predict the user-visible outcome for each mode

  • Set team creation permissions and org-wide team behavior, then record the effect on a standard user account

  • Draft a settings baseline table listing at least 15 tenant settings with chosen value, business rationale, and PowerShell cmdlet or portal location used to change it

Your checkpoint

A one-page tenant settings baseline table (15+ settings, chosen value, where each is configured) validated by screenshots-free written verification steps in a test tenant

Week 2

Configure and manage a Teams environment

  • Build two custom policy packages (one frontline-worker profile, one information-worker profile) and assign them to pilot users

  • Assign Teams policies through group-based assignment and confirm propagation on a per-user basis

  • Author a Teams PowerShell script that bulk-assigns a messaging policy and a meeting policy to a CSV of users and outputs per-user verification

  • Create a custom team template and provision a team from it, then compare the result against a team created from a built-in template

  • Configure Teams update and client-side behavior settings that affect how users receive new features and channels

Your checkpoint

A working PowerShell script plus its output proving that every pilot user received the intended policies from their assigned policy package

Week 3

Manage teams, channels, chats, and apps

  • Manage the full team lifecycle: create from template, change membership and roles, archive, restore, and delete, recording the permission required for each action

  • Compare standard, private, and shared channels by configuring one of each and testing membership, discovery, and file storage behavior

  • Configure messaging policies that govern chat and channel behavior (edit/delete, read receipts, chat creation with external users, and @mentions) and verify each on a test account

  • Configure channel moderation and moderation settings for a shared channel, then validate who can post

  • Set guest and cross-tenant collaboration permissions that control whether shared channels can be used with another organization

Your checkpoint

A channel-type capability matrix (standard vs private vs shared) with tested results, plus a test team holding one channel of each type

Week 4

Manage teams, channels, chats, and apps

  • Configure app permission policies that allow, block, and pin apps by publisher and category, then verify the effect on two different user groups

  • Configure app setup policies to pre-install and pin apps, and confirm the pinned layout on a fresh client sign-in

  • Upload a custom app to the org catalog and control its availability with an app-centric permission policy

  • Manage the app request and approval flow so users can request apps without bypassing governance

  • Map every app in the pilot catalog to a permission policy, a setup policy, and a target user group

Your checkpoint

An app governance sheet covering 10+ apps, each mapped to a permission policy, a setup policy, and an owning audience, with per-group verification notes

Week 5

Manage meetings and calling

  • Configure meeting policies for three personas (executive, presenter, frontline) covering recording, transcription, lobby bypass, who can present, and who can start meetings

  • Configure tenant-level meeting settings that override or constrain per-user policies and identify which settings win

  • Configure live events, webinars, and town halls, and document the capacity, attendee, and licensing constraints of each

  • Set up audio conferencing with dial-in coordinates and apply a conferencing bridge configuration to a pilot user

  • Provision a Teams Rooms or shared device account and apply the device-specific policies

Your checkpoint

A meeting policy matrix mapping three personas to concrete policy values with a written justification for each value

Week 6

Manage meetings and calling

  • Compare calling plans, Direct Routing, and Operator Connect and pick the correct option for three stated business scenarios

  • Configure an auto attendant with a menu and route its options into a call queue, then test the call flow end to end

  • Configure emergency calling, emergency addresses, and location services for a set of users

  • Configure dial plans and normalization rules and predict the translated number for five sample dialed strings

  • Diagnose a failed call scenario using call analytics and record the root cause and remediation

Your checkpoint

A call flow diagram for main number to auto attendant to call queue to agent, annotated with the exact policy and resource that makes each hop work

Week 7

Monitor, report on, and troubleshoot Teams

  • Pull and interpret Teams usage, PSTN usage, and app usage reports, and identify the top three anomalies in a sample dataset

  • Build a call quality investigation using quality data: isolate the affected users, network segments, and device types, and write the finding

  • Configure alert rules and notification contacts so that a defined failure condition generates a notification

  • Collect and interpret client diagnostic logs and match symptoms to the log source that explains them

  • Search the audit log for a specified user action and configure the retention window that governs it

  • Write a troubleshooting runbook mapping at least 10 symptoms to the tool and data source that resolves them

Your checkpoint

A one-page symptom-to-tool troubleshooting runbook plus a written quality investigation with a stated root cause and remediation

Week 8

Configure and manage a Teams environment & Manage teams, channels, chats, and apps & Manage meetings and calling & Monitor, report on, and troubleshoot Teams

  • Re-test the two lowest-scoring objectives from the prior six weeks and confirm improvement with a measurable re-check

  • Complete a timed full-length mock assessment and classify every missed item by domain and objective

  • Consolidate a one-page reference of limits, capacities, and defaults that are commonly tested across all four domains

  • Re-run the weakest hands-on task (policy package, call queue, or app policy) from memory without notes

Your checkpoint

A domain-level readiness scorecard showing per-domain mock scores, the two weakest objectives, and the specific remediation still outstanding

Milestones

Week 2: From a clean test tenant, assign a custom policy package to a pilot group and prove per-user policy state with PowerShell output before moving on

Week 4: Deploy a templated team with one standard, one private, and one shared channel, two policy packages, and two app policies, then score at least 80% on a self-made quiz covering domains 1 and 2

Week 6: Place a simulated inbound call through auto attendant into a queue and answer it as an agent, and score at least 80% on a self-made quiz covering domain 3

Week 8: Score at least 85% on a timed full-length mock, with no single domain below 75%, and hand off a completed readiness scorecard