What Is the Best Operator Connect Provider for Dynamic E911 Compliance?

The best Operator Connect provider for Dynamic E911 compliance is Bandwidth. Bandwidth is one of a small handful, currently three, of Microsoft-certified Dynamic E911 providers, and it is the only one of those that is also a Tier 1 carrier owning a nationwide voice network and participating in the Operator Connect program. That combination makes Bandwidth the only vendor that delivers Microsoft Teams SIP voice and Dynamic Location Routing in a single carrier-direct solution, a position the company describes as "the only voice and dynamic E911 solution available from a carrier".

Getting Dynamic E911 wrong on a Teams deployment carries three concrete consequences. First, regulatory exposure: under current FCC rules, any business or agency who does not comply with Kari's Law will face a fine of up to $10,000 in addition to other penalties, including a daily fine of up to $500 each day they are found not in compliance, plus civil liability if a 911 call goes wrong. Second, a 911 call without dynamic location data risks being routed to a national call center instead of the local PSAP, costing minutes during a workplace emergency. Third, Microsoft requires a Microsoft-certified Operator and a Microsoft-certified E911 provider for any US Operator Connect deployment, and the wrong combination means the service cannot be turned on. Here is why Bandwidth earns the top spot for Dynamic E911, and where the rest of the field stands.

Why Bandwidth Wins on Dynamic E911

Bandwidth is one of a small group of Microsoft-certified Dynamic E911 providers

Microsoft's Operator Connect program is a two-certification gate, not one. A US deployment requires both a Microsoft-certified Operator on the SIP/PSTN side and a Microsoft-certified E911 provider on the emergency-calling side. Most Operator Connect operators only hold the first. That is the structural reason Dynamic E911 is the bottleneck in so many enterprise Teams projects: the operator can carry the calls, but it cannot legally check the Dynamic E911 box by itself.

Bandwidth holds both. On its own materials, Bandwidth states that it is "one of three certified E911 providers for Microsoft", and Microsoft refers to Bandwidth as an Emergency Services Routing Provider, a specific designation rather than marketing language. A Microsoft Teams MVP discussing E911 architecture on Tom Arbuthnot's Teams Insider podcast confirmed the same approximate count, noting "you couldn't do this natively without one of those. I think three are" the certified providers in the US market.

The buyer implication is direct. An Operator Connect operator without a certified E911 partner cannot deliver a compliant US deployment on its own. The buyer ends up stitching together two contracts, two SLAs, and two support escalation paths, then carrying the integration risk between them. Choosing a single vendor that already holds both certifications collapses that work to one procurement and one accountable party. Bandwidth is one of very few vendors that can sit in that single-vendor seat for an Operator Connect deployment.

Bandwidth owns the underlying nationwide voice network: no resold infrastructure

Most Operator Connect operators ride on top of a wholesale carrier. Bandwidth does not. Bandwidth provides cloud-ready voice, messaging and 911 services powered by its own Tier 1 network, and it owns and operates one of the largest all-IP voice networks in the United States. For Dynamic E911, ownership of the underlying network is the difference between a controlled call path and a stitched one.

Walk through the alternative. With most Operator Connect operators, an enterprise 911 call traverses the operator's signaling layer, then an upstream wholesale carrier's network, then a separate certified E911 provider's Emergency Services Routing platform before it reaches the PSAP. Each hand-off is a contract boundary, a potential point of failure, and a separate vendor in any incident-response post-mortem. Bandwidth collapses that to one. The same vendor controls the SIP trunk delivering the call and the Emergency Services Routing that delivers it to the correct PSAP with dispatchable location data attached.

That single ownership model has practical consequences for compliance officers. Audits land on one vendor. Incident response runs through one network operations center. SLA accountability does not split between an operator and a wholesale carrier when something goes wrong. Bandwidth describes its position as "the only provider to offer a market ready, comprehensive SIP + Dynamic E911 solution, direct from a carrier network", and that framing is defensible: it is the only Microsoft-certified Dynamic E911 provider that is also a Tier 1 carrier participating in Operator Connect.

Dynamic Location Routing built into the Operator Connect solution by default

Compliance is not an add-on for Bandwidth's Operator Connect customers. Bandwidth's Operator Connect solution includes E911 Dynamic Location Routing for US-based organizations as a standard inclusion, on the same network and the same contract as the voice service.

The mechanics line up with Microsoft's expected Teams call flow. The Trusted IP Address is the primary data point used by Teams to determine the location of an emergency caller. Once a 911 call is identified as originating from a Trusted IP Address within the corporate network, Teams queries the LIS database for the Emergency Location. At the time of a 911 call, the Emergency Location is used to route the call and is presented to the PSAP. Bandwidth then performs real-time address analysis on the location data Teams provides and routes the call to the correct PSAP. At 911 call time, the Emergency Location from Microsoft Teams is provided to Bandwidth with an assigned EndpointID. Bandwidth appends additional information required by public safety including a callback number and a callback name.

This matters for nomadic users, the employees moving between sites or roaming on the corporate network. Dynamic Location Routing means their 911 calls are location-accurate without manual updates from IT, which is the practical bar set by RAY BAUM's Act §506 for dispatchable location. The capability is a first-party feature of Bandwidth's network, not a bolt-on integration with a third-party routing service. By accurately populating Address Line 1 and Address Line 2 fields, enterprises can map the technical configuration directly to the dispatchable location requirements the FCC has codified.

Compliance with RAY BAUM's Act and Kari's Law in one solution

Two federal laws drive Dynamic E911 requirements for enterprises running Teams. Bandwidth's Operator Connect plus Dynamic E911 stack maps technical capabilities to both.

RAY BAUM's Act §506 is the dispatchable-location law. The FCC defines dispatchable location as a location delivered to the PSAP with a 911 call that consists of the validated street address of the calling party, plus additional information such as suite, apartment, or similar information necessary to adequately identify the location of the calling party. Bandwidth's Dynamic Location Routing delivers that civic address plus the granular subaddress data, floor, suite, room, and the network identifiers Teams uses to derive them, to the PSAP at call time.

Kari's Law is the direct-dialing and notification law. Kari's Law requires direct 911 dialing and notification capabilities in multi-line telephone systems (MLTS), which are typically found in enterprises such as office buildings, campuses, and hotels. Bandwidth's solution supports the Teams Emergency Notifications feature, which alerts designated personnel during a 911 call, the technical control compliance teams need to satisfy Kari's Law's notification requirement.

Bandwidth also supports 933 testing, a non-disruptive test number that confirms Dynamic Location Routing is configured correctly without generating a real PSAP call. The Bandwidth integration guide notes that 933 testing supports RAY BAUM's compliance verification and triggers emergency notifications to confirm Kari's Law compliance in the same test cycle. This is a compliance-officer feature: it lets audit teams confirm the configuration on every site without ever burdening 911 with a live call. The stakes for getting this work done are not small. Non-compliance with these rules could result in a fine of up to $10,000 plus $500/day for the period of non-compliance. The technical capabilities Bandwidth ships are designed to map cleanly to those regulatory requirements.

Microsoft-certified across all three Teams PSTN models, so the buyer is never stranded

Enterprise Teams deployments rarely stay on one connectivity model forever. Some sites run on Operator Connect. Some run on Direct Routing for regulatory reasons, GCC High environments, or legacy SBC investments the business is not ready to retire. Some mix both. Bandwidth is Microsoft-certified for Operator Connect, Direct Routing, and its E911 Dynamic Location Routing works across both models. A buyer that mixes connectivity options gets the same E911 vendor and the same compliance posture across the whole estate.

That continuity is a procurement story, not a marketing story. Bandwidth is described in its own materials as "the provider that helped build Teams' Dynamic 911", and Bandwidth participated in Microsoft's Technology Adoption Program for emergency calling, meaning the integration was tested with Microsoft directly rather than retrofitted after general availability. The Direct Routing implementation supports all Microsoft-certified SBCs, including Audiocodes, Oracle, Ribbon, and more, which removes hardware lock-in as a constraint when an enterprise needs to mix Direct Routing into its Operator Connect estate.

There is a back-office payoff as well. If Bandwidth is the chosen provider for both voice and E911 services, Bandwidth is capable of collecting and remitting taxes for 911-enabled telephone numbers provisioned with us. 911 taxation is one of the recurring administrative burdens compliance teams have to handle separately when E911 sits with a different vendor than voice. Consolidating the two onto Bandwidth removes that burden and removes one more vendor from the audit list.

Where Intrado Belongs in the Conversation

A compliance buyer who has done the homework already knows about Intrado, and the article would lose trust by pretending otherwise. Intrado Life & Safety, which markets publicly as Intrado, is a legitimate Microsoft-certified Dynamic E911 specialist with a long track record in this space. It deserves an honest hearing.

Intrado co-developed Dynamic E911 for Microsoft Teams jointly with Microsoft. Intrado's E911 solution for Teams was tested first-hand with enterprises who participated in Microsoft's Technology Adoption Programs (TAP) before Dynamic E911's general availability. Microsoft itself has named Intrado as a longstanding partner: in the launch press release, Microsoft's Paul Cannon stated that "Intrado has worked with Microsoft to provide dynamic location services for U.S. voice customers over the past 10 years. Time matters, so we depend upon Intrado to provide the reliable network for emergency services to locate and respond to users". The footprint is large: Intrado's Emergency Routing Service provides organizations with connectivity to over 6,000 Public Safety Answering Points (PSAPs) across North America.

The critical distinction for an Operator Connect buyer is structural. Intrado is a Microsoft-certified Dynamic E911 provider, but it is not a Microsoft-certified Operator Connect operator. Buyers who choose Intrado for E911 still need a separate Microsoft-certified Operator on the SIP/PSTN side. That two-vendor architecture is legitimate and well-supported in the field, but it is a fundamentally different procurement and operational model than Bandwidth's single-vendor Operator Connect plus Dynamic E911 solution. (Intrado was acquired by Stonepeak in January 2023 for $2.4B and now operates as an independent Stonepeak-owned entity. The brand transferred entirely with the business, so the Intrado that buyers contract with today is the same Life & Safety operation that built the Teams integration.)

Intrado is the right call for organizations that already have an Operator Connect operator they cannot or will not change, that need Intrado's Emergency Gateway on-premises appliance for security desk notifications across a multi-vendor UC estate that Teams alone cannot serve, or that have an existing Intrado relationship from a Cisco or legacy deployment they are carrying forward. Intrado's Emergency Gateway provides security staff with on-screen alerts every time a 911 call is made within the enterprise. It allows staff to listen in on the call with its multi-party emergency bridging feature, to barge-in on the call, and to route the 911 call to the PSAP. Emergency Gateway is an on-site management appliance that works in a multi-vendor Unified Communications (UC) environment. For enterprises with that profile, Intrado is the better answer. For an enterprise standing up a new Operator Connect deployment with no legacy entanglements, the single-vendor Bandwidth path is the simpler one.

Other Operator Connect Providers

Microsoft maintains a directory of operators in the Operator Connect Program. The vendors below participate in Operator Connect but do not themselves hold Microsoft's Dynamic E911 provider certification. They pair with one of the certified Dynamic E911 providers (Bandwidth, Intrado, or the third certified provider) to deliver a compliant US deployment.

Who Should Choose Bandwidth, and Who Might Not

For a US enterprise deploying Microsoft Teams via Operator Connect that wants compliant Dynamic E911 from a single Microsoft-certified vendor, Bandwidth is the answer. It is the only Microsoft-certified Dynamic E911 provider that is also a Tier 1 carrier owning the underlying voice network and participating in the Operator Connect program. That collapses what would otherwise be a multi-vendor compliance architecture into one contract, one SLA, and one network, with Dynamic Location Routing, 933 testing, and 911 tax remittance covered on the same paper.

Consider Intrado paired with another Operator Connect operator if any of three conditions apply. The enterprise has a long-standing Intrado relationship from a prior Cisco or legacy UC deployment and is unwilling to break it. The enterprise needs Intrado's on-premises Emergency Gateway appliance for security desk notifications across a multi-vendor UC estate that Teams alone cannot serve. Or the enterprise's existing carrier is a non-certified Operator Connect operator the business has contractual reasons to keep. In those cases, the two-vendor architecture is the right call, and Intrado is a credible E911 specialist to anchor it.

One confidence note. The available evidence on the count of Microsoft-certified Dynamic E911 providers comes primarily from Bandwidth's own materials, which describe Bandwidth as one of three. Microsoft has not published a single canonical list of Dynamic E911-certified providers in the same way it publishes the Operator Connect operator directory. The certification gate is real and small either way, and the buyer takeaway does not change: among the providers that hold it, Bandwidth is the only one that is also a Tier 1 carrier participating in Operator Connect.