How to Inspect Real-Time Call Health and Network Diagnostics in Microsoft Teams

During critical business video conferences or client presentations in Microsoft Teams, experiencing robotic audio, sudden video freezing, or screen share lag can disrupt collaboration. When audio or video quality deteriorates, determining whether the problem originates from local Wi-Fi congestion, ISP packet loss, hardware CPU throttling, or enterprise proxy latency is essential. While administrators have access to delayed post-call telemetry in the Teams Admin Center, individual meeting participants can inspect real-time connection diagnostics directly inside the client using the built-in Call Health panel.

Understanding Call Health Telemetry in Microsoft Teams

Microsoft Teams negotiates audio, video, and screen-sharing media streams using WebRTC and Microsoft’s proprietary real-time media protocols. During an active call, Teams dynamically adjusts media resolution, framerate, and audio codecs (such as Satin, Silk, or Siren) in response to fluctuating network conditions.

The Call Health view queries the local media stack continuously, calculating moving averages of network transport statistics and endpoint performance. This provides immediate, client-side visibility into packet loss percentages, round-trip latency, hardware CPU utilization, and codec selection without waiting for tenant analytics or administrative log collection.

Opening the Call Health Panel During a Meeting

The Call Health panel is accessible during any one-to-one call, group meeting, or channel conference across both the new Microsoft Teams desktop client and the web app on Windows and macOS.

To launch the diagnostic interface:

1. Join or start a meeting in Microsoft Teams.
2. On the meeting control bar at the top of the meeting window, click the More (three dots ...) menu icon.
3. Scroll down and select Call health.
4. A dedicated diagnostic sidebar will open along the right side of the meeting window.

The panel is divided into four distinct diagnostic tabs: Overview, Audio, Video, and Screen Sharing.

Interpreting Network Metrics in the Overview Tab

The Overview tab delivers an instant high-level assessment of overall connection viability. It summarizes critical health indicators:

• Round-Trip Time (RTT): The time in milliseconds required for a network packet to travel from your Teams client to the nearest Microsoft Azure media relay and back. Values below 100 ms provide optimal responsiveness, 100 ms to 200 ms remain acceptable, and values exceeding 250 ms induce noticeable conversational overlap.
• Packet Loss: The percentage of transmitted packets that fail to reach their destination. Teams tolerates up to 2% to 3% packet loss using forward error correction; packet loss exceeding 5% produces audible audio clipping and video frame tearing.
• Jitter: The variance in packet arrival intervals. Jitter should remain below 30 ms to prevent audio buffer underruns.
• CPU Utilization: Displays Teams process CPU consumption versus total system CPU load. High system load (exceeding 85%) suggests background processes are starving Teams media encoders of CPU cycles.

Diagnosing Audio Quality and Codec Performance

Switching to the Audio tab isolates inbound and outbound voice streams. Key metrics include:

• Codec: Indicates the active speech compression algorithm. Microsoft’s modern Satin codec operates at ultra-low bitrates (as low as 6 kbps) with resilient error concealment, while Silk or Opus may be selected under high-bandwidth conditions.
• Send and Receive Bitrate: Typical voice streams occupy between 24 kbps and 48 kbps. A drop below 10 kbps indicates aggressive bandwidth throttling.
• Packet Rate: The frequency of voice packets sent per second (normally 50 packets per second).

If the Audio tab reports elevated packet loss while RTT remains low, the issue is typically local Wi-Fi interference or an over-subscribed home router rather than remote internet path congestion.

Auditing Video Streams and Frame Degradation

In the Video tab, Teams reveals the technical parameters of active camera streams. When network bandwidth drops, Teams prioritizes audio clarity by systematically degrading video resolution and framerate.

Inspect the following parameters:

• Resolution: Shows active capture resolution (such as 1920×1080, 1280×720, or downscaled 640×360).
• Framerate: Measures transmitted frames per second (fps). Fluid video targets 30 fps; under congested conditions, Teams may drop to 15 fps or 7 fps.
• Video Bitrate: HD video streams require 1,500 kbps to 2,500 kbps. If the available bitrate falls below 500 kbps, video feeds become blurry or pixelated.

If the sent resolution drops despite ample local bandwidth, check system CPU load—Teams automatically throttles outbound camera encoding when hardware temperatures spike or CPU cores are maxed out.

Troubleshooting Screen Sharing and Presentation Latency

Screen sharing uses a distinct transport profile that favors text sharpness and static image clarity over high framerates.

The Screen Sharing tab details:

• Sharing Mode: Indicates whether content is optimized for “Text and detail” (high resolution, lower framerate) or “Video and animation” (up to 30 fps for smooth motion).
• Capture Resolution: The resolution at which your desktop or window is being sampled.
• Sent Framerate: Static slides typically send at 1 to 5 fps to conserve bandwidth, scaling up to 24+ fps when scrolling or playing embedded media.

Actionable Steps Based on Call Health Findings

When Call Health exposes performance anomalies, take immediate remediation steps:

• High Packet Loss / Jitter: Switch from 2.4 GHz Wi-Fi to 5 GHz, or connect an Ethernet cable directly to your router. Disconnect active VPN tunnels that bypass Microsoft 365 optimized network endpoints.
• Elevated CPU Usage: Close resource-heavy browser tabs or compilation tasks. In Teams Settings, enable hardware graphics acceleration.
• Severe Bandwidth Constraints: Disable incoming video feeds via meeting settings to reserve all bandwidth for audio and essential screen shares.

Using the Call Health panel transforms subjective meeting complaints into objective technical data, allowing you to troubleshoot audio-video problems immediately.