Microsoft’s current Learn documentation distinguishes two layers. Standard encryption is on for all Teams customers without configuration: TLS 1.2 or later with AES-256 in transit, BitLocker and per-file encryption at rest in Azure, SharePoint, and OneDrive, plus Microsoft-managed service encryption. Customer Key / BYOK is an extra at-rest control through Microsoft Purview. End-to-end encryption (E2EE) is a separate, narrower feature.
For one-to-one VoIP calls, E2EE is disabled by default in the global enhanced-encryption policy. An admin must allow it, then both people must enable it in the Teams client. Microsoft says keys are generated on the devices and exchanged over a secure signalling session, media is DTLS-protected, and GCM_AES_256 covers audio, video, and video-based screen sharing. It does not cover chat. PSTN calls are excluded. During an encrypted call, Teams shows a 20-digit security code derived from SHA-256 thumbprints of endpoint certificates; participants are told to read the code aloud and hang up if it does not match.
For meetings, the admin policy that allows E2EE is enabled by default, but a meeting is end-to-end encrypted only when the organiser requires it at schedule time. That meeting feature requires Teams Premium for the organiser; attendees do not need Premium. Microsoft uses a Group Key Manager Protocol over TLS 1.3 among clients. Maximum attendance is 200. Web, VDI, and Cloud Video Interoperability clients are not supported; they are blocked from joining. Specified Teams Rooms and a list of Cisco, Logitech, Neat, and Yealink devices are supported with architecture caveats on Android rooms.
The unsupported-features table is the operational heart of the design. With E2EE on, live captions, transcription, recording, compliance recording, real-time text, call transfer, merge, park, consult-then-transfer, adding a participant, breakout rooms, Excel Live, PowerPoint Live, request control, companion/large gallery, PSTN dial-in, and Microsoft 365 Copilot in meetings are unavailable. Apps cannot access media streams. A user who is subject to compliance recording cannot join an E2EE call or meeting at all, because the recorder needs plaintext. Chat, shared files, meeting recordings, transcripts, recap, group calls, and channel meetings are listed in the modalities table as having standard encryption only — no E2EE column.
Microsoft therefore does not claim that “Teams is end-to-end encrypted” as a product-wide sentence. It claims transport and service encryption always, and E2EE for specific call and meeting configurations. Identity still rides on Microsoft Entra ID. A phished Entra session is outside the media-E2EE story.
The Learn pages are living documentation. They did not display a newsroom date in the fetched snapshot, so this item is dated to the access day, 24 September 2026, as the verification date of the current official text.
What this means in practice
Bangladeshi ministries and firms that need confidentiality for a board call should have a Teams admin enable 1:1 E2EE, train executives to turn it on, and verify the 20-digit code. They should schedule Premium E2EE meetings only when they can live without recording, Copilot, and PSTN guests. Ordinary chat about those meetings remains visible to Microsoft’s service encryption model, not to an E2EE ratchet. Cyber71 cannot flip tenant policies, issue Premium licences, or recover a meeting that was not recorded because E2EE was on.
What is still unclear
Microsoft does not publish, in these articles, the share of tenants that have enabled user-override E2EE, the cryptographic details of GKMP comparable to an academic whitepaper, or a third-party audit of the client. How quickly the 20-digit code detects a signalling MITM in all network conditions is a user procedure, not a lab result quoted here. Future Copilot features may change the incompatibility list; this briefing tracks the table as loaded.
Sources
- Microsoft Learn — Encryption in Microsoft Teams2026-09-24
- Microsoft Learn — Manage end-to-end encryption for Microsoft Teams meetings and one-to-one calls2026-09-24
Cyber71 links the primary material behind each report so readers can check it directly. External pages are not under our control and may change.
