Microsoft Teams Phone

Teams Phone license advisor

Compares Calling Plan, Operator Connect, Direct Routing, mixed model and special paths for Teams Phone with PSTN connectivity, phone numbers and additional needs.

Capture the telephony scenario

Describe license base, countries, carrier preference, operations and special cases. The evaluation separates Teams Phone, PSTN model and supplementary components.

License and user base
PSTN model and carrier
Operations, routing and special cases
Reset
Model Calling Plan

Standardized locations in countries with Microsoft Calling Plans and without existing carrier commitments.

Readiness 88%

Assesses Teams base, Teams Phone, PSTN path, coexistence and technical prerequisites.

Operations low

Estimates infrastructure, carrier, support and operational effort.

Flexibility medium

Assesses special routing, countries, carrier choice and freedom of integration.

License base

Microsoft 365 Business Premium

Strong Business base thanks to identity, device and protection features; Teams Phone is added.

Teams access
covered
Teams Phone
add

Additional components

Add-ons and special paths

These points should be considered separately in purchasing, rollout and operations.

  • Teams Phone: Teams Phone Standard or bundle with Calling Plan

Model comparison

Calling Plan, Operator Connect and Direct Routing

The table shows fit, operations, flexibility, typical strengths and limits of the models for your scenario.

Model Fit Operations Flexibility Suitable for Limitations
Calling Plan · Recommendation 92% low medium Standardized locations in countries with Microsoft Calling Plans and without existing carrier commitments.
  • Not available in every country
  • Special carrier contracts and special routing can only be mapped to a limited extent
  • Pay-as-you-go or overflows require clean cost control
Operator Connect 60% medium high Organizations with a suitable Operator Connect partner or a preference for carrier-run operations without their own SBC.
  • Only sensible with participating operators and countries
  • TeamsOnly mode required for affected users
  • Tariffs, porting and service levels depend on the operator
Mixed model 48% medium to high very high Several countries, different user groups, low-volume users, special locations and central telephony requirements.
  • Requires clean governance and documentation
  • The cost comparison must be calculated per persona
  • Porting and number management become more complex
Direct Routing 45% high very high Existing carrier contracts, PBX/analog/contact center integration, special routing or countries without Calling Plan.
  • Higher operational and support effort
  • Not suitable for Islands mode
  • Support usually starts with the SBC provider
Architecture review 30% to be clarified depends on the target state Unclear Teams base, missing PSTN path, unmet Direct Routing prerequisites or regulated special cases.
  • No blanket recommendation without detailed data
  • Migration planning and provider coordination required

Readiness-Checks

  • Teams base: ok
  • Teams Phone: addon
  • Calling Plan in the user's country: ok
  • TeamsOnly with carrier integration: ok
  • Direct Routing base: ok

Implementation steps

  1. Capture user groups, countries, phone numbers and existing carrier contracts.
  2. Check Teams entitlement and Teams Phone assignment per persona.
  3. Define the target model for PSTN, numbers, emergency calling and support.
  4. Check Calling Plan availability, number porting and minutes model per user country.

Prerequisites

What should be clarified before ordering and number porting

Costs depend on Domestic, International or Pay-As-You-Go.

Item Status Assessment
Teams access Check base Users need Teams access as the foundation for Teams Phone.
Teams Phone plan for License PBX and external telephony features per user.
PSTN connectivity required Define Calling Plan, Operator Connect, Direct Routing or a combination.

Sources

Source check: 2026-05-16. Internal guide values and market assumptions for scenario modeling; check Microsoft, CSP and carrier offers before procurement.

Show sources

PhinIT | Andreas Hepp

Need support with Microsoft 365?

We support you with license analysis, implementation, governance and ongoing optimization.