02 · Licensing
Interviews and design reviews both ask for the set, not a brand name.
Walk the picker in this order: does the person need PSTN, who is the carrier, do meetings need a dial-in number, is there a room, is there a voice app, does that app dial out. Audio Conferencing is the meeting dial-in. It is not implied by Teams Phone.
End with the sentence that Teams Premium changed none of those answers. Then cite the licensing page, because bundles move, and this campus was checked on 14 October 2026.
Defend a license set by separating the phone system, the carrier, meeting dial-in, and the resource account.
I separate Teams Phone, the carrier, Audio Conferencing, the resource account, and Premium.
If it fails: One SKU is expected to cover users, rooms, queues, and meeting dial-in.
A colleague reports: Every user was left numberless and the resource account was never funded. Where do you start?
Every user was left numberless and the resource account was never funded. Read the current shared-calling prerequisites before you promise it to a site. Source: https://learn.microsoft.com/en-us/microsoftteams/teams-phone-licensing accessed 2026-10-14.
Which description of Common area phone is accurate?
A shared handset. On Direct Routing it does not need a Calling Plan license. People copy a user bundle onto a hallway phone. Source: https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan accessed 2026-10-14.
A colleague reports: A Calling Plan was purchased for every corridor phone on a Direct Routing design. Where do you start?
A Calling Plan was purchased for every corridor phone on a Direct Routing design. License the device for Teams and the phone scenario you chose, then assign the number. 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.
One SKU is expected to cover users, rooms, queues, and meeting dial-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.
