Microsoft Places in 2026: APIs, Desk Booking, and Copilot Context

Prefer audio?

Who should listen: Microsoft 365 service owners, workplace technology and corporate real estate teams evaluating or rolling out Microsoft Places, and UC/AV professionals integrating room and desk booking, sensors and signage with M365.

Guest: Brennan McReynolds — Product Strategy Lead, Microsoft Places, Microsoft

Brennan McReynolds leads product strategy in the Microsoft Places product and engineering group. He reviews what shipped during Places' first full year of general availability — desk booking on maps, check-in signals and the Graph APIs — and sets out the three partner integration patterns and how location context feeds Work IQ and Copilot.

Key insights

• The summer release added individual desk booking on a map, with check-in triggered by simply plugging a laptop into the monitor at the reserved desk, which then updates the user's location in Teams. ▶ 2:03
• The desk supply argument in numbers: pre-pandemic most organisations globally ran roughly one desk per employee (1:1.25 people per desk); the data now shows a move to two employees per desk, with some customers at five to one. ▶ 4:38
• Microsoft's stated position is that desk booking is not needed for everybody — the product goal is assigning a desk and finding where a colleague is sitting so people can sit together, i.e. in-person connection rather than universal hotelling. ▶ 3:37
• The Places directory is now published to Microsoft Graph with full CRUD operations, so third-party systems of record can create, update and delete buildings, floors, rooms and desks — Microsoft is explicit it is not trying to replace real estate or facilities platforms. ▶ 8:44
• Why the API matters operationally: roughly one in ten buildings has a spatial layout change every month, so manually maintaining floor plans across a hundred buildings and a thousand floors is unmanageable without connectors. Mapping partners handle conversion of anything from a DWG/AutoCAD export to a photo of a fire escape plan into IMDF. ▶ 9:16
• Three integration patterns to plan around: (1) spatial data in and out of the Places directory, (2) occupancy and check-in signal in and out, (3) extensible experiences such as visitor management, kiosks, digital signage and locker booking. ▶ 14:22
• A further set of APIs is being published to let third-party signals — room sensors, badge swipes at building or room level, desk peripherals — check in or auto-release rooms, alongside first-party sensors in Teams-certified devices. ▶ 12:19
• The first desk device with a Teams mini-panel interface will be a Yealink unit, giving visual confirmation of desk assignment, with admin portal changes reflected downstream on the display instead of sticky notes on desks. ▶ 13:21
• The practical starting point is to add buildings to the Places directory, then floors, then rooms and desks, then maps — buildings alone enable work plans and Copilot questions such as 'what's the best day to go in this week?' Around a billion square feet of office space was added in year one. ▶ 16:55

Insights summarised by AI from the episode transcript, reviewed by the Empowering.Cloud team.

Listen: Apple Podcasts · Spotify · Other platforms