Multi-region phone system consolidation on Microsoft Teams Phone

I lead a multi-year program to retire a fragmented regional telephony estate and put the entire company on Microsoft Teams Phone with Microsoft Calling Plans. Every region and every acquired company funnels onto the same platform: one dial plan, one admin console, one cost model, and one known place to port numbers when a deal closes. Three regional waves are complete, each retiring a different legacy carrier, and the program continues.

The estate this replaced

Each part of the business had arrived with its own carrier, its own dial plan, and its own administrative overhead: a per-seat hosted PBX with its own billing relationship and console in one region, a carrier-hosted voice service in another, a third-party-managed FreePBX deployment in a third where every admin change routed through the hosting vendor, and assorted single-site legacy PBX deployments inherited through acquisition.

The cumulative cost was high across multiple parallel per-seat contracts. The admin surface was wide, a different portal for every region. And the things users actually expect from a phone system in a distributed company, cross-region transfer, a unified directory, presence, one softphone client, were simply not available.

The standard

• Platform: Microsoft Teams Phone on the existing tenant.
• Carrier model: Microsoft Calling Plans, with Microsoft as the carrier rather than Direct Routing. Chosen for single-vendor billing and a much smaller operational surface.
• Client: the Teams softphone as the default, with physical desk phones only where the use case genuinely requires one.
• Number management: centralized in Teams Admin Center, with a porting and orchestration partner engaged for cutover windows rather than as the steady-state carrier.
• Call handling: auto-attendants and queues built natively, with operator voicemail groups and after-hours routing standardized per site.
• Cross-region behavior: unified directory, presence, extension dialing, and transfer across every region and acquired company on one tenant.

The cutover playbook

Every regional cutover runs the same sequence, hardened over successive waves:

1. Pre-port discovery. Pull the full carrier inventory: DIDs, main numbers, fax lines, after-hours numbers, e911 addresses, and the analog dependencies people forget, including fire-alarm and elevator lines. Validate the account holder and authorized user of record, because a port-out request fails without it. Map every existing extension to a target user.
2. License procurement sized to the verified user list rather than the inherited seat count, which is almost always inflated against actual headcount.
3. Temporary number scaffolding in the correct area code, so forwarding chains can be tested end to end before production numbers move. This is what keeps cutover risk bounded.
4. Auto-attendant and voicemail pre-build validated against those temporary numbers, so the inbound caller experience is already correct at minute one of go-live.
5. Porting in waves: a single-number canary port to prove the path, then the bulk of the DIDs, then re-pointing user assignments once the port completes.
6. Failover wrap-up: fire-alarm cellular failover, elevator-line replacement, and any remaining analog dependencies reprovisioned before the legacy line is released.
7. Vendor decommission as an explicit step in the project plan, closed out rather than left to auto-renew quietly in the background.

Acquisitions land on the same rails

This playbook is the default path for every acquisition. Inherited telephony is mapped during pre-close discovery, DID porting gets a dedicated two to three week lead-time line in the integration timeline, and the legacy carrier contract is cancelled and closed rather than transferred.

The point is that a new acquisition lands directly on the standard platform instead of carrying a separate phone contract forward and accreting fresh consolidation debt. Without this, the program would regress every time a new entity joined.

Outcomes

• Tens of thousands of dollars a year in recurring telephony spend eliminated by retiring parallel hosted-PBX contracts and consolidating seats under the Calling Plan model on the existing tenant. The saving compounds with each region migrated and each acquisition landed.
• One admin console for number provisioning, auto-attendant changes, queue tuning, licensing, and move-add-change work, instead of one portal per region.
• Real UC behavior across the company: unified directory, extension dialing, presence, transfer, and a single softphone client.
• Cleaner M&A, with a known telephony landing zone and a documented cutover instead of bespoke design per deal.
• Smaller vendor surface: fewer carrier relationships, fewer renewal cycles, fewer billing disputes to triage.