Google Meet and Microsoft Teams Room Interoperability: 2026 Admin Guide
Business admin update — checked 6 October 2026: Google made built-in interoperability between Google Meet and Microsoft Teams generally available on supported Android/AOSP room hardware from 1 October 2026. This is a platform-and-device compatibility change, not a promise that every Android meeting-room product from Logitech, Poly, Neat or another vendor automatically supports both services.
Quick answer
Supported Android/AOSP Google Meet hardware can now join Microsoft Teams meetings, and supported Android/AOSP Microsoft Teams Rooms hardware can join Google Meet meetings. Before buying or reconfiguring a room, verify the exact hardware platform, current firmware, admin policy, service licensing and the vendor’s supported configuration.
What changed on 1 October 2026?
Google moved its built-in Meet/Teams room interoperability from preview to general availability. Google states that Android/AOSP-based Google Meet hardware can join Microsoft Teams meetings and Android/AOSP-based Microsoft Teams Rooms devices can join Google Meet meetings.
The rollout began on 1 October for Rapid and Scheduled Release domains. Google lists availability for Workspace customers with Google Meet hardware devices running Android/AOSP.
Compatibility checklist before buying room hardware
- Exact platform: confirm the device is actually running a supported Android/AOSP room platform, not merely “Android-based” marketing language.
- Exact mode: a room appliance may be sold in separate Google Meet and Microsoft Teams configurations.
- Firmware: confirm the current vendor firmware supports the required interoperability path.
- Admin controls: third-party conferencing access can require administrator configuration.
- Licensing: confirm the Workspace, Meet hardware and Teams Rooms licensing that applies to the deployment.
- Room peripherals: verify cameras, microphones, touch controllers and displays remain supported after any platform change.
- Support ownership: establish whether the hardware vendor, reseller, Google or Microsoft handles a fault before rolling out multiple rooms.
Do Logitech, Poly and Neat devices all support it?
Do not infer support from the brand name alone. Large meeting-room vendors sell different generations, operating platforms and certified configurations. The safe buying process is to check the exact SKU and current certification list. “Runs Android” is not enough.
Google Meet “Take notes for me” defaults changed from 29 September
Google introduced a pre-configuration option that can automatically enable AI note-taking for meetings with three or more people. For Business Standard and Business Plus organisations, Google says this setting is ON by default. For Enterprise Standard, Enterprise Plus, Frontline Plus and Google AI Pro for Education organisations, it is OFF by default. End users can override the admin default in their Meet settings where the feature is available.
Administrators should therefore check the actual Admin console state rather than assuming note-taking only starts when a host manually requests it.
Privacy and governance checks for automatic notes
AI-generated meeting notes can create a new business record. Organisations should decide how participants are informed, who receives the notes, how long they are retained, whether external guests are included, and how access aligns with employment, customer, confidentiality and regulatory policies.
The right configuration depends on the organisation and jurisdiction. This guide is not legal advice; the important technical point is that a new default can change behaviour without every employee deliberately switching it on meeting by meeting.
Logitech Rally Board 65 occupancy counting
Google also began rolling out occupancy counting to Android-based Logitech Gen 2 room hardware, starting with Rally Board 65, from 28 September 2026. Google says the feature is off by default and can be enabled by admins at domain, organisational-unit or group level.
Google states that occupancy detection processes data locally on the device and does not collect or store personally identifiable information. It counts room occupancy; it should not be described as identifying individual employees. Google says support for earlier Logitech Gen 1 hardware is planned through a future CollabOS update.
Why occupancy data still needs a policy
Even when a system does not identify individuals, room-utilisation data can influence workplace and real-estate decisions. Organisations should document the purpose, who can view exported occupancy data, retention periods and how it will be used. That avoids turning a facilities metric into an unexplained workplace-monitoring concern.
A practical deployment sequence
- Inventory every room by exact device model, platform and firmware.
- Identify whether each room is Google Meet hardware, Microsoft Teams Rooms or another platform.
- Confirm current vendor certification and interoperability support.
- Check Workspace and Teams licensing plus admin settings.
- Test one room with external and internal meetings before fleet rollout.
- Review AI note-taking defaults and notification/retention policies.
- Enable occupancy counting only where there is a defined facilities need and documented governance.
- Record the supported configuration for future firmware and hardware changes.
Buying advice for new meeting rooms
Interoperability reduces the risk of locking a physical room to one meeting platform, but it should not replace a proper room design. Camera coverage, microphone pickup, speaker clarity, touch controls, display size, cable management, remote administration and support contracts still matter. Buy the room around its actual size and meeting pattern, then treat cross-platform joining as an additional capability.
How we researched this update
We checked Google Workspace’s official 1 October interoperability announcement, its September note-taking configuration update and the official Logitech occupancy-counting rollout notice. We have not claimed that every vendor model is compatible; exact-device verification remains part of the purchasing process.
Primary sources reviewed
- Google Workspace: Meet/Teams interoperability general availability
- Google Workspace: Take notes for me settings
- Google Workspace: Logitech occupancy counting
Final verdict
The October interoperability change is valuable for mixed Google/Microsoft organisations, but the safe purchasing rule remains exact-model verification. Treat Android/AOSP as a platform requirement, not a universal compatibility badge. At the same time, admins should review Google Meet note-taking defaults and occupancy settings because those changes affect privacy and governance as much as room hardware.
Continue to our Business Media & Meeting Rooms section for room-system and collaboration coverage.
