Microsoft Teams

Definition: Microsoft’s business communication platform, bundled tightly with Microsoft 365 and often the default choice for organizations already on Microsoft’s ecosystem, combining chat, video meetings, and document collaboration in one app. Launched in 2017 as Microsoft’s answer to Slack’s rise, it was built on top of Office 365 Groups and gradually absorbed the calling and meeting functionality of the older Skype for Business product. Its historically free bundling into Microsoft 365 and Office suites drew formal EU antitrust scrutiny after a complaint from Slack, leading Microsoft to begin selling Microsoft 365 without Teams as a separate, unbundled SKU starting in 2023.

Core Services & Concepts

Microsoft Graph API — REST API, the unified API surface shared across Teams, Outlook, SharePoint, and OneDrive, so a single app can touch chat, calendar, and files through one authorization model
Entra ID (Azure AD) identity — SSO (Single Sign-On), Teams accounts are tied directly to the same identity system enterprise Microsoft 365 customers already run, so conditional access, MFA, and compliance policies apply automatically without a separate login
SharePoint-backed files — every channel’s Files tab is actually a SharePoint document library under the hood, inheriting the same permissioning, versioning, and retention policies as SharePoint itself
Adaptive Cards & bots — Webhook, incoming webhook connectors and the Bot Framework post structured, interactive Adaptive Card messages into a channel, conceptually similar to Slack’s Block Kit
Power Platform integration — first-party Power Automate and Power Apps let non-developers build workflow bots and forms directly inside Teams without writing custom backend code
OAuth 2.0 app permissions — OAuth 2.0, Teams apps request delegated or application permissions through Entra ID’s consent framework, and admins can centrally approve or block scopes tenant-wide
Teams Phone & meetings platform — PSTN calling, Town Hall broadcasts, and webinars are built directly into the same client, positioning Teams as a unified-communications platform rather than just chat

How Pricing Works

Bundled into Microsoft 365 Business Basic/Standard and Enterprise E3/E5 plans at no separate line-item cost for most organizations already licensed that way
A standalone Teams Essentials plan exists for small businesses without a full Microsoft 365 subscription, commonly priced in the low single-digit dollars per user per month
Teams Phone (PSTN calling/calling plans) is a separate paid add-on layered on top of any base license
Following EU antitrust scrutiny over the Office/Teams bundle, Microsoft began selling Microsoft 365 suites without Teams in Europe starting in 2023, later extending unbundled SKUs more broadly, with Teams available as a standalone purchase
A free version exists with meetings capped around 60 minutes and limited admin/security controls, aimed at individuals and very small teams
Government and education tenants (GCC/GCC High, Microsoft 365 Education) get separate compliance-focused SKUs with different pricing and feature sets than commercial plans

Pros

Deep integration with Microsoft 365 (Outlook, SharePoint, Word/Excel/PowerPoint), documents can be co-edited live inside a chat or channel
Often already included in enterprise licensing (E3/E5 bundles) at no extra incremental cost, making adoption an easy default for IT
Enterprise-grade compliance, retention, and identity controls inherited directly from Entra ID and Microsoft Purview
Mature admin tooling for provisioning, governance, and reporting scales well to very large organizations
Built-in PSTN calling via Teams Phone can replace a separate phone system for some organizations
Unified-communications positioning (chat, meetings, and calling in one client) can reduce vendor count for IT compared to stitching together chat plus a separate video/phone vendor

Cons

Historically criticized for being slower and more resource-heavy than Slack, though performance has improved significantly in newer client versions
Integration ecosystem outside Microsoft’s own products is smaller than Slack’s third-party app directory
Channel/Team sprawl and permission complexity (inherited from SharePoint) can confuse users migrating from simpler chat tools
Faced EU antitrust scrutiny over being bundled free with Microsoft 365, which regulators argued disadvantaged standalone competitors like Slack
Guest access and cross-tenant collaboration have historically been more cumbersome to configure than Slack Connect
Meeting and calling quality has historically varied more across network conditions than dedicated video-first tools like Zoom, though this gap has narrowed over time

Comparison: Microsoft Teams vs Slack

	Microsoft Teams	Slack
Primary strength	Deep Microsoft 365 bundling and enterprise identity/compliance	Polished UX and third-party integration ecosystem
Typical pricing model	Bundled into Microsoft 365 suites, or standalone Teams Essentials per user	Per-active-user monthly tiers (Free / Pro / Business+ / Enterprise Grid)
Best fit	Organizations already standardized on Microsoft 365/Windows	Tech-forward teams wanting fast UX and many integrations
API or product style	Microsoft Graph REST API, Adaptive Cards, tied to Entra ID	REST + Events API/Socket Mode, Block Kit for interactive messages

Best For

Organizations already standardized on Microsoft 365 and Windows environments wanting one bundled communication and collaboration suite
Enterprises needing identity, compliance, and retention controls that inherit directly from an existing Entra ID/Purview investment

Real Examples

The default communication tool at most large enterprises already using Microsoft 365, particularly in regulated industries like finance, government, and healthcare
Widely adopted by universities and school systems already on Microsoft 365 Education licensing for remote and hybrid classes
Common in professional services firms (consulting, law, accounting) that standardize their entire desktop environment on Microsoft’s stack
Frequently the default in government and public-sector tenants running Microsoft’s GCC/GCC High compliance environments

Use Cases

Enterprise team chat and channel-based collaboration
Video meetings and webinars, including large “Town Hall” broadcasts
Office document co-authoring inside a chat or channel
PSTN phone calling via Teams Phone as a replacement for a legacy office phone system
Workflow automation for non-developers via Power Automate connectors
Cross-tenant guest collaboration and shared channels with external partners via Teams Connect

Integration Notes & Common Pitfalls

Registering an app in Entra ID and requesting Graph API permissions is a separate step from building the Teams app manifest itself, teams new to the platform often build the bot before realizing the permissions/consent flow is its own project
Incoming webhook connectors are being deprecated in favor of Workflows (built on Power Automate), so new integrations should target Workflows rather than the legacy connector format
Microsoft Graph enforces per-application and per-tenant Rate Limiting, throttling responses return a Retry-After header that a robust integration must respect rather than retrying immediately
Teams app permissions are consent-gated by Entra ID admins, a bot that works fine in a personal/dev tenant can be silently blocked in a customer’s tenant until an admin approves its requested scopes
Tabs (custom web apps embedded inside a channel) run inside an iframe with Teams-specific SDK requirements (@microsoft/teams-js), a plain web app usually needs modification before it works correctly when embedded

Code Example

// Posting a message to a Teams channel via Microsoft Graph API
const response = await fetch(
  `https://graph.microsoft.com/v1.0/teams/${teamId}/channels/${channelId}/messages`,
  {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
      Authorization: `Bearer ${accessToken}`,
    },
    body: JSON.stringify({
      body: { content: 'Deploy finished: v2.4.1 shipped to production' },
    }),
  },
);
// accessToken is obtained via an Entra ID OAuth 2.0 client-credentials
// or delegated flow scoped to ChannelMessage.Send.

FAQ

Why is Microsoft Teams now sold separately from Microsoft 365 in some regions? Following EU antitrust complaints (notably from Slack) that free bundling of Teams into Office/Microsoft 365 was anticompetitive, Microsoft began offering Microsoft 365 suites without Teams in Europe starting in 2023, later extending unbundled SKUs more broadly.

Can people outside my company join a Teams meeting or channel? Yes, via guest access or Teams Connect shared channels, though historically this required more tenant-level admin configuration than Slack Connect’s comparatively simpler cross-workspace channel sharing.

Does Microsoft Graph API access require a separate login from Microsoft 365? No, Graph API calls authenticate through the same Entra ID identity as the rest of Microsoft 365, so an app registered in Entra ID can request delegated or application permissions covering Teams, Outlook, and SharePoint under one consent flow.

Is Microsoft Teams the same product as Skype for Business? No — Teams replaced it. Microsoft retired Skype for Business Online in 2021 and migrated its calling and meeting features into Teams, though some on-premises Skype for Business Server deployments still exist separately.

History

Launched in 2017 as Microsoft’s direct response to Slack’s rise, built on top of Office 365 Groups rather than as a standalone acquisition
Absorbed the calling and meeting functionality of Skype for Business over the following years, with Microsoft formally retiring Skype for Business Online in 2021
Usage surged dramatically during the 2020 shift to remote work, becoming one of Microsoft’s fastest-growing products ever by daily active users
Faced EU antitrust scrutiny starting around 2020 following a Slack complaint over free Microsoft 365 bundling, leading Microsoft to unbundle Teams into separate SKUs starting in 2023
Introduced Teams Phone as a full PSTN calling add-on, extending the product from chat and meetings into a genuine phone-system replacement for many organizations

Referenced by

Dig deeper

Spot an error in this note?