Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources or documents need attention: 271/271 feeds/APIs · 464/464 docs · 4/4 advisories · checked 01:01 UTC Customize Public modeDiscuss ChangeIntel on Discord

Teams admin center - Intelligent insights for meeting quality

Rollout

Roadmap
574108
Platforms
Web

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

What the notice says

Microsoft's text, with its sections, lists and tables; source markup removed

What and Why

Gain proactive visibility into meeting quality across your organization with AI-powered insights in Teams admin center that identify emerging patterns, highlight impacted users and locations, and surface likely causes with recommended actions. This helps IT administrators detect and address issues earlier, improve meeting quality, and stay ahead of potential disruptions.

Rollout Schedule

General Availability (Worldwide): We will begin rolling out in mid-November 2026 and expect to complete by early December 2026.

General Availability (GCC): We will begin rolling out in mid-November 2026 and expect to complete by mid-December 2026.

Impact on Your Organization

Administrators will find new enhancements to the meeting and call troubleshooting flow in Teams admin center. Administrators can find these insights in Teams admin center > Meetings > Meetings. The experience evaluates historical meeting-quality data across the organization and highlights locations or public IPs where meeting quality is behaving unusually.

When an anomaly is detected, administrators will be able to:

  • Identify meeting-quality hotspots across locations and public IPs and see how many users are affected.
  • Review quality trends to understand how meeting quality has changed over time.
  • Understand likely root causes across network factors such as bandwidth, Wi-Fi, VPN and proxy; compute factors such as CPU, memory and client; and devices such as microphones, cameras and speakers.
  • Take recommended actions based on the likely cause and severity of the issue.
  • Review affected users and supporting evidence to better understand the scope and impact of the anomaly.

Insights are refreshed daily and use machine learning to dynamically evaluate what constitutes anomalous behavior, so administrators don’t need to configure thresholds.

The insights use meeting data across the tenant and supported clients and platforms. They do not include meeting telemetry from SIP phones or telemetry from PSTN and peer-to-peer calls.

Action Required/Recommendations

No configuration is required. Once available in your tenant, navigate to Teams admin center > Meetings > Meetings to start reviewing insights. The experience is available to Global Administrators, Teams Administrators, Teams Communications Administrators, Teams Communications Support Engineers, and Teams Communications Support Specialists.

Compliance considerations

This feature uses AI/machine learning to analyze historical meeting-quality data and surface insights to admins; it does not alter how customer data is stored or processed. Review your organization’s data and AI governance policies as appropriate.

What changed

Between the versions this installation saw, newest first

This installation has seen one version of this notice, first on 23 Oct 2026. Later changes will show here.

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • Some history or links were left out of the website export to keep it within its size limits.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 24 Oct 01:01 UTC · 271 of 271 readable · 269 fully read · documentation 464/464 current