04 · Network and QoS

ExpressRoute is not the requirement

A private circuit is a purchasing choice. It is not the Teams network requirement.

Room HTMLAll downloads

Learn it in 5 minutes

Teams is designed to work over the internet with local egress. If your organization also has ExpressRoute, follow the current network documentation for which traffic belongs there. Do not assume media is automatically better on the private path.

QoS still has to be consistent on whatever path you chose. A private path with no marks and extra distance is a slower best-effort network.

Do not buy ExpressRoute to make Teams legal. Design the path, then mark it.

Room HTML

Visual

Dynamics unified routingWorkstreamClassificationVoicecap 2Chatcap 1Emailcap 0
Language, intent, and capacity for ExpressRoute is not the requirement. Overflow is a rule.
Decision, not a defaultInternet egress · UsualPrivate path · Only with a reason
Both can be valid. The article does not require ExpressRoute. Counts in this drawing are teaching order, not customers.

SVGPNGHTML

Worked example

Teams does not require ExpressRoute. Local internet egress is the normal plan.

  1. Choose Internet or private
  2. Egress Local if you can
  3. Mark Same DSCP story
  4. Measure RTT and loss

If it fails: Media is forced onto a long private path and delay gets worse.

Checklist HTML

Quiz

A colleague reports: The link was sized for silence and the all-hands call filled it. Where do you start?

Which description of Packetization 20 ms is accurate?

A colleague reports: One SBC uses 10 ms and the policer drops packets. Where do you start?

Flashcards

Ecosystem

Glossary

  • Shortest media path Microsoft’s network guidance prefers a short path to the Microsoft network, without a proxy in the media path. Config: Egress Teams media locally. Do not hairpin a branch through a distant data center unless you mean to. Fault: One city’s CQD is poor and the firewall team finds a proxy.
  • VPN and real-time media Microsoft recommends that you avoid sending real-time Teams media through a VPN. QoS on the VPN does not fix the extra delay. Config: Test a call on the VPN and off it before you blame the carrier. Fault: Every remote user shows high RTT and the office does not.
  • ExpressRoute is optional Teams does not require ExpressRoute. Local internet egress is the usual design. If you do use ExpressRoute, follow the current network article rather than assuming media is happier there. Config: Decide the path, then mark DSCP on the path you actually use. Fault: Media was forced onto a long private path and RTT jumped.
  • QoS markers enabled The Teams admin center setting that allows clients to insert DSCP. Without it, a correct ACL still sees unmarked client traffic from managed endpoints that honor the policy. Config: Turn the insert-markers setting on, then verify at the WAN edge. Fault: The network is marked and the clients were never told to mark.

Sister technologies

Around the call: compliance recording, workforce management, emergency location, analytics, CRM screen pop, and an agent with a human escape. Each one has its own failure.

Config and troubleshooting

Media is forced onto a long private path and delay gets worse.

Cross-platform bridges

CUCM

Cisco CUBE is one of the SBC families named in this lab’s certification lesson. A certified release can be the Direct Routing SBC between Unified CM and Teams.

The tenant still needs a verified domain on the SBC FQDN, and the user still needs Teams Phone. The studio translator does not open a live AXL session. Confirm the current certified release before you build.

Webex

Teams Phone and Webex Calling are separate clouds. This lab does not describe a feature that registers a Webex Calling user into a Teams tenant.

A number move is usually a carrier port, a certified SBC, or a meetings interop product. Confirm before relying.

UCCE

Unified CCE stays the ACD until you migrate it. Microsoft’s contact-center articles name Connect, Extend, and Unify. They do not name a UCCE connector in the notes this lab cites.

Voice into Teams is still Direct Routing or Operator Connect. The routing script stays on the contact-center product you bought. Confirm the vendor’s current model. Source: https://learn.microsoft.com/en-us/microsoftteams/teams-contact-center.

Future hooks

Copilot Studio, Azure Communication Services, and Graph are later tracks in this lab. Treat any uncited limit as confirm before relying.

BridgesEcosystem

Sources and go deeper

Opened 2026-10. A row marked confirm did not open. Wikipedia is background. The Teams blog row is the community index.

sources.json