Message Center

MC1183611Consult and merge into a meeting or group call via Dual-Tone Multi-Frequency (DTMF)

Summary

Microsoft Teams will enable consulting and merging PSTN callers into meetings via DTMF navigation through IVR or auto-attendants. Rolling out April to June 2026, this feature requires no admin action, is enabled by default, and allows seamless integration of external callers into active meetings.

More information

Updated May 18, 2026: We have updated the timeline. Thank you for your patience. 

Introduction

To improve collaboration and streamline meeting workflows, Microsoft Teams is introducing the ability to consult and merge Public Switched Telephone Network (PSTN) callers into active meetings—even when those callers are behind auto-attendants or Interactive Voice Response (IVR) systems that require Dual-Tone Multi-Frequency (DTMF) navigation. This enhancement allows users to reach subject matter experts via dial-in and seamlessly bring them into the broader conversation.

user settings

This message is associated with Microsoft 365 Roadmap ID 518218.

When this will happen:
  • Targeted Release: Rolling out early April 2026 (previously early March), expected to complete by mid-April 2026 (previously mid-March).
  • General Availability:  Rolling out mid-April 2026 (previously late March), expected to complete by mid-June 2026 (previously late April).

How this affects your organization:

  • Who is affected: All Microsoft Teams users who initiate or manage meetings with PSTN participants. Administrators overseeing Teams meeting policies and call configurations.
  • What will happen:
    • Users can consult with PSTN or Voice over Internet Protocol (VoIP) participants via the Participants panel.
    • A new interface will allow users to access a dialpad to navigate IVR systems and auto-attendants using DTMF tones.
    • Once the external party is reached, users can merge them into the ongoing meeting.
    • No changes to existing administrator policies; feature is enabled by default.

What you can do to prepare:

  • No administrator action is required for this rollout.
  • If your organization uses custom training or helpdesk documentation, consider updating it to reflect this new capability.
  • Before rollout, we will update this post with new documentation.

Compliance considerations:

No compliance considerations identified, review as appropriate for your organization.

Version history

6 versions tracked

Updated 5 times since Nov 7, 2025. Microsoft 365 Message Center only shows the current version; this archive preserves tracked history.

Compare any two versions

From
To
  1. May 18, 2026 - 04:26 PMLatest - v6

    Changed: Body

  2. Mar 16, 2026 - 04:20 PMv5

    Changed: End date

  3. Feb 20, 2026 - 10:51 PMv4

    Changed: Body, End date

  4. Jan 13, 2026 - 05:29 PMv3

    Changed: Body, End date

  5. Dec 3, 2025 - 05:52 PMv2

    Changed: Body, Tags, End date

  6. Nov 7, 2025 - 12:50 AMOriginal - v1

    Changed: Initial version