In highly regulated markets, communication service providers (CSPs) face a serious challenge: enabling Microsoft Teams telephony while meeting strict compliance requirements, especially for emergency calling. Whether you’re serving enterprise customers across the U.S., Europe, or globally, ensuring precise location reporting and emergency call routing is more than a best practice, it’s the law.
Direct Routing has emerged as a powerful solution, giving providers the flexibility to integrate Microsoft Teams with PSTN services while maintaining full control over routing policies, location data, and compliance mechanisms.
“It’s down to that level of detail, which office block you’re on, which floor,” explains Akshay John, Head of Engineering at Dstny Global Services. “Microsoft makes that possible when configuring users within the tenant.”
Why Compliance is Critical — and Complex
In the U.S., mandates like the RAY BAUM’s Act, which require dispatchable location information (e.g., building, floor, room) to be automatically transmitted with 911 calls, impose strict obligations on enterprises and service providers.
Europe has similar mandates under the European Electronic Communications Code (EECC), requiring access to emergency services with accurate location information.
This includes both network-based and handset-derived location data.
Regulations can also vary by country, for instance, in Germany, France, and Sweden, emergency calls are routed based on the caller’s registered address stored in a national Emergency Database (EDB).
This necessitates that organizations maintain up-to-date location information for their users to ensure compliance and effective emergency response.
Akshay highlights the implications, “One of the key requirements for any service provider offering numbers is that they can make and receive emergency calls to that number. The same applies for Direct Routing, and the U.S. is particularly sensitive to this.”
How Direct Routing Supports Compliance
With Direct Routing, CSPs can configure emergency calling behavior within Microsoft Teams while using their own infrastructure and numbering plans. This flexibility is essential in global or multi-region deployments.
“We had to build in a special capability where we can route those emergency calls directly over to the emergency response provider,” says John. “Especially for those providers whose downstream equipment is not able to handle this extra information coming in from Microsoft.”
This ensures critical information isn’t dropped — a key compliance and safety concern.
Handling the Technical Complexity
Emergency calling via Teams involves multiple technical layers:
- Defining Emergency Locations in Microsoft 365 Admin Center.
- Mapping Network Topologies to user locations — including Wi-Fi access points or subnet IDs.
- Assigning Emergency Policies — which determine how and where calls are routed.
These configurations ensure accurate location detection and proper routing to local Public Safety Answering Points (PSAPs).
However, not all downstream equipment supports Microsoft’s enhanced emergency data. Akshay notes, “The downstream PBX wouldn’t recognize this, and the call would bomb out. So, we built a mechanism that ensures calls route successfully regardless.”
This middleware approach is key — and a huge value proposition for Dstny ‘s partners.
Multi-Region, Multi-Compliance
Compliance isn’t just a checkbox for CSPs operating across borders — it’s a labyrinth of obstacles that must be navigated appropriately. The choice is also a simple one, do you have the depth of expertise to manage each individual region, understand the landscape, and pockets deep enough to deploy kit?
Akshay explains. “Do you want to actually go into each region, deploy equipment over there… or do you want to leverage a middleware provider like Dstny?”
With Dstny’s co-location with Microsoft across major global PoPs (Points of Presence), partners don’t need to invest in local infrastructure to ensure compliance. Everything from routing to emergency call handling is abstracted and streamlined.
“No one would even know that you don’t have any equipment on site,” John says.
Compliance Risks Are Real
According to a 2023 report by Nemertes Research, 72 percent of enterprises deploying Microsoft Teams telephony in North America faced regulatory challenges tied to emergency calling. Another study by Frost & Sullivan found that lack of compliance was a top reason for delaying cloud telephony rollouts in regulated sectors like healthcare and finance.
Dstny’s approach is to build compliance into their Direct Routing service to directly address this barrier.
Tools & Monitoring for Long-Term Success
Meeting compliance requirements once isn’t enough, it must be maintained. Direct Routing, when done right, includes tools for real-time monitoring and diagnostics.
“Microsoft have gone even further by making these dashboards and SLA metrics available within Microsoft Teams itself,” said John. “You can pull data on quality, location handling, and emergency call records via API.”
This helps providers generate audit-ready reports, proving compliance over time — something regulators increasingly demand.
In today’s complex regulatory landscape, Direct Routing gives CSPs the power to stay compliant, global, and agile — especially when paired with a partner like Dstny that handles the heavy lifting.
“They don’t have to invest in the technology,” John emphasizes. “We’ve learned through our experience and made that available as an option for them.”
