Google closed the preview chapter on cross-room video for Meet and Microsoft Teams. On October 1, 2026, Google Workspace Updates made built-in interoperability generally available for Android/AOSP meeting-room hardware: Meet rooms can join Teams meetings, and Android-based Teams Rooms can join Meet meetings. Rollout for Rapid and Scheduled Release domains is full visibility in one to three days from that date.
That matters if your company lives in Google Workspace but clients keep sending Teams links, or the reverse. You should not need a laptop on the table just because the invite came from the other campus. The catch is scope. This is dedicated room hardware on Android/AOSP, not the Meet or Teams apps on your phone.
Independent coverage the next morning, including Android-focused roundups of the Workspace post, stressed the same hardware boundary: room systems on Android/AOSP, not mobile clients. That matches Google's availability line for Workspace customers with Meet hardware on Android/AOSP. If your fleet is ChromeOS Meet hardware only, read the Admin help for your path before you promise Teams joins from every room on campus.
Preview to GA in under a month
Google put the same Android room path into Early Preview on September 2, 2026. October 1 is general availability for Workspace customers with Meet hardware running Android/AOSP. Call it 29 days from preview post to GA post. Admins enable or confirm the setting in the Admin console under Devices → Meet hardware → Built-in Interoperability → Microsoft Teams. Google's help center says Direct Guest Join style Teams interop is on by default for organizations, including organizational units, unless you override it.
Built-in versus Pexip: what you actually get
Google's own Meet hardware interop help page (updated October 1, 2026) is the best feature card. Built-in Teams joins sit next to free Zoom and Webex joins. Pexip Connect remains a paid path for SIP and some Teams setups. The unsupported-feature table is the part most press notes skip:
| Feature on Meet hardware | Built-in Teams | Teams via Pexip | Zoom (built-in) |
|---|---|---|---|
| Join the other platform's meeting | Yes | Yes | Yes |
| Extra license cost (per Google) | No additional cost | Paid Pexip | No additional cost |
| Presenting over HDMI | Not supported | Supported | Supported |
| Dual-screen support | Not supported | Not supported | Not supported |
| Change participant layout | Not supported | Not supported | Supported |
| Closed captions / in-meeting chat | Not supported | Not supported | Not supported |
So the GA win is joining the call from the room you already bought. It is not feature parity with a native Teams Room or a laptop client. If your workflow depends on HDMI present into a Teams meeting from Meet hardware, Google's table still points you at Pexip for that row. Firewall allowlists may still need Team/Zoom/Webex destinations on locked-down networks.
Geeknewz verdict
Geeknewz's view: turn built-in Teams interop on (or confirm the default) this week if you already run Android Meet hardware and your calendar is full of mixed invites. The September preview to October GA path is short, the setting is in the Admin console, and Google documents no extra license fee for the built-in path. Keep expectations honest: you are buying join reliability, not captions, chat, dual screens, or HDMI present on stock Teams interop. Phone and tablet apps are out of scope. If HDMI present into Teams is non-negotiable, budget Pexip or keep a laptop in the room until Google's matrix changes.
Source: Google Workspace Updates (Oct 1, 2026); Early Preview post (Sep 2, 2026); Google Meet hardware interop help.