Migrate to Direct Routing
This article describes what is needed to migrate to Direct Routing from a Skype for Business Online and Microsoft Teams configuration perspective. This article covers migrating from the following:
- Teams Phone with Calling Plans (for Teams and Skype for Business Online)
- Teams Phone with on-premises PSTN Connectivity in Skype for Business Server (for Skype for Business Online)
- Teams Phone with on-premises PSTN Connectivity by using the Cloud Connector Edition (for Skype for Business Online)
In addition to these configuration steps, configuration is also required on the Session Border Controller (SBC) to route the calls to the new route. That is outside the scope of this document. For more information, see your SBC vendor documentation.
User provisioning end-state for various PSTN connectivity options
The following table shows the end-state for a user provisioned for the selected PSTN connectivity options with Teams Phone. Only attributes relevant for voice are shown.
| User object attributes | Teams Phone with Calling Plans | Teams Phone with on-premises PSTN connectivity via Skype for Business Server | Teams Phone with on-premises PSTN connectivity via Cloud Connector | Teams Phone with on-premises PSTN connectivity via Direct Routing |
|---|---|---|---|---|
| Client | Skype for Business or Teams | Skype for Business | Skype for Business | Teams |
| Licenses | Skype Business Online Plan 2 (MCOProfessional or MCOSTANDARD) Teams Phone (MCOEV) Calling Plans Teams |
Skype Business Online Plan 2 (MCOProfessional or MCOSTANDARD) Teams Phone (MCOEV) |
Skype Business Online Plan 2 (MCOProfessional or MCOSTANDARD) Teams Phone (MCOEV) |
Skype Business Online Plan 2 (MCOProfessional or MCOSTANDARD) Teams Phone (MCOEV) Teams |
| OnPremLineURI | N/A | The phone number must be synced from the on-premises AD. | The phone number can be managed either in on-premises Active Directory or in Microsoft Entra ID. | The phone number can be managed either in on-premises Active Directory or in Microsoft Entra ID. However, if the organization has on-premises Skype for Business, the number must be synced from the on-premises Active Directory. |
| LineURI | PSTN Calling phone number | Set automatically from the OnPremLineURI parameter | Set automatically from the OnPremLineURI parameter | Set automatically from the OnPremLineURI parameter |
| EnterpriseVoiceEnabled | True | True | True | True |
| HostedVoiceMail | True | True | True | True |
| VoicePolicy | BusinessVoice | HybridVoice | HybridVoice | HybridVoice |
| HostedVoiceMailPolicy | BusinessVoice | BusinessVoice | BusinessVoice | BusinessVoice |
| VoiceRoutingPolicy | Has a value | Has a value | Has a value | N/A |
| OnlineVoiceRoutingPolicy | $Null | $Null | $Null | Has a value |
| TeamsUpgradePolicy1 | TeamsOnly, SfBOnly | $Null | $Null | TeamsOnly |
| TeamsCallingPolicy AllowPrivateCalling |
True | N/A | N/A | True |
| TeamsCallingPolicy AllowGroupCalling |
True | N/A | N/A | True |
1 Choosing the right mode of the TeamsUpgradePolicy depends on the scenario. Please read about the voice experience in different modes in Migration and interoperability Guidance for organizations using Teams together with Skype for Business.
As part of this effort, Microsoft recently updated the “Microsoft Teams admin center” (also known as Modern Portal) to reflect the new management model based on coexistence modes. In Modern Portal, configuring TeamsUpgradePolicy will now automatically also set TeamsInteropPolicy to consistent value, so TeamsInteropPolicy is no longer exposed in the user interface. However, admins using PowerShell must still set both TeamsUpgradePolicy and TeamsInteropPolicy together to ensure proper routing. After the transition to TeamsUpgradePolicy is complete, it will no longer be necessary to also set TeamsInteropPolicy.
For more information, please refer to Migration and interoperability Guidance for organizations using Teams together with Skype for Business.
Migrating from Calling Plans
For more information about migrating from Calling Plans, see:
It's recommended that you remove previously configured licensing plan information as follows:
$companyname = “contoso”
$lic1 = $companyname + “:MCOPSTN1”
$lic2 = $companyname + “:MCOPSTN2”
Set-MgUserLicense -UserId '11111111-0000-aaaa-bbbb-222222222222' -RemoveLicenses @($lic1)
Set-MgUserLicense -UserId '11111111-0000-aaaa-bbbb-222222222222' -RemoveLicenses @($lic2)
Migrating from Office 365 Teams Phone with on-premises PSTN connectivity in Skype for Business Server
For more information about migrating from Teams Phone with on-premises PSTN connectivity in Skype for Business Server, see the following:
It's recommended that you remove previously configured voice routing information as follows:
Grant-CsVoiceRoutingPolicy -PolicyName $NULL -Identity <UPN>
Note
If a global CsVoiceRoutingPolicy is configured, it's recommended that you remove any PSTN usages associated with this global policy.
Migrating from Office 365 Teams Phone with on-premises PSTN connectivity via Cloud Connector Edition
Important
Cloud Connector Edition will retire July 31, 2021 along with Skype for Business Online. Once your organization has upgraded to Teams, learn how to connect your on-premises telephony network to Teams using Direct Routing.
For more information about migrating from Teams Phone with on-premises PSTN connectivity via Cloud Connector, see the following:
It's recommended that you remove previously configured voice routing information as follows:
Grant-CsVoiceRoutingPolicy -PolicyName $NULL -Identity <UPN>
Set-CsUserPstnSettings -Identity <UPN> -AllowInternationalCalls $false -HybridPSTNSite $null