Source record · tier 2 current vendor documentation

Implement Quality of Service in Microsoft Teams

Publisher: Microsoft
URL: https://learn.microsoft.com/en-us/microsoftteams/qos-in-teams
Published: 2024-04-12
Updated: unknown
Accessed: 2026-09-24
HTTP status: 200
License: Microsoft Learn terms of use (not separately verified); no-redistribution; short excerpts and locators only

Source notes citing this source

Microsoft's recommended initial Teams QoS settings mark audio from client source ports 50000-50019 with DSCP 46 (EF). Video uses 50020-50039 with DSCP 34 (AF41), and screen sharing uses 50040-50059 with DSCP 18 (AF21). in context
Teams Mac, iOS and Android clients use hard-coded DSCP values (EF for audio, AF41 for video and screen sharing), but QoS marking still requires the 'Insert Quality of Service (QoS) markers for real-time media traffic' setting to be enabled in the Teams admin center. in context
Microsoft describes the effects of missing QoS as follows: jitter causes missing words or syllables, packet loss lowers voice quality and makes speech hard to understand, and long round-trip time makes people talk over each other. in context
Microsoft notes that port-based DSCP tagging with router ACLs works across Windows, Mac and Linux, but marks traffic only at the WAN edge, not all the way to the client. It recommends combining client DSCP marking with port-based ACLs. in context
Microsoft says QoS should be implemented on all segments of a managed network, and that any part of the path that fails to support the QoS priorities can degrade call quality. in context
To validate Teams QoS, Microsoft says to capture traffic, preferably at the network egress point using port mirroring, and confirm that the DSCP value is not changed or stripped as the traffic crosses the network. The marking must be present at both ends of the call. in context
Microsoft notes that QoS works as expected only when implemented on all links between callers. For a remote user, QoS can be prioritized only within the internal managed network, and a VPN adds packet overhead and delay to real-time traffic. in context
Microsoft's Teams QoS guidance recommends three to five hops from client to network edge and three hops from the ISP to the Microsoft network edge. in context
Microsoft's recommended starting QoS configuration for Teams audio is client source ports 50000-50019 marked DSCP 46 (EF). in context
Microsoft says Teams QoS works as expected only when it is applied on every link between callers, so for remote users traffic can be prioritized only within the internal managed network. in context
Microsoft's recommended starting QoS configuration for Teams is video on 50020-50039 at DSCP 34 (AF41) and screen sharing on 50040-50059 at DSCP 18 (AF21). in context
Teams QoS marking requires the 'Insert Quality of Service (QoS) markers for real-time media traffic' setting to be enabled globally in the Teams admin center, including for the Mac, mobile and Teams Phone clients that use hard-coded markings. in context
Microsoft recommends an initial Teams audio client source port range of 50000-50019 (TCP/UDP), marked DSCP 46 (EF). in context
Microsoft recommends combining client-side DSCP marking with port-based ACL tagging on routers, so that devices unable to mark are still classified. in context
Microsoft's Teams QoS checklist runs in this order: confirm network readiness; select an implementation method; choose port ranges per media type; implement settings on clients, routers and media traffic; validate by analyzing traffic; manage source ports. in context
In Teams, administrators can adjust the media port ranges but cannot configure the DSCP markings. in context
Teams Mac, iOS and Android clients use hard-coded markings that cannot be configured: EF for audio and AF41 for both video and application/screen sharing. in context
Microsoft says port-based tagging at the router works across platforms but marks traffic only at the WAN edge, not all the way to the client machine. in context
Microsoft recommends an initial Teams application and screen sharing client source port range of 50040-50059, marked DSCP 18 (AF21). in context
Teams calling and meetings signaling uses UDP source ports 50070-50089 marked DSCP 40 (CS5). Those ports are not currently configurable. in context
Microsoft says the DSCP value must be present at both ends of a call, and advises capturing traffic, preferably at the network egress point, to check that the marking is not changed or stripped. in context
Microsoft recommends an initial Teams video client source port range of 50020-50039, marked DSCP 34 (AF41). in context
Microsoft states that QoS works as expected only on links where it is implemented. For remote users it can prioritize traffic only within the managed network, and Microsoft recommends avoiding real-time traffic over VPN. in context
Because vendor QoS guidance applies only to managed links, DSCP markings from Teams or Webex clients give no guaranteed priority on a home user's consumer broadband or ISP path. inferred in context
Microsoft's recommended initial Teams QoS setting for audio is client source ports 50000-50019 (TCP/UDP) marked DSCP 46 (Expedited Forwarding). in context
Microsoft notes that a VPN can give remote locations a managed connection but adds packet overhead and delay to real-time traffic, and recommends against running real-time communications over a VPN. in context
Teams QoS works as expected only when it is implemented on every link between callers; when a user signs in remotely, traffic can be prioritised only within the organisation's own managed network. in context
Mac, iOS and Android Teams clients use fixed, non-configurable DSCP values, but QoS marking must still be turned on globally in the Teams admin center ('Insert Quality of Service (QoS) markers for real-time media traffic'). in context

Cite this source record

APA

WarmTransfer. (2024, April 12). Implement Quality of Service in Microsoft Teams. WarmTransfer. https://warmtransfer.net/knowledge/sources/ms-learn-qos-in-teams

BibTeX

@misc{warmtransfer-ms-learn-qos-in-teams,
  title  = {Implement Quality of Service in Microsoft Teams},
  author = {{WarmTransfer}},
  year   = {2024},
  url    = {https://warmtransfer.net/knowledge/sources/ms-learn-qos-in-teams},
  note   = {Microsoft, accessed 2026-09-24}
}