Teams Architecture Overview

Analogy categoryAnalogies

Microsoft Teams architecture spans three broad layers: client apps (desktop, web, mobile) built on a common web-based rendering engine; a set of cloud services (chat service, calling/media service, tabs/apps service) hosted on Azure; and durable storage split across SharePoint, Exchange, and Azure-based Teams-specific stores called the substrate. Every message you send is stored redundantly in Exchange Online mailboxes even though you never open Outlook to read it.

🏏

Cricket analogy: Similar to how a cricket broadcast has an on-screen graphics layer, a production truck processing feeds, and an archive server storing every ball bowled, even balls the viewer never rewatches, just like Teams messages sitting in Exchange unseen.

The Microsoft 365 Group Backbone

Every standard team maps 1:1 to a Microsoft 365 Group, which is the real unit of membership, security, and provisioning; the Group object carries the membership list, the connected SharePoint site, the shared mailbox, and the Entra ID security context, while Teams itself is essentially a UI and real-time messaging layer on top of that Group.

🏏

Cricket analogy: Like how a player's official cricket board registration record — not their jersey number — is the real source of truth for eligibility, while the jersey is just what fans see.

Media and Signaling

Real-time audio, video, and screen sharing in Teams meetings run over the Skype for Business-derived media stack, using SIP-like signaling for call setup and SRTP for encrypted media, routed through Azure-hosted media processors near the user's region to minimize latency.

🏏

Cricket analogy: Similar to how a stadium's broadcast signal is encrypted and routed through regional relay towers before reaching a viewer's TV, minimizing delay just as Teams routes media through nearby processors.

http

POST https://graph.microsoft.com/v1.0/teams/{team-id}/channels
Content-Type: application/json

{
  "displayName": "Release Planning",
  "description": "Sprint release coordination",
  "membershipType": "standard"
}

The Microsoft Graph API is the primary programmatic surface for Teams — almost every admin PowerShell cmdlet and every custom app ultimately calls Graph endpoints under the hood.

Extensibility Layer: Bots, Tabs, and Connectors

Teams apps extend the platform through three main surfaces — bots (conversational agents registered via the Bot Framework and Azure Bot Service), tabs (embedded web pages rendered inside an iframe using the Teams JavaScript SDK), and message extensions (search or action commands invoked from the compose box) — all declared in a single app manifest (manifest.json) that Teams validates against a published schema.

🏏

Cricket analogy: Similar to how a cricket team's toolkit includes a bowling machine, a video analysis rig, and a fitness tracker — three distinct tools serving one training program, like bots, tabs, and message extensions serving one app manifest.

Custom Teams apps must be sideloaded or published through the Teams admin center's app catalog; an app manifest with an invalid or missing permissions scope will fail validation silently in some clients and only surface as a runtime error in others.

Teams messages are durably stored in Exchange Online mailboxes behind the scenes.
Every standard team is backed 1:1 by a Microsoft 365 Group.
Real-time media uses SRTP encryption over the Skype for Business-derived stack.
Microsoft Graph API is the primary programmatic interface to Teams data.
Apps extend Teams via bots, tabs, and message extensions declared in a manifest.
Media routing uses regionally distributed processing to reduce call latency.

Practice what you learned

1. What backend object underlies every standard Teams team?

2. Where are chat messages durably stored?

3. What protocol secures real-time media in Teams calls?

4. What file declares a Teams app's bots, tabs, and permissions?

Was this page helpful?

What Is Microsoft Teams?

Teams Admin Center Basics

Related Study Notes in Microsoft Technologies

Browse all study notes

Microsoft Technologies

Windows 10 / UWP Development Study Notes

.NET · 30 topics

Microsoft Technologies

Windows Batch Scripting Study Notes

Batch · 30 topics

Microsoft Technologies

MFC (Microsoft Foundation Classes) Study Notes

C++ · 30 topics

Microsoft Technologies

Silverlight Study Notes

.NET · 30 topics

Microsoft Technologies

XAML Study Notes

.NET · 30 topics

Microsoft Technologies

WPF (Windows Presentation Foundation) Study Notes

.NET · 30 topics

Topics covered

#Microsoft365#MicrosoftTeamsDevelopmentStudyNotes#MicrosoftTechnologies#TeamsArchitectureOverview#Teams#Architecture#Microsoft#365#StudyNotes#SkillVeris

Teams Architecture Overview