04 · Network and QoS
A full-tunnel VPN adds delay and hides the office subnet from emergency location and from CQD.
Microsoft recommends that you avoid real-time media on a VPN. QoS inside the tunnel only prioritizes traffic inside a path that is already longer. Split tunnel is the usual way to let media go direct while other traffic stays on the VPN.
A VPN pool labeled as headquarters will make CQD accuse the wrong building and can make dynamic emergency calling report the wrong place. Treat the VPN range as its own site, or as not a site.
Do not send Teams media through a full-tunnel VPN. Do not call the VPN pool a building.
I keep real-time media off the full-tunnel VPN, and I do not label the VPN pool as HQ.
If it fails: Remote users show high jitter and DSCP 0, and CQD draws them inside headquarters.
Which description of QoS markers enabled is accurate?
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. Mac and mobile hard-code some marks. Windows follows policy. Source: https://learn.microsoft.com/en-us/microsoftteams/qos-in-teams accessed 2026-10-14.
A colleague reports: The network is marked and the clients were never told to mark. Where do you start?
The network is marked and the clients were never told to mark. Turn the insert-markers setting on, then verify at the WAN edge. Source: https://learn.microsoft.com/en-us/microsoftteams/qos-in-teams accessed 2026-10-14.
Which description of Three to five hops is accurate?
Microsoft’s planning note: keep the client-to-network-edge path short, on the order of three to five hops, and the ISP-to-Microsoft edge short as well. Each extra hop is a place a mark can be stripped. Source: https://learn.microsoft.com/en-us/microsoftteams/qos-in-teams accessed 2026-10-14.
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.
Remote users show high jitter and DSCP 0, and CQD draws them inside headquarters.
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.
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.
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.
Copilot Studio, Azure Communication Services, and Graph are later tracks in this lab. Treat any uncited limit as confirm before relying.
Opened 2026-10. A row marked confirm did not open. Wikipedia is background. The Teams blog row is the community index.
