Teams Phone consolidates desk phones, PBX, conference bridges, and PSTN trunking into a Microsoft cloud service. The brochure savings are real. The realized savings hold only when the Teams Phone SKU mix, the PSTN model, and the audio conferencing posture match how the organization actually uses voice. The most common waste pattern we find is Teams Phone Standard entitled to the whole estate when only a third of the user base places outbound PSTN calls.
Teams Phone licensing layers in three components: the calling SKU itself, the PSTN connectivity model, and the optional audio conferencing add ons. Each component is priced and counted independently. Knowing what is paid for and what is consumed is the precondition to right sizing.
The base Teams Phone SKU enables the user to be reached on a phone number from inside Teams. PSTN connectivity is layered on top through one of three models.
Connectivity to the public phone network is a separate decision from the user license. Each model has different economics and different lock in.
Teams Phone waste is usually the result of treating the SKU as a knowledge worker entitlement rather than as a tool for the population that actually makes outbound PSTN calls.
Teams Phone Standard entitled to the whole estate because procurement treated it as a feature toggle rather than a paid SKU. Two thirds of the user base never makes an outbound PSTN call but holds the license.
Bundled Calling Plan SKUs held by users who place fewer than 60 PSTN minutes per month. Direct Routing or Operator Connect at a carrier rate beats the bundled price comfortably at moderate usage.
Audio Conferencing entitled separately on top of E5 users who already carry it inside the bundle, because the standalone SKU was added at a moment when E5 attach was lower and the add on was never reconciled.
The Teams Phone engagement is a right size plus model switch question. The economics swing on whether the population is correctly bounded and whether the PSTN model matches the call profile.
We pull the call detail records from the tenant, segment users by monthly outbound PSTN minutes, and identify the population for whom Teams Phone Standard pays back, the population that warrants the bundled Calling Plan, and the population that should not hold a Teams Phone license at all. The output is the contracted seat count and bundled minute pool for the next renewal.
The exercise is most useful at the eighteen month mark of a three year EA because the data is mature and the renewal still has fourteen months of negotiation runway.
Direct Routing and Operator Connect should be evaluated against the bundled Microsoft Calling Plan whenever annual minute volume crosses a threshold the practice has benchmarked across comparable estates. The threshold moves with geography, regulated industry obligations, and existing carrier relationships.
The switch is more complex than it appears. SBC certification, emergency calling compliance, and the e911 obligations are non trivial. The cost saving is meaningful but only when the operational lift is accounted for honestly.
The Teams Phone economic picture is not just the per user license. It is the layered cost of license plus carrier plus shared device plus compliance plus emergency calling obligation. Modeling each layer honestly is the precondition to negotiating the line.
The per user license enables calling. The PSTN minutes are a separate cost in the Direct Routing and Operator Connect models and a bundled cost in the Microsoft Calling Plan. The break even between the two models lands somewhere between 60 and 250 outbound minutes per user per month depending on geography and carrier rate. Below the threshold, Calling Plan wins. Above it, Direct Routing or Operator Connect wins.
The threshold is geography sensitive. North American rates differ from European rates, which differ again from Asia Pacific. The honest model segments by country, by user role within country, and by call profile inside the role.
Emergency calling compliance is non negotiable. The e911 obligations in the United States and the equivalents in other jurisdictions impose specific routing and address registration requirements. Direct Routing puts the obligation on the buyer to manage. Operator Connect and Calling Plan shift it to Microsoft and the partner carrier respectively.
Regulated industry compliance, call recording, retentionobligations, and lawful intercept must also be modeled. The right model is the one that matches the regulatory environment, not the one that prices lowest at the user line.
The PSTN call profile and the model switch decision require six to twelve months of runway. The savings are structural. The diagnostic is straightforward when the call detail records are honest.