Microsoft Teams Administrator

Real-time audio and video punish a weak network. You plan bandwidth and ports, mark traffic for quality of service, check each site’s readiness, and design around VPNs and branch offices.

• How Teams media travels across a network
• Estimating bandwidth with the network planner
• Ports, addresses and firewall rules
• Quality of service and traffic marking
• VPNs, split tunneling and branch offices
• Testing network readiness

You build A network plan for three sites, with bandwidth estimates and firewall and quality-of-service settings.

Collaboration spreads data quickly, so controls must be there from the start. You apply Conditional Access and multifactor, set expiration and naming rules, and use labels, retention and DLP to govern what teams hold.

• Conditional Access and multifactor for Teams
• Group expiration and naming policies
• Sensitivity labels for teams and channels
• Retention and DLP for chat and channels
• Who may create teams
• Auditing Teams activity

You build A governance plan for Teams covering creation, naming, labels, retention and expiry.

Teams is often used with outsiders, and each option exposes something different. You compare guest access, external access and shared channels, and set the controls that let partners in without opening the door wide.

• Guest access compared with external access
• Shared channels and cross-tenant settings
• Guest permissions and expiry
• Controlling which domains may connect
• Securing external meetings

You build An external collaboration policy that names the right option for partners, customers and contractors.

The experience people get depends on the client and the device in front of them. You deploy and update clients, manage phones, panels and Teams Rooms, and keep devices configured and healthy.

• Deploying and updating the Teams client
• Teams phones and displays
• Teams Rooms: components and setup
• Managing devices in the admin center
• Updating device firmware and software

You build A device rollout plan for a meeting room and a desk phone, with its management settings.

A tenant can grow thousands of teams that nobody tends. You create teams from templates and existing groups, choose standard, private or shared channels, and manage owners and the life cycle through archiving and cleanup.

• Team templates and creating from a group
• Standard, private and shared channels
• Owners, members and ownerless teams
• Archiving and restoring teams
• Bulk management with PowerShell

You build A set of team templates and a life-cycle process from creation to archive.

Apps make Teams useful and can make it risky. You manage messaging policies, control apps with permission and setup policies, handle custom app uploads, and decide how users consent to app permissions.

• Messaging and chat policies
• App permission policies
• App setup policies and pinned apps
• Custom and third-party app approval
• Org-wide app settings and consent

You build An app governance model with permission and setup policies for three user groups.

Meeting settings shape how people work together every day. You choose between meeting types, write policies and templates, control recording and transcription, and set audio conferencing for people who dial in.

• Meeting policies and meeting templates
• Webinars and town halls compared
• Lobby, attendee and presenter controls
• Recording, transcription and where files go
• Audio conferencing and dial-in numbers

You build A meeting policy design for staff, executives and external events, with a template for each.

Phone service replaces the old PBX only if numbers and routing are right. You choose a calling model, provision and assign numbers, set voice and voicemail policies, and build call queues and auto attendants.

• Calling Plans, Operator Connect and Direct Routing compared
• Getting, porting and assigning phone numbers
• Emergency calling basics
• Call policies and voicemail settings
• Auto attendants, call queues and resource accounts

You build A phone setup for a small office, with numbers, an auto attendant and a call queue.

You cannot improve what you do not measure. You read usage and adoption reports, then use Call Analytics and the Call Quality Dashboard to find who had a bad call and why.

• Usage and adoption reports
• Call Analytics for a single user’s call
• Call Quality Dashboard for patterns
• Network and device causes of poor quality
• Reporting to stakeholders

You build A call quality report that finds the sites and devices behind poor calls.

Problems reach you through users, so tell them apart quickly. You set alert rules, read service health, and troubleshoot audio, video and client installation faults using logs and a repeatable method.

• Alert rules and notifications
• Service health and incident history
• Collecting and reading client logs
• Fixing audio and video problems
• Installation and sign-in failures

You build A troubleshooting guide for the faults users report most often, with log steps for each.

One scenario joins every area. You plan the network and security, design teams, apps, meetings and phone, and set up monitoring, then explain how you would run it day to day.

• Reading the company’s collaboration needs
• Designing network, security and governance
• Designing teams, apps, meetings and calling
• Setting up monitoring and support
• Presenting the operating model

You build A complete Teams operating design: policies, governance, phone, monitoring and support runbooks.