(Updated) Microsoft Teams: Proximity join support for presenters in Teams events from Teams Rooms on Windows and Android [MC1319213]

Message ID: MC1319213 (Updated)

Updated June 29, 2026: We have updated the timeline. Thank you for your patience. 

[What and Why]

We are introducing proximity join support for presenters in Microsoft Teams events (town halls, webinars, and structured meetings) using Teams Rooms on Windows and Android. This improvement enables presenters to quickly connect their personal device to a nearby Teams Room system, delivering a more seamless and efficient presentation experience. This update enhances hybrid meeting scenarios by simplifying room system interactions and improving presenter productivity.

This message is associated with Microsoft 365 Roadmap ID 561550.

[Rollout Schedule]

• General Availability (Worldwide, GCC, and GCCH): Begins rolling out in early June 2026 and completes by mid-July 2026 (previously mid-June).

[Impact on Your Organization]

Who is affected

• Presenters participating in Teams events (town halls, webinars, structured meetings)
• Organizations using Teams Rooms on Windows or Android devices

Platforms/Services

• Microsoft Teams
• Teams Rooms on Windows
• Teams Rooms on Android
• Desktop/mobile Teams clients (for proximity join initiation)

What will happen

• Presenters can use proximity join from their personal device to connect to nearby Teams Rooms during events.
• The connected Teams Room can be used to support live presentations.
• The experience is designed to reduce setup time and simplify presenter workflows in shared spaces.
• This feature will be enabled by default.
• No changes to existing policies or configurations are required.

[Action Required/Recommendations]

No action is required to enable this feature.

Recommended actions:

• Inform presenters and meeting organizers about this improved experience.
• Update internal training or documentation for Teams Rooms and hybrid presentations.
• Review Teams Rooms configurations to ensure devices are updated and functioning as expected.

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

Source: Microsoft

<<< [MC1319213] Archive
Tooltip: View earlier revisions of this post

Latest Posts