New policy setting to require explicit consent for recording and transcription in Teams 1:1 calls
Microsoft Teams will require explicit consent before recording or transcribing 1:1 PSTN or VoIP calls, enhancing privacy and compliance. This feature, off by default, can be enabled by admins and applies to desktop apps starting November 2025. Consent prompts disable participant media until granted. 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). 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 November 2025, completes early November 2025. General Availability (Worldwide, GCC): Begins mid-November 2025, completes mid-November 2025. General Availability (GCC High): Begins late November 2025, completes early December 2025. General Availability (DoD): Begins early December 2025, completes early December 2025. 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. What will happen: 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: Compliance considerations: 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 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. Administrators can apply this policy tenant-wide or to specific users. Set-CsTeamsCallingPolicy -Identity Global -ExplicitRecordingConsent "Enabled"Set-CsTeamsCallingPolicy -Identity Global -ExplicitRecordingConsent "Disabled" Learn […]
The post New policy setting to require explicit consent for recording and transcription in Teams 1:1 calls appeared first on M365 Admin.
Published on:
Learn moreWe can help you with New policy setting to require explicit consent for recording and transcription in Teams 1:1 calls
If you want help implementing, troubleshooting, or improving this product, contact us and we’ll point you in the right direction.
Related posts
Dynamics 365 Contact Center: Quality evaluation – One-Time Evaluation Frequency
Quality evaluation plans now support a Once frequency type for both case evaluations and conversation evaluations. When creating an evaluation...
Microsoft Teams: Phishing Detection in Teams Messaging
Microsoft Teams is introducing AI-powered phishing detection that uses conversation context to identify phishing and social engineering in hig...
Microsoft Purview: Data Loss Prevention-Admin Units Support for Copilot & Cowork DLP
Microsoft Purview Data Loss Prevention is extending Administrative Units support to Microsoft 365 Copilot, Copilot Chat, and Cowork. This enab...
Take action: NTLMv1 hardening changes might affect network connections on devices without Credential Guard
Beginning with the October 2026 security update, Windows 11, versions 26H2, 25H2, and 24H2, along with Windows Server 2025 enforce restriction...
Power Platform – Recreate connections made to the Azure DevOps connector prior to September 2024
We identified that an app, flow, or agent in your environment utilizes a connection to the Azure DevOps connector that was created prior to Se...
Microsoft Purview | Data Loss Prevention: Count of labeled documents condition for Exchange Online
Microsoft Purview DLP introduces a new Exchange Online condition to detect emails with a high count of sensitivity-labeled attachments, enhanc...
Microsoft Teams: Automatic recording and transcription options align with admin policies
Microsoft Teams will update meeting options to show only automatic recording and transcription settings allowed by assigned policies, adding a...
Copilot Studio – Information regarding the end of support for selected AI models
We are announcing the end of support for selected AI models on the Standard and GitHub Copilot harnesses in Copilot Studio. Beginning on each ...
Updates available for Microsoft 365 Apps for all channels
We’ve released updates to the following update channels for Microsoft 365 Apps: Current Channel Monthly Enterprise Channel Semi-Annual E...
Microsoft Planner: AI-generated status reports in Planner Agent
Microsoft Planner now includes AI-generated status reports via Planner Agent in Microsoft 365 Copilot, summarizing plan progress, risks, and n...