Microsoft has completed the rollout of proximity join for presenters during Teams events, allowing a personal device such as a laptop or phone to bring a nearby Teams Room system into a town hall, webinar, or structured meeting without manual setup. The feature, tracked under Microsoft 365 Roadmap ID 561550, reached general availability in June 2026 and is now listed as fully launched. It works with Teams Rooms on Windows and Android, and it is available across Worldwide Standard Multi-Tenant, GCC, and GCC High clouds.

What actually changed

In a standard Teams meeting, proximity join has long let a user walk into a conference room, have their personal client detect a nearby room system via Bluetooth or ultrasound, and add that room to the call with a couple of taps. The room takes over the heavy lifting for audio and video, while the laptop stays connected as a companion for content sharing, chat, and notes.

Events are different. Town halls, webinars, and structured meetings introduce roles like organizer, presenter, and attendee; they have backstage green rooms, controlled stage management, and separate media paths. Until now, a presenter who wanted to use a room’s professional cameras, microphones, and displays during an event had to rely on the room’s own calendar invitation, manually search for the event on the room console, or cable up a laptop—none of which is quick or foolproof under pre-show pressure.

The new capability lets a designated presenter open the event on their own Teams client, discover an eligible nearby room, and connect that room as the AV endpoint. The room joins with its certified hardware, event-appropriate controls, and front-of-room attendee view, while the presenter retains their personal device for notes, private chat, and content sharing—without creating echo or feedback loops.

Microsoft explicitly calls out town halls, webinars, and structured meetings as supported scenarios. Android-based Teams Rooms, which previously lagged Windows rooms in event presenter support, are now included. This closes one of the most visible functional gaps between the two platforms for hybrid event production.

What it means for you

For presenters

If you have ever scrambled to join a town hall from an unfamiliar conference room—retyping meeting IDs, juggling a resource account you don’t own, or resigning yourself to using a laptop webcam while the perfectly good room system sits idle—this feature is for you. The workflow follows the same logic as proximity join in regular meetings: walk in, select the room from the join experience in your Teams client, and confirm. You don’t need to know the room account name, operating system, or hardware vendor.

Critically, connecting the room does not put you live on stage automatically. Event organizers still control when your feed appears to attendees. Your laptop remains essential for speaker notes, monitoring chat, or sharing a specific application. Teams also suppresses the laptop’s speaker and microphone when a room is joined to prevent howling feedback, so you do not have to manually mute one device.

The feature shines when you are a visiting speaker, when the room was not originally invited, or when the production team needs to swap presenters quickly. It reduces the risk of joining with the wrong account or accidentally exposing backstage content.

For IT administrators and event producers

This launch lets you standardize presenter guidance across your entire room estate—Windows and Android—and reduce last-minute support calls caused by confused presenters. Update your event runbooks to include the proximity join path as the preferred method for in-room presenters, but keep a documented fallback. Bluetooth or ultrasound discovery can fail in open-plan offices, when laptop radios are off, or when two rooms are too close. QR-code joining from the room console is a reliable backup that Teams Rooms already supports.

You will also need to validate the feature on your actual hardware. Android room systems depend on manufacturer firmware and may not all behave identically on day one. Test each certified device family for town hall and webinar behavior, green-room access, stage controls, and content sharing. Verify that the room’s resource account, meeting policies, and network rules allow the intended event types. A generally available cloud feature does not fix a room with outdated Teams Rooms application, expired credentials, or blocked services.

Help-desk scripts should distinguish between discovery failures, authorization failures, and event-production failures. A presenter who sees a disabled join button may be dealing with a wrong role assignment, a room that is already in another call, or a policy restriction—not a broken feature. Work with your event organizers to assign presenter roles in advance and rehearse the join and stage transition at least once before important broadcasts.

For organizations using government clouds

Availability in GCC and GCC High means public-sector teams can adopt the same workflow for controlled briefings, training webinars, and leadership town halls. Because these environments often enforce stricter guest-access and device-management policies, test the feature under your actual compliance configuration. A feature that works in a commercial tenant may be intentionally blocked in certain cross-tenant or anonymous scenarios.

How we got here

Proximity join was originally built to solve a simple hybrid-work annoyance: you walk into a room, and your laptop already has the meeting open, but the room’s AV equipment is far better. Instead of forwarding invitations or typing meeting IDs, Teams could discover the room via Bluetooth or ultrasound and hand off audio and video. That workflow became second nature in everyday meetings.

Events, however, have a more complex state model. A person may be invited, promoted to presenter, held in a green room, previewed, and only then exposed to attendees. The room must respect those stages without exposing backstage controls on its front display or letting an unintended feed reach hundreds of viewers.

Teams Rooms on Windows gained the ability to join webinars and town halls as a presenter through an earlier service-side update. Android rooms later received town hall presenter support as Microsoft worked toward platform parity. Roadmap item 561550 ties these capabilities together with proximity join, so the presenter’s identity and event role can travel with them into any compatible room.

The March 2025 general availability of the feature on Android, combined with its earlier availability on Windows, means that an enterprise with a mixed room fleet can now give presenters a consistent experience. The separation of person (identity, role) from room (hardware, resource account) is what makes this architecturally clean: Microsoft coordinates the authenticated user’s event participation with the room’s session join, preserving both role integrity and AV quality.

What to do now

If you manage Teams Rooms

  • Inventory your devices: Confirm which Windows and Android models are in scope. For each Android family, note manufacturer, firmware version, and Teams Rooms app version.
  • Run a pilot: Schedule a test town hall and webinar with a mix of internal and external presenters. Validate proximity join via Bluetooth/ultrasound, QR-code fallback, green-room entry, stage activation, and content sharing. Record differences between platforms.
  • Update policies and documentation: Ensure your room resource accounts, meeting policies, and network allow the event types you plan to run. Publish a one-page presenter card that explains how to join, what the room display will show, and who to call for help.
  • Train support staff: Give your help desk a clear troubleshooting flow: check user account, role assignment, room online status, discovery method, and fallback options before escalation.
  • Establish a fallback for live events: For any important broadcast, ensure the production team knows how to join the room directly from its console if proximity join fails. This is not a substitute for proper rehearsal; it is an insurance policy.

If you present at live events

  • Arrive early: Walk into the room, open the event in Teams, and test proximity join before attendees are admitted. Confirm that you see the room as discoverable and that it connects without issues.
  • Understand your role: Connecting the room does not mean you are instantly on stage. Your organizer may still need to promote you or move you from backstage. Coordinate with your production team.
  • Use your laptop as a companion: Keep speaker notes, private chat, or a second screen on your personal device. Share content deliberately—only the window or screen you want attendees to see.
  • Mute your laptop speakers: Teams usually handles this automatically, but double-check that you are not creating an audio loop. If you hear echo, mute your laptop mic and speaker manually.
  • Leave the event cleanly: After the broadcast, leave the event on both the room system and your personal device. Confirm that screen sharing has stopped and that no content remains visible on the room displays.

Outloook

This launch is part of a broader Microsoft push to make Teams Rooms a credible front end for managed live events, not just for ad-hoc meetings. Future improvements could include better join-readiness diagnostics that pinpoint whether a failure is due to discovery, identity, policy, or network issues—saving support teams precious minutes during a live broadcast. We may also see deeper role-awareness, where the room console proactively guides a presenter through backstage entry and stage activation, while giving producers final say over what reaches the audience. For now, the feature delivers the most immediate value by removing a fiddly, time-consuming step at the moment remote and in-room presenters need it least.