05 · PSTN connectivity
The connectivity option decides who operates the carrier, who you call at 2 a.m., and which license you buy.
The four options on the connectivity page are Calling Plans, Operator Connect, Teams Phone Mobile, and Direct Routing. Microsoft is the carrier only for Calling Plans. The others use a partner or your SBC. One tenant may use all four for different people.
Operator Connect for India is its own plan because the regulatory problem is different. Do not hide an India office inside a UK SBC and call it Operator Connect.
Calling Plans, Operator Connect, Teams Phone Mobile, and Direct Routing can share a tenant. They cannot share one careless route.
Four options. Microsoft is the carrier only for Calling Plans. Mixing them in one tenant is allowed.
If it fails: One global route assumes every user has the same carrier.
Which description of Operator Connect is accurate?
A certified carrier manages PSTN for you inside the tenant. You need Teams Phone. You do not need a Microsoft Calling Plan or your own SBC. It is the low-operations option when your carrier is in the program. Source: https://learn.microsoft.com/en-us/microsoftteams/operator-connect-plan accessed 2026-10-14.
A colleague reports: Someone also builds a Direct Routing SBC for the same numbers and the routes fight. Where do you start?
Someone also builds a Direct Routing SBC for the same numbers and the routes fight. Enable the operator in the admin center and assign the numbers they provide. Source: https://learn.microsoft.com/en-us/microsoftteams/operator-connect-plan accessed 2026-10-14.
Which description of Operator Connect for India is accurate?
The India-specific operator model. It exists because India PSTN rules are not the same as a generic Operator Connect deployment. A global design that ignores it will fail a regulatory review. Source: https://learn.microsoft.com/en-us/microsoftteams/operator-connect-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 global route assumes every user has the same carrier.
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.
