🎯 Teams Administration Course · Module 1 of 6
Teams Admin Center Overview & Navigation
MS-700 Exam Alignment
MS-700
Plan and configure a Microsoft Teams environment: navigate the Teams Admin Center, understand its left navigation sections, configure tenant-wide settings, plan network requirements using Network Planner, and connect via Microsoft Teams PowerShell.
- Know the URL for the Teams Admin Center (admin.teams.microsoft.com) and the required admin roles
- Identify which TAC section manages each Teams configuration area
- Understand the difference between Teams Administrator and Teams Communications Administrator roles
- Configure Teams upgrade settings — coexistence modes (Islands, Teams Only, SfB with Teams Collab)
- Use Network Planner to estimate bandwidth requirements before Teams rollout
Exam Tip: MS-700 regularly tests role scoping — know that the Teams Administrator role manages all Teams features, while Teams Communications Administrator is scoped to calling, meetings, and voice only. Also know coexistence modes: most organisations go directly to Teams Only mode when migrating from Skype for Business.
The Microsoft Teams Admin Center at admin.teams.microsoft.com is the dedicated portal for administering Microsoft Teams across your organisation. As a Teams administrator, you spend most of your time here — managing policies, configuring calling, governing apps, and monitoring usage. This module walks through the portal from first login to confident daily navigation.
🖥️ Accessing the Teams Admin Center
admin.teams.microsoft.com
🏠 Dashboard
👥 Teams
Manage teams
Teams policies
Templates
👤 Users
🖥️ Devices
📅 Meetings
Meeting policies
Meeting settings
Audio conferencing
📞 Voice
💬 Messaging
📱 Apps
🔔 Notifications
⚙️ Org-wide settings
📊 Analytics & reports
🔧 Planning
Dashboard
Active users
1,247
Teams created
184
Meeting minutes (7d)
42.6K
Recent admin activity
Meeting policy "Corporate-Meetings" updated · 2 hours ago
Guest access enabled for tenant · Yesterday
App permission policy assigned to 45 users · 2 days ago
🗺️ Left Navigation — Section by Section
The Teams Admin Center left navigation organises everything by functional area. Understanding which section manages what is a core MS-700 exam skill.
| Section | What You Manage |
|---|---|
| Teams | Create/delete individual teams, manage membership, configure Teams policies (who can create teams, private channels, shared channels), Teams templates, update policies |
| Users | View all Teams users, manage per-user policy assignments, view call history and call quality per user |
| Devices | Manage Teams-certified IP phones, displays, panels, collaboration bars, and Teams Rooms devices (Windows and Android) |
| Locations | Configure emergency addresses (E911), network sites, and subnets for location-based routing and emergency calling |
| Meetings | Meeting policies (recording, transcription, lobby, attendance), meeting settings (PSTN conferencing), live event policies, audio conferencing |
| Voice | Phone numbers, calling policies, dial plans, voicemail, emergency calling policies, call park policies, caller ID policies, auto attendants, call queues |
| Messaging | Messaging policies — who can use Giphy, memes, stickers, priority notifications, read receipts, URL previews |
| Apps | Manage Teams apps — org-wide app settings, app permission policies (which apps users can install), app setup policies (pinned apps), custom app publishing |
| Org-wide settings | External access (federation), guest access, Teams settings (email integration, file sharing, devices), Teams upgrade (coexistence mode) |
| Analytics & reports | Teams usage reports, PSTN usage reports, app usage reports, Call Quality Dashboard (CQD) |
| Planning | Network Planner (bandwidth calculator), Teams Advisor (guided deployment), Teams health assessments |
🔑 Admin Roles for Teams
Not all Teams administrators need the same level of access. Microsoft provides several scoped roles to apply the principle of least privilege:
| Role | Scope | Typical Assignee |
|---|---|---|
| Teams Administrator | Full access to all Teams Admin Center sections — policies, settings, devices, voice, apps, analytics | Senior Microsoft Teams Engineers |
| Teams Communications Administrator | Manage meetings, calling, voice, audio conferencing, and PSTN settings — cannot manage teams/channels governance or apps | Unified Communications Engineers |
| Teams Communications Support Engineer | View detailed call analytics per user (full call record with all details) — troubleshooting tool, no configuration access | Senior Help Desk / UC Support |
| Teams Communications Support Specialist | View limited call analytics per user (redacted details — can't see full phone numbers or internal information) — basic troubleshooting | Tier 1 / 2 Help Desk |
| Teams Devices Administrator | Manage Teams-certified devices only — no access to policies, voice, or other sections | IT Desktop / AV Support |
| Global Administrator | Full access to all Microsoft 365 services including Teams | Only when absolutely required (break-glass) |
⚠️ Exam Distinction — Communications Admin vs Teams Admin
The most-tested role scoping question on MS-700: if someone needs to manage meeting recording policies and audio conferencing, assign Teams Communications Administrator. If they also need to manage team creation policies, naming policies, and app governance, they need the full Teams Administrator role. The Communications Administrator cannot touch team/channel governance, app policies, or Teams templates.
🔄 Teams Upgrade — Coexistence Modes
When organisations migrate from Skype for Business (on-premises or Online) to Teams, the coexistence mode controls how the two applications interact during the transition period. Configured under Org-wide settings → Teams upgrade.
| Mode | Chat & Calling | Meetings | Use Case |
|---|---|---|---|
| Islands | Both Teams and SfB run simultaneously — users receive messages and calls in both apps | Users can schedule meetings in both apps | Early pilot — users test Teams alongside SfB. Can cause confusion (missed calls/chats in one app) |
| SfB Only | All chat and calling stays in Skype for Business — Teams is not used | All meetings in SfB | Not commonly used — typically just a starting point |
| SfB with Teams Collab | Chat and calling in SfB — Teams used only for channels/collaboration | Meetings in SfB | Introducing Teams for file collaboration while SfB handles UC |
| SfB with Teams Collab and Meetings | Chat and calling in SfB — Teams for channels + Teams for meeting scheduling | Teams meetings (better meeting experience early) | Transitional — getting users onto Teams Meetings before full UC switch |
| Teams Only | All chat, calling, and meetings move to Teams — SfB client no longer used | All meetings in Teams | Final target state for all Microsoft 365 organisations. SfB Online was retired in July 2021. |
✅ For New Microsoft 365 Tenants
New Microsoft 365 tenants that have never used Skype for Business should be set directly to Teams Only mode — there is no legacy platform to coexist with. The coexistence modes are only relevant when migrating from an existing Skype for Business deployment.
🌐 Network Planner
Network Planner (under Planning → Network planner) is a tool in the Teams Admin Center that estimates the bandwidth requirements for Teams audio, video, and screen sharing based on your organisation's network sites, number of users, and usage patterns.
TAC › Planning › Network planner
💡 What Network Planner Calculates
- Bandwidth per modality — Audio (up to 70 Kbps), video (up to 4 Mbps for HD), screen sharing (up to 15 Mbps), file transfers
- Per-site estimates — Enter each office location with its user count and internet connection capacity; Network Planner tells you whether your current bandwidth is sufficient
- Personas — Define the mix of user types (Office Worker, Remote Worker, Teams Rooms on Surface Hub, Teams Phone) for each site to get realistic estimates
- Network requirements report — Exportable report showing recommended bandwidth per site for each call type
⚡ Microsoft Teams PowerShell
The MicrosoftTeams PowerShell module provides cmdlets for every Teams Admin Center operation. It is separate from Microsoft Graph PowerShell and must be installed independently.
PowerShell — Install & Connect to Microsoft Teams
# Install the Microsoft Teams PowerShell module (run once) Install-Module MicrosoftTeams -Scope CurrentUser -Force # Connect to Teams (prompts for M365 admin credentials) Connect-MicrosoftTeams # Verify the connection and tenant details Get-CsTenant | Select-Object DisplayName,TenantId,TeamsUpgradeEffectiveMode # Check the current tenant-wide Teams coexistence mode Get-CsTeamsUpgradeConfiguration # Check a specific user's effective upgrade mode Get-CsOnlineUser -Identity user@techcareers.in | Select-Object DisplayName,TeamsUpgradeEffectiveMode # Disconnect when finished Disconnect-MicrosoftTeams
PowerShell — Set Coexistence Mode & Check Licensing
Connect-MicrosoftTeams # Set the entire tenant to Teams Only mode Grant-CsTeamsUpgradePolicy -PolicyName UpgradeToTeams -Global # Set a single user to Teams Only mode Grant-CsTeamsUpgradePolicy -Identity user@techcareers.in -PolicyName UpgradeToTeams # Find users still on Islands mode Get-CsOnlineUser -ResultSize Unlimited | Where-Object TeamsUpgradeEffectiveMode -eq "Islands" | Select-Object DisplayName,UserPrincipalName,TeamsUpgradeEffectiveMode # List all available upgrade policies Get-CsTeamsUpgradePolicy | Select-Object Identity,Mode,Description
💡 Best Practices
- Assign the minimum required Teams admin role — most day-to-day operations can be done by Teams Communications Administrator without needing the full Teams Administrator role
- For new Microsoft 365 tenants, set Teams upgrade mode to Teams Only immediately — there is no SfB to coexist with and Islands mode only causes confusion
- Run Network Planner before deploying Teams to a new office or site — bandwidth surprises discovered post-deployment are much harder to fix than pre-planned network upgrades
- Use the Teams Admin Center dashboard's recent admin activity log as a first-line audit tool — if something changed unexpectedly, the dashboard often surfaces it immediately
- Never use Global Administrator for routine Teams administration — the Teams Administrator role provides complete Teams management without the risk of accidental changes to other M365 services
🎓 Interview Q&A
Q: What is the URL for the Microsoft Teams Admin Center and which admin role is required?
The Teams Admin Center is at admin.teams.microsoft.com. The minimum role required for full administrative access is Teams Administrator. For meeting and calling management only, Teams Communications Administrator is sufficient. Global Administrator also has access. Standard Microsoft 365 users with no admin role cannot access the Teams Admin Center.
Q: What is the difference between the Teams Administrator role and the Teams Communications Administrator role?
Teams Administrator has full access to all Teams Admin Center sections — teams and channels governance, policies, apps, voice, meetings, devices, org-wide settings, and analytics. Teams Communications Administrator is scoped to meetings, calling, audio conferencing, voice, and PSTN settings — it cannot manage team creation policies, app governance, Teams templates, or naming policies. Assign Communications Administrator to UC engineers who manage the calling and meetings stack but should not touch Teams governance.
Q: What is Teams upgrade Islands mode and when would you use it?
Islands mode is a Teams upgrade coexistence mode where both Teams and Skype for Business run simultaneously — users receive chat messages and calls in both clients and can schedule meetings in either. It is used during the early pilot phase of a Skype for Business to Teams migration when users are still discovering Teams. The main risk is message and call routing confusion — a user may be chatted in Teams but respond in SfB, or receive calls in SfB that they expected in Teams. Most organisations move quickly past Islands mode to Teams Only.
Q: What PowerShell module is used for Microsoft Teams administration and how do you connect?
The MicrosoftTeams PowerShell module (installed with Install-Module MicrosoftTeams) is the primary module for Teams administration. Connect with Connect-MicrosoftTeams, which prompts for Microsoft 365 admin credentials. The module uses Cs* cmdlets (from legacy Skype for Business PowerShell) alongside newer Teams-specific cmdlets. It is separate from Microsoft Graph PowerShell and must be installed and connected independently.
Q: What does Network Planner in the Teams Admin Center do?
Network Planner (TAC → Planning → Network planner) calculates estimated bandwidth requirements for Teams audio, video, screen sharing, and file transfers at each office location. You define your network sites (with user counts and current internet bandwidth) and user personas (office worker, remote worker, Teams Rooms), and Network Planner outputs whether your existing bandwidth is sufficient and what upgrade is needed before deploying Teams. It is a pre-deployment planning tool — not a real-time monitoring tool.
🎯 MS-700 Mock Test
Module 1 — Teams Admin Center Overview & Navigation
Question 1 of 5
A UC engineer needs to manage Teams meeting policies and configure audio conferencing bridge numbers. They should not be able to change team creation policies or app permission settings. Which role should be assigned?
✅ Correct answer: B. Teams Communications Administrator is scoped to meetings, audio conferencing, calling, and voice — exactly what's needed. It cannot access team/channel governance settings (who can create teams), app permission policies, or Teams templates. Teams Administrator (A) would give too much access. Global Administrator (D) violates least privilege. Communications Support Engineer (C) can only view call data — cannot make configuration changes.
Question 2 of 5
A new Microsoft 365 tenant that has never used Skype for Business is being set up for Teams. Which Teams upgrade coexistence mode should be configured?
✅ Correct answer: D. For a new Microsoft 365 tenant with no Skype for Business deployment, set the mode directly to Teams Only. The coexistence modes (Islands, SfB with Teams Collab, etc.) are designed specifically for organisations migrating from an existing Skype for Business platform — they have no benefit and only add confusion for new tenants.
Question 3 of 5
An IT technician needs to check the call quality data for a specific user who reported poor audio quality on their Teams calls. The technician should not be able to make any configuration changes. Which role should be assigned?
✅ Correct answer: C. Teams Communications Support Specialist can view limited per-user call analytics for troubleshooting (redacted details — cannot see full phone numbers or sensitive information) and cannot make any configuration changes. Teams Communications Support Engineer (not listed) can see full detailed call records. Both support roles are read-only troubleshooting roles. Teams Devices Administrator (B) is scoped to device management only — it cannot view call data.
Question 4 of 5
An organisation is planning a Teams rollout to 5 regional offices. Management wants to know if the existing internet connections at each office can handle Teams video calls. Which tool in the Teams Admin Center should you use?
✅ Correct answer: A. Network Planner (Planning → Network planner) is specifically designed for pre-deployment bandwidth planning. You define your network sites with their user counts and current internet bandwidth, select user personas (office worker, remote worker, Teams Rooms), and Network Planner calculates whether the existing connections are sufficient and shows the recommended bandwidth per site. This is a planning tool — Call Quality Dashboard (C) requires Teams to already be deployed and in use.
Question 5 of 5
Which PowerShell cmdlet connects your session to Microsoft Teams for administrative management?
✅ Correct answer: B. Connect-MicrosoftTeams is the correct cmdlet from the MicrosoftTeams PowerShell module. It authenticates against Microsoft 365 and provides access to all Cs* Teams cmdlets. Connect-MgGraph (A) is for Microsoft Graph PowerShell — it can access some Teams data via Graph API but is not the primary Teams admin module. Connect-ExchangeOnline (C) is for Exchange Online only. Connect-AzureAD (D) is the deprecated Azure AD module.
🔒
This module is lockedComplete the previous module and pass its mock test to unlock this module.