What it does

Uses the monitors, cameras and USB audio people plug their laptops into to work out which room or desk they're in. For desks, plugging in can book the desk; for BYOD rooms (spaces with no Teams Rooms console), it gives you usage and peripheral health data in the Teams Rooms Pro Management Portal.

Key facts

• Desks come in two Exchange types: individual desks (desk) and desk pools (workspace). Microsoft recommends individual desks for user experience and reporting.
• Bookable desks need the tenant's Places enableBuildings setting on (check with Get-PlacesSettings) and allow 24–48 hours after creating accounts for things to show up.
• Individual desks need the Teams Shared Space licences; BYOD room usage reports need a Teams Shared Device licence on the room account. To access the BYOD features in the portal at all, the tenant needs at least one Pro, Premium or Teams Shared Device licence.
• Clients: new Teams on Windows or Mac, with the bookable desks app installed by default. The new VDI solution for Teams is supported.
• Peripherals must report a unique serial number. Devices with missing, shared or odd-character serials can't be managed. Microsoft publishes a PowerShell script to check this and to bulk-associate peripherals.
• A peripheral is identified by product ID, vendor ID and serial, and can only belong to one room or desk.
• Association options: the PowerShell script, auto-association, or manually in the portal under Planning > Inventory > Devices (unassociated devices show "Needs action").
• Auto-association for desks works on individual desks only. For BYOD rooms it needs a bookable room mailbox visible in the GAL and several unique user signals (threshold configurable in the portal).
• Data collection is controlled by CsTeamsBYODAndDesksPolicy with -DeviceDataCollection Enabled|Disabled (Teams PowerShell 6.5.0 or later). It's on by default commercially and off by default in government clouds.
• CsTeamsWorkLocationDetectionPolicy can set a user's work location to "In the office" when they plug in, if the user opts in.
• Desk reports show utilisation, unplanned reservations and reservation occupancy for weekday business hours; BYOD room reports show utilisation, meeting quality and peripheral Offline or Moved states.

When to use / skip

Worth doing when the client is running a hybrid-working programme and wants real occupancy data, or already uses Microsoft Places for desk booking. Plugging in to book is the closest thing to zero-effort desk booking you'll get, and the BYOD room reports finally tell estates teams which small rooms are actually used.

Skip it if the desk and room peripherals are a mixed bag of old monitors with no serials, or the client books desks through a third-party product that doesn't write to Exchange — auto-association depends on Exchange bookings. And don't start without the works council or privacy team's sign-off; it's location data about staff, even if Microsoft says no personal data is collected.

Configuration decisions

• Individual desks versus desk pools for each floor or neighbourhood.
• Whether to enable auto-association, and the signal threshold — lower is faster, higher is more accurate.
• Whether to roll out DeviceDataCollection to everyone, a pilot group, or leave it disabled for certain populations.
• Whether to turn on automatic work location updates, and how to communicate the user opt-in.
• Who in the facilities team gets inventory permissions in the portal to associate peripherals.
• Hidden versus GAL-visible rooms — hidden rooms aren't discoverable for BYOD management.

Gotchas

• Peripherals with no unique serial are the main failure. Run Microsoft's checker on a sample of each monitor and dock model before committing.
• Docking stations and webcams aren't supported for desks yet, so a desk with only a dock can't be identified.
• The BYOD room personal-device filter (a minimum number of unique users before a peripheral appears) is deliberate. A new room can look empty in the portal for a while.
• Disabling the portal-level BYOD and desk data setting hides inventory and halts reports, but the data stays in the service until you delete it.
• Peripherals that get moved between desks show as "Moved" or re-associate somewhere else. Agree who fixes that.
• Propagation takes 24–48 hours after creating desk accounts. Don't test on day one.

Consultant notes

• Start with one floor of individual desks with known-good monitors; prove the plug-in-to-book experience before scaling.
• Get the privacy and HR conversation done before enabling data collection, and record the decision.
• Use the Microsoft script for initial bulk association; let auto-association handle the churn afterwards.
• Tie desk and room names to the same building and floor structure used in Places so reports line up.
• Hand the usage reports to the workplace team, not IT. They're the ones who'll act on them.

---

Revisit when docks and webcams become supported for desk association, or when Places changes how desk resources are created