Take a look and decide whether this affects your tenant, users or support teams.
Primary Audience
Why this score?
AT A GLANCE
END USERS
IT ADMINS
ROLLOUT TIMELINE
December 2026
📢 Official Microsoft Message Center Announcement
(Updated) Microsoft Teams: Analytics for desk utilization in Teams Pro Management portal
Message ID: MC1490906 (Updated)
Updated October 28, 2026: We have updated the timeline. Thank you for your patience.
[What and Why:]
We’re expanding analytics in the Microsoft Teams Pro Management portal to include utilization insights for bookable desks. IT admins will be able to better understand how desk spaces are being used across their organization, with insights into desk utilization, reservations, occupancy, and peak usage patterns. Desk-specific filters, including location and desk mode, will help admins analyze usage across their workplace and make more informed space planning decisions.
For utilization analytics to be enabled, a desk needs to have one or more peripheral device associated, and the desk needs to be licensed with Microsoft Teams Shared Space license or Microsoft Teams Shared Space – Single Space license.
This message is associated with Microsoft 365 Roadmap ID 570648
[Rollout Schedule:]
General Availability (Worldwide): We will begin rolling out on early December 2026 (previously early November) and expect to complete by mid-January 2027 (previously mid-December 2026).
[Impact on Your Organization:]
These insights can help organizations better understand how bookable desks are being used and inform workplace and space planning decisions.
[Action Required/Recommendations:]
To enable utilization analytics, a desk must have one or more associated peripheral devices and be licensed with a Microsoft Teams Shared Space or Microsoft Teams Shared Space – Single Space license.
[Compliance considerations:]
No compliance considerations identified. Review as appropriate for your organization.
Source: Microsoft Message Center • Analysed by MWPro
<<< [MC1490906] Archive
Tooltip: View earlier revisions of this post


