Teams Phone emergency calling

For organisations using Teams Phone as their primary telephony, emergency calling is a critical capability. When someone dials 911 (US/CA), 112 (EU), 999 (UK), or other emergency numbers, the call must reach the right emergency services with the right location information. Getting it wrong creates legal liability and, more importantly, real-world risk.

How emergency calling works in Teams Phone

When a user dials an emergency number, Teams Phone:

1. Detects it's an emergency call based on country-specific dial patterns.
2. Determines the user's location from one of several sources (covered below).
3. Routes the call to a Public Safety Answering Point (PSAP) appropriate for that location.
4. Provides the location to the PSAP via the country's emergency-services protocol.
5. Optionally notifies internal security or designated responders that an emergency call has been placed.

The complexity is in step 2 — knowing where the user actually is when they dial.

Sources of location

For each user, Teams Phone uses location from one of:

Calling Plan / Operator Connect emergency locations

For users on Microsoft Calling Plans or Operator Connect, emergency locations are pre-registered in the Teams admin center per address. Each user has a default emergency address.

Dynamic emergency calling

For organisations operating multiple offices or where users are mobile, dynamic emergency calling detects the user's current network location and provides the corresponding emergency address automatically:

• Network sites define corporate networks by subnet, IP range, or BSSID.
• Network identifiers map network attributes to specific addresses.
• When a user dials emergency, Teams uses their current network to determine location.

This is essential for organisations with multiple buildings — if a user in Building A dials emergency, the call should reach Building A's emergency services, not the headquarters address.

Manual location confirmation

For roaming users on unknown networks (working from home, hotel, coffee shop), Teams can prompt the user to confirm their current address before completing the emergency call. The user's manually-entered address is used for routing and PSAP delivery.

Direct Routing emergency calling

For Direct Routing configurations, emergency calling is the customer's responsibility to configure correctly via the SBC and SIP carrier. Microsoft provides emergency-calling APIs and integration points, but the heavy lifting is in your telecoms configuration.

Country-specific requirements

Each country has its own emergency-services protocol:

• United States — E911 with specific federal regulations. Kari's Law (notification requirements), Ray Baum's Act (dispatchable location requirements).
• Canada — E911 with Canadian-specific PSAP integration.
• United Kingdom — 999 with location-based routing.
• European Union — 112 with E112 location requirements per country.
• Australia — 000 with specific routing requirements.

Microsoft Calling Plans cover specific countries; for other countries, Direct Routing or Operator Connect with local emergency-calling configuration is required.

Operational considerations

• Test emergency calling during deployment, but don't dial 911 / 112 for testing in production — those are real emergency services. Use Microsoft's test numbers or carrier-specific test paths.
• Network site definitions need ongoing maintenance — when offices open / close / change subnet ranges, emergency configuration must update.
• Roaming users on company devices — communicate the location-confirmation prompt; users should know to provide accurate information when prompted.
• Common Area Phones — emergency configuration applies per-device, fixed location.
• Compliance recording — Teams Phone with compliance recording captures emergency calls by default; verify regulatory implications.

Internal notification

A useful Teams Phone capability: emergency call notification alerts an internal contact list when emergency calls are placed. Reception, building security, or facilities can respond in parallel with emergency services.

Configured via emergency call routing policies in the Teams admin center. Typically configured to alert via email and SMS to designated security responders.

Documentation and audit

Every emergency-related configuration matters for legal compliance:

• Document the emergency calling design — which users on which carriers in which locations.
• Audit annually — re-verify configurations, addresses, network site definitions.
• Pre-deployment legal review in jurisdictions with strict E911 / E112 regulations.
• Post-incident review if emergency calling fails — failure to deliver location to PSAP is a serious finding.

For organisations relying on Teams Phone as their primary telephony, emergency calling is not an afterthought. Plan it deliberately; document carefully; audit annually. The cost of failure is too high to leave to chance.