Microsoft Teams: Explicit consent for PSTN participants in one-to-one calls
Returned by 2 reference tenants · Corroborated by Microsoft 365 Message Center Archive by Merill FernandoRollout
- Roadmap
- 577543
- Platforms
- Android, iOS, Mobile
Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".
What the notice says
Microsoft’s text, safely structuredWhat and why
Microsoft Teams will support explicit consent for participants connected through the public switched telephone network (PSTN) in one-to-one Teams calls. When explicit consent is required, PSTN participants will hear an audio prompt when recording or transcription starts and can use their phone keypad to consent or decline. Participants who decline can remain in the call but stay muted. This capability extends the existing Teams calling policy for explicit consent to one-to-one PSTN calls.
Rollout schedule
- General Availability (Worldwide): Beginning in early December 2026
Impact on your organization
Who is affected
- PSTN participants in applicable one-to-one Teams calls where explicit consent for recording or transcription is required
What will happen
- PSTN participants will hear an audio prompt requesting consent when recording or transcription starts.
- Participants can press 1 to consent or 2 to decline.
- The PSTN participant's audio will not be included in the recording or transcript before consent is provided.
- PSTN participants who decline can remain in the call but stay muted.
- This capability uses the existing explicit consent setting in Teams calling policies. It does not introduce a new admin policy setting.
- The existing explicit consent setting is disabled by default.
- This update applies to one-to-one PSTN calls. It does not change compliance recording or the existing consent experience for meetings and group calls.
Action required and recommendations
No new policy configuration is required if your existing explicit consent configuration meets your organization's requirements.
- Review your organization's Teams calling policies and explicit consent requirements.
- In the Teams admin center, go to Voice > Calling policies and review Require participant agreement for recording and transcription for applicable policies.
- If explicit consent is already enabled, prepare users and support teams for the new PSTN keypad consent experience.
- If your organization wants to require explicit consent, enable the existing setting in the appropriate calling policies.
- Update internal guidance so users understand that PSTN participants who decline consent remain muted while the consent requirement applies.
Compliance considerations
| Question | Answer |
|---|---|
| Does the change include an admin control? | Yes. The capability uses the existing Teams calling policy for explicit recording consent rather than introducing a new policy setting. Microsoft Learn documents management through Teams calling policy and the -ExplicitRecordingConsent parameter. |
What changed
Between the versions we saw, newest firstThis installation has seen one version of this notice, first on 29 Oct 2026. Later changes will show here.
Archive version history
Microsoft 365 Message Center Archive by Merill FernandoThese are the archive's capture times. They are separate from the versions returned by our reference tenants.
Read the archive's current copy
What and why
Microsoft Teams will support explicit consent for participants connected through the public switched telephone network (PSTN) in one-to-one Teams calls. When explicit consent is required, PSTN participants will hear an audio prompt when recording or transcription starts and can use their phone keypad to consent or decline. Participants who decline can remain in the call but stay muted. This capability extends the existing Teams calling policy for explicit consent to one-to-one PSTN calls.
Rollout schedule
- General Availability (Worldwide): Beginning in early December 2026
Impact on your organization
Who is affected
- PSTN participants in applicable one-to-one Teams calls where explicit consent for recording or transcription is required
What will happen
- PSTN participants will hear an audio prompt requesting consent when recording or transcription starts.
- Participants can press 1 to consent or 2 to decline.
- The PSTN participant's audio will not be included in the recording or transcript before consent is provided.
- PSTN participants who decline can remain in the call but stay muted.
- This capability uses the existing explicit consent setting in Teams calling policies. It does not introduce a new admin policy setting.
- The existing explicit consent setting is disabled by default.
- This update applies to one-to-one PSTN calls. It does not change compliance recording or the existing consent experience for meetings and group calls.
Action required and recommendations
No new policy configuration is required if your existing explicit consent configuration meets your organization's requirements.
- Review your organization's Teams calling policies and explicit consent requirements.
- In the Teams admin center, go to Voice > Calling policies and review Require participant agreement for recording and transcription for applicable policies.
- If explicit consent is already enabled, prepare users and support teams for the new PSTN keypad consent experience.
- If your organization wants to require explicit consent, enable the existing setting in the appropriate calling policies.
- Update internal guidance so users understand that PSTN participants who decline consent remain muted while the consent requirement applies.
Compliance considerations
| Question | Answer |
|---|---|
| Does the change include an admin control? | Yes. The capability uses the existing Teams calling policy for explicit recording consent rather than introducing a new policy setting. Microsoft Learn documents management through Teams calling policy and the -ExplicitRecordingConsent parameter. |
- Microsoft Teams: Explicit consent for PSTN participants in one-to-one calls Action date: Not supplied
Learn more
Links from the notice and their documentation checksRelated public changes
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.
- 2 linked pages have not been read yet.
- Some history or links were left out of the website export to keep it within its size limits.