09 · Devices and media
A room account with a user license and a strict Conditional Access policy is a dark screen at the start of a meeting.
Rooms use the current Teams Rooms license. Do not borrow a user Calling Plan and hope. The room resource account must be allowed to sign in as a device. Conditional Access that assumes an interactive user will lock it out.
QoS for Teams Rooms is documented separately for Windows and Android. Include the room in the same DSCP plan as the PCs, and test a call from the room, not only from a laptop.
License Teams Rooms with the current room SKU and let the device sign in.
Rooms get a room license and a Conditional Access exception you can explain.
If it fails: The room has a user E5 stack and still cannot sign in.
A colleague reports: Bypass is on for a VPN user and audio is worse than the processor path. Where do you start?
Bypass is on for a VPN user and audio is worse than the processor path. Enable it on the gateway only when the client can reach the SBC and LBR does not forbid the path. Source: https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan accessed 2026-10-14.
Which description of Local media optimization is accurate?
A Direct Routing pattern with internal and external SBC interfaces so a branch user stays on the local media path. It is more specific than a single bypass flag. Source: https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan accessed 2026-10-14.
A colleague reports: Internal users hairpin out to the internet and back to the SBC on the same LAN. Where do you start?
Internal users hairpin out to the internet and back to the SBC on the same LAN. Use the current media optimization article and the SBC vendor’s build. Source: https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan 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.
The room has a user E5 stack and still cannot sign in.
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.
