What is the best way to use Zoom Phone with Microsoft Teams?
Short answer
Start with user experience, not with technology. If people must live in the native Teams dialer and you want the simplest PSTN with no customer SBC, start with Operator Connect. If you need advanced Zoom Phone features or routing that Operator Connect does not provide, start with Direct Routing. If you need Zoom capabilities inside Teams rather than native Teams Phone, use embedded Zoom. Run five steps: UX, mandatory features, countries and numbers, operating model, then a pilot. Hybrid by user population is valid. There is no single best design for every tenant.
Hub: Zoom + Microsoft Teams: Complete Integration Guide. Models: Can Zoom Phone work with Microsoft Teams?
Why start with UX instead of the stack?
Because Operator Connect and Direct Routing can look identical to the user — native Teams Calls — while embedded Zoom looks like Zoom Phone inside Teams. If you pick the stack first, you will argue about SBCs while the actual requirement was “do not make people leave Teams” or “we must keep Zoom SMS.”
Which architecture matches which UX?
| If this is the non-negotiable | Start with |
|---|---|
| Simplest native Teams PSTN, no customer SBC | Operator Connect |
| Advanced Zoom features, PBX/analog, or routing Operator Connect lacks | Direct Routing |
| Zoom capabilities (SMS, fax, Zoom Phone UI) inside Teams | Embedded Zoom — plug-in or Workplace for Teams, named separately on the hub |
| Teams chat, Zoom Phone as its own app, minimal integration | Native Zoom Phone beside Teams. Integration is optional. |
What are the five steps?
- UX. Native Teams dialer, Zoom Phone UI inside Teams, or Zoom Workplace beside Teams. One sentence, written down.
- Mandatory features. SMS, fax, recording, queues, common area phones, extension coexistence, business continuity. If SMS or fax is mandatory and you were heading toward Operator Connect, Zoom says those are not available on that path.
- Countries and numbers. Operator Connect number provisioning is country-limited in Zoom KB0087617. Direct Routing has its own exclusions (Zoom: India, China, and Japan phone numbers). Check the list that matches the architecture, not a blended list.
- Operating model. Who administers numbers, emergency addresses, queues, and day-two tickets — the Zoom team, the Microsoft team, or both with a named split?
- Pilot. A mixed group, test numbers, no main-number port. Operator Connect setup: How to set up Zoom Operator Connect.
When is a hybrid valid?
When two populations have two UX requirements. Example: knowledge workers on Operator Connect in the native Teams dialer; a contact-center or front-desk group on embedded Zoom Phone for SMS and queues; a plant floor still on Zoom Workplace. Microsoft allows combined PSTN options. Zoom documents Direct Routing coexistence. Hybrid fails when you give one person two dialers and no owner.
When should we stop adding integration?
When Teams is already the collaboration surface and Zoom Phone already works, and nobody can name a workflow that integration would fix. Adding Operator Connect or Direct Routing so the architecture diagram looks unified is not a reason. Zoom Phone vs Microsoft Teams Phone is the comparison when someone is trying to pick a winner instead of a design.
Frequently asked questions
What is the best way to use Zoom Phone with Microsoft Teams?
Start with user experience, not with a product name. If users must stay in the native Teams dialer and you do not want a customer SBC, start with Operator Connect. If you need routing flexibility or Zoom Phone features Operator Connect lacks, start with Direct Routing. If you need Zoom capabilities inside Teams, use embedded Zoom (plug-in or Workplace for Teams).
Should every user be on the same architecture?
No. Hybrid by user population is valid. Microsoft allows combined PSTN options. Name each population.
What are the five steps?
Decide the calling UX, list mandatory features, check countries and number types, choose the operating model (who runs Zoom vs Teams), then pilot before porting.
Why not start with licensing?
Licensing follows the architecture. Operator Connect, Direct Routing, and embedded Zoom have different Zoom and Microsoft license lists. Buying SKUs first is how the wrong path gets locked in.
Where do we go for setup clicks?
Operator Connect: How to set up Zoom Operator Connect. Direct Routing and in-app operational detail: the existing live spoke Zoom Phone and Microsoft Teams together: what actually integrates?
Is there a single recommended Zoom plus Teams design?
No. The recommended design is the one that matches the UX and the mandatory feature list with the fewest extra layers.
Related articles
- Zoom + Microsoft Teams: Complete Integration Guide — the four-architecture hub so Operator Connect, Direct Routing, the plug-in, and Workplace for Teams are not mixed on a quote.
- Can Zoom Phone work with Microsoft Teams? — yes, and which of the three models you are actually buying.
- Zoom Operator Connect vs Direct Routing — simplified operator PSTN versus certified/DRaaS SBC flexibility.
- Zoom Phone vs Microsoft Teams Phone — two cloud PBXs; choosing the Teams client does not pick Microsoft as the PSTN carrier.
- How to set up Zoom Operator Connect — Zoom KB0087617 sequence: tenant, emergency addresses, numbers, Teams assignment, pilot.
- Zoom Phone and Microsoft Teams together: what actually integrates? — the existing live operational spoke for Direct Routing versus in-app Zoom Phone.
References
First-party Zoom and Microsoft pages, verified 28 August 2026. Start with UX; then re-read the current vendor pages for the architecture you picked.
- Zoom — Zoom Workplace for Microsoft Teams— three options: embedded, Direct Routing, Operator Connect. Match the user experience to the option, not the other way around.
- Zoom — Setting up Zoom for Microsoft Operator Connect (KB0087617)— simplest native Teams PSTN path; SMS and fax not in native Operator Connect; country list.
- Zoom — Managing Zoom Phone for Microsoft Teams (KB0057686)— Direct Routing when you need native Teams dialer plus Zoom Phone capabilities Operator Connect does not carry.
- Microsoft Learn — PSTN connectivity options (ms.date 2026-07-31)— combine options by user population in one tenant.
- Microsoft Learn — Plan for Operator Connect (ms.date 2026-08-24)— operator-managed PSTN, no customer SBC.
Managed Zoom Phone with Microsoft Teams, SDVOSB. We start from the calling experience and the mandatory feature list, then we name Operator Connect, Direct Routing, or embedded Zoom — including hybrid populations when that is the honest design. Support: (888) 989-4872 · support@adampulse.us