LearnMicrosoft Teams › 8 · Devices & rooms

Rooms and phones: choosing and deploying the estate

The hardware decision tree — bar vs compute+console, phone vs headset, panel or not — decided per space type once, deployed a hundred times. Standardise or drown in snowflakes.

Decide per space type, not per room

Space Sensible kit Licence
Focus/phone booth (1-2) No room system; BYOD + wall display, or a hot-deskable deskphone none/CAP
Small huddle (2-5) All-in-one MTRoA bar Rooms Basic or Pro
Standard meeting room (6-12) MTRoA bar or MTRoW + console; scheduling panel Rooms Pro (health matters here)
Boardroom/divisible MTRoW, dual display, ceiling audio DSP, Pro Rooms Pro, always
Frontline/warehouse Rugged handsets/CAP + walkie-talkie on mobile CAP/F licences
Reception/lobby CAP phone (restricted policy) CAP

The standardisation dividend compounds in operations: one bar model per size class means one firmware train to ring-test per class (device-management concept), spares that fit everywhere, and console instructions that are true in every room.

Deployment gotchas that recur

  • The resource account precedes the hardware: licence + calendar processing
    • CA treatment ready BEFORE the installer arrives, or the install day becomes an identity day.
  • Panels need their own thinking: scheduling panels sign in as the room (or linked) — their occupancy/booking behaviours ride room policy.
  • BYOD rooms are still rooms: a display + USB puck space benefits from being INVENTORIED (BYOD device policies exist in TAC and — per your scan — TeamsBYODAndDesksPolicy governs the desk/BYOD experience). Unmanaged meeting spaces are where AV budgets leak invisibly.
  • Network per room: room systems on a device VLAN with the QoS/Optimize path proven from THAT segment (media concepts apply per-VLAN; test once per template, not once per estate).

What to watch (proofs)

  • Estate census: TAC device categories vs the space audit — rooms without systems, systems without rooms (moved hardware) — reconcile quarterly.
  • Per-space-type incident rate: tickets tagged by space class — the class with outlier rates has a design problem, not a luck problem.
  • BYOD/desk policy state: Get-CsTeamsBYODAndDesksPolicy (in the scan) — the governed-vs-wild boundary for unmanaged spaces.
  • The room-readiness pre-flight per install: account sign-in tested, calendar auto-accept verified, test call from the room's VLAN — three checks, zero install-day surprises.

PowerShell for this concept

  • Get-CsTeamsBYODAndDesksPolicy
  • Get-CsTeamsIPPhonePolicy Get-CsTeamsIPPhonePolicy allows IT Admins to view policies for IP Phone experiences in...

Discussion

No messages yet — start the thread.

Sign in with your email to join the discussion — we send a one-time link, no password.