ADAM PULSE Knowledge Base
Zoom Phone · Microsoft Teams · Operator Connect · Direct Routing

Can Zoom Phone work with Microsoft Teams?

Short answer

Yes. Zoom Phone can work with Microsoft Teams in three models: embedded Zoom inside Teams; Zoom Phone Direct Routing, which keeps the native Teams dialer and uses Zoom telephony underneath; and Zoom Operator Connect, where Zoom is the PSTN operator and you do not deploy a customer SBC. The right choice depends on user experience, which features you must keep, infrastructure, and who operates the voice platform. Teams Phone licensing is required for native Teams telephony. Operator Connect does not include every Zoom Phone feature — validate SMS, fax, recording, and queues. More than one approach can coexist in one tenant if you name each population.

This is the question spoke. The four-architecture quoting map is Zoom + Microsoft Teams: Complete Integration Guide. The existing live operational article is Zoom Phone and Microsoft Teams together: what actually integrates?

What are the three models?

Three ways Zoom Phone works with Microsoft Teams. Embedded Zoom itself splits into two UIs on the hub.
Model What the user sees What you are buying
Embedded Zoom in Teams Zoom Phone UI inside Teams (Workplace tabs, or the phone-only plug-in) Zoom as the phone platform, surfaced in Teams. Not native Teams Phone.
Zoom Phone Direct Routing Native Teams Calls / dialer Microsoft Teams Phone plus Zoom telephony on a certified or DRaaS Session Border Controller path.
Zoom Operator Connect Native Teams Calls / dialer Microsoft Teams Phone plus Zoom as the Operator Connect PSTN operator. No customer SBC.

Zoom’s Teams product page names the same three deployment options: an embedded Zoom Phone experience, advanced calling with Direct Routing, and simplified PSTN connectivity through Operator Connect. The hub further splits embedded Zoom into the Zoom Phone plug-in (no Workplace desktop) and Zoom Workplace for Teams (Meetings, Phone, and Whiteboard tabs, desktop client still required for calling). Do not quote those two as one SKU.

Do you need a customer SBC?

Not for Operator Connect. Microsoft’s Operator Connect planning page says it is a good choice when you want a managed PSTN solution without deploying and maintaining your own Session Border Controllers. Zoom’s Operator Connect product bullets include “No SBC deployment and maintenance.”

Direct Routing is the opposite Microsoft model: a certified Session Border Controller procured, installed, and managed by you, your integrator, or a Direct-Routing-as-a-Service provider. Zoom Phone for Microsoft Teams is Zoom’s Direct Routing as a Service offering on that path. See Operator Connect vs Direct Routing.

Do you need Teams Phone licensing?

For native Teams telephony — Operator Connect or Direct Routing — yes. Microsoft requires Teams Phone licenses for Operator Connect. Zoom’s Operator Connect setup article (KB0087617) lists:

Zoom’s Direct Routing management article (KB0057686) lists a Zoom Phone for Microsoft Teams license and several Microsoft plan families that include or add Teams Phone (including E5, E1/E3 + Teams Phone, F1/F3 + Teams Phone, and education plans). Those lists are not interchangeable. Verify the current Zoom article for the architecture you are quoting.

Embedded Zoom in Teams is not native Teams Phone. Users need the Microsoft Teams environment and the Zoom licensing the in-app or plug-in path requires. Do not copy Operator Connect SKUs onto an embedded quote.

Does Operator Connect include every Zoom Phone feature?

No. Zoom’s Operator Connect setup article states it directly: Microsoft Teams does not support all Zoom Phone features via Operator Connect (for example, SMS and fax are not available). Treat recording, queues, SMS, and fax as a validation list, not as inherited Zoom Phone capabilities.

SMS and fax that you need inside Teams belong on the embedded path. Zoom’s plug-in article (KB0088117) lists SMS/MMS and fax among plug-in capabilities. Zoom’s Direct Routing library says native SMS inside the Teams client is not currently supported and should be supplemented with the in-app integration. That is why a quote that says “Operator Connect plus SMS” as one line is wrong.

Can multiple approaches coexist in one tenant?

Yes. Microsoft’s PSTN connectivity article says organizations can use the same PSTN option with multiple operators or combine multiple PSTN options for different users, locations, and requirements. Zoom documents Direct Routing coexistence with some users remaining on Zoom Phone and others synced to Teams, including extension dialing when configured.

Coexistence is a named split: who uses which client, who owns the number, who owns the queue, who owns emergency calling. It is not a reason to mix SKUs on a single user.

How is this different from the live integration article?

The live URL /articles/zoom-phone-microsoft-teams-integration already answers what actually integrates on Direct Routing versus in-app Zoom Phone: presence, queues, E911, GCC High limits, and the background Zoom client. This new page answers the search question “can Zoom Phone work with Teams?” and introduces Operator Connect as a third model. Keep both. Link both ways. Do not merge them.

Frequently asked questions

Can Zoom Phone work with Microsoft Teams?

Yes. Three models exist: embedded Zoom inside Teams; Zoom Phone Direct Routing behind the native Teams dialer; and Zoom Operator Connect, where Zoom is the PSTN operator and there is no customer SBC.

Do I need an SBC for Operator Connect?

No. Microsoft documents Operator Connect as the path when you do not want to deploy and maintain your own Session Border Controllers. Zoom's Operator Connect product page says the same: no SBC deployment and maintenance.

Do I need Teams Phone licensing for native Teams telephony?

Yes. Native Teams dialer paths (Operator Connect and Direct Routing) require Microsoft Teams Phone licensing. Zoom's Operator Connect article lists Microsoft E5, which includes Teams Phone Standard, or E1, E3, or Business plus the Teams Phone Standard add-on. Zoom's Direct Routing article lists additional eligible plans. Verify the current Zoom and Microsoft pages before you buy.

Does Operator Connect include every Zoom Phone feature?

No. Zoom states that Microsoft Teams does not support all Zoom Phone features via Operator Connect, and gives SMS and fax as examples that are not available. Validate recording, queues, SMS, and fax against current Zoom docs for the architecture you are quoting.

Can more than one approach coexist in one tenant?

Yes. Microsoft documents that organizations can combine PSTN connectivity options. Zoom documents hybrid Direct Routing deployments with some users on Zoom Phone and some on Teams. Name each population; do not treat coexistence as one SKU.

Is this the same page as Zoom Phone and Microsoft Teams together: what actually integrates?

No. That existing live article is the operational spoke for Direct Routing versus the in-app Zoom Phone experience. This page answers whether Zoom Phone can work with Teams and names the three models. The four-architecture hub splits the embedded path into the Zoom Phone plug-in and Zoom Workplace for Teams.

References

First-party Zoom and Microsoft pages, verified 28 August 2026. Feature availability, operator listings, and licensing change; the current vendor page controls.

  1. Zoom — Zoom Workplace for Microsoft Teams— three deployment options: embedded Zoom Phone, Direct Routing, and Operator Connect.
  2. Zoom — Setting up Zoom for Microsoft Operator Connect (KB0087617)— Operator Connect Assignment license, Teams Phone licensing (E5 or E1/E3/Business + Teams Phone Standard), SMS and fax not available, country list, emergency addresses, number allocation.
  3. Zoom — Managing Zoom Phone for Microsoft Teams (KB0057686)— Direct Routing (native Teams dialer), Zoom Phone for Microsoft Teams license, Teams Phone-eligible Microsoft plans.
  4. Zoom — Zoom Phone plug-in for Microsoft Teams (KB0088117)— Zoom Phone UI in Teams without Workplace desktop; SMS/MMS and fax on the plug-in path; disabled by default.
  5. Microsoft Learn — Plan for Operator Connect (ms.date 2026-08-24)— certified operator, no customer SBC, Teams Phone licenses, Teams Only mode.
  6. Microsoft Learn — PSTN connectivity options (ms.date 2026-07-31)— Calling Plan, Operator Connect, Teams Phone Mobile, and Direct Routing as separate models; organizations can combine options.
Prepared by ADAM Pulse (USA Telecom Consulting LLC)

Managed Zoom Phone and Microsoft Teams architecture, SDVOSB. We name which of these three models a Teams-first organisation is actually buying, and we do not put SMS, fax, or an SBC on the Operator Connect line. Support: (888) 989-4872 · support@adampulse.us