Plan your Teams voice solution
This article helps you decide which Microsoft voice solution is right for your organization. After you've decided, the article provides a roadmap to content that will enable you to implement your chosen solution.
You might want the simplest solution—Phone System with Calling Plan. This option is Microsoft's all-in-the-cloud solution that provides Private Branch Exchange (PBX) functionality and calls to the Public Switched Telephone Network (PSTN), as shown in the following diagram. With this solution, Microsoft is your PSTN carrier.
If you answer yes to the following, then Phone System with Calling Plan is the right solution for you:
- Calling Plan is available in your region.
- You don't need to retain your current PSTN carrier.
- You want to use Microsoft-managed access to the PSTN.
However, your situation might be more complex. For example, you might have offices in locations where Calling Plan isn't available. Or you might need a combination solution that supports a complex, multi-national deployment, with different requirements for different geographic locations. Microsoft supports a combination of solutions:
- Phone System with Calling Plan
- Phone System with your own PSTN carrier with Operator Connect
- Phone System with your own PSTN carrier with Direct Routing
- A combination solution that uses Phone System with Calling Plan, Phone System with Operator Connect, and/or Phone System with Direct Routing
If you’re a small to medium business (300 or fewer people), Microsoft now bundles Phone System with a Domestic Calling Plan. For more information, see Phone System guidance for small and medium businesses to help you plan, set up, and manage your voice solution.
What do you need to read?
Required for all. Some of the sections in this article pertain to all organizations. For example, everyone should read about Phone System and understand the options for connecting to the Public Switched Telephone Network (PSTN).
|Required for all||Description|
|Phone System||Microsoft's technology for enabling call control and Private Branch Exchange (PBX) capabilities in the Microsoft 365 cloud with Microsoft Teams.|
|Public Switched Telephone Network (PSTN) connectivity options||Choose Microsoft as your telephony carrier or connect your own telephony carrier to Microsoft Teams by using Operator Connect or Direct Routing. Combined with Phone System, PSTN connectivity options enable your users to make phone calls all over the world.|
Depending on your requirements. Some of the sections in this and related articles are pertinent depending on your existing deployment and requirements. For example, Location-Based Routing is only required for Direct Routing customers in geographic locations that do not allow toll bypass.
Consider which of these other configurations you might need:
|Depending on your requirements||Description|
|Phone number management||How to get and manage phone numbers differs depending on your PSTN connectivity option. Read this section if you need to obtain phone numbers, transfer existing numbers, obtain service numbers, and so on.|
|Call routing and dial plans||How to configure and manage dial plans that translate dialed phone numbers into an alternate format (typically E.164 format) for call authorization and call routing. Read this section if you need to understand what dial plans are and whether you need to specify dial plans for your organization.|
|Emergency calling||How to manage and configure emergency calling differs depending on your PSTN connectivity option. Read this section if you need to understand how to manage emergency calling for your organization.|
|Location-Based Routing for Direct Routing||How to use Location-Based Routing (LBR) to restrict toll bypass for Microsoft Teams users based on their geographic location. Read this section if your organization is using Direct Routing at a location that doesn't allow toll bypass.|
|Network topology for cloud voice features||If your organization is deploying Location-Based Routing (LBR) for Direct Routing or dynamic emergency calling, you must configure network settings for these features in Microsoft Teams. Read this section if you're implementing LBR for Direct Routing, or if you're implementing dynamic emergency calling with Calling Plan or Direct Routing.|
|Migrate your existing voice solution||What you need to think about when migrating your voice solution to Teams. Read this section if you're migrating from an existing voice solution to Teams.|
This article focuses on voice solutions with Microsoft Teams. Due to the retirement of Skype for Business Online on July 31, 2021, PSTN connectivity between your on-premises environment—whether through Skype for Business Server or Cloud Connector Edition—and Skype for Business Online is no longer supported. This article introduces Teams voice solutions and how you can connect your on-premises telephony network, if necessary, to Teams by using Operator Connect or Direct Routing.
Phone System is Microsoft's technology for enabling call control and Private Branch Exchange (PBX) capabilities in the Microsoft 365 cloud with Microsoft Teams.
Phone System works with Teams clients and certified devices. Phone System allows you to replace your existing PBX system with a set of features directly delivered from Microsoft 365.
Calls between users in your organization--regardless of geographical area--are handled internally within Phone System. These internal calls never go to the Public Switched Telephone Network (PSTN), so your company avoids long-distance charges.
This article introduces the following Phone System key features and functionality, and the deployment decisions you'll need to consider:
For information about all Phone System features, and how to set up Phone System, see the following articles:
- Here's what you get with Phone System
- Set up Phone System in your organization
Describes how to buy and assign Phone System licenses, manage phone numbers, and set up communication credits for toll-free numbers.
Auto attendants and Call queues
Auto attendants allow you to set up menu options to route calls based on caller input. Call queues are waiting areas for callers. Used together, auto attendants and call queues can easily route callers to the appropriate person or department in your organization.
For information about auto attendants and call queues, see the following articles:
- Plan for Teams auto attendants and call queues
- Set up an auto attendant
- Create a call queue
- Contoso case study: Auto attendants and call queues
Describes how a fictional multi-national corporation, Contoso, implemented auto attendants and call queues for their voice solution.
Cloud Voicemail, powered by Azure Voicemail services, supports voicemail deposits to Exchange mailboxes only. It doesn't support third-party email systems.
Cloud Voicemail includes voicemail transcription, which is enabled for all users in your organization by default. Your business needs might require that you disable voicemail transcription for specific users or everyone throughout the organization.
Cloud Voicemail is automatically set up and provisioned for Teams users.
For more information about Cloud Voicemail and its configuration, see the following articles:
By default, all outbound calls use the assigned phone number as calling identity (caller ID). The recipient of the call can quickly identify the caller and decide whether to accept or reject the call. For information about configuring caller ID or to change or block the caller ID, see Set the caller ID for a user.
Public Switched Telephone Network connectivity options
Phone System provides complete PBX capabilities for your organization. However, to enable users to make calls outside your organization, you need to connect Phone System to the Public Switched Telephone Network (PSTN). To connect Phone System to the PSTN, you can choose one of the following options:
Phone System with Calling Plan. An all-in-the-cloud solution with Microsoft as your PSTN carrier.
Phone System with your own PSTN carrier by using Operator Connect. With Operator Connect, if your existing operator is a participates in the Microsoft Operator Connect program, they can manage the service for bringing PSTN calling to Teams. For information on the benefits and requirements of Operator Connect, see Plan Operator Connect.
Phone System with your own PSTN carrier by using Direct Routing to connect your on-premises environment to Teams.
You can choose a combination of options, which enables you to design a solution for a complex environment, or manage a multi-step migration. You'll read more about migration later.
Most Phone System features are the same regardless of the PSTN connectivity option you choose. There are some differences in functionality, however, that affect how you configure certain Phone System features, such as call routing and emergency calling. For more information about PSTN connectivity options and configuration considerations, see PSTN connectivity options.
Migrate your existing voice solution to Teams
For guidance on planning a Teams voice solution as part as your overall plan to upgrade to Teams from Skype for Business Server, see PSTN considerations for upgrading to Teams from Skype for Business on-premises.
For an organization that is upgrading to Teams, the ultimate goal is to move all users to TeamsOnly mode. Using Phone System is only supported when the user is in TeamsOnly mode. If you need basic information about upgrading to Teams, start here:
- Getting started with your Microsoft Teams upgrade
- About the upgrade framework
- Upgrade strategies for IT administrators
When migrating your voice solution, there are four possible calling scenarios when moving to TeamsOnly mode:
A user in Skype for Business Online, with a Microsoft Calling Plan. Upon upgrade, this user will continue to have a Microsoft Calling Plan.
A user in Skype for Business Online, with on-premises voice functionality through Skype for Business on-premises or Cloud Connector Edition. The user’s upgrade to Teams needs to be coordinated with migration of the user to Direct Routing to ensure the TeamsOnly user has PSTN functionality.
A user in Skype for Business on-premises with Enterprise Voice, who will be moving to online and keeping on-premises PSTN connectivity. Migrating this user to Teams requires moving the user’s on-premises Skype for Business account to the cloud, and coordinating that move with migration of the user to Direct Routing.
A user in Skype for Business on-premises with Enterprise Voice, who will be moving to online and using a Microsoft Calling plan. Migrating this user to Teams requires moving the user’s on-premises Skype for Business account to the cloud, and coordinating that move with either A) the port of that user’s phone number to a Microsoft Calling Plan or B) assigning a new subscriber number from available regions.
For more information about how to implement your voice migration for each of these scenarios, see the following articles:
Contoso voice migration case study
The case study describes how a fictional multi-national corporation, Contoso, implemented a Teams voice solution for their organization. It contains the following articles:
Feedback verzenden en weergeven voor