# Teams emergency calling and location policies Canonical: https://warmtransfer.net/knowledge/teams-emergency-calling Last verified: 2026-09-24 Teams emergency calling policies control security-desk notifications and call-in conferencing across Calling Plan, Operator Connect, Teams Phone Mobile, and Direct Routing deployments[^58][^59][^54]. Dynamic emergency location capabilities determine how endpoint network data or user input resolves to a dispatchable civic address and routes to public safety answering points (PSAPs)[^3][^18]. ## Policy Types and Precedence Microsoft Teams provides two distinct emergency policy types[^54]: - **Emergency calling policy:** Configures security desk notifications and applies to Calling Plans, Operator Connect, Teams Phone Mobile, and Direct Routing[^58][^54]. - **Emergency call routing policy:** Defines emergency numbers, dial masks, and PSTN voice routes, and applies only to Direct Routing[^54]. While an emergency call routing policy can be assigned to Calling Plan, Operator Connect, or Teams Phone Mobile users, it has no effect on them; those users are automatically enabled with the emergency numbers of the country or region of their Microsoft 365 usage location[^47]. When Shared Calling is used with Calling Plans or Operator Connect, emergency call routing policies only identify emergency numbers, and site-assigned emergency call routing policies cannot be used if Shared Calling for Calling Plans or Operator Connect coexists with Direct Routing in the same tenant[^50]. Users automatically receive the global (Org-wide default) emergency calling policy unless a custom policy is assigned[^30]. The global policy can be edited but cannot be renamed or deleted, whereas network sites require custom policies[^30]. When an emergency calling policy is assigned both to a network site and to a user who is located at that site, the site's policy overrides the user's policy[^60][^51]. For Direct Routing, Teams applies the network site's emergency call routing policy if present[^23]. It falls back to the user's policy if the site has no policy, the client is at an undefined site, or the dialed number matches none of the site policy's configured numbers; if no policy can be obtained, the user is not enabled for emergency calling[^23]. ## Direct Routing Emergency Setup A Direct Routing emergency call routing policy holds a Dynamic emergency calling toggle and 1 or more emergency numbers[^46]. Each emergency number defines an emergency dial string, 0 or more semicolon-separated dial masks, and a PSTN usage record that selects the route[^46]. The policy references an online PSTN usage, and an OnlineVoiceRoute matching the dial string must reach the intended PSTN gateways[^21]. Teams clients do not prepend a '+' in front of emergency numbers (such as +911) on Direct Routing, requiring voice route patterns to match the number without a '+' prefix[^38]. For dynamic emergency location delivery, the PSTN gateway must have PidfloSupported set to True (using Set-CsOnlinePSTNGateway or the "SBC supports PIDF/LO for emergency calls" toggle in Teams admin center), which adds location information to the outgoing SIP INVITE[^22]. Sources disagree on the geographic scope of Emergency Routing Service Providers (ERSPs) for Direct Routing: the dynamic emergency calling configuration documentation states that Direct Routing requires an ERSP connection or an SBC ELIN application for the United States and Canada, whereas the Direct Routing considerations documentation lists ERSPs as a United States-only option, alongside ELIN applications[^25][^26]. Microsoft lists Bandwidth Dynamic Location Routing, Intrado Emergency Routing Service, and Inteliquent as certified and supported 911 service providers for Direct Routing in the US, and may reject support cases that involve non-certified providers[^8]. When using an SBC Emergency Location Identification Number (ELIN) application, emergency addresses and ELIN numbers are configured in the application and uploaded to the PSTN emergency database[^24]. On an emergency call, the ELIN application matches the caller's location to an ELIN record, substitutes the ELIN as the calling number, and reverses the substitution when the PSAP initiates a callback[^24]. ## Security Desk Notifications An emergency calling policy supports 3 notification modes[^40]: - Notification only (Teams chat) (NotificationOnly)[^40] - Conferenced in muted (ConferenceMuted)[^40] - Conferenced in unmuted (ConferenceUnMuted)[^40] During an emergency call, Teams initiates a group chat with each security desk member and shares the caller's location as an important message; under conference modes, security desk users are also called into the conference call[^48]. A PSTN number configured as the notification dial-out number joins only in conference modes and cannot unmute, even when the mode is set to ConferenceUnMuted[^45]. The NotificationGroup parameter accepts a semicolon-separated list of at most 10 email addresses (users or groups, UPN or SMTP), and at most 50 total users can be notified[^39]. Extended notifications allow different settings per emergency dial string; if a matching extended notification exists, it controls behavior, otherwise policy-level defaults apply[^27]. In the US, an extended notification can be set for the test number 933 so test calls do not notify the security desk[^1]. If any extended notification uses a conferenced-in mode, the policy's default emergency number must have at least 1 user, group, or PSTN number and a conferenced-in notification mode[^17]. Security desk notifications are documented as available with Calling Plans, Operator Connect, and Direct Routing; documentation pages do not list Teams Phone Mobile[^49]. Sources disagree on the length limit of the custom emergency disclaimer banner: the concepts documentation states it is limited to 250 characters, whereas the New-CsTeamsEmergencyCallingPolicy reference states that the EnhancedEmergencyServiceDisclaimer parameter accepts up to 350 characters and is displayed at the top of the Calls app after each client restart[^19][^20]. ## Emergency Addresses and Dynamic Locations In Teams, an emergency address is a civic street address, which can be linked to an unlimited number of places such as floors, buildings, wings, or offices[^3]. Creating an address generates a unique location ID, and adding a place generates an additional location ID for the address-plus-place combination; this location ID is what is assigned to a user or network site[^33]. An emergency address must be marked validated before assignment to a user or network identifier; addresses created via the address map search in the Teams admin center are validated automatically[^4]. Assigning an emergency address to a network identifier for dynamic emergency calling requires the address to carry a geo code (latitude and longitude)[^29]. Emergency addresses more than a couple of years old cannot be assigned to network identifiers and must be re-created[^43]. Dynamic emergency calling operates through Location Information Service (LIS) queries and network identifiers[^32][^52]: - **Match order:** When querying the LIS, the Teams client evaluates network identifiers in this order: wireless access point (BSSID), then Ethernet switch and port, then Ethernet switch, then subnet[^32]. - **Subnet definition:** Subnets defined only in network sites do not produce dynamic locations; they must also be defined in the LIS with an associated emergency location[^52]. - **Trusted IP gating:** IP address-based lookups (subnets and dynamic policy evaluation) are attempted only when the client's external IP matches a tenant trusted IP address[^53]. Switch/port and BSSID lookups occur regardless of whether the external IP matches a trusted IP[^53]. - **Network changes:** Setting changes, including new addresses or network identifiers, can take up to 4 hours to propagate to Teams clients[^44]. - **Cloud proxies:** Deployments using cloud proxy services that modify client source IP addresses are not supported for network configuration setting lookups[^13]. WarmTransfer's reading of the sources is that when a cloud proxy rewrites client source IPs, trusted-IP and subnet lookups fail, causing on-premises clients to fall back to switch/port or BSSID matches if configured, and otherwise to user-confirmed or registered addresses, resulting in screened rather than direct-to-PSAP calls in the US[^31]. Prerequisites for dynamic network settings vary by deployment model[^36][^37]: | Deployment | Dynamic Locations Alone | Dynamic Security Desk / Dynamic Enablement | |:--- |:--- |:--- | | Calling Plan, Operator Connect, Teams Phone Mobile | Trusted IP addresses only[^36] | Trusted IP addresses and network sites[^36] | | Direct Routing | Trusted IP addresses only[^37] | Trusted IP addresses and network sites[^37] | ### Client Identifier Support Dynamic emergency calling support depends on client platform and network identifier type[^12][^56]: - **Subnets:** Supported across all Teams clients[^12]. - **Wi-Fi access points (BSSID):** Supported on all clients except Teams phones[^12]. - **Ethernet switch (LLDP):** Supported on Windows 10 or later, macOS with Microsoft's LLDP enablement software, Teams phones running app version 1449/1.0.94.2021110101 or later, and Teams Rooms[^12]. - **Web client:** The Teams web client does not support dynamic emergency calling or security desk notifications; Microsoft advises turning off Web PSTN calling in a Teams calling policy for web users[^56]. ## Remote Users and Dispatchable Location Microsoft's remote-location emergency calling article states compliance with the RAY BAUM'S Act for multi-line telephone systems in the US, and notes that user-entered locations are passed to the national screening center in Canada[^35]. Setting ExternalLocationLookupMode to Enabled in an emergency calling policy allows users working outside corporate boundaries to add, edit, or confirm their emergency address directly within the Calls tab[^28]. This work-from-home feature is supported on Teams desktop for Windows and Mac; Teams phones do not support it, and Teams mobile supports automatic location detection but not user-entered addresses[^57]. When an emergency call is dialed in the US, Teams uses location in the order of a dynamic address from the tenant LIS, a user-confirmed or edited address tied to the current network, an address suggested by the operating system, a manually entered user address without service resolution, and finally the static address assigned by an administrator to the user's phone number[^34]. In the US, calls using an admin-defined dynamic address, an OS-suggested address confirmed by the user, or an address selected through autosuggest route directly to the PSAP[^18]. Calls using an unconfirmed OS address, a manually typed address, a static user address, or no address are routed to a national call center for screening before transfer to the PSAP[^18][^55]. If a caller cannot provide an updated location to the screening center, the call routes to the PSAP matching the registered address[^55]. Statically assigned emergency calls from Common Area Phones and Microsoft Teams Rooms route directly to the PSAP without screening[^6]. ## Regional Carrier Behavior and Testing Microsoft Calling Plans, Operator Connect partners, and Teams Phone Mobile partners provide dynamic emergency routing services in the United States and Canada[^7]. For Operator Connect in the US and Canada, dynamic routing is included in the carrier service without requiring a third-party ERSP[^42]. Regional operational rules vary: - **Canada:** Dynamic routing functions identically to the US, but all emergency calls across Calling Plans, Operator Connect, and Direct Routing are screened nationally before PSAP transfer[^5]. - **EMEA and Other Regions:** Calling Plan users require a registered emergency address; in the US and Canada this occurs at user assignment, whereas in regions such as EMEA it is required when acquiring or porting the phone number[^14]. - **UK, Ireland, Luxembourg, New Zealand:** Calling Plan emergency calls are always screened first to verify location before routing to the local PSAP[^16]. - **Japan:** Emergency calling is unsupported for Microsoft Calling Plans[^15]. - **Operator Connect Carrier Control:** Operator Connect users are automatically enabled for emergency calling; calls route via the assigned carrier, and the ability of an administrator to edit a user's address depends on the profile capabilities set by the carrier when provisioning numbers[^41]. In the US and Canada, Calling Plan, Operator Connect, and Teams Phone Mobile users can dial 933 to reach an automated bot that reads back their calling line ID, registered location, and whether emergency calls would route directly or undergo screening[^2]. Direct Routing customers in the US arrange test services with their ERSP[^2]. ## See also See also [Microsoft Teams Phone architecture and licensing](https://warmtransfer.net/knowledge/teams-phone-architecture). See also [Dispatchable location and nomadic user handling](https://warmtransfer.net/knowledge/dispatchable-location). See also [US emergency calling regulatory requirements](https://warmtransfer.net/knowledge/e911-us-regulatory). See also [International emergency calling requirements](https://warmtransfer.net/knowledge/emergency-calling-international). See also [Webex Calling enhanced emergency calling](https://warmtransfer.net/knowledge/webex-calling-emergency-calling). See also [NG911 and i3 architecture transition](https://warmtransfer.net/knowledge/ng911-transition). ## Applicability Applies to: Microsoft Teams Phone, Microsoft Teams Phone Direct Routing, Microsoft Teams Phone Calling Plans, and Microsoft Teams Phone Operator Connect. Deployments: cloud and multi-tenant. Sources checked 2026-09-24. Emergency calling policies apply to Microsoft Teams Phone across Calling Plan, Operator Connect, Teams Phone Mobile, and Direct Routing deployments[^58]. LLDP switch location discovery requires Windows 10 or later, macOS with Microsoft LLDP software, Teams phones running app version 1449/1.0.94.2021110101 or later, or Teams Rooms[^12]. Emergency calling is unsupported for Calling Plans in Japan[^15]. ## What remains uncertain - Specifics of ERSP services and automated test numbers provided by Bandwidth, Intrado, and Inteliquent are not covered by the sources below. - SBC-side ELIN and PIDF-LO configuration parameters on third-party session border controllers are not covered by the sources below. - Specifics from any dedicated Teams Phone Mobile emergency calling considerations documentation are not covered by the sources below. - Emergency calling call flows and address behavior under Shared Calling are not covered by the sources below. - How PSAP callback routing functions for Direct Routing users when an ELIN application is not deployed is not covered by the sources below. - Field patterns regarding specific cloud proxy platforms altering source IPs and breaking trusted-IP lookups are not covered by the sources below. - Numerical tenant capacity limits for LIS subnets, switches, ports, wireless access points, and emergency addresses are not covered by the sources below. - Emergency location detection behavior and support limits for Teams clients running in virtual desktop infrastructure (VDI) environments are not covered by the sources below. ## Sources [^1]: An extended notification can be defined for the test number 933 so that test calls send no notification to the security desk. Source: [Configure security desk notifications](https://learn.microsoft.com/en-us/microsoftteams/emergency-calling-security-desk-notifications), Configure extended notifications > bullet list. Checked 2026-09-24. [^2]: 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. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Test emergency calling. Checked 2026-09-24. [^3]: In Teams an emergency address is a civic (street) address, and a place (floor, building, wing or office) can be associated with it; an emergency address can have an unlimited number of places. Source: [Plan and manage emergency calling](https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing), Emergency address > definitions table, rows Emergency address and Place. Checked 2026-09-24. [^4]: An emergency address must be marked validated before it can be assigned to a user or network identifier, and addresses created with the address map search in Teams admin center are validated automatically. Source: [Plan and manage emergency calling](https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing), Emergency address > Emergency address validation. Checked 2026-09-24. [^5]: In Canada, dynamic location routing works as in the US except that all emergency calls are screened nationally before transfer to the PSAP, for Calling Plans, Operator Connect and Direct Routing. Source: [Considerations for Calling Plans](https://learn.microsoft.com/en-us/microsoftteams/considerations-calling-plan), Dynamic emergency calling for Calling Plans > final paragraph. Checked 2026-09-24. [^6]: Emergency calls from Common Area Phones and Microsoft Teams Rooms that use a statically assigned address are routed directly to the PSAP without screening. Source: [Emergency addresses for remote locations](https://learn.microsoft.com/en-us/microsoftteams/emergency-calling-dispatchable-location), Emergency address classification and routing > table row 'Emergency address statically assigned to a Common Area Phone or Microsoft Teams Room'. Checked 2026-09-24. [^7]: Microsoft Calling Plans, Operator Connect partners and Teams Phone Mobile partners provide dynamic emergency routing services for users in the United States and Canada. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Plan for emergency calling > final paragraph. Checked 2026-09-24. [^8]: Microsoft lists Bandwidth Dynamic Location Routing, Intrado Emergency Routing Service and Inteliquent as the certified and supported 911 service providers for Direct Routing, and may reject support cases that involve a non-certified provider. Source: [Session Border Controllers certified for Direct Routing - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-border-controllers), Certified SBC vendors > footnote '911 service providers'. Checked 2026-09-24. [^9]: 47 CFR 9.16(b)(3) requires fixed on-premises MLTS devices to provide automated dispatchable location from January 6, 2021, and non-fixed on-premises and off-premises devices from January 6, 2022; for non-fixed devices automated location is required where technically feasible, otherwise a manual end-user update or alternative/enhanced location information. Source: [47 CFR § 9.16 - General obligations for MLTS (Cornell LII republication)](https://www.law.cornell.edu/cfr/text/47/9.16), § 9.16(b)(3)(i)-(iii). Checked 2026-09-24. [^10]: 47 CFR 9.3 defines dispatchable location as a location delivered to the PSAP with a 911 call consisting of the calling party's validated street address plus information such as suite or apartment needed to adequately identify the caller's location. Source: [47 CFR § 9.3 - Definitions (Cornell LII republication)](https://www.law.cornell.edu/cfr/text/47/9.3), § 9.3, definition 'Dispatchable location'. Checked 2026-09-24. [^11]: Under 47 CFR 9.16(b)(2), MLTS notification of a 911 call must start at the same time as the call where technically feasible, must not delay the call, and must be sent to a place where someone is likely to see or hear it. Source: [47 CFR § 9.16 - General obligations for MLTS (Cornell LII republication)](https://www.law.cornell.edu/cfr/text/47/9.16), § 9.16(b)(2)(i)-(iii). Checked 2026-09-24. [^12]: 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. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Supported clients > first Note and LLDP list. Checked 2026-09-24. [^13]: Network configuration setting lookups are not supported with cloud proxy service deployments that modify the source IP addresses of Teams clients. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Configure network settings > Important callout. Checked 2026-09-24. [^14]: Every Calling Plan user is automatically enabled for emergency calling and needs a registered emergency address on their number; in the US and Canada the address is required when the number is assigned to a user, and in other regions such as EMEA when the number is acquired or ported in. Source: [Considerations for Calling Plans](https://learn.microsoft.com/en-us/microsoftteams/considerations-calling-plan), Emergency call enablement for Calling Plans. Checked 2026-09-24. [^15]: Emergency calling is not supported for Microsoft Calling Plans in Japan. Source: [Considerations for Calling Plans](https://learn.microsoft.com/en-us/microsoftteams/considerations-calling-plan), Emergency call routing for different countries/regions > table row Japan. Checked 2026-09-24. [^16]: For Calling Plans in the United Kingdom, Ireland, Luxembourg and New Zealand, all emergency calls are first screened to determine the caller's current location before routing to the local PSAP. Source: [Considerations for Calling Plans](https://learn.microsoft.com/en-us/microsoftteams/considerations-calling-plan), Emergency call routing for different countries/regions > table rows Ireland, Luxembourg, New Zealand, United Kingdom. Checked 2026-09-24. [^17]: If any extended notification uses a conferenced-in mode, the policy's default emergency number (no dial string) must have at least one user, group or PSTN number and a conferenced-in notification mode. Source: [Configure security desk notifications](https://learn.microsoft.com/en-us/microsoftteams/emergency-calling-security-desk-notifications), Configure extended notifications > Note after settings table. Checked 2026-09-24. [^18]: In the US, calls with an admin-defined dynamic address, an operating-system address the user confirmed, or an address chosen through autosuggest go directly to the PSAP; calls with an unconfirmed operating-system address, a manually typed address, the static user or number address, or no address are screened before transfer to the PSAP. Source: [Emergency addresses for remote locations](https://learn.microsoft.com/en-us/microsoftteams/emergency-calling-dispatchable-location), Emergency address classification and routing > table. Checked 2026-09-24. [^19]: The concepts page says the emergency service disclaimer banner string in the emergency calling policy is limited to 250 characters (disputed). Source: [Plan and manage emergency calling](https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing), Create a custom emergency service disclaimer. Checked 2026-09-24. [^20]: The New-CsTeamsEmergencyCallingPolicy reference says the EnhancedEmergencyServiceDisclaimer string can be up to 350 characters and is shown at the top of the Calls app again after each client restart (disputed). Source: [New-CsTeamsEmergencyCallingPolicy (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/teams/new-csteamsemergencycallingpolicy), Parameters > -EnhancedEmergencyServiceDisclaimer. Checked 2026-09-24. [^21]: The Direct Routing emergency call routing policy references an online PSTN usage, and there must be an OnlineVoiceRoute for the emergency dial string that reaches the right PSTN gateways. Source: [Considerations for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/considerations-direct-routing), Emergency call routing for Direct Routing > first paragraph. Checked 2026-09-24. [^22]: 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. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Emergency calling prerequisites for Direct Routing; Change PIDF/LO in Teams admin center; Change PIDF/LO in PowerShell. Checked 2026-09-24. [^23]: For Direct Routing, Teams uses the network site's emergency call routing policy if one exists; it falls back to the user's policy if the site has none, the client is at an undefined site, or the dialed number matches none of the site policy's emergency numbers; if no policy can be obtained, the user is not enabled for emergency calling. Source: [Considerations for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/considerations-direct-routing), Emergency call enablement for Direct Routing > bullet list. Checked 2026-09-24. [^24]: With an SBC ELIN application, emergency addresses and ELIN numbers are configured in the application and uploaded to the PSTN emergency database; on an emergency call the application matches the caller's location to an ELIN record, substitutes the ELIN as the calling number, and reverses the substitution when the PSAP calls back. Source: [Considerations for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/considerations-direct-routing), Emergency call routing for Direct Routing > Emergency Location Identification Number applications. Checked 2026-09-24. [^25]: 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). Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Emergency calling prerequisites for Direct Routing > Set up an Emergency Routing Service provider. Checked 2026-09-24. [^26]: The Direct Routing considerations page lists Emergency Routing Service Providers as a United States-only option for dynamically routing Direct Routing emergency calls, with ELIN applications as the other option (disputed). Source: [Considerations for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/considerations-direct-routing), Emergency call routing for Direct Routing > two-solution bullet list; Emergency Routing Service Providers. Checked 2026-09-24. [^27]: Extended notifications let an emergency calling policy set different notification settings for each emergency dial string; if a matching extended notification exists it controls notification, otherwise the policy-level settings apply. Source: [New-CsTeamsEmergencyCallingPolicy (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/teams/new-csteamsemergencycallingpolicy), Parameters > -ExtendedNotifications. Checked 2026-09-24. [^28]: Setting ExternalLocationLookupMode to Enabled in an emergency calling policy (the 'External location lookup mode' toggle in Teams admin center) lets users add, edit or confirm their emergency address from the Calls tab when working outside the corporate network. Source: [Emergency addresses for remote locations](https://learn.microsoft.com/en-us/microsoftteams/emergency-calling-dispatchable-location), Enable end users to configure their emergency address > Using PowerShell. Checked 2026-09-24. [^29]: An emergency address can only be assigned to a network identifier for dynamic emergency calling if it carries a geo code (latitude and longitude). Source: [Plan and manage emergency calling](https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing), Emergency address > Emergency address geo codes > Important callout. Checked 2026-09-24. [^30]: Users automatically receive the global (Org-wide default) emergency calling policy unless a custom policy is assigned; the global policy can be edited but not renamed or deleted, and network sites need custom policies. Source: [Manage emergency calling policies in Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/manage-emergency-calling-policies), Introduction, paragraph beginning 'For users, you can use the global'. Checked 2026-09-24. [^31]: 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). Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Configure network settings > Note and Important callout; combined with emergency-calling-dispatchable-location classification table. Checked 2026-09-24. [^32]: 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. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Plan for emergency calling > step 2 > LIS match bullet list. Checked 2026-09-24. [^33]: Creating an emergency address generates a unique location ID, adding a place creates a further location ID for the address-plus-place combination, and it is the location ID that is associated when an emergency location is assigned to a user or site. Source: [Plan and manage emergency calling](https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing), Emergency address > definitions table, row Emergency location. Checked 2026-09-24. [^34]: When an emergency number is dialed, Teams uses location in this order: a dynamic address from the tenant's LIS; a user-confirmed or edited address tied to the current network; an address suggested by the operating system; an address the user entered manually without service resolution; and finally the address the administrator statically associated with the user's phone number. Source: [Emergency addresses for remote locations](https://learn.microsoft.com/en-us/microsoftteams/emergency-calling-dispatchable-location), Location precedence > numbered list 1-5. Checked 2026-09-24. [^35]: Microsoft's remote-location emergency address article says it covers Microsoft's compliance with the RAY BAUM'S Act for multi-line telephone systems in the US, and that user-entered locations are also passed to the screening center in Canada. Source: [Emergency addresses for remote locations](https://learn.microsoft.com/en-us/microsoftteams/emergency-calling-dispatchable-location), Introduction, paragraphs 2 and 5. Checked 2026-09-24. [^36]: 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. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Configure network settings > For Calling Plan, Operator Connect, and Teams Phone Mobile users. Checked 2026-09-24. [^37]: 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. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Configure network settings > For Direct Routing users. Checked 2026-09-24. [^38]: Teams clients no longer put a '+' in front of emergency numbers (for example +911) on Direct Routing, so voice route patterns for emergency dial strings must match the number without '+'. Source: [Considerations for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/considerations-direct-routing), Emergency call routing for Direct Routing > Note. Checked 2026-09-24. [^39]: The NotificationGroup parameter accepts a semicolon-separated list of at most 10 email addresses (users or groups, UPN or SMTP), and at most 50 users in total can be notified. Source: [New-CsTeamsEmergencyCallingPolicy (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/teams/new-csteamsemergencycallingpolicy), Parameters > -NotificationGroup. Checked 2026-09-24. [^40]: The emergency calling policy offers three security desk notification modes: notification only (Teams chat), conferenced in but muted, and conferenced in and unmuted (NotificationOnly, ConferenceMuted, ConferenceUnMuted in PowerShell). Source: [Manage emergency calling policies in Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/manage-emergency-calling-policies), Create a custom emergency calling policy > Use the Teams admin center, step 6.3. Checked 2026-09-24. [^41]: Operator Connect users are automatically enabled for emergency calling, their emergency calls go to the Operator Connect carrier for the number, and whether the tenant admin can set or change a user's registered address depends on the capabilities the carrier assigned when uploading the numbers. Source: [Considerations for Operator Connect](https://learn.microsoft.com/en-us/microsoftteams/considerations-operator-connect), Emergency call enablement for Operator Connect. Checked 2026-09-24. [^42]: For Operator Connect in the US and Canada, dynamic emergency routing is part of the carrier's service and does not have to be bought from another provider. Source: [Considerations for Operator Connect](https://learn.microsoft.com/en-us/microsoftteams/considerations-operator-connect), Emergency call routing for Operator Connect > bullet list. Checked 2026-09-24. [^43]: Emergency addresses more than a couple of years old cannot be assigned to network identifiers and must be re-created. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Assign emergency addresses > Note. Checked 2026-09-24. [^44]: Some network settings changes, such as a new address or network identifier, can take up to four hours to propagate to Teams clients. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Configure network settings > paragraph before subnet Note. Checked 2026-09-24. [^45]: A PSTN number configured as the notification dial-out number joins only in the conference modes and cannot unmute, even when the mode is ConferenceUnMuted. Source: [New-CsTeamsEmergencyCallingPolicy (MicrosoftTeams)](https://learn.microsoft.com/en-us/powershell/module/teams/new-csteamsemergencycallingpolicy), Parameters > -NotificationDialOutNumber. Checked 2026-09-24. [^46]: A Direct Routing emergency call routing policy holds a Dynamic emergency calling toggle and one or more emergency numbers, each with an emergency dial string, zero or more semicolon-separated dial masks, and a PSTN usage record that selects the emergency route. Source: [Manage emergency call routing policies for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/manage-emergency-call-routing-policies), Create a custom emergency call routing policy > Using the Microsoft Teams admin center, steps 4-5. Checked 2026-09-24. [^47]: 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. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Configure emergency policies (parenthetical); Enable users and sites (first paragraph). Checked 2026-09-24. [^48]: During an emergency call Teams starts a group chat with each security desk member and shares the caller's location as an important message, and in conference modes each security desk user is also called into the conference. Source: [Configure security desk notifications](https://learn.microsoft.com/en-us/microsoftteams/emergency-calling-security-desk-notifications), Introduction, third paragraph. Checked 2026-09-24. [^49]: Microsoft documents security desk notifications as available with Calling Plans, Operator Connect and Direct Routing; the pages do not list Teams Phone Mobile. Source: [Configure security desk notifications](https://learn.microsoft.com/en-us/microsoftteams/emergency-calling-security-desk-notifications), Introduction, second paragraph. Checked 2026-09-24. [^50]: When Shared Calling is used with Calling Plans or Operator Connect, emergency call routing policies only identify emergency numbers, and site-assigned emergency call routing policies cannot be used if Shared Calling for Calling Plans or Operator Connect coexists with Direct Routing in the same tenant. Source: [Manage emergency call routing policies for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/manage-emergency-call-routing-policies), Introductory Notes (first and second). Checked 2026-09-24. [^51]: When an emergency calling policy is assigned both to a network site and to a user who is at that site, the site policy overrides the user policy. Source: [Manage emergency calling policies in Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/manage-emergency-calling-policies), Introduction, paragraph beginning 'If you assigned an emergency calling policy to a network site'. Checked 2026-09-24. [^52]: Subnets defined in network sites do not produce dynamic locations; they must also be defined in the Location Information Service with an emergency location. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Configure Location Information Service > Using PowerShell > Important callout. Checked 2026-09-24. [^53]: 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. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Configure network settings > trusted IP paragraph and following Note. Checked 2026-09-24. [^54]: 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. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Configure emergency policies. Checked 2026-09-24. [^55]: For US Calling Plan users, a client outside any tenant-defined dynamic emergency location is screened by a national call center, and if the caller cannot give the screening center an updated location the call goes to the PSAP serving the registered address. Source: [Considerations for Calling Plans](https://learn.microsoft.com/en-us/microsoftteams/considerations-calling-plan), Emergency call routing for different countries/regions > table row United States. Checked 2026-09-24. [^56]: 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. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Supported clients > second Note. Checked 2026-09-24. [^57]: The work-from-home location experience covers Teams desktop on Windows and Mac; Teams phones do not support it, and Teams mobile supports automatic location detection but not user-entered addresses. Source: [Emergency addresses for remote locations](https://learn.microsoft.com/en-us/microsoftteams/emergency-calling-dispatchable-location), Notes and restrictions. Checked 2026-09-24. [^58]: Teams emergency calling policies apply to Calling Plan Operator Connect Teams Phone Mobile and Direct Routing deployments. Source: [Manage emergency calling policies in Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/manage-emergency-calling-policies), Manage emergency calling policies, opening paragraph. Checked 2026-09-06. [^59]: A Teams emergency calling policy can send security-desk chat notifications or conference configured recipients into the emergency call in muted or unmuted mode. Source: [Manage emergency calling policies in Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/manage-emergency-calling-policies), Create a custom emergency calling policy, notification mode. Checked 2026-09-06. [^60]: When a Teams user and the network site the user is at both have emergency calling policies the site's policy overrides the user's policy. Source: [Manage emergency calling policies in Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/manage-emergency-calling-policies), Manage emergency calling policies, policy assignment overview. Checked 2026-09-06.