Microsoft cloud
Microsoft Teams
Microsoft Teams is Microsoft's unified communication and collaboration platform, combining persistent chat, video and audio meetings, file collaboration, and an extensible app and workflow layer into a single client.
Why Microsoft Teams matters in a Microsoft estate
Microsoft Teams matters because Microsoft 365, Azure, Windows 365, Teams, and related services are usually managed as one estate. The term connects to planning, cost, configuration, security, and day-two operational decisions across that estate.
How Microsoft Teams shows up in practice
It has become the default real-time collaboration surface for most Microsoft 365 organisations since Skype for Business was retired. Structurally, Teams is built on top of other Microsoft 365 services rather than being a standalone data store. Each team is backed by a Microsoft 365 group, its files live in a connected SharePoint Online document library, its chat and channel messages live in Exchange Online-adjacent storage, and its meeting recordings default to OneDrive or Stream. This means Teams governance and Teams storage cost are really governance and storage decisions about several other services wearing a single front end. Licensing follows the wider Microsoft 365 structure, with Teams included in Business Basic and above.
Separate add-on licensing is required for Teams Phone (PSTN calling and a phone system replacing traditional telephony) and for Teams Premium, which layers on advanced meeting intelligence features like live translation and meeting recaps atop the base product. Teams sprawl is one of the most common and most underestimated operational problems in mature Microsoft 365 estates. Because any user can create a new team in a couple of clicks, organisations that do not enforce a naming convention, an approval workflow, or a lifecycle/expiration policy through Entra ID group-based governance routinely accumulate hundreds or thousands of abandoned, near-duplicate, or single-purpose teams that nobody owns. Each one still consumes storage, still appears in search results, and still represents an access-control surface that has to be reviewed during any security or compliance audit.
Guest access, where external users are invited into a team, is another area demanding active management. It is genuinely useful for cross-organisation collaboration, but left unreviewed it becomes a slow accumulation of external accounts with standing access to internal channels and files long after the original project or relationship ended. Teams' integration with the Microsoft Graph API and its app store also makes it a common vector for third-party and custom application access into a tenant. Reviewing which apps and bots have been consented into a Teams environment, and what Graph permissions they were granted, is a standard part of the same governance exercise that covers channel sprawl and guest access, rather than a separate concern.