MS-700 remains the Managing Microsoft Teams exam for the Teams Administrator Associate role. As of October 4, 2026, the live English skills are the July 29, 2026 version. Microsoft has already published another English-language update for October 27, so candidates should align final preparation to the date of the appointment rather than blend current and future objective wording.
The current MS-700 weighting is 40–45% Configure and manage a Teams environment, 20–25% Manage teams, channels, chats, and apps, 15–20% Manage meetings and calling, and 15–20% Monitor, report on, and troubleshoot Teams. Microsoft requires a score of 700 or greater to pass.
Teams environment management dominates at 40–45%
This domain covers network planning, security/compliance, governance, external collaboration, clients, and devices. It deserves the largest study block because most Teams administration problems begin with the environment around the team or meeting, not the visible chat interface itself.
A Teams governance model helps connect policy assignment, group lifecycle, naming, guest access, and administration at scale.
Network readiness is a Teams administration responsibility
Voice, video, meetings, and events depend on bandwidth, ports/protocols, client paths, and Microsoft 365 connectivity. Teams Network Planner, network assessment tooling, and connectivity testing help administrators distinguish service problems from local network design problems.
A collaboration platform can be correctly configured yet deliver poor user experience when the network path is weak.
Security and compliance cross several Microsoft 365 services
The current blueprint includes Teams admin roles, Defender for Office 365 threat policies, retention, sensitivity labels, DLP, Conditional Access, Information Barriers, Communication Compliance, and Insider Risk Management concepts.
A Teams security and compliance approach should identify whether the requirement is identity access, message/file protection, retention, insider behavior, or threat protection rather than treating security as one Teams-only setting.
Governance includes policy, lifecycle, and automation
Teams content is distributed across Teams, SharePoint, OneDrive, Exchange, and Microsoft 365 Groups. The administrator should understand policy packages, policy assignment, group-creation settings, expiration/naming, archive/delete/restore, access reviews, and PowerShell/Graph operations.
Lifecycle management is important because inactive teams, stale guests, and unmanaged policies accumulate risk and complexity over time.
External collaboration has several boundaries
External access, guest access, SharePoint/OneDrive external sharing, Entra external collaboration, shared channels, B2B direct connect, cross-tenant settings, and multitenant organization concepts solve different collaboration patterns.
A cross-workload external-sharing model is useful because Teams conversations and files can be governed by different underlying services.
Teams, channels, chats, and apps account for 20–25%
This domain covers team creation, templates, membership/roles, frontline experiences, standard/private/shared channels, messaging policies, app assignments, app setup policies, permissions/consent, app-store purchasing/customization, and custom app upload.
Channel type is an architectural choice because private and shared channels create different membership and collaboration boundaries from standard channels.
Meetings and calling represent 15–20%
Administrators need to choose meeting types such as meetings, webinars, town halls, and Appointments; configure meeting settings/policies/templates; and manage event behavior. Teams Phone topics include numbers, voice policies, voicemail, auto attendants, call queues, and calling policies.
The current role spans collaboration and telephony, so meeting/calling operations cannot be treated as optional specialist material.
Monitoring and troubleshooting is another 15–20%
Current objectives include voice and meeting quality, alerts, Teams usage, app usage, active users, per-meeting metrics, storage usage, team creation/deletion, guest access, network-connectivity testing, feedback, and troubleshooting of audio/video/client behavior.
A Teams analytics and reporting mindset turns usage and quality data into operational decisions rather than monthly statistics.
Teams troubleshooting starts with the client but does not end there
Administrators may collect client logs, clear cache, run self-help diagnostics, troubleshoot install/update/sign-in, and investigate meeting feature problems. Symptoms can also originate in licensing, identity, network, policy, device firmware, or Microsoft service health.
Effective troubleshooting therefore follows evidence through the dependency chain instead of resetting the client for every problem.
October 27 creates a near-term version boundary
Microsoft has already published the October 27 update and change log. The four top-level weights stay the same, but several detailed objectives receive minor changes. Candidates testing before October 27 should use July 29 skills; later candidates should refresh against the updated guide.
The current audience profile describes a Teams administrator as responsible for internal and external collaboration and communication while working with identity, licensing, information management, adoption, security, compliance, devices, and networking owners. This explains why the exam feels broader than Teams chat and meetings: the administrator coordinates dependencies that sit across Microsoft 365.
Network bandwidth calculations matter because voice/video quality is sensitive to latency, jitter, packet loss, and congestion. The administrator should understand when a branch office needs remediation or QoS/network changes before rolling out large meetings or Teams Phone broadly.
Teams network ports and protocols should be learned as operational dependencies rather than a memorization contest. Firewalls, proxies, VPN designs, and split tunneling can influence media paths. A policy change inside Teams cannot fix a blocked or inefficient network path.
Teams security/compliance licensing should be checked because features such as advanced Purview or Defender capabilities may depend on licensing beyond the base Teams service. Scenario questions can test whether the capability is technically available to the organization before configuration begins.
Sensitivity labels for Teams can influence privacy and external sharing of teams or meetings, while retention policies determine lifecycle of messages or associated content. These controls operate alongside identity and threat policies, illustrating why Teams administration spans several Microsoft portals.
Information Barriers address communication restrictions between defined groups, while Communication Compliance and Insider Risk Management serve monitoring/investigation use cases. The administrator should recognize the business purpose of each rather than treat all three as generic compliance controls.
Policy packages are useful when groups of users need a consistent set of Teams policies. Frontline workers, education users, or other populations can require different meeting, messaging, or app behavior. Centralized assignment reduces configuration drift compared with manual user-by-user changes.
Teams update policies matter because client experience and feature availability can depend on update channels or rollout behavior. Administrators need enough change-management awareness to support new features without surprising critical user groups or device fleets.
Access reviews for groups and teams help solve stale membership, particularly in long-running collaboration spaces. A team can begin with the correct users and still become overexposed months later when projects end or roles change.
Shared channels are an important cross-tenant collaboration pattern because external participants can collaborate through B2B direct connect under configured cross-tenant trust rather than always joining as traditional guests. The design changes identity lifecycle, policy, and governance expectations.
Multitenant organization capabilities matter when related tenants need richer cross-tenant collaboration. This is different from opening external access broadly to the internet. The administrator should understand the business relationship and trust configuration before enabling wider collaboration.
Teams devices are managed service endpoints. Configuration profiles, firmware, tags, remote sign-in, resource accounts, and licensing affect meeting rooms, phones, panels, and other hardware. A room issue can originate in device health even when users’ desktop clients work normally.
VDI introduces another media/client model because Teams needs optimization for virtualized desktops to deliver acceptable audio/video performance. The current scope expects administrators to plan and configure Teams for VDI rather than assume the standard desktop-client architecture applies unchanged.
App governance includes consent and permissions because a Teams app can access Microsoft 365 data or act on behalf of users. Store purchasing, custom apps, setup policies, and permission policies therefore have security and support implications, not only productivity benefits.
Webinars and town halls should be distinguished by audience scale and event model. Meeting templates/policies and event settings define experience consistently across organizers. Microsoft 365 Copilot meeting settings also appear in the current detailed objectives, reflecting how AI-assisted collaboration now reaches the admin role.
Teams Phone auto attendants and call queues are service workflows rather than ordinary user numbers. They rely on resource accounts and policies in addition to PSTN connectivity. Voice administration should therefore connect numbers, identities, routing, and user experience.
Monitoring team creation/deletion and guest access is a governance signal. Rapid creation can indicate adoption or sprawl; many stale guests can indicate lifecycle weakness. Reports are most valuable when they drive ownership reviews or policy changes.
Microsoft’s upcoming October 27 update is minor rather than a replacement of the exam structure. Candidates do not need to relearn Teams from scratch, but they should update changed wording around network settings, external collaboration, team/app management, and troubleshooting if their exam is after the date.
Microsoft 365 Group naming and expiration policies matter because teams often inherit or depend on the group lifecycle underneath. A team name can therefore be constrained by organizational naming rules, and inactive groups can expire unless renewed. Teams governance is partly Microsoft 365 Groups governance.
Restore/troubleshoot deletion of a Microsoft 365 Group is another lifecycle objective because deleting a team can affect connected resources. Administrators need to know that recovery and retention windows exist and that “team deleted” can be broader than one chat container disappearing.
Teams Advisor is included in the team-management domain as a rollout-planning tool. It helps administrators structure deployment tasks for Teams workloads rather than relying on an ad-hoc launch. The exam can test planning and governance, not only steady-state administration.
Frontline teams and experiences appear because Teams administration must support workers who may share devices, work shifts, or use specialized workflows. Policies and deployment patterns can differ from knowledge-worker scenarios, so one universal configuration may not fit the entire organization.
Standard, private, and shared channels should be chosen deliberately. Private channels create restricted membership inside a team; shared channels can reach people outside the team or tenant under supported cross-tenant settings. Membership boundaries affect both files and communication.
Messaging policies are separate from meeting policies. Messaging policies affect chat/channel features, while meeting policies govern meeting capabilities. When a user can chat but cannot use a meeting feature, the administrator should inspect the correct policy family instead of changing unrelated collaboration settings.
App extensibility includes tabs, meeting apps, messaging extensions, and workflows. These features can improve productivity but introduce permission and support dependencies. Administrators need enough awareness to choose an extension model and govern how apps are acquired and consented.
Meeting templates are useful for standardizing organizer choices around scenarios such as confidential meetings or webinars, while meeting policies define what users are allowed to do. Templates help consistency; policies enforce capability boundaries. Knowing that distinction improves troubleshooting.
Voice policies and calling policies should also be kept separate conceptually. Voice routing/phone settings determine PSTN behavior and number-related capabilities, while calling policies can enable or restrict user calling features. A Teams Phone scenario often involves several policy layers.
Auto attendants and call queues create organization-facing call flows. Auto attendants route callers through menu/time rules, while call queues distribute calls to agents. Both can depend on resource accounts and numbers, so service-account design is part of voice administration.
Per-meeting metrics and Call Analytics help administrators examine quality for a specific experience, while broader reports reveal location/device/tenant trends. Troubleshooting should move from individual event evidence to systemic pattern only when the data supports it.
Guest-access reporting is valuable because guests can remain after projects end. A healthy tenant should have a process for reviewing or removing external users and shared-channel relationships. External collaboration should have an end state, not only an onboarding path.
Feedback management appears because Teams continuously evolves. User feedback, client health, usage, and support incidents can reveal where policies or training are creating friction. Administration includes adoption and usability, not only enforcement.
The Teams Administrator role remains an integration role across identity, licensing, information management, security, compliance, devices, adoption, and networking. That breadth is the real meaning of the blueprint.