Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 268/272 feeds/APIs · 469/469 docs · 7/9 advisories · checked 06:40 UTC Customize Public modeDiscuss ChangeIntel on Discord

New policy setting to require explicit consent for recording and transcription in Teams 1:1 calls

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Roadmap
503295

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions this installation saw
  • Seen 20 Mar 2026 late January 2026, late February 2026 → late April 2026
  • Seen 21 Nov 2025 early December 2025, mid-December 2025 → early January 2026, late February 2026
  • Seen 17 Nov 2025 mid-February 2026
  • Seen 17 Oct 2025 early November 2025, mid-November 2025, late November 2025 → mid-December 2025, mid-January 2026, late January 2026, early February 2026

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, with source markup removed
Updated March 20, 2026: We have updated the timeline. Thank you for your patience. Introduction To enhance transparency and user control, Microsoft Teams is expanding the Explicit Recording Consent feature to include 1:1 Teams calls. This update ensures that participants must provide explicit consent before their media (audio, video, and content sharing) is included in any recording or transcription initiated by another user. This change supports privacy compliance and aligns with customer feedback requesting more granular consent controls. This message is associated with Roadmap ID 503295. When this will happen:Targeted Release: Begins early January 2026 (previously early December 2025), completes mid-January 2026 (previously mid-December 2025). General Availability (Worldwide, GCC): Begins mid-January 2026 (previously mid-December 2025), completes late April 2026 (previously late January). General Availability (GCC High): Begins early February 2026 (previously late January), completes late April 2026 (previously mid-February). General Availability (DoD): Begins mid-February 2026 (previously late January), completes late April 2026 (previously late February). How this affects your organization: Who is affected: Microsoft Teams administrators managing calling policies. Users participating in 1:1 Teams VoIP calls where recording or transcription is initiated. Public Switched Telephone Network (PSTN) endpoints will be auto consented. Explicit consent support for PSTN will be included in a future release. What will happen: This feature applies to Microsoft Teams desktop apps on Windows and macOS. By default, Explicit Recording Consent is OFF and must be enabled by administrators. When enabled:Users initiating recording or transcription in 1:1 calls will trigger a consent prompt for the other VoIP participant. Until consent is granted, the participant’s audio, video, and screen/content sharing will be disabled, and as a result, excluded from the recording. PSTN users will be auto-consented. Learn more at Manage Teams recording policies | Auto consent endpoints and platforms Administrators can apply this policy tenant-wide or to specific users. What you can do to prepare:Update training materials to reflect that Explicit Recording Consent now applies to 1:1 calls (PSTN and Teams VoIP). Inform users that consent is required before recording or transcription can begin in 1:1 calls. Administrators can manage this feature via PowerShell or the Microsoft Teams admin center. PowerShell commands: Set-CsTeamsCallingPolicy -Identity Global -ExplicitRecordingConsent "Enabled" Set-CsTeamsCallingPolicy -Identity Global -ExplicitRecordingConsent "Disabled" Learn more: Set-CsTeamsCallingPolicy documentation Compliance considerations: Compliance Area Explanation Audit Logging Consent data is captured in audit logs. Refer to Audit log activities in Microsoft Purview.

What changed

Between archive captures, newest first
  1. Updated NovemberMarch 20, 2025:2026: We have updated the timeline. Thank you for your patience. Introduction To … General Availability (Worldwide, GCC): Begins mid-January 2026 (previously mid-December 2025), completes late JanuaryApril 2026 (previously mid-January).late January). General Availability (GCC High): Begins early February 2026 (previously late January), completes mid-Februarylate April 2026 (previously early February). mid-February). General Availability (DoD): Begins mid-February 2026 (previously late January), completes late FebruaryApril 2026 (previously mid-February).late February). How this affects your organization: Who is affected: Microsoft Teams administrators managing …

  2. Updated November 17,20, 2025: We have updated the timeline. Thank you for your patience. Introduction … associated with Roadmap ID 503295. When this will happen:Targeted Release: Begins early January 2026 (previously early December 2025,2025), completes mid-January 2026 (previously mid-December 2025.2025). General Availability (Worldwide, GCC): Begins mid-January 2026 (previously mid-December 2025,2025), completes mid-January 2026.late January 2026 (previously mid-January). General Availability (GCC High): Begins late Januaryearly February 2026 (previously mid-January),late January), completes early February mid-February 2026 (previously late January).early February). General Availability (DoD): Begins mid-February 2026 (previously late January 2026, completes mid-FebruaryJanuary), completes late February 2026 (previously mid-February). How this affects your organization: Who is affected: Microsoft …

  3. Updated OctoberNovember 17, 2025: We have updated this MC ID. the timeline. Thank you for your patience. Introduction To enhance transparency and user control, … GCC): Begins mid-December 2025, completes mid-January 2026. General Availability (GCC High): Begins mid-January 2026,late January 2026 (previously mid-January), completes early February 2026 (previously late January 2026. January). General Availability (DoD): Begins late January 2026, completes early February 2026.mid-February 2026 (previously mid-February). How this affects your organization: Who is affected: Microsoft Teams administrators managing …

    • Tags New feature, User impact, Admin impact → Updated message, New feature, User impact, Admin impact

    Updated October 17, 2025: We have updated this MC ID. Thank you for your patience. Introduction To enhance transparency and user control, Microsoft Teams is expanding the Explicit Recording Consent feature to include 1:1 calls made via the Public Switched Telephone Network (PSTN) or Teams Voice over Internet Protocol (VoIP). calls. This update ensures that participants must provide explicit consent before their media … associated with Roadmap ID 503295. When this will happen:Targeted Release: Begins early NovemberDecember 2025, completes early November mid-December 2025. General Availability (Worldwide, GCC): Begins mid-Novembermid-December 2025, completes mid-November 2025.mid-January 2026. General Availability (GCC High): Begins late November 2025, mid-January 2026, completes early December 2025.late January 2026. General Availability (DoD): Begins early December 2025,late January 2026, completes early December 2025.February 2026. How this affects your organization: Who is affected: Microsoft Teams administrators managing calling policies. Users participating in 1:1 PSTN or Teams VoIP calls where recording or transcription is initiated. Public Switched Telephone Network (PSTN) endpoints will be auto consented. Explicit consent support for PSTN will be included in a future release. What will happen: This feature applies to Microsoft Teams desktop apps on … transcription in 1:1 calls will trigger a consent prompt for the other VoIP participant. Until consent is granted, the participant’s audio, video, and screen/content sharing will be disabled, and as a result, excluded from the recording. PSTN users will be auto-consented. Learn more at Manage Teams recording policies | Auto consent endpoints and platforms Administrators can apply this policy tenant-wide or to specific users. What you …

  4. · first version seen

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 27 Oct 06:40 UTC · 268 of 272 readable · 267 fully read · documentation 469/469 current