{
"title": "Microsoft Targets September 2026 for Teams Rooms Call Quality Feedback on Android",
"content": "Microsoft plans to give IT teams a direct line to how meeting rooms actually feel to users by adding call quality feedback surveys to Teams Rooms on Android. Listed as Microsoft 365 roadmap ID 543713, the feature is in development for standard multi-tenant customers and currently targets general availability in September 2026. The surveys will ask meeting participants to rate calling, video, and screen sharing quality, with the goal of helping organizations deliver more consistent hybrid meeting experiences.
A New Feedback Channel for Meeting Rooms
According to the roadmap, the feature will be available on Android-based Teams Rooms and Teams/Surface Devices. Once enabled, users may see a prompt after a meeting ends that lets them provide a rating and optional feedback focused on three categories: calling quality, video quality, and screen sharing. Microsoft says this will help IT departments understand and improve the meeting-room experience where traditional telemetry falls short.
Shared spaces are notoriously hard to monitor. A conference room can show up as “healthy” in every admin panel—the Teams Room app is signed in, network connectivity is good, and no hardware faults are flagged—yet the actual meeting is a struggle. Audio may echo or cut out, remote video may stutter, or a critical spreadsheet may be unreadable to online participants. Until now, capturing these frustrations required someone to file a support ticket, often hours later, with vague details. The new survey creates an immediate feedback loop tied to a specific room and meeting time, giving IT teams a precise beacon for investigation.
What Changes for IT Administrators
The feedback feature doesn’t replace Microsoft’s existing quality toolkit; it adds a human layer on top of it. The Call Quality Dashboard (CQD) remains the engine for analyzing packet loss, jitter, and stream health across the organization. But CQD can’t tell you that the room’s microphone placement is causing echo, or that the ceiling-mounted camera misses half the participants. User surveys fill this perception gap.
When a room user submits a poor video rating, an administrator can pull up the corresponding meeting in CQD to look for correlated signals: did the device experience CPU throttling? Were other calls on the same subnet suffering? Did a firmware update coincide with the complaint? Over time, patterns will emerge: the same room always gets bad ratings on Tuesday mornings, or screen-sharing complaints cluster after 3 p.m. That allows network engineers to focus on specific time slots or building segments rather than treating every complaint as a one-off mystery.
The operational workflow after September 2026 might look like this: a survey comes in; support identifies the room and meeting window; CQD data for that call is retrieved and compared with recent trends; device health in the Teams admin center is checked; if the complaint is isolated, a local hardware check is scheduled; if multiple rooms show the same pattern, a network or update issue is suspected. Crucially, the feedback itself doesn’t automatically create an incident ticket—it’s a pointer that IT teams can use to prioritize investigations.
There’s a policy twist that catches many admins off guard. Microsoft’s documentation states that the usual PowerShell CsTeamsFeedbackPolicy cmdlets, used to control desktop client surveys, do not apply to Teams Rooms. Instead, in-product surveys on room devices are governed by the Cloud Policy service for Microsoft 365. Before September 2026, organizations should verify whether their current cloud policies inadvertently allow or block these prompts, especially in regulated environments or executive boardrooms where unsolicited pop-ups could cause confusion.
Behind the Decision: Bridging Telemetry and Perception
Microsoft has collected user sentiment from