The page Configure Teams Phone in the voice channel says the PSTN connectivity is a Teams Calling Plan, Operator Connect, or Direct Routing.For a Teams Calling Plan, that page says service numbers only are supported.It also lists Enterprise Voice, outbound-calling prerequisites, and a licensing guide.This room does not copy SKU names from the licensing guide.
Synchronization needs the Teams Administrator or Teams Telephony Administrator role, and the delegated Graph permission TeamsResourceAccount.Read.All with admin consent.The page says a Teams resource account is required for every number used with Dynamics 365 Contact Center.Direct Routing uses Set-CsPhoneNumberAssignment with PhoneNumberType DirectRouting, then Grant-CsOnlineVoiceRoutingPolicy.Operator Connect uses PhoneNumberType OperatorConnect.
Teams Phone in this channel allows Calling Plan service numbers, Operator Connect, or Direct Routing.Copy the application ID from the current page.
Signaling for Teams Phone into the voice channel. Teams keeps the dialog. A 488 is codecs, not a greeting.Three options the page names. Not a preference. Counts in this drawing are teaching order, not customers.
Which description of Salesforce Voice is accurate?
The help page Connect Voice from a Partner Contact Center says Salesforce Voice with Telephony Providers, formerly Service Cloud Voice, is now part of Partner Contact Center. That note still names Salesforce Voice with Amazon Connect, Partner Telephony, and Partner Telephony from Amazon Connect. Source: https://help.salesforce.com/s/articleView?id=service.voice_about.htm&language=en_US&type=5 accessed 2026-10-14.
A colleague reports: A runbook still says only Service Cloud Voice and never opens the current title. Where do you start?
A runbook still says only Service Cloud Voice and never opens the current title. Use the learning map on that page. A developer-guide URL did not open from this build, so it is not quoted here. Source: https://help.salesforce.com/s/articleView?id=service.voice_about.htm&language=en_US&type=5 accessed 2026-10-14.
Which description of Partner Contact Center is accurate?
The Salesforce help page titled Connect Voice from a Partner Contact Center says Salesforce Voice with Telephony Providers, formerly Service Cloud Voice, is now part of Partner Contact Center. The same note still names Salesforce Voice with Amazon Connect, Partner Telephony, and Partner Telephony from Amazon Connect, and points to Agentforce Contact Center Voice for built-in telephony. Source: https://help.salesforce.com/s/articleView?id=service.voice_about.htm&language=en_US&type=5 accessed 2026-10-14.
Computer telephony integration Wikipedia’s opened page says computer-telephony integration, also computer–telephone integration or CTI, is a general term for technologies that coordinate interactions between telephones and computers. Config: Use the vendor page for the product you are configuring. Keep Wikipedia as the name only. Fault: A design calls every CRM screen a CTI product.
Dynamics 365 voice channel The voice-channel page says it applies to Dynamics 365 Contact Center embedded, Contact Center standalone, and Customer Service. It provides native PSTN calling in Dynamics and says the channel is built on Azure Communication Services. Config: Read the capabilities table on that page. Do not copy the marketing section above it. Fault: Someone expects the Teams client because the number was bought in Teams.
Teams Phone in the voice channel The configure-Teams-Phone page says PSTN connectivity can be a Teams Calling Plan (service numbers only), Operator Connect, or Direct Routing, and that a Teams resource account is required for every number used with Dynamics 365 Contact Center. Config: Sync from Teams in Copilot Service admin center after the resource account and the number exist. Copy the application ID from the current page. Fault: Sync is run before TeamsResourceAccount.Read.All has admin consent.
Salesforce Voice The help page Connect Voice from a Partner Contact Center says Salesforce Voice with Telephony Providers, formerly Service Cloud Voice, is now part of Partner Contact Center. Config: Use the learning map on that page. A developer-guide URL did not open from this build, so it is not quoted here. Fault: A runbook still says only Service Cloud Voice and never opens the current title.
Sister technologies
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.
Config and troubleshooting
A user Calling Plan number is synced because the service-number limit was skipped.
Cross-platform bridges
CUCM
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.
Webex
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.
UCCE
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.
