01 · Foundations
Voice objects are split across the Teams admin center, the Microsoft 365 admin center, and PowerShell. Hunting in one pane wastes the outage.
Numbers, voice routing, attendants, and queues are Teams admin center work, with PowerShell beside them. Licenses, including the Teams Phone Resource Account license, are assigned in the Microsoft 365 admin center. Emergency addresses and network topology sit with the voice configuration, not with a random SharePoint site.
When the portal and the shell disagree, read the user with Get-CsOnlineUser. The effective policy is the one that was actually granted, including grants that came from a group.
Assign licenses in the Microsoft 365 admin center. Read the effective voice policy from PowerShell before you celebrate.
Licenses in one center, voice objects in the other, effective policy from the shell.
If it fails: The portal toast says success and the user still has the old policy.
A colleague reports: PSTN fails only for the Islands users and nowhere else. Where do you start?
PSTN fails only for the Islands users and nowhere else. Move the user to a supported mode before you test PSTN. Source: https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan accessed 2026-10-14.
Which description of Entra ID is accurate?
The identity directory for the tenant. Teams users, resource accounts, and admin roles are Entra objects. Voice licenses attach to these objects. Source: https://learn.microsoft.com/en-us/microsoftteams/using-admin-roles accessed 2026-10-14.
A colleague reports: A resource account exists in Teams and has no license because nobody looked in Entra. Where do you start?
A resource account exists in Teams and has no license because nobody looked in Entra. Create the user or resource account here, then license it, then grant policies. Source: https://learn.microsoft.com/en-us/microsoftteams/using-admin-roles 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 portal toast says success and the user still has the old policy.
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.
