Prepare my service
This article gives an overview of the requirements for preparing cloud voice services for your organization. By preparing properly, you can be sure you're ready to provide cloud voice capabilities to your organization.
Onboarding checklists for Microsoft Teams voice workloads
The following checklists walk you through the steps for implementing Audio Conferencing, Phone System with Calling Plans ("Calling Plans"), and Phone System Direct Routing ("Direct Routing") capabilities in Microsoft Teams.
The tasks and activities in these checklists are the core "to-do" items that apply to every deployment of cloud voice capabilities with Teams. You can customize the checklists to include the activities and tasks that are specific to your own Teams journey.
Note
This guidance focuses solely on Calling Plans, Audio Conferencing, and Direct Routing. If you're new to Teams, review Overview of Microsoft Teams. For general guidance for planning your Teams deployment, start with Deploy chat, teams, channels, and apps in Microsoft Teams.
Use the provided checklists to track the status of each individual activity and task, and to be sure you haven't skipped any critical steps. Each activity includes a detailed description of required actions and references to additional information that you can use to complete that activity.
Although we recommend that you follow the checklists in order, the exact sequence will depend on the scope of your deployment and the configuration and complexity of your environment. They're organized to support either a "greenfield" Teams deployment (one with no previous Skype for Business Online presence) or migrating from Skype for Business Online to Teams. If you're migrating from Skype for Business Online, you might have already completed some of these activities and can ignore them now.
When you're onboarding users on a per-site basis, we highly recommended that you use the Site Enablement Playbook for Voice (Playbook) as a supplementary guide to these checklists.
Note
Most of the configuration settings are common between Teams and Skype for Business Online. You use the Microsoft 365 Admin Center and Microsoft Teams admin center to configure those settings.
 Decision points |
|
 Next steps |
|
Continue onboarding
After you complete these checklists, you'll have successfully added voice capabilities to your Teams deployment.
As the next step, use the Site Enablement Playbook for Voice (Playbook) to help you onboard your users on each site, and help ensure that you plan and execute important site-specific activities.
Ready Site by Site Rollout Plan
Establish Service Management Process
Execute Testing and Remediation
Test cloud voice workloads in Teams
After you've defined and documented your Teams cloud voice business success and technical implementation plans as part of the Envision phase and undertaken the configuration you want in the admin center, the next step is to validate that your organization's expectations and requirements are met through feature, functionality, and usability. You should perform this validation step before you deploy a pilot or final deployment in your production environment.
You can leverage the business success plan you defined during the Envision phase to serve as the basis for determining the activities, expectations, feature/functionality test cases, and overall scope to be evaluated during the testing phase.
Define your testing approach
In its simplest form, your testing approach is based on your reviewing the feature capabilities of the Audio Conferencing, Calling Plans, or Direct Routing service and developing a test plan to verify that your functionality requirements are met for users in scope. The following is an example test plan for the Onboard phase of an audio conferencing implementation.
| Audio Conferencing feature to test | Results summary | Additional notes |
|---|---|---|
| Schedule an ad-hoc Teams meeting that contains audio conferencing dial-in information | Pass/Fail | TBD |
| Use a phone for meeting audio by dialing into a meeting from the PSTN with the dial-in information provided | Pass/Fail | TBD |
| Join other people to an existing meeting by dialing out via the PSTN | Pass/Fail | TBD |
| Calling Plans or Direct Routing feature to test | Results summary | Additional notes |
|---|---|---|
| Make a PSTN call by dialing a PSTN number | Pass/Fail | TBD |
| Receive a PSTN call by dialing your PSTN number from an external line (mobile, landline) | Pass/Fail | TBD |
| Transfer a PSTN call from one Teams user to another | Pass/Fail | TBD |
Tip
To assist with test-case creation as a starting point, see the list of user guidance available at Teams Meetings and calls.
Set up cloud voice workloads for Teams
Now that you've defined your testing approach, the next step is configuring your service environment and users in scope for Teams cloud voice features.
For additional information, see:
Execute the test plan
After the user environment and the service have been configured, the last step of testing includes test plan execution with focus on feature and functionality validation.
Audio Conferencing testing prerequisites and assumptions for users and sites in scope:
Business use case definition for the Audio Conferencing service has been completed.
Licensing required for Audio Conferencing is available and has been assigned.
The list of organizational sites and user groups have been identified.
The list of dedicated and shared audio conferencing dial in numbers with language preference have been identified and configured.
Communications Credits (if required) have been set up for your organization.
Audio Conferencing conference bridge settings have been identified and configured (PIN length, entry/exit notifications, enablement notification preference).
Tenant conferencing policies and dial plan settings that support Audio Conferencing dial-out scenarios have been identified, configured, and applied.
Audio Conferencing compliance requirements have been identified and configured.
Calling Plans testing prerequisites and assumptions for users and sites in scope:
Business use case definition for the Calling Plans service has been completed.
Licensing required for Calling Plans is available and has been assigned.
The list of organizational sites and user groups have been identified.
Phone numbers to be assigned to users have been acquired or ported to Microsoft and are available in the tenant portal.
Communications Credits (if required) have been set up for your organization.
Tenant user policies and dial plan settings that support Calling Plans scenarios have been identified, configured, and applied.
Calling Plans compliance requirements have been identified and configured.
Direct Routing testing prerequisites and assumptions for users and sites in scope:
Business use case definition for the Direct Routing service has been completed.
Licensing required for Direct Routing is available and has been assigned.
The list of organizational sites and user groups have been identified.
A certified session border controller (SBC) has been deployed, configured and paired with Phone System.
Enterprise voice has been enabled, and the phone numbers have been assigned.
Voice routing policies have been identified, configured, and assigned.
Microsoft Teams has been set as the preferred calling client for the users in scope.
Direct Routing compliance requirements have been identified and configured.
| Decision points |
|
Next steps |
|
For additional detailed guidance on how to perform testing for Audio Conferencing in Teams, see the detailed testing guide for Audio Conferencing.
For additional detailed guidance on how to perform testing for Calling Plans in Teams, see the detailed testing guide for Phone System.
Feedback
Submit and view feedback for