Teams Insider

Microsoft Teams Phone Mobile Deep Dive with Vandana Thomas

Vandana Thomas, product owner for Teams Phone Mobile in Microsoft's carrier and operator integrations team, explains how a corporate-liable mobile number becomes a native Teams number, and gives an early read on operator launches, licensing and enterprise adoption. She also covers the roadmap around

Who should listen: Microsoft 365 service owners, telephony architects and UC consultants evaluating mobile-first calling, compliance recording of mobile calls, or operator-delivered Teams Phone options.

Guest: Vandana Thomas — Product Leader, Teams Phone Mobile, Microsoft

Key insights

Teams Phone Mobile only works with a corporate-liable number ordered from the carrier — there is no bring-your-own consumer mobile number path, because of billing, compliance and privacy implications. ▶ 2:43
Because the mobile number is a Teams number, native cellular calls made from the handset dialler are captured by the same Teams compliance recording estate as meetings and VoIP calls — removing the need for special recording SIMs or separate contracts. Financial services customers are the strongest driver here. ▶ 4:16
Single-platform ownership of the number fixes the handoff/hand-on problem that dogged traditional fixed-mobile convergence, where two platforms each owned half the call and transfers only worked in one direction. Uplift from native dialler to Teams works today, with the reverse direction in progress for when data connectivity degrades. ▶ 8:29
Launched with five operators — Rogers (Canada, first), Verizon (US), Deutsche Telekom (Germany), Swisscom (Switzerland) and Telia (Nordics) — with BT in the UK due shortly. Each is currently home-market only, so multinationals cannot yet get consistent coverage. ▶ 12:21
Microsoft reversed its plan to charge for Teams Phone Mobile: a separate zero-cost licence exists for legacy reasons, effectively a feature flag, and long term it will be folded into Teams Phone. Operators package it differently by market — some bundle it with the business calling plan, others sit alongside Microsoft enterprise volume licensing. ▶ 17:07
Early adoption skews to smaller and mid-market customers actually in production, while enterprises are taking a handful of numbers to trial because of longer sales cycles. Some organisations already deploying Teams Phone are pausing to see how Teams Phone Mobile develops. ▶ 19:12
Onboarding is materially harder for operators than Operator Connect — it is not a configuration delta on top of direct routing but the wireless core handing part of call control to Teams for the first time, which is why expansion is being pursued by taking existing operators into new markets rather than signing more carriers. ▶ 21:50
SMS/MMS integration is the most requested missing feature; the open design question is how much chat and messaging should cross over. RCS is not a shortcut given Apple's refusal to adopt it, which also means Apple-to-Apple traffic never touches the operator to be pulled into Teams. ▶ 23:20
Admin setup mirrors Operator Connect: the operator uploads numbers into Teams admin center, the admin assigns licences and numbers to users, and routing starts. Existing numbers can be brought over by working with Microsoft alongside the operator. ▶ 31:51