Teams Rooms & Device Management
From conference rooms to common area phones, Teams devices need careful management. Learn configuration profiles, Teams Rooms setup, firmware policies, remote sign-in, and VDI planning.
Managing Teams devices at scale
Imagine you manage 200 conference rooms, each with a screen, camera, microphone, and speaker.
You canβt walk into each room to update settings. Instead, you manage everything remotely from the Teams admin center β like a fleet management dashboard for meeting rooms. Configuration profiles push settings to groups of devices. Firmware updates roll out automatically. Device tags help you organise rooms by building or floor. And for new devices, remote sign-in means you donβt even need to be in the room to set them up.
Teams device types
| Device | Purpose | Licence | Example |
|---|---|---|---|
| Teams Rooms on Windows | Full meeting room experience β join meetings, share content, whiteboard | Teams Rooms Basic or Pro | Poly Studio, Lenovo ThinkSmart Hub |
| Teams Rooms on Android | Meeting room experience on Android hardware | Teams Rooms Basic or Pro | Neat Bar, DTEN D7X |
| Teams Phone (desk phone) | Voice calling with Teams | Teams Phone Standard + Calling Plan | Poly CCX400, Yealink T58A |
| Common area phone | Shared phone in lobby, break room | Teams Shared Devices | Poly CCX200, AudioCodes C470HD |
| Teams display | Personal desk display with Teams features | Teams Phone Standard | Lenovo ThinkSmart View Plus |
| Teams panel | Room scheduling display outside meeting rooms | Teams Rooms Basic or Pro | Crestron TSS-770, Poly TC10 |
| SIP device | Legacy SIP phones connected through SIP Gateway | SIP Gateway licence | Existing Cisco/Polycom SIP phones |
Microsoft Teams Rooms
Setting up a Teams Room
Each Teams Room needs:
- A resource account β like a room mailbox in Exchange
- Create in Microsoft 365 admin center β Resources β Rooms & equipment
- The account represents the room (e.g., βConf-Room-5A@pinnacle.com.auβ)
- A licence β Teams Rooms Basic (free, max 25 rooms) or Teams Rooms Pro
- A password for the resource account (used to sign into the room device)
- Calendar configured in Exchange (for scheduling)
Teams Rooms Basic vs. Pro
| Feature | Teams Rooms Basic (Free) | Teams Rooms Pro |
|---|---|---|
| Cost | Free (up to 25 rooms) | Paid per-device per-month |
| Join meetings | Yes | Yes |
| Share content | Yes | Yes |
| Intelligent cameras | No | Yes β speaker tracking, people recognition |
| Teams Rooms Pro Management | No | Yes β remote management portal, AI-driven insights |
| Front Row layout | No | Yes β optimised for hybrid meetings |
| Cloud IntelliFrame | No | Yes β AI-enhanced video |
| Max rooms per tenant | 25 | Unlimited |
Scenario: Tara manages 200+ rooms at Pinnacle Corp
Pinnacle Corp has 210 meeting rooms across APAC. Taraβs licensing strategy:
- 25 executive boardrooms β Teams Rooms Basic (free) β uses the full 25-room allocation for premium rooms that donβt need advanced features
- Wait β thatβs backwards. Executive rooms NEED intelligent cameras.
Revised:
- 25 small huddle rooms β Teams Rooms Basic (free) β basic join/share only
- 185 conference rooms β Teams Rooms Pro β intelligent cameras, Pro management, Front Row layout
- Each room has a resource account (Conf-Room-Building-Floor-Number@pinnacle.com.au)
Configuration profiles
Configuration profiles push settings to groups of devices without touching each one:
Teams admin center β Teams devices β Configuration profiles
| Setting Category | Examples |
|---|---|
| Display | Screen timeout, brightness, language |
| Network | Proxy settings, DHCP vs static IP |
| Account | Auto sign-in settings |
| Meetings | Default volume, auto-accept meeting invites |
| Device | Timezone, update ring |
Profiles are assigned to devices by device tag or individually.
Device tags
Tags are labels you apply to devices for organisation and bulk management:
- βBuilding-A-Floor-3β β all devices on Floor 3 of Building A
- βExecutiveβ β all executive boardroom devices
- βCommon-Areaβ β all lobby and break room phones
Tags enable you to:
- Apply configuration profiles to tagged groups
- Filter the device list in the admin center
- Run bulk operations (restart, update) on tagged devices
Firmware management
Teams device firmware is managed in the Teams admin center:
| Update Option | Behaviour |
|---|---|
| Auto-update (default) | Devices update automatically when firmware is available |
| Manual | Admin selects specific firmware versions to deploy |
| Defer | Delay updates for testing (30/60/90 days) |
Best practice: Use auto-update for most devices. Defer updates for a small βpilotβ group of devices to test firmware before broad rollout (similar to update rings for the Teams client).
Remote sign-in (provisioning)
New Teams devices can be provisioned without physically being at the device:
- In the Teams admin center, add the deviceβs MAC address and generate a verification code
- On the device, the technician selects Provision device and enters the verification code
- The device appears under Waiting for sign in in the admin center, where the admin completes remote sign-in with a resource account
This is critical for large-scale deployments β Tara doesnβt need to visit all 200 rooms to sign in each device.
Teams for VDI
Virtual Desktop Infrastructure (VDI) environments need special handling for Teams:
How Teams works in VDI
| Component | Hosted Where | Notes |
|---|---|---|
| Teams client (chat, channels, apps) | Virtual desktop (server) | Standard functionality |
| Media (audio, video, screen share) | Thin client (local device) | Media optimisation offloads to local device |
VDI platforms supported
- Azure Virtual Desktop (AVD) β native media optimisation
- Citrix Virtual Apps and Desktops β media optimisation plugin
- VMware Horizon β media optimisation via Teams VDI plugin
Exam point: Without media optimisation, Teams audio/video runs on the server and streams to the thin client β this causes high latency and poor quality. Media optimisation redirects media processing to the local device, dramatically improving call quality.
Key VDI considerations
- New Teams client is required (classic Teams deprecated for VDI)
- Media optimisation plugins must match the Teams client version
- Per-machine installation (not per-user) is recommended for VDI
- Persistent and non-persistent VDI both supported
- Some features may be limited in VDI (e.g., background effects, Together mode)
π¬ Video walkthrough
π¬ Video coming soon
Teams Rooms & Device Management β MS-700 Module 12
Teams Rooms & Device Management β MS-700 Module 12
~11 minFlashcards
Knowledge Check
Pinnacle Corp has 210 meeting rooms. Tara wants intelligent cameras and the Pro Management portal for 185 rooms, but needs to minimise costs for 25 small huddle rooms. What licensing approach should she use?
Tara is deploying 50 new Teams Rooms devices across Pinnacle Corp's APAC offices. She can't travel to each office for setup. How should she provision the devices?
Next up: PowerShell & Graph Automation β automate Teams management with the Teams PowerShell module and Microsoft Graph API.