Note: Microsoft changes Teams Phone features, licensing and calling options regularly. Treat this as a planning checklist and confirm current details with Microsoft documentation and your carrier before committing to a design.
1. Define scope and outcomes
Start with what is changing and why. Inventory the sites, user groups and existing phone systems being replaced. Identify special needs: contact-center workflows, call recording, shared lines, analog devices, and any regulatory requirements. Agree on success measures, such as a cutover date, user adoption and call quality, and name an accountable owner for each.
2. Choose the calling model
Teams Phone connects to the public telephone network in different ways: Microsoft-provided calling plans, carrier-provided connectivity through Operator Connect, or your own carrier and equipment through Direct Routing. Availability varies by country and licensing. The choice affects cost, contracts, number management and support, so decide early with procurement and your carrier.
3. Check network readiness
Voice is sensitive to poor networks. Assess internet bandwidth at each site, Wi-Fi coverage, firewall and port configuration and quality-of-service settings. Use Microsoft's planning and call-quality tools to estimate load and find weak sites before users do. Remediation lead times for network upgrades are often the longest item on the schedule.
4. Inventory and port numbers
Build a complete inventory of phone numbers, main lines, direct dials, fax and any lines tied to alarms, elevators or other critical equipment. Number porting involves carriers and can take time, so start early, group numbers into waves and plan for porting delays in the schedule.
5. Plan emergency calling
Emergency calling needs deliberate design: accurate location information for users and devices, correct emergency addresses for each site, and internal notification. In the United States, requirements such as Kari's Law and the RAY BAUM'S Act affect how multi-line telephone systems handle 911 calls and location. Confirm obligations with your carrier and counsel, and test emergency calls during the pilot.
6. Prepare devices and endpoints
Decide which users get desk phones, headsets or the Teams app only. Use devices certified for Teams, plan for conference rooms and common areas, and identify any analog devices that need adapters or a different solution. Order early, since hardware lead times can affect your schedule.
7. Design call flows
Document how calls should behave: main numbers, auto attendants, call queues, hunt groups, shared lines, delegation and after-hours routing. Walk business owners through these designs before build, because gaps found after cutover become help-desk tickets.
8. Licensing, identity and policy
Confirm that users have the right licenses, that identity and Teams policies are configured, and that administrators have roles and runbooks. Align with security and compliance teams on recording, retention and access.
9. Pilot, then roll out in waves
Start with a pilot group that includes a mix of roles and sites. Test calling, voicemail, queues, emergency calling and devices. Use what you learn to refine the plan, then move to waves sized to what your support team can absorb. For large, multi-site and statewide programs, wave planning and a clear escalation path matter as much as the technology.
10. Train users and drive adoption
A technically successful cutover can still fail if people do not know how to use the new system. Provide short role-based training, quick-reference guides and visible support during cutover. Communicate early and often about dates, number changes and what to expect.
11. Cutover, hypercare and decommission
Plan the cutover window, rollback options and a hypercare period with extra support. When stable, decommission the legacy system, close contracts and capture lessons learned. Finally, hand the environment to operations with documentation, runbooks and monitoring in place.
Top risks to put in your risk register
- Number porting delays or errors.
- Network quality problems at specific sites.
- Emergency calling configuration gaps.
- Device delivery and compatibility issues.
- Undocumented analog or special-purpose lines.
- Low user adoption or insufficient training.
- Carrier or vendor schedule slippage.
Talk to Demdio. If you are weighing PMaaS or a fractional project manager for a program, a 30-minute discovery call is the fastest way to find out whether it fits. Contact our team or read about our PMaaS service.