This chapter provides a comprehensive deep dive into Microsoft Teams, a core workload in Microsoft 365. As a key component of the MS-900 exam (Objective 2.1: Describe productivity solutions of Microsoft 365), understanding Teams—its architecture, features, and licensing—is critical. Exam questions on Teams typically account for 15–20% of the productivity solutions section. We will cover Teams' internal workings, its integration with other Microsoft 365 services, and common deployment scenarios, ensuring you are exam-ready with precise technical details.
Jump to a section
Imagine a large office building with multiple floors, each floor dedicated to a different department. Microsoft Teams is like that building. The building itself is the Teams app, providing the structure and access. Each floor is a Team, dedicated to a specific project or department. Within each floor, there are rooms (channels) for specific topics or tasks. Some rooms are open to everyone on that floor (standard channels), while others are locked and require a key (private channels) accessible only to specific members. The building has a central lobby (Chat) where anyone can have quick conversations. There's also a phone system (calling) and a mailroom (email integration via Outlook). The building's security guard (Azure Active Directory) checks IDs (licenses and permissions) at the entrance. When you want to collaborate on a document, you don't bring your own paper; you use the shared filing cabinets (SharePoint and OneDrive) that are built into each room. The building even has a video conferencing room (meetings) that can connect to other buildings (external organizations) via a special bridge (Azure Communication Services). Just as a building needs a maintenance crew to keep it running, Teams relies on Microsoft 365 services (Exchange, SharePoint, OneDrive) to function smoothly. If the building's plumbing fails (network issues), people can't use the facilities. This analogy helps understand how Teams integrates various Microsoft 365 components into a single collaborative environment.
What is Microsoft Teams and Why It Exists
Microsoft Teams is a unified communication and collaboration platform that combines persistent workplace chat, video meetings, file storage, and application integration. It was launched in 2017 as a direct competitor to Slack, but has since evolved into the hub for teamwork in Microsoft 365. Teams is built on top of several Microsoft 365 services: Exchange Online for chat and calendar, SharePoint Online for file storage, OneDrive for Business for personal file storage, and Azure Active Directory for identity. The core value proposition is that it replaces multiple disparate tools (email, chat, file sharing, meeting software) with a single interface, reducing context switching and improving productivity.
How Teams Works Internally – The Mechanism
At the architectural level, Teams uses a multi-tiered approach. The client (desktop, web, mobile) communicates with the Teams service over HTTPS and WebSockets. The service itself is a microservices-based architecture hosted in Azure. Key components include: - Chat Service: Handles 1:1 and group chat messages. Messages are stored in Exchange Online mailboxes (hidden folders) for compliance and eDiscovery. The chat service uses a notification system to push messages to clients via WebSockets. - Meetings and Calling: Uses Azure Communication Services (ACS) for media processing. For voice and video, Teams uses the industry-standard Session Initiation Protocol (SIP) and Real-time Transport Protocol (RTP). Media traffic is peer-to-peer when possible, but falls back to a cloud-based media relay (Azure Media Services) when direct connection fails (e.g., due to NAT/firewall). The media relay is located in Azure datacenters closest to the participants. - Files: Each Team has a corresponding SharePoint site. Files uploaded to a channel are stored in that site's document library. The Teams client uses SharePoint APIs to list and sync files. OneDrive is used for file sharing in private chat (1:1 or group). - Channels: Teams are containers with channels. Standard channels are visible to all team members, while private channels are hidden from non-members. Each private channel has its own SharePoint site with unique permissions. - Apps and Bots: Apps are web applications hosted in Azure or third-party clouds, rendered in the Teams client via an iframe. Bots use the Microsoft Bot Framework and communicate via the Teams Bot API.
Key Components, Values, Defaults, and Timers
Teams and Channels: A Team can have up to 200 private channels (as of 2025). Standard channels have no hard limit but practical limits due to performance. Channel names must be unique within a team.
Members: A Team can have up to 25,000 members (including guests). Guest access is limited to 5 guests per 1 licensed user.
Chat: 1:1 chat messages are stored in each participant's Exchange mailbox. Group chat supports up to 250 participants. Messages are retained based on the organization's retention policy (default: 1 year for Teams chat).
Meetings: Scheduled meetings can have up to 1,000 participants. For larger audiences, Teams Live Events supports up to 20,000 attendees. Meeting recordings are stored in SharePoint (channel meetings) or OneDrive (non-channel meetings).
Calling: Direct routing allows connection to on-premises PBX via a Session Border Controller (SBC). Teams Calling Plans provide a phone number from Microsoft. The default emergency address is required for each user.
Presence: Presence state is determined by calendar events, activity, and manual setting. The idle timeout is 5 minutes of inactivity to show "Away".
Configuration and Verification Commands
Administrators manage Teams via the Teams admin center (admin.teams.microsoft.com) or PowerShell. Key PowerShell commands:
To create a new Team:
New-Team -DisplayName "Project Alpha" -Description "Team for Project Alpha" -Visibility PrivateTo add a user to a Team:
Add-TeamUser -GroupId <GroupId> -User user@contoso.com -Role MemberTo list all Teams:
Get-Team | Format-Table DisplayName, GroupIdTo configure messaging policies:
Set-CsTeamsMessagingPolicy -Identity Global -AllowMemes $true -AllowGiphy $trueVerification: Use the Teams client to confirm features. For network readiness, use the Microsoft 365 Network Connectivity Test (https://connectivity.office.com).
How Teams Interacts with Related Technologies
Exchange Online: Provides calendar, contact, and chat storage. Meeting invites are sent via Exchange. Chat messages are stored in Exchange mailboxes for compliance.
SharePoint Online: Each Team gets a SharePoint site. Files in channels are stored in SharePoint document libraries. SharePoint permissions control access.
OneDrive for Business: Used for personal file storage in chat (non-channel files). Users can share files from OneDrive within Teams.
Azure Active Directory: Provides identity and access management. Guest access uses Azure AD B2B collaboration.
Microsoft 365 Groups: Every Team is backed by a Microsoft 365 Group. The group provides membership management and a shared mailbox, calendar, and Planner plan.
Power Platform: Teams integrates with Power Apps, Power Automate, and Power BI. You can embed custom apps and dashboards.
Third-party apps: Via the Teams app store, apps like Trello, Asana, and GitHub can be added.
Security and Compliance
Teams supports Data Loss Prevention (DLP) policies, eDiscovery, legal hold, and retention policies. Communication compliance can monitor for inappropriate content. Teams is ISO 27001, SOC 2, and HIPAA compliant when configured appropriately. Private channels have their own SharePoint site with unique permissions, preventing unauthorized access.
Licensing
Teams is included in most Microsoft 365 business plans (Business Basic, Business Standard, Business Premium, Enterprise E1/E3/E5). However, some features require specific licenses: Audio Conferencing (E5 or add-on), Phone System (E5 or add-on), and Advanced eDiscovery (E5). The free version of Teams (Teams Free) is limited to 300 users and lacks advanced admin controls.
Performance and Scale
Teams uses adaptive bitrate streaming for video (range: 30 kbps to 4 Mbps). The network requirements: bandwidth of at least 1.5 Mbps for HD video (1080p). Teams optimizes media traffic using UDP ports 3478-3481 for media and TCP 443 for signaling. The service uses Azure Front Door for global load balancing.
Creating a New Team
An administrator or owner clicks 'Create Team' in the Teams client. They choose between building from scratch, creating from an existing group, or using a template. They provide a name, description, and visibility (Private or Public). This triggers creation of a Microsoft 365 Group in Azure AD, which provisions a shared mailbox in Exchange, a SharePoint site, a OneNote notebook, and a Planner plan. The team appears in the Teams client for all members. The entire process takes seconds. The group is created with the same name as the team. The SharePoint site URL is generated based on the team name (with a unique suffix if needed).
Adding Members and Guests
Owners add members by searching for users in the organization or by entering email addresses for guests. For guests, an invitation is sent via email. The guest must accept the invitation and sign in with a Microsoft account or their organization's Azure AD. Once added, the guest appears in the team's member list with limited capabilities (e.g., cannot create teams, limited to 5 guests per licensed user). The underlying Azure AD B2B collaboration creates a guest user object in the tenant. The guest's access is governed by the same compliance policies as internal users.
Starting a Chat
A user clicks the Chat icon and selects a contact or starts a new group chat. The chat service creates a conversation thread. Messages are sent via HTTPS POST to the Teams service, which stores them in each participant's Exchange Online mailbox in a hidden folder. The service pushes notifications to online clients via WebSocket. Offline users receive push notifications via the Microsoft 365 push notification service. Messages support rich formatting, emojis, GIFs, and file attachments. Files are uploaded to the sender's OneDrive and shared via a link. The chat is searchable in the Teams client and via eDiscovery.
Scheduling a Meeting
The user clicks the Calendar icon and selects 'New Meeting'. They fill in title, time, participants, and options. The meeting invite is sent via Exchange Online. The meeting object is stored in the organizer's Exchange calendar. Participants receive the invite and can respond. At the scheduled time, the Teams client joins the meeting using the meeting ID or link. The meeting uses Azure Communication Services for media. The organizer can enable recording, transcription, and live captions. Recordings are stored in the organizer's OneDrive (for non-channel meetings) or the channel's SharePoint site (for channel meetings). The meeting can have up to 1,000 participants.
Using a Private Channel
An owner creates a private channel within a team. They specify a name and description. Only members of the private channel can see it and its content. The private channel has its own SharePoint site with a unique URL and permission set. When a file is uploaded to the private channel, it is stored in that site's document library, not the main team's SharePoint site. The owner can add members to the private channel individually. Private channels are limited to 200 per team. The underlying Microsoft 365 Group for the private channel is separate from the parent team's group, but membership is managed within the Teams client.
Enterprise Scenario 1: Global IT Support Team
A multinational company uses Teams as the central hub for its IT support team. The team has 500 members across three continents. They use a single Team with multiple channels: 'Incidents', 'Requests', 'Knowledge Base', and 'Escalations'. The 'Incidents' channel uses a Power Automate flow that creates a ticket in ServiceNow when a new message is posted. The team uses @mentions to escalate urgent issues. They have integrated a custom bot that queries the knowledge base and returns solutions. The challenge: network latency between continents causes occasional delays in chat message delivery. To mitigate, they use the 'Urgent' message flag, which sends push notifications every 2 minutes until read. They also use Teams Live Events for monthly all-hands meetings, broadcasting to 5,000 employees. The main performance consideration: bandwidth for video meetings is prioritized using Quality of Service (QoS) policies on the corporate network, marking Teams media traffic with DSCP 46. Misconfiguration: One administrator accidentally set the retention policy to 30 days, causing all chat history older than 30 days to be deleted, which impacted compliance audits. The fix: set retention to 1 year as per regulatory requirements.
Enterprise Scenario 2: Healthcare Collaboration
A hospital network uses Teams with HIPAA compliance. They use private channels for patient case discussions. Each channel is named with a patient ID and restricted to the care team. They use Teams Phone System for voice calls, with Direct Routing connecting to their on-premises PBX via a Session Border Controller (SBC). The SBC is configured to encrypt media with SRTP. They use compliance recording via a certified partner solution. Challenges: Guest access for external specialists requires careful management of B2B collaboration. They limit guest access to specific channels. Misconfiguration: A guest was accidentally added to a private channel with patient data, violating HIPAA. The fix: implement a policy that requires owner approval for guest additions. Performance: The hospital's network uses 802.1X authentication, causing re-authentication during active calls. They configured QoS to prioritize Teams media traffic. The default emergency address is set for each user based on their hospital location, ensuring 911 calls are routed to the correct Public Safety Answering Point (PSAP).
Exactly What MS-900 Tests on Microsoft Teams
MS-900 Objective 2.1 focuses on understanding the core capabilities of Microsoft Teams as a productivity solution. The exam tests: - Core features: Chat, meetings, calling, collaboration (files, apps). - Integration: How Teams integrates with Exchange, SharePoint, OneDrive, and Azure AD. - Licensing: Which plans include Teams and which features require add-ons (Audio Conferencing, Phone System). - Security and compliance: Retention policies, DLP, eDiscovery, guest access limitations. - Teams vs. other tools: When to use Teams vs. SharePoint vs. Yammer vs. Outlook.
Common Wrong Answers and Why Candidates Choose Them
"Teams replaces SharePoint for file storage" – Wrong. Teams uses SharePoint for file storage; it doesn't replace it. Candidates think Teams has its own file system, but in reality, files are stored in SharePoint libraries.
"Teams chat messages are stored in Azure SQL" – Wrong. They are stored in Exchange Online mailboxes (hidden folders). Candidates might assume a cloud app uses a database.
"Guest users have the same permissions as internal users" – Wrong. Guests have limited capabilities (e.g., cannot create teams, cannot access SharePoint sites unless explicitly added). Candidates overlook the restrictions.
"Teams is available in all Microsoft 365 plans" – Wrong. Teams is included in all business plans, but some enterprise plans (E1, E3, E5) include it, while some legacy plans (Business Essentials) also include it. However, standalone Teams is not available; you need a Microsoft 365 subscription. The trap: candidates think Teams is a separate product you can buy alone.
Specific Numbers and Values That Appear on the Exam
Maximum members per team: 25,000 (including guests).
Maximum private channels per team: 200.
Maximum participants in a meeting: 1,000 (for scheduled meetings), 20,000 for Live Events.
Guest limit: 5 guests per 1 licensed user.
Retention policy default for chat: 1 year.
Ports for media: UDP 3478-3481.
Edge Cases and Exceptions
Teams Free: Limited to 300 users, no admin controls, no guest access. Exam may ask about limitations of the free version.
Teams for Education: Different licensing (A1, A3, A5). Features like Assignments are available.
Teams in GCC/GCC High/DoD: Separate environments with different compliance requirements. Exam may mention these for government customers.
How to Eliminate Wrong Answers
If the question involves file storage, think SharePoint.
If the question involves chat storage, think Exchange.
If the question involves guest access, remember limitations (cannot create teams, limited to 5 per user).
If the question involves licensing, recall that Audio Conferencing and Phone System are add-ons (included in E5).
If the question involves meetings, recall participant limits (1,000 for standard meetings).
Teams is built on Microsoft 365 Groups, using Exchange for chat, SharePoint for files, and Azure AD for identity.
Maximum team size is 25,000 members; private channels max is 200 per team.
Guest access is limited to 5 guests per licensed user; guests cannot create teams.
Meeting participants: up to 1,000 for standard meetings; up to 20,000 for Live Events.
Chat messages are stored in Exchange Online mailboxes; retention policy default is 1 year.
Teams is included in all Microsoft 365 business plans; Audio Conferencing and Phone System are E5 features or add-ons.
Media traffic uses UDP ports 3478-3481; QoS with DSCP 46 is recommended for network optimization.
These come up on the exam all the time. Here's how to tell them apart.
Microsoft Teams
Integrated with Microsoft 365 (SharePoint, OneDrive, Exchange)
Supports up to 25,000 members per team
Meetings with up to 1,000 participants natively
Includes phone system (with add-on licenses)
Compliance features (DLP, eDiscovery) built-in
Slack
Third-party integrations via apps (not native Microsoft 365)
Limited to 10,000 members per workspace (Enterprise Grid)
Meetings require Slack Connect or third-party integration
No native phone system; relies on integrations
Compliance features require additional add-ons
Mistake
Teams stores all data in its own proprietary database.
Correct
Teams stores chat messages in Exchange Online mailboxes, files in SharePoint Online and OneDrive for Business, and meeting recordings in SharePoint or OneDrive. There is no separate Teams database.
Mistake
Guest users in Teams have full access to all team content.
Correct
Guest users have limited permissions. They cannot create teams, share files externally, or access SharePoint sites unless explicitly granted. They are subject to the same compliance policies as internal users.
Mistake
Teams is a standalone product that can be purchased separately.
Correct
Teams is included with most Microsoft 365 business and enterprise plans. There is no option to buy Teams alone; you must subscribe to a Microsoft 365 plan.
Mistake
Private channels are just hidden channels within the same SharePoint site.
Correct
Each private channel has its own separate SharePoint site with unique permissions, separate from the parent team's site. This ensures that only members of the private channel can access its content.
Mistake
Teams Live Events can have unlimited attendees.
Correct
Teams Live Events support up to 20,000 attendees. For larger audiences, you need a third-party solution or use the Microsoft 365 Live Events Assistance Program.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Microsoft Teams is included in all Microsoft 365 business plans (Business Basic, Standard, Premium) and enterprise plans (E1, E3, E5). There is no standalone Teams license. Some features require additional licenses: Audio Conferencing (included in E5, or as an add-on), Phone System (included in E5, or as an add-on), and Advanced eDiscovery (E5 only). The free version of Teams is limited to 300 users and lacks admin controls.
Chat messages are stored in each participant's Exchange Online mailbox in hidden folders, making them discoverable via eDiscovery. Files uploaded to channels are stored in the corresponding SharePoint Online site's document library. Files shared in private chat are stored in the sender's OneDrive for Business. This integration ensures compliance and retention policies apply uniformly.
Standard channels are visible to all team members and files are stored in the team's SharePoint site. Private channels are hidden from non-members and have their own separate SharePoint site with unique permissions. Private channels are limited to 200 per team. Creating a private channel requires the owner to add members individually.
Yes, Teams supports guest access via Azure AD B2B collaboration. Guests must accept an invitation and sign in with a Microsoft account or their organization's Azure AD. Guests have limited capabilities: they cannot create teams, they are limited to 5 guests per licensed user, and they can be restricted to specific channels. All guest access is subject to the same compliance policies as internal users.
Teams requires internet connectivity with a minimum bandwidth of 1.5 Mbps for HD video (1080p). Media traffic uses UDP ports 3478-3481; signaling uses TCP 443. For optimal performance, configure QoS with DSCP 46 for Teams media traffic. Use the Microsoft 365 Network Connectivity Test to assess readiness. Direct internet egress without proxy interception is recommended.
Retention policies in Microsoft 365 apply to Teams chat messages and channel messages. By default, chat messages are retained for 1 year. Administrators can configure custom retention policies via the Microsoft 365 compliance center. Deleted messages are recoverable within the retention period. eDiscovery holds can preserve content indefinitely.
Teams is designed for real-time collaboration within a team or project, with chat, meetings, and file sharing. Yammer is an enterprise social network for company-wide announcements and discussions, often used for leadership communication and communities of practice. They can be integrated, but serve different purposes. The exam may ask when to use each.
You've just covered Microsoft Teams — now see how well it sticks with free MS-900 practice questions. Full explanations included, no account needed.
Done with this chapter?