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.