Plan and configure dynamic emergency calling

Dynamic emergency calling for Microsoft Calling Plans and Phone System Direct Routing provides the capability to configure and route emergency calls and notify security personnel based on the current location of the Teams client.

Based on the network topology that the tenant administrator defines, the Teams client provides network connectivity information in a request to the Location Information Service (LIS). If there's a match, the LIS returns a location to the client. This location data is transmitted back to the client.

The Teams client includes location data as part of an emergency call. This data is then used by the emergency service provider to determine the appropriate Public Safety Answering Point (PSAP) and to route the call to that PSAP, which allows the PSAP dispatcher to obtain the caller's location.

For dynamic emergency calling, the following must occur:

  1. The network administrator configures network settings and the LIS to create a network/emergency location map.

    For Direct Routing, additional configuration is required for routing emergency calls and possibly for partner connectivity. The administrator must configure connection to an Emergency Routing Service (ERS) provider (United States) OR configure the Session Border Controller (SBC) for an Emergency Location Identification Number (ELIN) application.

  2. During startup and periodically afterwards, or when a network connection is changed, the Teams client sends a location request that contains its network connectivity information to the network settings and the LIS.

    • If there's a network settings site match – emergency calling policies are returned to the Teams client from that site. (For more information about policies, see Configure emergency policies).

    • If there's an LIS match – an emergency location from the network element the Teams client is connected to is returned to the Teams client. The match is performed in the following order with the first matched result being returned:

      • WAP
      • Ethernet switch/port
      • Ethernet switch
      • Subnet
  3. When the Teams client makes an emergency call, the emergency location is conveyed to the PSTN network.

    For Direct Routing, the administrator must configure the SBC to send emergency calls to the ERS provider or configure the SBC ELIN application.

This article contains the following sections.

The ability to do automatic routing to the appropriate Public Safety Answering Point (PSAP) varies depending on the country of usage of the Teams user.

For more information about emergency calling, including information about emergency addresses and emergency call routing, information specific to countries, and information about network settings and network topology, see the following:

Supported clients

The following clients are currently supported. Check back often to see updates to this list.

  • Teams desktop client for Microsoft Windows
  • Teams desktop client for Apple macOS
  • Teams mobile client for Apple iOS client version and App Store version 1.0.92 and greater
  • Teams mobile client for Android client and Google Play store version 1416/ and greater
  • Teams phone version 1449/ and greater
  • Teams Rooms version and greater


Dynamic emergency calling including security desk notification isn't supported on the Teams web client. To prevent users from using the Teams web client to call PSTN numbers, you can set a Teams calling policy and turn off the Allow web PSTN calling setting. To learn more, see Calling policies in Teams and Set-CsTeamsCallingPolicy.

Assign emergency addresses

You can assign emergency addresses to both Calling Plan users and to the network identifiers that are required for dynamically obtaining a location. (Subnet and WiFi AP are supported. Ethernet switch/port is supported on Windows 8.1 and later at this time).

To support automated routing of emergency calls within the United States, you must ensure that the emergency locations that are assigned to network identifiers include the associated geo codes. (Emergency addresses without geo codes can't be assigned to the network identifiers that are required for dynamic locations.)

Azure Maps is used for location-based services. When you enter an emergency address by using the Microsoft Teams admin center, Teams checks Azure Maps for the address:

  • If a match is found, the geo codes are automatically included.

  • If a match isn't found, you will have the opportunity to manually create an emergency address. You can use the PIN drop feature to do this.

This means that if an existing emergency location that is created for assigning to Calling Plan users is intended for a dynamic location, the same address needs to be re-created to include the geo codes. To distinguish between the two locations, you should include a different description. The new emergency location can be assigned to the users who have the old location. When fully migrated, the old location can be deleted.

You add and assign emergency addresses in the Microsoft Teams admin center or by using PowerShell. For more information, see Add an emergency location for your organization and Assign an emergency location for a user.

Configure network settings

Network settings are used to determine the location of a Teams client, and to dynamically obtain emergency calling policies and an emergency location. You can configure network settings according to how your organization wants emergency calling to function.

Network settings include sites that include a collection of subnets and these are used exclusively for dynamic policy assignment to users. For example, an emergency calling policy and an emergency call routing policy might be assigned to the "Redmond site" so that any user that roams from home or another Microsoft location is configured with emergency numbers, routing, and security desk specific to Redmond.


Subnets can also be defined in LIS and can be associated with an emergency location.

Keep the following definitions in mind. For more information, see Network settings for cloud voice features.

  • Trusted IP addresses contain a collection of the internet external IP addresses of the enterprise network and are used to determine if the user's endpoint is inside the corporate network. An attempt to obtain a dynamic policy or location will only be made if the user's external IP address matches an IP address in the trusted IP address. A match can be made against either IPv4 or IPv6 IP addresses and is dependent upon the format of the IP packet sent to the network settings. (If a public IP address has both IPv4 and IPv6, you need to add both as trusted IP addresses.)

  • A network region contains a collection of network sites.

  • A network site represents a location where your organization has a physical value, such as an office, a set of buildings, or a campus. These sites are defined as a collection of IP subnets.

  • A network subnet must be associated with a specific network site. A client's location is determined based on the network subnet and the associated network site.

You configure network settings in the Microsoft Teams admin center or by using PowerShell. To learn more, see Manage your network topology for cloud voice features.

Note that it can take some time (up to a couple of hours) for some changes to network settings (such as a new address, network identifier, and so on) to propagate and be available to Teams clients.

For Calling Plan users:

  • If dynamic configuration of security desk notification is required, you must configure both trusted IP addresses and network sites.

  • If only dynamic locations are required, you must configure only trusted IP addresses.

  • If neither are required, configuring network settings isn't required.

For Direct Routing users:

  • If dynamic enablement of emergency calling or dynamic configuration of security desk notification is required, then you must configure both Trusted IP addresses and network sites.

  • If only dynamic locations are required, you must configure only trusted IP addresses.

  • If neither are required, configuring network settings isn't required.

Configure Location Information Service

A Teams client obtains emergency addresses from the locations associated with different network identifiers. Both subnets and wireless access points (WAPs) are supported. Ethernet switch/port is supported on Windows 8.1 and later at this time.

For a client to obtain a location, you must populate the LIS with network identifiers (subnets, WAPs, switches, ports) and emergency locations. You can do this in the Microsoft Teams admin center or by using PowerShell.

Using the Microsoft Teams admin center

  1. In the left navigation, go to Locations > Networks & locations.
  2. Click the tab that represents the network identifier that you want to add. For example, click Subnets, Wi-Fi access points, Switches, or Ports. Then click Add.
  3. Complete the fields, add an emergency location, and then click Apply.

Using PowerShell

Use the following cmdlets to add ports, switches, subnets, and WAPs to the LIS.


If subnets are being used as part of network sites, they must be redefined in the Location Information Service to render dynamic locations.

Configure emergency policies

Use the following policies to configure emergency calling. You can manage these policies in the Microsoft Teams admin center or by using PowerShell.

  • Emergency call routing policy – Applies only to Direct Routing. This policy configures the emergency numbers, masks per number if desired, and the PSTN route per number. You can assign this policy to users, to network sites, or to both. (Calling Plans Teams clients are automatically enabled for emergency calling with the emergency numbers from the country based upon their Microsoft 365 or Office 365 usage location.) To learn more, see Manage emergency call routing policies for Direct Routing.

  • Emergency calling policy - Applies to Calling Plans and Direct Routing. This policy configures the security desk notification experience when an emergency call is made. You can set who to notify and how they are notified. For example, to automatically notify your organization's security desk and have them listen in on emergency calls. This policy can either be assigned to users or network sites or both. To learn more, see Manage emergency calling policies in Teams.

Enable users and sites

You can assign emergency call routing policies and emergency calling policies to users and to sites. Keep in mind that emergency call routing policies apply to Direct Routing only. (Although it's possible to assign this policy to a Calling Plan user, the policy will have no effect.)

You assign policies in the Microsoft Teams admin center or by using PowerShell. To learn more, see:

Here's some PowerShell examples.

To enable a specific user for security desk notification, use the following command:

Grant-CsTeamsEmergencyCallingPolicy -Identity user1 -PolicyName SecurityDeskNotification

To assign a policy called "Contoso Emergency Calling Policy 1" to Site 1, use the following command:

Set-CsTenantNetworkSite -identity "site1" -EmergencyCallingPolicy "Contoso Emergency Calling Policy 1"

To enable a specific Direct Routing user for emergency calling, use the following command:

Grant-CsTeamsEmergencyCallRoutingPolicy -Identity user1 -PolicyName UnitedStates

To assign a policy called "Contoso New York Emergency Call Routing" to Site 1, use the following command:

Set-CsTenantNetworkSite -identity "site1" -EmergencyCallRoutingPolicy "Contoso New York Emergency Call Routing"

If you assigned an emergency calling policy to a network site and to a user, and if that user is at that network site, the policy that's assigned to the network site overrides the policy that's assigned to the user.

Test emergency calling

Some Emergency Routing Service Providers (ERSPs) in the United States offer an emergency calling test bot.

  • Calling Plan users in the United States can use the predefined test emergency number 933 to validate their emergency calling configuration. This number is routed to a bot, which then echoes back the caller phone number (calling line ID), emergency address or location, and whether the call would be automatically routed to the PSAP or screened first.

  • Direct Routing customers in the United States should coordinate with their ERSP for a test service.