Microsoft Teams
In plain English
Plain definition
Microsoft Teams is a cloud-based application from Microsoft that brings chat, meetings, calling and file sharing into a single workspace. Teams organises people, conversations and shared files around named "teams" and "channels", and integrates closely with the wider Microsoft 365 environment.
How Teams is built on Microsoft 365 Groups
Each Team corresponds to an underlying Microsoft 365 Group, which unifies membership, permissions and provisioning across Teams, SharePoint Online, Exchange Online and Planner. Channels within a Team map to folders in an associated SharePoint document library for file storage, while channel conversations and private chats are stored in Exchange Online mailboxes, making them subject to the same compliance, retention and eDiscovery controls as email. Real-time audio, video and screen-sharing rely on Microsoft’s calling infrastructure together with standard Internet media-transport and NAT-traversal techniques of the kind documented in the IETF’s RFC Series. Protocol versions and configuration parameters change over time, so check them against current Microsoft documentation.
What Teams depends on day to day
For the people who run it, Microsoft Teams is rarely an isolated system: it depends on Microsoft Entra ID (Azure AD) for identity and conditional access, on SharePoint Online and OneDrive for Business for file storage, and on Exchange Online for message and calendar data. The everyday concerns are guest and external access governance, data residency and retention policy alignment, Team-sprawl control (each new Team creates a Microsoft 365 Group, site and mailbox), and network readiness for real-time media. You can usually tell a contained Teams change worked by confirming that the expected users, and only the expected users, retain access; that associated SharePoint and mailbox artefacts exist where expected; and that retention or compliance policies apply as configured. Run these checks in an isolated or non-production tenant before any change reaches production, and confirm the current product version and your permission levels first, because administrative capabilities and defaults change over time.
Where Teams sits in Microsoft 365
Microsoft Teams is part of the wider Microsoft 365 architecture, not a standalone product. Identity and access flow through Microsoft Entra ID; file storage flows through SharePoint Online (channel files) and OneDrive for Business (personal and chat files); message and calendar data flow through Exchange Online; and programmatic access is exposed through Microsoft Graph. Third-party and custom extensibility (apps, bots, connectors, tabs) plug into Teams through defined app manifests rather than direct code execution inside the client. Because of these dependencies, the real cause of a Teams incident or change, and the place to gather evidence and fix it, often sits in a neighbouring service, such as an Entra ID conditional access policy, a SharePoint site permission, or an Exchange retention policy, rather than in Teams itself.
A short-lived Team for an incident
Here is a low-risk case: an operations team creates a new Team for a time-limited incident-response effort, restricts external and guest access to named individuals, and verifies, before relying on it, that messages posted in the incident channel are retained under the organisation’s existing retention policy, that uploaded files land in the associated SharePoint site with the intended permissions, and that access is fully removed once the incident closes. Each of these checks is read-only verification against existing configuration; no destructive action is required to validate them.
Deleting a Team does not erase its data at once
People often treat a Team or channel as a temporary, self-contained chat space. Teams conversations, files and membership are backed by persistent Microsoft 365 objects (a Group, a SharePoint site, an Exchange mailbox), so deleting a Team does not immediately or irreversibly erase its data: Microsoft 365 Groups typically follow a soft-delete and retention window, and associated content may remain recoverable or subject to legal hold for a period afterwards. If you assume that removing a Team deletes everything at once, you may believe data has been disposed of when it has not, so check the current tenant configuration instead.
Terms that sit alongside Teams
- Microsoft 365
- Microsoft 365 Groups
- SharePoint Online
- Exchange Online
- Microsoft Entra ID (Azure AD)
- Microsoft Graph
Further Reading
For the standards underpinning Internet real-time media transport referenced above, consult the RFC Editor’s RFC Series (rfc-editor.org), the authoritative publication channel for Internet technical specifications. For current Microsoft Teams administrative guidance, licensing tiers and version-specific capabilities, consult Microsoft’s official Teams documentation and confirm details against the tenant’s actual configuration before relying on them operationally.
Related reading
Authoritative Sources
About this page
Was this useful?
Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.