Microsoft Teams Internet Speed Requirements

Teams bandwidth by call type

Microsoft publishes specific bandwidth figures for each Teams media mode. Real-world usage varies with network conditions, but these are the authoritative minimums:

For a group meeting with 5 participants all sending 1080p video, your download requirement is approximately 5 × 2 Mbps = 10 Mbps. Add screen sharing and the number rises further. Use these figures to calculate your actual meeting scenario rather than relying on generic rules of thumb.

Teams adaptive quality

Teams uses an adaptive bitrate algorithm that continuously monitors network conditions and degrades gracefully when bandwidth or quality drops. The degradation order is designed to preserve the most critical media first: Teams will reduce video resolution and frame rate before dropping video entirely, and it will drop video entirely before degrading audio. If your connection deteriorates mid-call, you may notice video becoming blurry or pixelated before it freezes — this is Teams deliberately trading visual quality for connection stability. Audio typically remains clear until packet loss exceeds 5–8% or jitter exceeds 30 ms consistently.

Teams Network Assessment Tool

Microsoft provides a free Teams Network Assessment Tool (downloadable from Microsoft's documentation site) that tests your network's readiness for Teams media traffic. It sends test UDP packets to Teams media relay servers and measures packet loss, jitter, and round-trip latency over a 5-minute window. Microsoft's recommended thresholds for good call quality: packet loss below 1%, jitter below 15 ms, round-trip latency below 100 ms. Results outside these thresholds indicate network conditions that will cause perceptible call quality issues. Run the tool from the device and network location you actually use for calls, at the time of day you normally have meetings.

DSCP marking and QoS

Teams marks its media traffic with DSCP (Differentiated Services Code Point) values to enable quality-of-service prioritization on enterprise networks. Audio traffic uses DSCP 46 (Expedited Forwarding / EF), which network equipment treats as the highest-priority traffic class. Video traffic uses DSCP 34 (AF41). Screen sharing uses DSCP 18 (AF21). On a home router, DSCP marking has no effect unless the router is configured to honor DSCP values in its QoS rules — most consumer routers ignore DSCP by default. On a corporate LAN or managed Wi-Fi with QoS configured, Teams audio and video packets automatically receive preferential queuing over background traffic like file downloads and cloud sync.

VPN and Teams: why split tunneling matters

Routing Teams media traffic through a corporate VPN adds significant latency and jitter — media packets travel from your device to the VPN server, through the corporate network, then out to the Teams media relay, doubling or tripling the path length. Microsoft explicitly recommends split tunneling for Teams: configure the VPN client to send Teams media traffic directly to the internet while routing other corporate traffic (file shares, internal apps, email) through the VPN tunnel. The specific IP ranges and ports for Teams media relays are published by Microsoft and can be added to most enterprise VPN clients as split tunnel exclusions. Teams signaling (call setup, presence, chat) can safely go through the VPN; only media packets need to bypass it.

Teams Call Quality Dashboard

Teams administrators have access to the Call Quality Dashboard (CQD) in the Teams Admin Center. CQD aggregates call quality data across all users in a tenant and provides reports on poor call rates, packet loss percentages, jitter, and latency broken down by location, device type, network, and time period. For home workers experiencing persistent Teams quality issues, asking your IT admin to check CQD data for your account can quickly reveal whether the problem is network-side (consistent packet loss from your location) or device-side (audio driver issues, CPU throttling during calls).

Wi-Fi vs wired for Teams calls

Wired Ethernet eliminates the most common source of Teams call degradation: Wi-Fi jitter and intermittent packet loss. A Gigabit Ethernet connection adds essentially zero jitter and virtually no packet loss from the local network side. Wi-Fi — even excellent Wi-Fi — introduces variable latency as the protocol handles channel contention, retransmissions, and roaming between access points. For important calls, Ethernet is the single highest-impact change you can make. If running a cable is impractical, a powerline adapter or MoCA adapter provides a wired connection through existing electrical or coaxial wiring with substantially better jitter characteristics than Wi-Fi.

Teams Quality Planning Table

Frequently Asked Questions

What internet speed is recommended for Microsoft Teams?

A practical baseline is 10 Mbps down and 5 Mbps up per active user, with consistent low jitter and packet loss.

Why is Teams audio choppy on fast internet?

Because jitter and loss affect audio quality more than raw download speed.

Does Wi-Fi quality matter more than plan speed for Teams?

In many cases yes, especially when the device is far from the router or on a congested channel.

Should I use QoS for Microsoft Teams?

QoS is often helpful when many users share one connection and real-time calls must stay stable.

How do I test Teams readiness before important calls?

Run repeated tests during your real meeting window and verify latency stability from your actual call setup.