Microsoft Teams

Technical Definition

Microsoft Teams is a software-as-a-service collaboration platform delivered as part of Microsoft 365. 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; this entry treats the general existence of such standards-based media handling as established, while specific protocol versions or configuration parameters used by Teams at any given time are outside the scope of the verified evidence available here and should be confirmed against current Microsoft documentation.

Operational Relevance

For systems, platform and operations practitioners, 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. Practical operational concerns include 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. Observable success for a bounded Teams-related change is typically defined 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. These checks should be performed in an isolated or non-production tenant before any change reaches production, and current product version and permission levels should be confirmed first, since administrative capabilities and defaults change over time.

Architecture Relationship

Microsoft Teams sits within the broader Microsoft 365 architecture rather than functioning as 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. This layered dependency means a Teams-related incident or change frequently has its real cause, evidence and remediation point in an adjacent service, such as an Entra ID conditional access policy, a SharePoint site permission, or an Exchange retention policy, rather than in Teams itself.

Example

A bounded, low-risk example: 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.

Common Misunderstanding

A frequent misunderstanding is treating a Team or channel as an ephemeral, self-contained chat space. In practice, 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. Assuming that removing a Team is an instant, complete deletion can lead to false confidence about data disposal and should be verified against current tenant configuration rather than assumed.

Related Terms

• 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, none of which are covered by the verified evidence used for this entry, consult Microsoft’s official product documentation directly and confirm details against the tenant’s actual configuration before relying on them operationally.