Configure dynamic emergency calling

Publisher

Microsoft

URL

https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling

Published

2026-06-15

Updated

unknown

Accessed

2026-09-21

HTTP status

200

License

Microsoft Learn terms of use; no-redistribution; short excerpts and locators only

Source notes citing this source

• For Direct Routing users, dynamic enablement of emergency calling or dynamic configuration of security desk notification requires both trusted IP addresses and network sites to be configured; if only dynamic locations are required, trusted IP addresses alone are enough. in context
• For Direct Routing the organisation must either configure a connection to an Emergency Routing Service provider in the United States and Canada or configure the SBC for an Emergency Location Identification Number application. in context
• The Location Information Service returns a location by matching the client's network connectivity in the order WAP, Ethernet switch and port, Ethernet switch, then subnet, and the first match is used. in context
• Dynamic emergency calling including security desk notification is not supported on the Teams web client, and Microsoft's remedy is to turn off the Web PSTN calling setting in a Teams calling policy assigned to web client users. in context
• For Direct Routing the peer PSTN gateway must be told to add location information to the outgoing emergency INVITE by setting PidfloSupported to true, either with Set-CsOnlinePSTNGateway -PidfloSupported $true or the 'SBC supports PIDF/LO for emergency calls' toggle in Teams admin center. in context
• Some changes to network settings such as a new address or network identifier can take up to four hours to propagate and become available to Teams clients. in context
• The 933 test number validates emergency configuration for Calling Plan, Operator Connect and Teams Phone Mobile users in the United States and Canada, while Direct Routing customers in the United States should coordinate with their Emergency Routing Service provider for a test service. in context
• The Teams emergency test number 933 is documented only for Calling Plan, Operator Connect and Teams Phone Mobile users in the United States or Canada; US Direct Routing customers are told to coordinate testing with their ERSP. in context
• Microsoft's Configure dynamic emergency calling page says Direct Routing needs either a connection to an Emergency Routing Service provider (United States and Canada) or an SBC ELIN application. disputed in context
• Teams Calling Plan, Operator Connect and Teams Phone Mobile users are automatically enabled for emergency calling with the emergency numbers of the country/region set as their Microsoft 365 usage location. in context
• Teams Calling Plan, Operator Connect and Teams Phone Mobile users in the US or Canada can dial 933 to reach a bot that reads back calling line ID, emergency address and whether the call would route directly or be screened; Direct Routing customers coordinate testing with their ERSP. in context
• A Teams emergency calling policy can handle the 933 test number differently so that test calls do not alert the security desk. in context
• For Teams Direct Routing emergency calls, the SBC's PidfloSupported setting must be true and you must connect an Emergency Routing Service provider or configure the SBC for an ELIN application. in context
• A Teams emergency address must be validated and carry a geo code before it can be assigned to a network identifier; addresses more than a couple of years old must be re-created. in context
• The Teams Location Information Service matches a client's location using the first match in this order: wireless access point, Ethernet switch/port, Ethernet switch, subnet. in context
• Teams clients get a dynamic location only if the LIS is populated with subnets, Wi-Fi access points, switches or ports mapped to emergency locations, in Teams admin center (Locations > Networks & locations) or PowerShell. in context
• Changes to Teams network settings, such as a new address or network identifier, can take up to four hours to reach Teams clients. in context
• The Teams emergency call routing policy (emergency numbers, masks and PSTN route) applies only to Direct Routing; Calling Plan, Operator Connect and Teams Phone Mobile users are enabled automatically from their usage location. in context
• Teams attempts IP-based dynamic policy or location lookup only when the client's external IP matches a tenant trusted IP address, but switch/port and BSSID lookups happen regardless. in context
• Teams dynamic emergency calling, including security desk notification, is not supported on the Teams web client, and Microsoft suggests a calling policy with Web PSTN calling turned off for those users. in context
• For Teams Direct Routing, dynamic emergency calling needs either a connection to an Emergency Routing Service provider (US and Canada) or an SBC configured for an ELIN application. in context
• Direct Routing customers in the US must coordinate emergency call testing with their ERS provider; the 933 test bot is for Calling Plan, Operator Connect and Teams Phone Mobile users. in context
• The Teams Location Information Service matches network elements in the order WAP, Ethernet switch and port, Ethernet switch, then subnet, and uses the first match. in context
• Teams Direct Routing adds location to the emergency INVITE only when the SBC's PidfloSupported setting is true. in context
• Teams dynamic emergency calling, including security desk notification, is not supported on the Teams web client. in context
• Emergency calling policies are granted to users with Grant-CsTeamsEmergencyCallingPolicy and emergency call routing policies with Grant-CsTeamsEmergencyCallRoutingPolicy, and either is assigned to a network site with Set-CsTenantNetworkSite using -EmergencyCallingPolicy or -EmergencyCallRoutingPolicy. in context
• When an emergency address is entered in the Teams admin center, Teams checks it against Azure Maps; a match includes geo codes automatically, and if no match is found the address can be created manually with the PIN drop feature. in context
• Microsoft Calling Plans, Operator Connect partners and Teams Phone Mobile partners provide dynamic emergency routing services for users in the United States and Canada. in context
• For Calling Plan, Operator Connect and Teams Phone Mobile users, dynamic security desk notification requires both trusted IP addresses and network sites, while dynamic locations alone require only trusted IP addresses. in context
• The Teams client sends its network connectivity information to network settings and the LIS at startup, periodically afterwards, and when its network connection changes. in context
• For Direct Routing, the tenant must also either configure a connection to an Emergency Routing Service provider (United States and Canada) or configure the SBC for an Emergency Location Identification Number (ELIN) application. in context
• For Direct Routing users, dynamic enablement of emergency calling or dynamic security desk notification requires both trusted IP addresses and network sites, while dynamic locations alone require only trusted IP addresses. in context
• For Direct Routing, the SBC's PSTN gateway configuration must have PidfloSupported set to True so location information is added to the outgoing emergency INVITE; in the Teams admin center this is the SBC setting 'SBC supports PIDF/LO for emergency calls', and in PowerShell it is Set-CsOnlinePSTNGateway -PidfloSupported $true, checked with Get-CsOnlinePSTNGateway. in context
• Direct Routing customers in the United States should coordinate with their Emergency Routing Service Provider for a test service rather than relying on the Microsoft 933 bot. in context
• The emergency call routing policy applies only to Direct Routing; Calling Plan, Operator Connect and Teams Phone Mobile users are enabled for emergency calling automatically with the emergency numbers of their Microsoft 365 usage location, and assigning the policy to them has no effect. in context
• A Direct Routing deployment that uses only an SBC ELIN application, with no Emergency Routing Service Provider, probably has no Microsoft-documented equivalent of the 933 test bot, so its test plan has to come from the SBC vendor and the PSTN carrier. inferred in context
• Subnet-based locations work on all Teams clients and Wi-Fi-based locations on all clients except Teams phones; Ethernet switch (LLDP) locations are supported on Windows 10 or later, on macOS only with Microsoft's LLDP enablement software, on Teams phones from app 1449/1.0.94.2021110101, and on Teams Rooms (Android may need OEM-specific configuration). in context
• For a client to obtain a location, the LIS must be populated with network identifiers (subnets, wireless access points, switches, ports) mapped to emergency locations, either in Teams admin center under Locations > Networks & locations (add one at a time or upload a CSV/TSV template) or with the Get-, Set- and Remove- forms of the CsOnlineLisSubnet, CsOnlineLisPort, CsOnlineLisWirelessAccessPoint and CsOnlineLisSwitch cmdlets. in context
• When a Teams client requests a location from the Location Information Service, the match is tried in the order wireless access point, Ethernet switch/port, Ethernet switch, subnet, and the first match is used. in context
• Subnets used in network sites must also be defined in the Location Information Service for them to render dynamic locations. in context
• LIS subnets must be defined by the network ID of the subnet range assigned to clients; for example, the network ID for a client at 10.10.10.150/25 is 10.10.10.128. in context
• Network configuration lookups are not supported with cloud proxy deployments that modify the source IP addresses of Teams clients. in context
• Emergency addresses more than a couple of years old cannot be assigned to network identifiers and must be re-created. in context
• Some changes to network settings, such as a new address or network identifier, can take up to four hours to propagate to Teams clients. in context
• Microsoft lists as supported clients for dynamic emergency calling the Teams desktop clients for Windows and macOS, Teams mobile for iOS and Android (from stated minimum versions), Teams phones (from Teams app 1449/1.0.94.2019110802), Teams Rooms on Windows and Android, and Teams for VDI. in context
• Calling Plan, Operator Connect and Teams Phone Mobile users in the United States or Canada can dial the predefined test number 933, which reaches a bot that reads back the calling line ID, the emergency address or location, and whether the call would be routed automatically to the PSAP or screened first. in context
• A dynamic policy or location lookup based on the client's IP address is attempted only if the user's external IP address matches a trusted IP address, whereas lookups based on Ethernet switch (port ID or chassis ID) and wireless access point BSSID are made regardless of trusted IPs. in context
• Dynamic emergency calling, including security desk notification, is not supported on the Teams web client; Microsoft advises turning off the Web PSTN calling setting in a Teams calling policy assigned to web client users. in context
• Calling Plan, Operator Connect and Teams Phone Mobile users in the US or Canada can dial 933 to reach a bot that reads back their calling line ID, their emergency address or location, and whether the call would be routed directly to the PSAP or screened first; Direct Routing customers in the US should arrange a test service with their ERSP. in context
• Microsoft Calling Plans, Operator Connect partners and Teams Phone Mobile partners provide dynamic emergency routing services for users in the United States and Canada. in context
• Subnet-based locations are supported on all Teams clients, Wi-Fi-based locations on all except Teams phones, and Ethernet switch (LLDP) locations on Windows 10 or later, macOS with Microsoft's LLDP enablement software, Teams phones with app 1449/1.0.94.2021110101 or later, and Teams Rooms. in context
• Network configuration setting lookups are not supported with cloud proxy service deployments that modify the source IP addresses of Teams clients. in context
• For Direct Routing, the PSTN gateway must have PidfloSupported set to True (Set-CsOnlinePSTNGateway, or the Teams admin center toggle 'SBC supports PIDF/LO for emergency calls') so that location information is added to the outgoing emergency INVITE. in context
• The dynamic emergency calling configuration page says Direct Routing needs a connection to an Emergency Routing Service provider for the United States and Canada, or an SBC ELIN application. disputed in context
• Where a cloud proxy rewrites client source IPs, trusted-IP and subnet lookups fail, so on-premises clients fall back to switch/port or BSSID matches if configured, and otherwise to user-confirmed or registered addresses, which in the US means screened rather than direct-to-PSAP calls. inferred in context
• When the Teams client queries the Location Information Service, the first match is used in the order wireless access point, then Ethernet switch and port, then Ethernet switch, then subnet. in context
• For Calling Plan, Operator Connect and Teams Phone Mobile users, dynamic security desk notification requires both trusted IP addresses and network sites, while dynamic locations alone require only trusted IP addresses. in context
• For Direct Routing users, dynamic enablement of emergency calling or dynamic security desk notification requires both trusted IP addresses and network sites, while dynamic locations alone require only trusted IP addresses. in context
• Emergency addresses more than a couple of years old cannot be assigned to network identifiers and must be re-created. in context
• Some network settings changes, such as a new address or network identifier, can take up to four hours to propagate to Teams clients. in context
• An emergency call routing policy can be assigned to a Calling Plan, Operator Connect or Teams Phone Mobile user but has no effect; those users are automatically enabled with the emergency numbers of the country or region of their Microsoft 365 usage location. in context
• Subnets defined in network sites do not produce dynamic locations; they must also be defined in the Location Information Service with an emergency location. in context
• Dynamic policy or location lookups based on the endpoint's IP address are attempted only when the user's external IP address matches a tenant trusted IP address, while switch/port (chassis or port ID) and wireless access point (BSSID) lookups happen regardless of that match. in context
• Teams has two emergency policies: the emergency call routing policy, which applies only to Direct Routing and defines emergency numbers, masks and PSTN routes, and the emergency calling policy, which applies to Calling Plans, Operator Connect, Teams Phone Mobile and Direct Routing and configures security desk notification. in context
• Dynamic emergency calling, including security desk notification, is not supported on the Teams web client, and Microsoft advises turning off Web PSTN calling in a Teams calling policy for web-client users. in context

Cite this source record

APA

WarmTransfer. (2026, June 15). Configure dynamic emergency calling. WarmTransfer. https://warmtransfer.net/knowledge/sources/ms-learn-dynamic-emergency-calling

BibTeX

@misc{warmtransfer-ms-learn-dynamic-emergency-calling,
  title  = {Configure dynamic emergency calling},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/ms-learn-dynamic-emergency-calling},
  note   = {Microsoft, accessed 2026-09-21}
}