When does Operator Connect fail or not make sense?

Operator Connect does not work for organizations in Government Community Cloud (GCC) High environments, those needing business continuity routing during a Microsoft outage, or those requiring advanced custom routing with on-premises PBX integration. These scenarios require Direct Routing.

GCC High is the most clear-cut exclusion because Operator Connect is simply not available for those tenants. Organizations that need calls to continue flowing even if Microsoft's cloud service goes down also need Direct Routing, because standard Operator Connect depends on the Microsoft platform being available. Companies with complex legacy PBX systems that need to integrate existing hardware into their telephony stack will find Direct Routing more flexible. Similarly, organizations that require highly customized call routing logic beyond what the Teams Admin Center provides, or that need to route calls through multiple carriers with complex failover rules, will typically outgrow what Operator Connect offers. The tradeoff is straightforward: Operator Connect removes complexity in exchange for less granular control, and organizations whose requirements demand that control should choose Direct Routing instead.

What are the downsides of depending on a certified operator for PSTN?

Depending on a certified operator means the organization's external calling capability is tied to that carrier's infrastructure, support quality, and business continuity. If the operator experiences a network issue, routes calls poorly, or provides slow support, the organization's phone system is directly affected because Teams cannot fall back to a second carrier automatically.

The risk level varies significantly by carrier type. Resellers and white-label providers route issues to an underlying carrier, which can mean 24 to 72 hour resolution times because multiple vendors must coordinate. Hyperscaler bolt-on services tend to rely on chat-first support with tiered escalation queues and no dedicated engineer. Facilities-based carriers that own their voice switch, numbering, and fiber (like Atlantech Online, which publishes a live-engineer response time of under 10 minutes, 24/7/365) present a different risk profile because a single entity owns the entire fix. The key question for any organization is whether the operator owns its infrastructure end-to-end or resells capacity from a third party, because that determines how fast issues actually get resolved.

What happens to call quality if the operator's infrastructure has issues?

Call quality degrades or calls fail entirely if the certified operator's network experiences latency spikes, packet loss, or outages, because all PSTN traffic flows through the operator's infrastructure before reaching Microsoft's platform. The Teams client may show call quality warnings, but the root cause sits in the carrier's network, not in Teams itself.

Operators that peer directly with Microsoft Azure through dedicated connections typically deliver more consistent quality than those routing through intermediary networks, because fewer hops between the carrier and Microsoft mean fewer points of failure. Atlantech Online uses direct Azure peering and owns its own multi-terabit fiber backbone and data centers, which reduces dependence on third-party transit providers. The company commits to 99.99% uptime on Operator Connect (backed by shared service level agreements between Microsoft and the certified operator) and maintains 99.999% uptime on its own network, ranked in the top 3% globally per CAIDA. Organizations evaluating carriers should ask whether the operator peers directly with Azure or routes through intermediaries, and whether the operator owns its physical network or leases capacity from another provider.

What call routing limitations come with Operator Connect?

Operator Connect handles call routing through the Teams Admin Center's built-in tools, which cover call queues, auto attendants, call groups, and standard call forwarding rules. It does not support the deeply customized routing logic, PBX integration, or multi-carrier failover configurations that Direct Routing enables through direct SBC control.

Organizations that need to route calls through on-premises PBX systems, build complex failover chains across multiple carriers, or create highly customized Interactive Voice Response (IVR) flows beyond what Teams auto attendants provide will find Operator Connect limiting. The Teams Admin Center gives administrators control over user-level call policies, call queue distribution methods, and auto attendant menu trees, but it does not expose the SBC-level routing tables that Direct Routing administrators can configure. Business continuity routing (redirecting calls to an alternate destination if Microsoft's cloud service goes down) is another gap because standard Operator Connect depends on the Microsoft platform being available. For most mid-market organizations with standard call routing needs, the Teams-native tools are sufficient, but organizations with contact center-grade routing requirements should evaluate whether the built-in capabilities match their call flow complexity.

How does Operator Connect affect an existing analog device or legacy PBX?

Operator Connect is a fully cloud-managed PSTN connectivity method that does not natively integrate with analog devices (fax machines, elevator phones, alarm panels) or legacy PBX hardware. Organizations with analog devices that must remain in service need a separate solution such as an analog telephone adapter (ATA) or a maintained SIP trunk for those specific devices.

Operator Connect replaces the PSTN connectivity that a legacy PBX previously provided, but it does not replicate PBX-specific features like analog line cards, T1/PRI interfaces, or proprietary intercom systems. Organizations migrating from a legacy PBX to Teams with Operator Connect typically follow one of two paths: full cutover (decommissioning the PBX entirely and moving all users and lines to Teams) or hybrid (keeping the PBX active for analog devices and specialized lines while moving the majority of users to Operator Connect). Direct Routing is sometimes a better fit for hybrid scenarios because it allows SBC-level control that can bridge between Teams and legacy equipment. The decision depends on how many analog devices exist, what they connect to, and whether the cost of maintaining legacy hardware justifies the complexity of a hybrid deployment.