06 · Routing and dial plans
A branch that dials differently needs its own plan. Editing the global plan does not change a user who has a more specific one.
Tenant dial plans hold the rules. Grant the plan to the users it describes. A user with a specific plan will not pick up your edit to the global plan.
Keep rules anchored. A pattern without an end anchor will match a prefix of a longer number and translate the wrong thing. The lab on this campus is a teaching matcher with the same first-match idea, not the Microsoft service.
Grant a dial plan to the user who needs it. First match wins, so emergency and specific rules go first.
Specific rules first, grant the plan to the user, test as that user.
If it fails: You edit Global and the branch plan still has the old rule.
A colleague reports: You edit the global plan and a branch with its own plan does not change. Where do you start?
You edit the global plan and a branch with its own plan does not change. Grant the plan to the user and test from that user. Source: https://learn.microsoft.com/en-us/microsoftteams/create-and-manage-dial-plans accessed 2026-10-14.
Which description of PSTN usage is accurate?
A name that links a voice routing policy to one or more voice routes. The policy’s ordered list of usages is the permission to place those calls. Usages are how you let one site call internationally and another not. Source: https://learn.microsoft.com/en-us/microsoftteams/manage-voice-routing-policies accessed 2026-10-14.
A colleague reports: International works because the international usage was left on a branch policy. Where do you start?
International works because the international usage was left on a branch policy. Create the usage, attach routes, then put the usage on the policy in the right order. Source: https://learn.microsoft.com/en-us/microsoftteams/manage-voice-routing-policies 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.
You edit Global and the branch plan still has the old rule.
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.
