Contoso case study: Teams voice migration overview
This article introduces a case study for how a fictional multi-national corporation, Contoso, implemented a Teams voice solution for their organization.
Contoso has deployed Microsoft 365 Enterprise and addressed major design decisions and implementation details for the following: networking, identity, Windows 10 Enterprise, Office 365 ProPlus, mobile device management, information protection, security, upgrade from Skype for Business to Teams, Phone System, and Audio Conferencing.
This article focuses on how Contoso migrated their on-premises users to Teams for unified communication, collaboration, and voice. For background information about how Contoso accelerated their digital transformation by using Microsoft's cloud services, see all the core articles starting with the Contoso case study overview.
In the core articles, you'll find information on the following:
- Contoso's IT infrastructure needs
- Windows 10 Enterprise
- Office 365 Pro Plus
- Mobile device management
- Information protection
- Summary of Microsoft 365 Enterprise security
- Team for a top-secret project
- SharePoint Online site for highly confidential digital assets
For information about planning an upgrade, you'll want to start with Getting started with your Microsoft Teams upgrade.
Contoso business goals for Teams
To migrate their on-premises users to Teams for unified communication, collaboration, and voice, Contoso decided on the following business goals:
Contoso's unified communication and collaboration team enabled Teams with the correct policies to govern and enable secure internal and external collaboration.
Skype for Business to Teams upgrade
Skype for Business was widely deployed within Contoso. With the need to move off legacy systems, Contoso decided to upgrade their Skype for Business users to Teams. For more information, see Contoso case study: Teams upgrade plan.
Skype for Business with enterprise voice was widely deployed within Contoso. With the need to move off legacy systems that were the next hop for their mediation servers, Contoso migrated their Skype for Business enterprise voice users to Phone System. Contoso sites used Microsoft Calling Plan, Phone System Direct Routing, or a combination of both. For more information, see Contoso case study: Phone System.
With office locations in telephony-regulated countries/regions, Contoso needed to recreate the Location-Based Routing that was present in Skype for Business in their Phone System deployment. For more information, see Contoso case study: Location-Based Routing.
Where Direct Routing was implemented, Contoso set up emergency calling with approved third parties. For more information, see Contoso case study: Emergency Calling.
Contoso set up Audio Conferencing service numbers that were hosted on their SIP trunk to their PSTN provider. For more information, see Contoso case study: Audio Conferencing.
Local Media Optimization
Contoso took advantage of Local Media Optimization in locations where they had one direct route trunk to Microsoft Phone System that was leveraged by remote sites. For more information, see Plan for Local Media Optimization and Configure Local Media Optimization.
Auto Attendants and Call Queues
Contoso wanted to provide receptionist support while their staff was working remotely. Contoso used auto attendants and call queues to manage incoming calls to their receptionist's phone number. For more information, see Contoso case study: Auto Attendants and Call Queues.