Teams Insider

Microsoft M365 Telco Strategy with Taimoor Husain

Taimoor Husain leads global telco go-to-market strategy for Microsoft 365 at Microsoft. Recorded in person at Shure's London office, he covers the origins and growth of Operator Connect, how customers choose between Calling Plans, Direct Routing, Operator Connect and Teams Phone Mobile, the SMB whit

Prefer audio?

Who should listen: Microsoft 365 service owners planning or reviewing a Teams Phone migration, and operator, CSP and system integrator teams building telephony propositions around Operator Connect and Teams Phone Mobile.

Guest: Taimoor Husain — Global Telco M365 GTM Strategy Lead, Microsoft

Many thanks to Numonix, sponsor of this episode.

Key insights

Operator Connect is growing roughly 100% year-on-year on enabled seats, with coverage now at 97 operators and 97 countries and closing in on 100 of each. ▶ 3:06
Operator Connect was created to add governance to the direct routing as a service market — security, resiliency, SLAs and programmatic APIs — because customers could not distinguish a tier-one telco from someone running a single SBC in the cloud. Direct routing as a service still exists alongside it. ▶ 3:37
Around 20 million Teams Phone seats are active (not just licensed) across Calling Plans, Direct Routing, Operator Connect and Teams Phone Mobile. Husain is explicit that Microsoft is not pushing customers to Calling Plans or to Operator Connect only — choice is deliberate, and Calling Plans cover 35 countries so most global customers still need OC or DR alongside. ▶ 5:09
Connectivity choice is an IT decision, not a user-experience one: end-user functionality is identical across Calling Plans, DR and OC. DR retains an edge for local survivability, regulated markets and SCIF/on-premises environments. Smaller customers typically pick one model; larger ones mix OC with DR and increasingly split mobile and fixed across the user base. ▶ 6:10
Copilot is reversing the buying order in enterprises — customers who started a Copilot deployment are now moving off legacy IP PBXs they had judged 'good enough', because call summaries, transcription and action items only apply to calls that land in Teams. ▶ 13:23
Teams Phone Mobile is an identity play, not SIM ring or forking: the mobile number becomes an M365 identity with a single voicemail box, single call history, enterprise presence, policy and discoverability, delivered via deep IMS-to-cloud integration built on the Operator Connect platform. ▶ 18:01
Teams Phone Mobile market expansion is intentionally slow because each operator integration is deep; Microsoft has prioritised large markets (US, UK, Canada, Germany) and is now adding second and third operators per market — the UK will be the first with three providers, following BT with VMO2 and Vodafone. ▶ 22:40
Reduced-cost frontline worker licences and Teams Essentials plus Teams Phone remove the Microsoft-side cost barrier for mobile-first and SMB deployments; the Queues app in Teams Premium adds supervisor whisper and barge-in for lightweight contact-centre needs without replacing established CCaaS partners. ▶ 25:44
FY25 priorities for Operator Connect and Teams Phone Mobile are making them easier to buy, enable and manage — more APIs and management tooling from engineering, plus partner incentives and funded customer workshops, with SMB success dependent on partner-to-partner integrations and automated digital journeys. ▶ 26:16