Teams Phone E911
How E911 works with Microsoft Teams
Teams E911 succeeds when the tenant network map, LIS locations, emergency policies, PSTN route, and emergency-routing provider all agree about where the user is when 911 is dialed.
LIS
Network-to-location map
Teams can match Wi-Fi access points, switch ports, switches, and subnets to emergency locations.
Routing
Policy decides path
Emergency call routing policies attach to users and network sites, then drive emergency routes and notifications.
Users
Remote work needs prompts
Users may need to confirm or enter emergency addresses when they work away from trusted locations.
The Teams E911 call path
A Teams client starts by learning where it is. If the device connects on a known network, Teams can use the tenant’s network topology and Location Information Service data to match the endpoint to an emergency location. Microsoft documents the match order for LIS as wireless access point, Ethernet switch/port, Ethernet switch, then subnet.
When 911 is dialed, the client and Phone System policy decide the emergency behavior. The final call path depends on whether the organization uses Microsoft Calling Plans, Operator Connect, Teams Phone Mobile, or Direct Routing.
- Build trusted IP ranges and network sites.
- Populate LIS with subnets, WAP BSSIDs, switches, ports, and emergency addresses.
- Attach emergency call routing and emergency calling policies.
- Confirm the session border controller or operator path supports emergency calls and test numbers.
- Validate dispatchable location and internal notification evidence.
Direct Routing gotchas
Direct Routing gives enterprises control, but it also gives them more ways to fail. Emergency route patterns, online PSTN usage, session border controller behavior, and fallback routes must be explicit. Microsoft notes that Teams emergency calls no longer prepend a plus sign to emergency numbers, so route patterns must match the actual dial string.
- Do not assume the normal outbound route is acceptable for 911.
- Separate emergency routing from ordinary local calling.
- Check common area phones and Teams Rooms separately.
- Retest after session border controller certificate, trunk, dial-plan, carrier, or policy changes.
- Keep a 933/test-call workflow where the provider supports it.
Provider decision points
Teams E911 providers differ less on the slogan and more on operating details: how they ingest locations, how they validate addresses, how they handle nomadic users, how quickly changes propagate, and what evidence they return after tests.
- Certified Teams integration or validated Direct Routing pattern.
- Dynamic location routing support for office, hybrid, and remote users.
- Portal/API support for bulk location and phone number management.
- Alerting for security, front desk, or crisis teams.
- Exception handling if a call is missing a valid dispatchable location.