Almanac
Microsoft/teamsMicrosoft 365

Consultant-focused KB for Microsoft Teams: implementation notes, gotchas and configuration decisions beyond the official docs — across chat and collaboration, meetings, webinars and town halls, Teams Phone, PSTN connectivity (Direct Routing, Operator Connect, Calling Plans, Teams Phone Mobile), auto attendants, call queues and contact centre integration, Teams Rooms and devices, apps and extensibility, Copilot in Teams, administration and governance, security and compliance, network and call quality, and licensing — plus cross-cutting decision guides.

teams/06-teams-rooms-and-devices/feature-rooms-direct-guest-join.md
feature-rooms-direct-guest-join.mdv1 · history
CurrentApplies to Teams Rooms Basic, Teams Rooms ProUpdated 3 weeks agoSource Microsoft Learn ↗

What it does

Lets a Teams Rooms device join Zoom, Webex or Google Meet meetings from the calendar, without a separate codec. Direct Guest Join runs the other platform's web client on the room; the alternative, cross-platform SIP join, dials the meeting as a SIP video endpoint.

Key facts

  • Direct Guest Join (WebRTC) supports Cisco Webex, Zoom and Google Meet. Cross-platform SIP join covers a wider list including Amazon Chime, GoToMeeting and RingCentral.
  • Direct Guest Join works with either Teams Rooms Basic or Pro. SIP join needs Teams Rooms Pro, plus a SIP calling service.
  • Direct Guest Join sends and receives up to 720p/30fps on one display and only receives content. SIP join goes up to 1080p/30fps, supports two displays, and can share via HDMI and content camera.
  • Direct Guest Join needs direct internet access to the third-party service — firewalls and web filters must let it through without authentication.
  • Teams Rooms on Windows supports both methods; Teams Rooms on Android supports Direct Guest Join.
  • The room mailbox needs Set-CalendarProcessing <upn> -ProcessExternalMeetingMessages $True -DeleteComments $False so the invite body (and the join link) survives.
  • URL rewriting breaks link detection. Add *.webex.com/*, *.zoom.us/*, *.zoom.com/*, *.zoomgov.com/* and *.meet.google.com/* (as needed) to the Safe Links "Don't rewrite" list or your third-party filter's exceptions.
  • Enable per platform in the Pro Management Portal (Rooms > room > Settings > Meetings) or locally on the console under Settings > Meetings. On Windows you choose "Join with room info" or "Join with custom info"; saving restarts the device.
  • If SIP is enabled and a SIP dial string isn't in the invite, calendar join falls back to Direct Guest Join. Join-by-ID doesn't fall back and will fail.
  • Not available in third-party meetings: PTZ camera controls, reactions, annotations, transcript, lobby admit, mic mute sync, coordinated join, and Whiteboard interaction (view only).

When to use / skip

Turn on Direct Guest Join for whichever platforms the client's customers and partners actually use. It costs nothing extra, works on Basic, and covers the "the client sent a Zoom" problem that otherwise ends with someone's laptop on the table. Expect a decent but basic experience — it's a guest in someone else's meeting.

Go for SIP join only when third-party meetings are a big part of the room's life (boardrooms that regularly meet external partners on Webex, for example) and the client is already paying for SIP interop. It's better quality and handles content properly, but needs Pro and a SIP provider. For most estates, DGJ alone is the right answer.

Configuration decisions

  • Which platforms to enable. Don't switch on everything by default if the security team only allows specific external services.
  • "Join with room info" versus custom identity — some clients want the room to appear under a friendlier display name in external meetings.
  • Whether the security team will accept the Safe Links don't-rewrite exceptions. No exception, no join button.
  • Whether proxy authentication can be bypassed for the rooms' traffic to those services.
  • QoS treatment for third-party media, if the network team marks it at all.
  • Whether SIP join is worth it for specific high-value rooms, and how users will be told join-by-ID won't fall back.

Gotchas

  • The single biggest failure is URL rewriting. The meeting's on the room calendar, the link is in the body, and there's still no join button because Safe Links has mangled the URL.
  • DeleteComments $true from an older room-hardening script strips the body and kills DGJ. Check before blaming the device.
  • Invites forwarded by a user from an external organiser need ProcessExternalMeetingMessages $true or the room never accepts them.
  • Authenticating proxies are a hard stop. DGJ has no way to answer a proxy auth prompt.
  • Third-party features change on the other vendor's schedule. Something that worked in testing can change without anything changing on your side.
  • Content sharing via HDMI into a DGJ meeting isn't supported — users will try it, so tell them to share from their laptop into the meeting instead.

Consultant notes

  • Test each enabled platform end to end with a real external organiser, not an internal invite. Forwarded and external invites behave differently.
  • Agree the Safe Links exception list with security up front and document it in the design; it often blocks go-live.
  • Include a one-page "joining non-Teams meetings" guide in room signage or the panel. Users need to know what won't work.
  • If the client has a mix of Pro and Basic, document which rooms have SIP so the helpdesk can explain the difference.
  • Re-test after major Teams Rooms app updates and after the client changes web filtering vendors.

Worth revisiting after the next round of third-party platform changes, or if Android rooms get SIP join parity

Was this accurate?
Related
Breakout Rooms in Teams Meetings02-meetings-webinars-and-eventsMeeting Policies, Lobby Bypass and Meeting Options02-meetings-webinars-and-eventsTeams Phone Survivable Branch Appliance (SBA)03-teams-phoneTeams Premium meeting protection: watermarking and end-to-end encryption10-security-and-complianceTeams Webinars and Event Registration02-meetings-webinars-and-eventsTeams Rooms on Windows vs Android, and Rooms Basic vs Pro13-decision-guides