The entry is listed as In development, with general availability estimated for December 2026 on the Worldwide (Standard Multi-Tenant) cloud. Treat that date as Microsoft's estimate, not a promise.
What the roadmap says
Here is what the roadmap entry commits to:
- Scope: Explicit consent for PSTN participants in one-to-one Teams calls.
- Trigger: When an admin requires explicit consent and someone starts recording or transcription, the PSTN participant hears an audio prompt.
- Response: The caller presses keys on the phone keypad to consent or decline.
- If they decline: They stay on the call but remain muted.
- Policy: This extends the existing explicit-consent setting in Teams calling policy. It is not a new, separate control.
- Metadata: Microsoft Teams; Android, iOS and Mobile platform tags; General Availability ring; Worldwide (Standard Multi-Tenant) cloud.
The platform tags are odd for a feature aimed at people on a regular phone line. The entry doesn't say whether they refer to the Teams user's client or something else. Wait for Microsoft's rollout notice before assuming which clients and devices will show the new flow.
Microsoft's own roadmap page says its dates are estimates and that items can be removed when they ship, are cancelled, or are postponed.
Section summary: This is a planned addition to an existing calling-policy setting. PSTN callers get a keypad consent prompt, and anyone who declines stays on the call muted.
Why this matters: PSTN callers have been auto-consented
The recent history explains why this entry matters. Late in 2025, Microsoft announced that explicit recording consent was coming to one-to-one Teams calls under Message Center post MC1163766 and roadmap ID 503295. Early versions of that announcement covered PSTN too. Third-party trackers quoted it as saying "Microsoft Teams will require explicit consent before recording or transcribing 1:1 PSTN or VoIP calls, enhancing privacy and compliance."
Microsoft then narrowed the scope. The updated post said Microsoft Teams will require explicit consent for recording and transcription in 1:1 VoIP calls starting early 2026, and that PSTN calls are auto-consented; explicit consent for PSTN will come later. Rollout dates also slipped. According to a March 2026 summary of the updated post, General Availability (Worldwide, GCC): Begins mid-January 2026 (previously mid-December 2025), completes late April 2026 (previously late January).
The same pattern showed up for desk phones. Microsoft's notice for Teams Phone devices said Public Switched Telephone Network (PSTN) endpoints will be auto-consented. Explicit consent support for PSTN will be included in a future release. It also told admins to update Microsoft Teams Phone Devices to 1449/1.0.94.2025443703 before enabling the policy.
Roadmap item 577543 looks like that promised "future release." For a year, an admin could turn on explicit consent and still have PSTN legs quietly auto-consented. If the PSTN leg was the external party you most needed consent from, that gap mattered.
Section summary: The VoIP version of this feature shipped with PSTN callers auto-consented, and Microsoft said PSTN support would follow. This roadmap item is that follow-up.
How explicit consent works today
The PSTN change plugs into an existing feature, so it helps to know how that feature behaves. Microsoft Learn describes the one-to-one call experience this way:
- Once a user starts recording, transcription or both, the other participant is muted and their camera and content sharing are turned off.
- The person who started recording is treated as having consented and stays unmuted.
- When the other person tries to unmute, turn on their camera or share content, Teams asks them to answer Yes or No.
- If they answer No, they get a view-only experience and can't unmute or turn on their camera.
- Each participant's choice is visible to admins and is recorded in the Purview audit log for the call.
The roadmap entry confirms only two things for PSTN callers: the keypad prompt, and staying muted after declining. It doesn't list which keys to press. Teams Audio Conferencing, a separate meeting feature, uses 1 to consent and unmute and 2 to decline and stay muted. That is a different scenario, so don't assume the one-to-one call flow will use the same keys until Microsoft documents it.
Learn also notes that explicit consent is not supported for call queue calls. The calling-policy setting covers one-to-one VoIP and PSTN calls only. Admins use the Teams admin center or the -ExplicitRecordingConsent parameter in the New-CsTeamsCallingPolicy cmdlet to manage recording consent for Teams calls. This parameter manages recording consent for Teams 1:1 VoIP and PSTN calls. Audio conferencing and group calls are handled by Teams Meeting Policy, and nothing in this roadmap entry changes them.
Section summary: The existing feature mutes the other party until they agree and logs each choice. For PSTN callers, the roadmap confirms only a keypad prompt and muting on refusal.
What admins should check before December
The PSTN prompt only appears when the underlying features are turned on, so it's worth checking your policies now. Microsoft documents three separate pieces:
| Control | Teams admin center | PowerShell parameter |
|---|---|---|
| Call recording | Voice > Calling policies > Cloud recording for calling | -AllowCloudRecordingForCalls |
| Call transcription (off by default) | Voice > Calling policies > Transcription | -AllowTranscriptionForCalling |
| Explicit consent | Calling policy setting | -ExplicitRecordingConsent (Enabled/Disabled) |
Requiring consent doesn't turn on recording or transcription. It only controls what happens once someone uses them. A tenant with call recording switched off will never play the PSTN prompt.
The consent setting itself is off unless you change it. Topedia's write-up of the calling-policy setting says this property is disabled by default, meaning explicit recording consent is not required. The documented command shown in Microsoft's notice is:
Set-CsTeamsCallingPolicy -Identity Global -ExplicitRecordingConsent "Enabled"
You can also apply it to a named policy instead of Global. Microsoft's notices said administrators can apply this policy tenant-wide or to specific users.
Before the PSTN flow arrives:
- Check who has explicit consent enabled. If it's already on for VoIP, the PSTN prompt should apply to those same users once it ships. The roadmap describes this as an extension of the existing setting, not a new switch.
- Compare call and meeting policies. Microsoft recommends checking meeting recording settings too, because users switch between calls and meetings and different rules for each can confuse them.
- Update training and scripts. Staff who record calls with customers or suppliers on regular phones should know the other party will soon hear a prompt and may decline. A caller who stays on the line but can't be heard needs a plan: switch off recording, or carry on without it.
- Review your audit reports. Consent data appears under the "Added information about call participants" filter in the Teams calling audit logs in Purview. Topedia reported that, for now, you will find auto-consent information for PSTN calls, compared to VoIP calls, where the state is Yes or No. Once the PSTN flow ships, check whether keypad answers show up as Yes/No entries before your compliance reports rely on that.
- Test with real phone lines. When the rollout notice arrives, test with your actual calling setup, whether that's Calling Plans, Operator Connect or Direct Routing. The roadmap doesn't say whether any of those routes are excluded.
Section summary: Check your recording, transcription and consent settings, tell users that callers may decline, and test the audit trail once the feature ships.
Caveats
This is a privacy improvement, but it has limits:
- The date may slip. The VoIP version of this feature slipped by about a month at the start and finished months late. December 2026 is a target.
- The prompt doesn't settle legal questions. A keypad prompt gives you a clearer consent record. Whether it meets the consent rules where you operate is a question for your legal team, not Teams.
- Compliance recording isn't covered. The entry is about the recording and transcription users start themselves in calling policy. It doesn't mention changes to policy-based compliance recording, call queues or group calls.
- Details are still missing. Key mappings, whether the prompt can be re-offered after a refusal, and supported clients all depend on Microsoft's final documentation.
Bottom line
Microsoft's own notices described PSTN support as unfinished business when explicit consent came to one-to-one VoIP calls. Roadmap item 577543 is meant to finish it: PSTN callers hear an audio prompt, answer on the keypad, and stay muted if they decline. Until it ships, PSTN legs are still auto-consented, and the December 2026 date is only an estimate. Check your calling policies now, and test the feature yourself once Microsoft's Message Center rollout notice arrives.
References
- Microsoft Teams: Explicit consent for recording & transcription in one-to-one PSTN calls Microsoft 365 Roadmap · 2026-10-23T21:59:27.914792Z
- Explicit recording and transcription consent for Audio Conferencing - Microsoft Teams | Microsoft Learn learn.microsoft.com
- Teams Policy Update: Explicit Consent for Recording MC1163766-4 mwpro.co.uk