Microsoft 365
What is Microsoft Teams?
Quick answer
Microsoft Teams brings chat, channels, meetings, calling, and app teamwork into one surface, but its data lives in familiar services: channel files in SharePoint, meetings on Exchange calendars, identity in Entra ID. That architecture explains the admin reality — Teams governance means SharePoint permissions, retention spanning workloads, and guest access controlled across all three. Copilot Studio agents and Power Automate approvals commonly surface inside Teams because that is where users already work.
Key takeaways
- Chat, meetings, and calling up front; SharePoint and Exchange underneath.
- Govern files, retention, and guests across all three services.
- Agents and approvals surface in Teams where users work.
Detailed Explanation
Microsoft Teams brings chat, channels, meetings, calling, and app teamwork into one surface, but its data lives in familiar services: channel files in SharePoint, meetings on Exchange calendars, identity in Entra ID. That architecture explains the admin reality — Teams governance means SharePoint permissions, retention spanning workloads, and guest access controlled across all three. Copilot Studio agents and Power Automate approvals commonly surface inside Teams because that is where users already work.
How it works
Creating a team provisions the backing services in one motion — a SharePoint site for files, an Exchange group mailbox for calendar, an Entra group for identity — and Teams renders them as channels, tabs, and meetings. Every message, file, and membership change fans out to the owning service, which is why governance must target the back end rather than the Teams client.
Limitations and considerations
Teams sprawl — unmanaged team creation, duplicated channels, guest accumulation — becomes SharePoint sprawl and identity sprawl. Naming, lifecycle, and guest-review policies belong in the rollout, not year two.
For broader context, see the Microsoft 365 Hub — it collects the guides around this topic.
When to use it
Treat Teams as the collaboration front end and govern the underlying SharePoint, Exchange, and Entra surfaces as one system.
Practical example
Each client engagement gets one team (backed by a SharePoint site with scoped permissions), a quarterly reviewed guest list, and an archived lifecycle — collaboration without sprawl.