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

Zoom + Microsoft Teams: Complete Integration Guide

By Michael Obraitis, Managing Partner, and Michael Dale, CEO · Published August 28, 2026 · Last reviewed August 2026 · Last reviewed August 28, 2026 · ADAM Pulse Knowledge Base

Short answer

Can Zoom Phone work with Microsoft Teams? Yes. Several models exist, and they are not interchangeable. Operator Connect and Zoom Phone Direct Routing both put PSTN calling behind the native Teams dialer. The Zoom Phone plug-in and Zoom Workplace for Teams put Zoom’s own UI inside Teams. Choose one architecture before anyone quotes licenses, SBCs, SMS, or fax.

This is the hub. The five Wave 1 spokes from this page are Can Zoom Phone work with Microsoft Teams?, Operator Connect vs Direct Routing, Zoom Phone vs Microsoft Teams Phone, How to set up Zoom Operator Connect, and What is the best way to use Zoom Phone with Microsoft Teams?. The existing live operational article is Zoom Phone and Microsoft Teams together: what actually integrates?.

Scope

This page maps four architectures so a quote cannot mix them. It does not cover Microsoft Calling Plans, SKU-by-SKU licensing, migration sequencing, or an SBC bill of materials. Microsoft and Zoom change feature availability; verify the current first-party page before you buy or cut over.

The four architectures, kept separate

People say “Zoom with Teams” and mean four different products. Two of them are PSTN connectivity models for the native Teams Calls experience. Two of them are Zoom UI inside Teams. A quote that borrows an SBC from B, SMS from C, and a native dialer from A is not a design.

Four Zoom + Microsoft Teams architectures. Do not mix columns on a quote.
Architecture What the user sees What Zoom is doing SBC / desktop Do not assume
A. Operator Connect Native Teams dialer / Calls app PSTN operator for Teams Phone No customer SBC SMS, fax, GCC High, or a live Operator Directory listing you have not checked
B. Zoom Phone Direct Routing Native Teams dialer / Calls app PSTN via Microsoft Direct Routing; Zoom Phone features on that path Certified or DRaaS Session Border Controller in the path That this is Operator Connect, or that native Teams-client SMS is automatic
C. Zoom Phone plug-in Zoom Phone UI inside Teams Zoom Phone client experience hosted in Teams No Zoom Workplace desktop required for the phone-only path Native Teams dialer, Operator Connect, or that existing tenants already have this enabled
D. Zoom Workplace for Teams Workplace, Meetings, Phone, and Whiteboard tabs In-app Zoom Meetings, Phone, and Whiteboard inside Teams Zoom desktop client still required in the background for Phone calling on this path That this is native Teams Phone, or that it is the same as the plug-in

A. Operator Connect

Microsoft’s definition: Operator Connect connects Teams Phone to the PSTN through a Microsoft-certified operator. Operators manage the PSTN infrastructure. Administrators manage users from the Teams admin center. Microsoft recommends it when you want a managed PSTN solution without deploying and maintaining your own Session Border Controllers, or when you want to keep working with an operator that already offers Operator Connect.

Zoom’s product page for this path is titled Zoom Operator Connect for Microsoft Teams. It documents:

Zoom’s 20 July 2026 Zoom Phone release notes introduce the same offering as Zoom for Microsoft Operator Connect: eligible Zoom-managed numbers provisioned for Microsoft Teams through the supported Operator Connect integration, with administrators able to manage eligible numbers from the Zoom web portal and, where supported, move numbers between Zoom Phone and Microsoft Teams without onsite hardware.

Microsoft’s support-boundary list for Operator Connect is PSTN connectivity, telephone number provisioning and porting, calling services, and PSTN-related support. Zoom’s Operator Connect product bullets are calling, number procurement, no SBC, and PSTN coverage. Neither page documents SMS or fax as Operator Connect capabilities. Do not put SMS or fax on an Operator Connect quote line.

Directory check, not a listing claim

Microsoft tells you to confirm participating operators in the Operator Connect directory. This article does not claim that the name Zoom currently renders in that live directory. Check the directory for the country you are quoting before you treat Zoom as a certified Operator Connect operator.

Do not design Operator Connect into GCC High or DoD. Microsoft’s GCC High and DoD service description delivers Phone System and Audio Conferencing via Direct Routing, and states that PSTN Calling is not available in those environments.

B. Zoom Phone Direct Routing

This is still the native Teams dialer. It is not Operator Connect.

Microsoft’s Direct Routing model lets you use any PSTN operator. Integration is through a certified Session Border Controller that is procured, installed, and managed by you, your integrator, or a Direct-Routing-as-a-Service provider. That is the “customer / supported SBC path” this architecture requires. Operator Connect exists specifically so you do not have to do that.

Zoom documents Zoom Phone for Microsoft Teams as a Direct Routing as a Service offering: Zoom Phone supplies PSTN underneath Microsoft Teams Phone System, and users call from the native Teams client. Zoom’s Teams product page lists this path as Zoom Phone Direct Routing for Teams (an add-on) and includes:

Zoom’s technical library is stricter on SMS than the product page. It states that Zoom Phone for Microsoft Teams does not currently support native SMS inside the Teams client, and that customers who need SMS should supplement with Zoom’s in-app Microsoft Teams integration. Treat that as: Zoom can sell SMS on the Zoom Phone side; it is not the same as native SMS in the Teams Calls app. If SMS in Teams is a requirement, that is a C or D conversation, not an A conversation, and it is not automatic on B.

Zoom also requires a Microsoft Phone System license and a Zoom license for this service. Feature support, country coverage, the press-1 accept behavior, and dial-pad activation delay belong on the operational spoke, not on this hub.

C. Zoom Phone plug-in

This is not the native Teams dialer. Users work in a Zoom Phone UI that lives inside Teams.

Zoom’s configuration article for the Microsoft Teams integration ends with a distinct path: to offer a phone-only experience that does not require the Zoom Workplace desktop app, enable or disable the Zoom Phone Plug-in for Microsoft Teams.

Zoom’s 16 August 2026 Zoom Phone release notes describe the same split in admin language: account owners can enable a plugin-based Zoom Phone experience under the Microsoft Teams integration section. It supports core Zoom Phone capabilities inside Teams, including making and receiving calls and advanced call controls. The setting is disabled by default. Existing customers remain on the current Workplace-app-dependent experience unless that setting is explicitly enabled.

Quote this path when the requirement is Zoom Phone inside Teams without deploying Zoom Workplace as the calling engine. Do not quote it as Operator Connect, Direct Routing, or native Teams Phone.

D. Zoom Workplace for Teams

This is the in-app Zoom app: a Zoom Workplace tab with Meetings, Phone, and Whiteboard. Zoom’s configuration article documents those tabs, plus SMS from the Phone tab, Outlook contacts, and presence configuration. Zoom’s technical library still states that, on this path, the Zoom desktop client must be running in the background to place or receive Zoom Phone calls. Silent start counts as running. Signed out does not.

That background-client requirement is the operational difference between D and C. Mixing them on a quote produces a deployment that either ships a desktop client nobody budgeted or omits a client the calling path still needs.

Zoom documents that a standalone Zoom Phone-only app is not supported in Microsoft Government GCC High and DoD. In those environments, Zoom supports phone through the Zoom Workplace app. That is a D constraint, not an A constraint, and it is still not Operator Connect.

Sales quoting checkbox

Fill this before SKUs, ports, or a statement of work. One primary architecture per quote. A second architecture is allowed only when it is named as a supplement (for example, B for native dialer PSTN plus C or D for SMS in the Zoom UI) and both sides initial that split.

Decision table for a Zoom + Microsoft Teams quote. Tick one primary architecture.
Check If yes, you are quoting If you also need… Do not also tick
Users must live in the native Teams Calls / dial-pad experience, with Zoom as the PSTN operator and no customer SBC A. Operator Connect Confirm the operator name actually appears in Microsoft’s Operator Connect directory for the country. Do not add SMS or fax on this line. B, C, or D as if they were the same SKU
Users must live in the native Teams dialer, and you need Zoom Phone recording, Zoom-side SMS, or a certified / DRaaS SBC path B. Zoom Phone Direct Routing Microsoft Teams Phone licensing plus the Zoom Phone for Microsoft Teams license. Native SMS inside Teams Calls is not automatic; see Zoom’s library note. A (no-SBC Operator Connect)
Users must use Zoom Phone UI inside Teams, without installing Zoom Workplace desktop as the calling engine C. Zoom Phone plug-in The plugin setting is off by default. Existing tenants stay on D until an admin enables it. A or B (native Teams dialer)
Users must have Zoom Meetings, Phone, and Whiteboard tabs inside Teams, and running Zoom Workplace in the background is acceptable D. Zoom Workplace for Teams Budget the desktop client (including silent start). GCC High / DoD phone-only app is not this commercial plug-in. C as if desktop were already gone, or A/B as if this were native Teams Phone
The tenant is GCC High or DoD Not A. Microsoft delivers Phone System there via Direct Routing. Zoom: no standalone Zoom Phone-only app; phone through the Workplace app. Verify the exact Zoom government environment. Commercial Operator Connect, commercial plug-in assumptions, or “it works the same”
SMS or fax is on the requirements list Not A. Point SMS at C/D (Zoom UI) or at B only with Zoom’s current SMS caveat. Fax in the Teams Zoom Phone widget is a Zoom UI feature, not Operator Connect. Write the surface: native Teams Calls vs Zoom Phone tab vs Zoom widget. A plus “SMS included”

If the checkbox cannot be completed, stop. The spoke article cannot rescue a quote that never named the architecture.

What not to mix

Phrases that collapse two architectures into one, and the correction.
Phrase on a quote Why it is wrong
“Zoom Operator Connect Direct Routing” Microsoft documents Operator Connect and Direct Routing as different PSTN models. One has no customer SBC. The other has a certified or DRaaS SBC in the path.
“Native Teams dialer with Zoom Phone tabs, no extra licenses” Native dialer is A or B and needs Teams Phone licensing. Tabs are C or D. Zoom documents a Microsoft Phone System license plus a Zoom license for Direct Routing.
“No desktop client, native Teams calling, SMS and fax included” No-desktop Zoom Phone UI is C. Native Teams calling is A or B. Operator Connect is not documented for SMS or fax. D still needs the desktop client for calling.
“Same design for GCC High” Microsoft: Phone System in GCC High and DoD is via Direct Routing. Zoom: no standalone Zoom Phone-only app in those Microsoft government environments.
“Zoom is in Microsoft’s Operator Directory, so OC is approved” Zoom announced Operator Connect. The live directory is the check. This page does not treat an announcement as a rendered listing.

How to choose, briefly

  1. If the non-negotiable is the native Teams Calls app, you are on A or B. Then ask whether a customer or DRaaS SBC is acceptable, whether SMS/fax is in scope, and whether you can confirm Operator Connect in Microsoft’s directory for the country.
  2. If the non-negotiable is Zoom Phone UI inside Teams, you are on C or D. Then ask whether Zoom Workplace desktop is allowed to run. If it is not, that is C, and an admin must enable the plug-in. If Meetings and Whiteboard tabs matter, that is D.
  3. If both native Teams calling and Zoom SMS in Teams are requirements, write two lines: PSTN architecture (A or B) plus Zoom UI supplement (C or D). Do not pretend they are one SKU.
  4. If the tenant is GCC High or DoD, discard A. Start from Microsoft Direct Routing plus Zoom’s government-environment notes, then read the Zoom for Government / CMMC article.

For coexistence, extension dialing, queues, E911 ownership, and the Direct Routing feature matrix, use the spoke. For bringing a carrier or PBX to Zoom Phone itself — a different problem than Teams PSTN — use BYOC vs BYOP.

Frequently asked questions

Can Zoom Phone work with Microsoft Teams?

Yes. Several models exist. Operator Connect and Zoom Phone Direct Routing use the native Teams dialer for PSTN. The Zoom Phone plug-in and Zoom Workplace for Teams put Zoom’s own UI inside Teams. They are not interchangeable.

What are the four Zoom and Microsoft Teams architectures?

A) Operator Connect: native Teams dialer, Zoom as PSTN operator, no customer SBC. B) Zoom Phone Direct Routing: native Teams dialer with a certified or DRaaS Session Border Controller path and more Zoom Phone features. C) Zoom Phone plug-in: Zoom Phone UI inside Teams without requiring the Zoom Workplace desktop client. D) Zoom Workplace for Teams: Meetings, Phone, and Whiteboard tabs inside Teams.

Is Operator Connect the same as Zoom Phone Direct Routing?

No. Microsoft documents them as different PSTN connectivity models. Operator Connect uses a Microsoft-certified operator and does not require the customer to deploy an SBC. Direct Routing connects Teams Phone through a certified Session Border Controller that you, an integrator, or a Direct-Routing-as-a-Service provider manage.

Does Operator Connect include SMS or fax?

Do not quote SMS or fax as Operator Connect capabilities. Microsoft’s Operator Connect documentation describes PSTN connectivity, number provisioning, and calling services. Zoom’s Operator Connect product page lists calling, number procurement into Teams admin center, no SBC, and PSTN coverage. Neither page documents SMS or fax as Operator Connect features.

Is Zoom listed in Microsoft’s live Operator Connect directory?

This article does not claim that. Zoom’s 20 July 2026 Zoom Phone release notes introduce Zoom for Microsoft Operator Connect. Microsoft’s planning page tells you to confirm participating operators in the Operator Connect directory. Check that live directory for your country before a quote treats Zoom as a certified Operator Connect operator.

Does Operator Connect work in GCC or GCC High?

Do not design Operator Connect into GCC High or DoD. Microsoft’s GCC High and DoD service description delivers Phone System and Audio Conferencing via Direct Routing, and states that PSTN Calling is not available in those environments.

Does the Zoom Phone plug-in require the Zoom Workplace desktop app?

No. Zoom’s Microsoft Teams configuration article points to the Zoom Phone plug-in as the phone-only experience that does not require the Zoom Workplace desktop app. Zoom’s 16 August 2026 Zoom Phone release notes describe a plugin-based Zoom Phone app, disabled by default, with existing customers remaining on the Workplace-app-dependent experience until the setting is enabled.

Is Zoom Workplace for Teams the same as the Zoom Phone plug-in?

No. Zoom Workplace for Teams is the in-app integration with Workplace, Meetings, Phone, and Whiteboard tabs. Zoom’s technical library still states that the Zoom desktop client must run in the background to place or receive Zoom Phone calls on that path. The plug-in is the separate phone-only Teams experience.

Can I mix these four architectures on one quote?

No. A quote should name one primary architecture. Mixing Operator Connect SBCs, Direct Routing SMS assumptions, plug-in desktop requirements, and Workplace tabs is how the wrong licenses and the wrong user experience get sold.

Where is the deeper Zoom Phone plus Teams operational article?

The spoke article Zoom Phone and Microsoft Teams together: what actually integrates? covers Direct Routing versus the in-app Zoom Phone experience, licensing, presence, E911, queues, and GCC High limits in operational detail. Use this page as the four-architecture hub, then that page for the Direct Routing and in-app spoke.

References

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

  1. Zoom — Release notes for Zoom Phone (KB0062333)— 20 July 2026: Introducing Zoom for Microsoft Operator Connect (eligible Zoom-managed numbers for Teams through Operator Connect; move numbers between Zoom Phone and Teams without onsite hardware). 16 August 2026: plugin-based Zoom Phone app for Microsoft Teams (disabled by default; existing customers remain on the Workplace-app-dependent experience). Also notes fax support in the Zoom Phone widget for Microsoft Teams as a Zoom UI feature, not as Operator Connect.
  2. Zoom — Zoom Workplace for Microsoft Teams— product page that names three deployment options: embedded Zoom Phone, Direct Routing, and Operator Connect. Direct Routing bullets include native Teams dialer, recording, SMS, business continuity, and no Teams Calling Plan. Operator Connect bullets include native Teams calling, number push into Teams admin center, no SBC, and PSTN coverage. Does not list SMS or fax under Operator Connect.
  3. Microsoft Learn — Plan for Operator Connect (ms.date 2026-08-24)— certified operator, Teams admin center, no customer SBC when you do not want to deploy and maintain your own, Operator Connect directory, Teams Phone licenses, Teams Only mode. Support boundaries: Microsoft owns Teams; the operator owns PSTN, numbers, calling services, and PSTN support.
  4. Microsoft Learn — PSTN connectivity options (ms.date 2026-07-31)— Calling Plan, Operator Connect, Teams Phone Mobile, and Direct Routing as separate models. Direct Routing: certified SBC procured, installed, and managed by you, an integrator, or a DRaaS provider.
  5. Microsoft Learn — Office 365 GCC High and DoD service description (ms.date 2026-08-03)— Phone System and Audio Conferencing for GCC High and DoD via Direct Routing. PSTN Calling not available in those environments. Do not design Operator Connect into GCC High or DoD from this page.
  6. Microsoft — Operator Connect directory— the live list Microsoft tells customers to use. This article does not assert that Zoom currently renders there.
  7. Zoom Technical Library — Zoom Phone for Microsoft Teams— Direct Routing as a service; not the in-app integration; native SMS inside the Teams client is not currently supported; Microsoft Phone System license plus a Zoom license required.
  8. Zoom — Managing Zoom Phone for Microsoft Teams (KB0057686)— native Teams app via Direct Routing; not the Zoom for Microsoft Teams app; no extra add-ons or plugins on that path; GCC High / DoD: no standalone Zoom Phone-only app.
  9. Zoom — Configuring Zoom for Microsoft Teams (KB0067825)— Workplace, Meetings, Phone, and Whiteboard tabs; GCC High / DoD notes; phone-only experience that does not require the Zoom Workplace desktop app is the Zoom Phone Plug-in.
  10. Zoom Technical Library — Zoom’s in-app integration for Microsoft Teams— Meetings, Phone, and Whiteboard in Teams; Zoom desktop client must run in the background to place or receive Zoom Phone calls on that path.
  11. Zoom — Using the Zoom Phone for the Microsoft Teams integration (KB0078701)— Zoom Workplace app used to route calls on the in-app Phone path; signed-in Workplace client required.
Prepared by ADAM Pulse (USA Telecom Consulting LLC)

Managed Zoom Phone and Microsoft Teams voice design, SDVOSB. We name one of these four architectures before anyone quotes licenses, SBCs, SMS, or a port date, and we do not treat a Zoom announcement as a live Operator Connect directory listing. Support: (888) 989-4872 · support@adampulse.us