Teams Phone is the Microsoft voice platform inside Microsoft Teams, licensed as a Phone System add-on with optional Calling Plan or Operator Connect connectivity. The Admodum read on the SKUs, the Direct Routing alternative, the seat economics and the audit posture.
Teams Phone is the voice platform inside Microsoft Teams. The product adds call control (the ability to place and receive PSTN calls inside the Teams client), voicemail, auto attendant (an interactive voice response surface), call queue (the agent-distribution surface) and the wider voice-feature set to the Teams baseline.
The licence is per-user, every user with a phone number requires a Teams Phone licence. The Teams meetings and chat surface is licensed separately under the Microsoft 365 suite; Teams Phone is the upgrade for voice. The wider Microsoft 365 plans framework is the suite reading against which the Teams Phone add-on is read.
Teams Phone is included in Microsoft 365 E5 (and the corresponding Office 365 E5 SKU, and the Business Premium and Frontline F5 SKUs in selected geographies). The licence is an add-on to Microsoft 365 E3, E1 and the corresponding Business Basic, Business Standard, Frontline F1 and F3 SKUs.
The economic question on the suite-to-add-on transition is the Teams Phone-only versus E5-bundle cost comparison. A buyer with E3 and a Teams Phone add-on (and a Power BI Pro and Defender for Endpoint stack on the side) typically approaches the E5-bundle cost; the bundle includes incremental benefits (Defender suite expansions, the Audio Conferencing entitlement, the Power BI Pro seat). The wider Defender suite licensing and Power BI Pro and Premium spokes are the adjacent inclusion reads.
The connectivity-route choice carries three routes. The Microsoft Calling Plan is the Microsoft-as-carrier route: Microsoft provides the PSTN connectivity; the buyer purchases per-user minute bundles (domestic, international or unlimited) and pays overage at the per-minute rate. The Calling Plan is structurally appropriate for small-to-mid-sized estates and for geographies where Microsoft Calling Plan is available.
Operator Connect is the certified-third-party-carrier route: a participating carrier (BT, Lumen, Telstra, NTT and many others) provides PSTN through a Microsoft-managed integration; the buyer holds the carrier contract separately and the integration sits within the Microsoft admin surface. Direct Routing is the buyer's-own-SBC route: the buyer operates a session border controller (or a managed-SBC service); the buyer holds the carrier contract; the integration sits on the buyer's network. The wider Microsoft BATNA framework reads the alternative voice-platform routes (Zoom Phone, RingCentral, Cisco Webex Calling) against which Teams Phone is measured.
The Calling Plan economics tilt to Direct Routing at scale: a Direct Routing estate carries the per-user Teams Phone licence (no Calling Plan add-on cost) and a separate per-minute carrier contract that runs at carrier-market rates (typically lower than the Microsoft Calling Plan rate at scale). The Operator Connect economics sit between the two: per-user Teams Phone licence, per-user-per-month integration fee in many participating-carrier contracts, carrier per-minute rate.
The break-even depends on the estate size, the international call mix and the geography. A 10,000-user estate with heavy international calling typically reads to Direct Routing; a 500-user estate in a Calling Plan-available geography typically reads to Calling Plan. The Admodum read on the route choice is the multi-vector calculus, not the per-user-only comparison.
Teams Phone audit posture examines four axes: the licensed-user inventory (every user with a Teams Phone licence, the suite-inclusion or add-on source), the assigned-number register (every phone number, every assigned user, every unassigned-but-active number), the calling-policy assignment (every user, the assigned policy, the dial-out-permission scope), and the connectivity-route declaration (Calling Plan, Operator Connect, Direct Routing, per user).
The principal false-positive pattern is the assigned-number-without-active-user: a phone number remains assigned to a former user; the audit catches the assignment-inspection as a licence-non-compliance finding (or a hygiene finding, depending on the buyer's licence-pool position). The wider seat assignment hygiene spoke reads the parallel principle across the wider Microsoft 365 surface.
The buyer-side artefacts to hold against the Teams Phone estate are: the licensed-user inventory (every Teams Phone licence, every user, every suite-inclusion or add-on declaration), the phone-number register (every number, every assigned user, every unassigned-but-active number, every release date for un-active numbers), the connectivity-route declaration (every user, the Calling Plan, Operator Connect or Direct Routing route), the carrier-minute consumption (per user, per month, per call type), the auto-attendant and call-queue inventory.
The wider engagement sits in the Microsoft practice; the aggregated reading list sits in the Microsoft knowledge hub; active renewal moments route to the Renewal Programme; active audit moments route to Audit Defence.
The wider per-seat hygiene framework against which Teams Phone runs.
The adjacent Microsoft EMS surface that frequently shares the seat profile.
A senior Admodum Microsoft advisor will read your Teams Phone licence inventory, your phone-number register and your connectivity-route declaration against your renewal and audit posture on a private call. Active audit moments route to Audit Defence.