UC Platforms — Microsoft Teams Rooms and Zoom Rooms

Microsoft Teams Rooms (MTR) and Zoom Rooms are the two dominant unified communications (UC) room platforms in the commercial market as of 2026. Both turn a standard conference room into a managed, software-defined meeting space — a certified compute module runs the meeting application full-screen, a certified touch controller handles room controls, and certified cameras, microphones, and speakers deliver the audio/video experience. The integrator's role is hardware selection and placement, network provisioning, licensing coordination, and commissioning. Understanding both platforms — their hardware ecosystems, licensing tiers, and interoperability capabilities — is essential for any AVC project touching conference rooms.

Microsoft Teams Rooms (MTR)

Compute Options

MTR runs on Windows or Android. Windows-based compute is the mature, full-featured choice for most commercial installs.

Lenovo ThinkSmart Core — The most widely deployed MTR compute module. Available in Core (standard) and Core+ (higher performance for multi-display rooms). Ships with the Lenovo ThinkSmart Controller (10" touch panel). The IP Controller add-on enables Crestron or AMX integration via IP. Third-party USB peripherals connect via the ThinkSmart One USB hub.

HP Presence Mini / HP Elite Slice G2 — Compact form-factor compute well-suited to huddle rooms. The Presence Mini includes built-in camera and speaker bar option. HP manages updates through HP Device Manager.

Poly GC8 / Studio X series — All-in-one form factors where compute and camera/speaker bar are integrated. Good for small-to-medium rooms where cable runs to a separate compute module are undesirable.

Crestron Flex — Crestron's MTR compute line (UC-MX50-T, UC-CX100-T, etc.) integrates directly with Crestron control systems. Crestron Flex pods combine the compute, touch panel, speakerphone, and camera into configured bundles. Uniquely, Crestron Flex allows AV control system programming (SIMPL, C#) to coexist with the MTR application.

Android-based MTR — Select devices from Yealink, Poly (Trio C60), and DTEN run MTR on Android. Android MTR has feature parity gaps compared to Windows for complex room configurations (multi-camera, content sharing from HDMI ingest) and is primarily suitable for smaller, simpler rooms.

Licensing Tiers

• Teams Rooms Basic (free, included with Microsoft 365): Limited to joining Teams meetings. No third-party meeting join (Zoom, Webex), no intelligent camera features (speaker tracking, people counting), no advanced analytics.
• Teams Rooms Pro (~$40/room/month as of 2025): Required for direct guest join (Zoom, Webex via CVI), AI-powered camera features (automatic framing, speaker tracking), Teams Admin Center advanced management, remote device health monitoring, and conditional access policies.

For enterprise clients with multi-room deployments, Teams Rooms Pro is effectively mandatory. Specify Pro licenses in the system design — Basic is insufficient for most commercial installations.

Content Sharing (HDMI Ingest)

MTR rooms support HDMI ingest — a laptop connected by HDMI can share content to the display and to remote participants simultaneously without launching the Teams client. The compute module includes an HDMI input (or requires a certified HDMI ingest module like the Crestron AirBoard or Lenovo ThinkSmart Hub with HDMI in). This is distinct from wireless sharing (AirMedia, ClickShare) and must be physically cabled.

Touch Controller Options

• Lenovo ThinkSmart Controller — Ships with ThinkSmart Core bundles. 10" Android-based, POE-powered.
• Crestron TSS-770-T — 7" Teams-certified touch controller; integrates with Crestron control systems.
• Logitech TAP — USB-based touch controller; connects to compute module via USB-C.
• Yealink CTP18 — 18" touch console for large room deployments.

Zoom Rooms

Compute and Hardware Ecosystem

Zoom Rooms runs on Windows, macOS, or Android/iOS. Hardware certification is less prescriptive than MTR — Zoom certifies individual peripherals (cameras, speakerphones, controllers) rather than tightly bundled compute systems.

Common compute configurations:

• Intel NUC (small form factor PC) + certified USB camera/mic/speaker — the most flexible integrator option
• Lenovo ThinkSmart Core running Zoom Rooms software (not MTR) — same hardware, different software image
• Poly Studio G7500 — all-in-one Zoom Rooms device with integrated 4K camera
• Neat devices (Neat Bar, Neat Bar Pro, Neat Board) — purpose-built Zoom Rooms hardware with excellent camera tracking

Controllers: Zoom Rooms Controller app runs on certified iPad or Android tablets (Logitech TAP, Yealink CTP18, Crestron TSS-7) mounted on the table. The iPad/tablet must be enrolled in Zoom Device Management.

Zoom Rooms Licensing

• Zoom Rooms license (~$50/room/month) is required for each room — this covers the room software.
• Zoom Phone is a separate add-on for PSTN calling from the room.
• Enterprise volume pricing is available through Zoom reseller channel.

Zoom Rooms vs. MTR Selection Guide

Select the platform based on the client's primary collaboration platform, not on hardware preference. Mixing platforms in a single enterprise creates management overhead and interoperability friction.

Interoperability Between Platforms

Enterprise clients frequently need a Teams room to join a Zoom call, or vice versa. Three approaches exist:

Cloud Video Interop (CVI) — Microsoft-approved CVI partners (Pexip, Cisco, Neat) provide a cloud gateway that bridges Zoom/Webex calls into a Teams Rooms device. Requires Teams Rooms Pro license and a separate CVI subscription. Adds latency and a monthly cost but is transparent to the user.

Direct Guest Join — With Teams Rooms Pro, a Teams room device can join Zoom or Webex meetings natively without a CVI. The experience is slightly degraded compared to native Teams, and requires an active internet connection regardless of local network conditions.

Zoom's One-Click Join — Zoom Rooms can accept Teams meeting invites and join via CVI or direct federation depending on configuration.

For clients with mixed UC environments, recommend standardizing on one platform and using CVI for exceptions. Trying to run both MTR and Zoom Rooms across the same estate creates two management portals, two licensing relationships, and inconsistent user experiences.

Network Requirements

Both platforms are bandwidth-intensive and latency-sensitive. See video conferencing room design for full coverage, but key requirements:

• Bandwidth per room: 4–6 Mbps up/down for 1080p video; 8–12 Mbps for dual-stream (content + video)
• Latency: <150 ms one-way preferred; >250 ms causes detectable echo and conversation disruption
• QoS markings: Teams uses DSCP 46 (EF) for audio, DSCP 34 (AF41) for video; Zoom uses similar DSCP markings. Verify with QoS configuration that markings are honored across the network
• Firewall ports: Both platforms require specific UDP/TCP ports to Microsoft/Zoom cloud endpoints. Review and whitelist in client's firewall before go-live
• VLAN isolation: Dedicate a VLAN for UC room devices for management simplicity and QoS enforcement

Common Pitfalls

• Specifying Basic license where Pro features are needed. Teams Rooms Basic is effectively a demo tier. Any client that expects third-party meeting join, AI cameras, or Teams Admin Center device management needs Pro. Mis-specifying Basic forces a license upgrade after install — price it correctly upfront.

• Mixing compute and software versions across a campus. A fleet of MTR rooms running different Windows versions and Teams app versions behaves inconsistently — features available in one room may not exist in another. Enroll all devices in Microsoft's automatic update channel or manage updates via Intune to maintain version parity.

• Ignoring HDMI ingest cable routing. HDMI ingest requires a cable from the table to the compute module. If rack and table positions were not designed to accommodate this cable run, the installed system will be missing a key feature. Plan the cable pathway before equipment placement is finalized.

• Touch controller placement without regard to sightlines. A touch controller mounted at the end of a table forces participants at the far end to walk to it. Center the controller on the table (directly in front of the display), and specify cable length accordingly. 5–7 m POE or USB-C table runs are common.

• Android MTR deployed in rooms requiring HDMI ingest or dual display. Android MTR does not support HDMI ingest (table cable content sharing) or true dual front-of-room display in all configurations as of 2025. Verify feature support against the Android MTR feature matrix before specifying Android to reduce cost.

• Firewall blocking UC cloud endpoints. Both Teams and Zoom require access to cloud endpoints that vary by region and update regularly. A firewall blocking these endpoints produces one-way audio, no video, or call failures that are difficult to diagnose. Implement URL-based firewall rules using the published Microsoft/Zoom endpoint lists, not IP ranges.