# Setting up dynamic emergency calling in Microsoft Teams Systems: Microsoft Teams Phone For Teams Phone administrators configuring dynamic emergency calling and security desk notification. Canonical: https://warmtransfer.net/guides/teams-dynamic-e911-setup Last verified: 2026-09-24 Dynamic emergency calling routes emergency calls and notifies security personnel based on the client's current location across Microsoft Calling Plans, Operator Connect, Teams Phone Mobile, and Direct Routing[^67]. Implementing this requires configuring validated emergency addresses, network identifiers in the Location Information Service (LIS), and emergency calling and routing policies[^6][^37][^8]. ## Before you start - Ensure users are assigned the appropriate Teams Phone licenses and equipped with a PSTN solution[^68]. - For Direct Routing, verify that the Session Border Controller (SBC) is Microsoft-certified and connected with a publicly trusted TLS certificate[^69][^70]. - For Operator Connect, confirm that users are in Teams Only mode and that the certified operator covers your operating regions[^71]. - Obtain administrator permissions in the Microsoft Teams admin center and the Microsoft Teams PowerShell Module[^1][^8]. ## What changes by situation - How do your users reach the PSTN, and who routes their emergency calls? Microsoft Calling Plan (Microsoft is the carrier); Operator Connect (a certified operator is the carrier); Direct Routing through your own SBC, with a third-party Emergency Routing Service Provider (ERSP); Direct Routing through your own SBC, with an ELIN application on the SBC. - Should emergency policies follow the user's current site, or stay fixed on the user? Per site: assign emergency policies to network sites so a roaming user picks up the local security desk; Per user: assign emergency policies to users only. - Can users set their own emergency address when they are off the corporate network? Yes: turn on External location lookup mode so users can confirm or enter an address; No: users off-network rely only on the address the administrator registered on their number. ## Step 1: Confirm client coverage and block PSTN calling from the web client ### Do Check the client inventory against supported endpoints: Teams desktop for Windows and macOS, Teams mobile for iOS and Android, Teams phones (from app version 1449/1.0.94.2019110802), Teams Rooms on Windows and Android, and Teams for VDI[^60]. Subnet-based locations function on all clients, Wi-Fi locations function on all clients except Teams phones, and Ethernet switch (LLDP) detection requires Windows 10 or later, Microsoft LLDP enablement software on macOS, or Teams phones from app 1449/1.0.94.2021110101[^36]. Because the Teams web client does not support dynamic emergency calling or security desk notifications, disable Web PSTN calling in a Teams calling policy and assign that policy to web client users[^64]. ### Verify Confirm in the Teams admin center that the calling policy assigned to web-only users has Web PSTN calling turned off[^64]. ### Rollback Turn Web PSTN calling back on in the calling policy assigned to web users[^64]. ## Step 2: Create validated, geo-coded emergency addresses and their places **Microsoft Calling Plan (Microsoft is the carrier)** ### Do In the Teams admin center, navigate to **Locations > Emergency addresses > Add** and locate the address using map search so that it is validated and geo-coded automatically[^6][^9]. If Azure Maps does not match the location, place a pin manually using the PIN drop feature[^9]. Ensure the address includes the house or building number, street, city, postal code, latitude, longitude, and organization name, adding state or province for addresses in Canada, Israel, Italy, and the United States[^2]. On the address's **Places** tab, add specific floors, wings, or offices to generate distinct location IDs[^49][^48]. ### Verify Verify that every configured address displays as validated with geo codes[^6][^72]. Re-create any emergency addresses older than a couple of years, as they cannot be assigned to network identifiers[^46]. ### Rollback A validated address cannot be updated in place; delete it and re-create it if corrections are required[^5]. Remove places or addresses only after clearing all assigned users and phone numbers[^3][^47]. **Operator Connect (a certified operator is the carrier)** ### Do In the Teams admin center, go to **Locations > Emergency addresses > Add** and add addresses using map search to generate automatic validation and geo codes[^6][^9]. Use PIN drop if Azure Maps cannot locate the address[^9]. On the **Places** tab, add any required sub-locations such as building, floor, or office[^49][^48]. ### Verify Verify that the emergency address shows as validated and has geo codes[^6][^72]. Re-create any addresses older than a couple of years before attempting to bind them to network identifiers[^46]. ### Rollback Delete a place or address only after unassigning all associated users and numbers[^3][^47]. Re-create validated addresses from scratch to modify their street details[^5]. **Direct Routing through your own SBC, with a third-party Emergency Routing Service Provider (ERSP)** ### Do In the Teams admin center, add the emergency address under **Locations > Emergency addresses > Add** using map search to validate it and populate geo codes[^6][^9]. Use PIN drop if Azure Maps does not find a match[^9]. Define sub-locations on the address's **Places** tab as needed[^49][^48]. ### Verify Verify that each address reflects validated status and contains a geo code[^6][^72]. Ensure the addresses are not older than a couple of years, re-creating them if necessary[^46]. ### Rollback Remove any associated users and phone numbers from the place or address before deleting it[^3][^47]. Re-create any validated address that needs modification[^5]. **Direct Routing through your own SBC, with an ELIN application on the SBC** ### Do Navigate to **Locations > Emergency addresses > Add** and add addresses using map search to secure automatic validation and geo codes, using PIN drop if map search yields no match[^6][^9]. On the **Places** tab, add each place and enter its corresponding ELIN[^48]. Ensure that every place carrying an ELIN identifier matches an emergency record defined in the SBC ELIN application[^19]. ### Verify Verify that each address has a geo code and validated status[^6][^72]. Confirm that the ELIN identifiers entered on the places match the records in the SBC ELIN application[^19]. ### Rollback Unassign all users and phone numbers prior to deleting any place[^47]. Suggested rollback: delete the place or update the ELIN value in the Teams admin center to match the SBC configuration. ## Step 3: Set the registered (static) emergency address on each number **Microsoft Calling Plan (Microsoft is the carrier)** ### Do Navigate to **Voice > Phone numbers > Numbers**, select the user's phone number, select **Edit**, and select the emergency location or place, or run `Set-CsPhoneNumberAssignment` in PowerShell[^1]. In the United States and Canada, assigning an emergency location is required when assigning the number to the user[^15]. Ensure that the location, the user, and the assigned number are all located within the same country[^4]. ### Verify Confirm that each assigned user number displays a registered emergency location[^15]. ### Rollback In the **Edit** pane under **Voice > Phone numbers > Numbers**, select the X next to the location to clear it and select an alternative address[^1]. **Operator Connect (a certified operator is the carrier)** ### Do Check the number capabilities assigned by your carrier to confirm whether tenant administrators can modify registered emergency addresses[^44]. If permitted, assign the address under **Voice > Phone numbers > Numbers > Edit** or by running `Set-CsPhoneNumberAssignment`, ensuring the user, number, and location share the same country[^1][^4]. ### Verify Confirm that the emergency location appears on the number in the Teams admin center or that the operator confirms it maintains the registered address record[^44]. ### Rollback Where supported by carrier capabilities, clear or replace the location via the **Edit** pane in **Voice > Phone numbers > Numbers**[^1][^44]. **Direct Routing through your own SBC, with a third-party Emergency Routing Service Provider (ERSP)** ### Do Go to **Users > Manage users**, select the user, and open **Account > General information > Edit** to assign the Direct Routing telephone number and, optionally, an emergency location, or execute `Set-CsPhoneNumberAssignment`[^1]. Ensure the location, user, and phone number are within the same country[^4]. ### Verify Verify in the user's General information tab that the emergency location is configured[^1]. Note that for ERSP environments in the United States, calls lacking dynamic location are screened first before transfer to the PSAP[^22]. ### Rollback Open **Users > Manage users > Account > General information > Edit** and clear or modify the emergency location assignment[^1]. **Direct Routing through your own SBC, with an ELIN application on the SBC** ### Do In **Users > Manage users**, choose the target user, select **Account > General information > Edit**, and assign the Direct Routing number with an optional static emergency location or place, or use `Set-CsPhoneNumberAssignment`[^1]. Keep the location, user, and phone number in the same country[^4]. ### Verify Confirm that the assigned emergency location appears under the user's General information[^1]. ### Rollback Open the user's General information pane and clear or update the assigned emergency location[^1]. ## Step 4: Prepare the PSTN side to carry location **Microsoft Calling Plan (Microsoft is the carrier)** ### Do No additional PSTN configuration is required, as Calling Plan users are automatically enabled for emergency calling with the emergency numbers corresponding to their Microsoft 365 usage location[^31]. Microsoft supplies dynamic emergency routing services directly in the United States and Canada[^10]. ### Verify Verify that each user's assigned Microsoft 365 usage location corresponds to the correct country[^31]. ### Rollback Suggested rollback: no changes were made to the PSTN infrastructure. **Operator Connect (a certified operator is the carrier)** ### Do No additional PSTN routing configuration is required in Teams, as emergency calls route automatically to the certified operator, which provides dynamic routing in the United States and Canada[^45]. ### Verify Confirm that the Operator Connect partner provides calling services and PSTN support in your operational regions[^73][^71]. ### Rollback Suggested rollback: no changes were made to the PSTN infrastructure. **Direct Routing through your own SBC, with a third-party Emergency Routing Service Provider (ERSP)** ### Do In the Teams admin center, navigate to **Voice > Direct Routing**, select the emergency SBC, and enable **SBC supports PIDF/LO for emergency calls**, or run PowerShell `Set-CsOnlinePSTNGateway -Identity -PidfloSupported $true`[^24]. Connect the SBC to an Emergency Routing Service provider[^21]. ### Verify Run `Get-CsOnlinePSTNGateway -Identity ` and confirm that `PidfloSupported` reports `True`[^24]. ### Rollback Run `Set-CsOnlinePSTNGateway -Identity -PidfloSupported $false` or toggle the setting off in the Teams admin center[^24]. **Direct Routing through your own SBC, with an ELIN application on the SBC** ### Do Enable PIDF/LO on each emergency SBC by configuring **SBC supports PIDF/LO for emergency calls** or running `Set-CsOnlinePSTNGateway -Identity -PidfloSupported $true`[^24]. Within the SBC's ELIN application, define the emergency addresses and corresponding ELIN telephone numbers, and upload these records to the PSTN emergency calling database[^19]. ### Verify Verify that `Get-CsOnlinePSTNGateway -Identity ` outputs `PidfloSupported: True`[^24]. Confirm that the ELIN database matches the ELINs configured on Teams places[^19]. ### Rollback Run `Set-CsOnlinePSTNGateway -Identity -PidfloSupported $false` to stop sending location bodies in the SIP INVITE[^24]. Suggested rollback: remove or de-register the uploaded ELIN records from the carrier emergency database. ## Step 5: Add your external trusted IP addresses ### Do In the Teams admin center, go to **Locations > Network topology > Trusted IPs** and enter each public egress IP subnet used by corporate sites, or run `New-CsTenantTrustedIPAddress`[^59]. External trusted IPs are required for dynamic location lookups based on client subnet matching, whereas lookups by Wi-Fi BSSID or Ethernet switch occur regardless of trusted IPs[^62][^11][^23]. ### Verify Verify that all egress IP ranges are listed[^59]. Note that network configuration lookups are unsupported if client source IPs are modified by cloud proxies[^42]. ### Rollback Select the IP range on the **Trusted IPs** tab and choose **Delete**, or remove it via PowerShell[^59]. ## Step 6: Define network regions, sites and subnets **Per site: assign emergency policies to network sites so a roaming user picks up the local security desk** ### Do In the Teams admin center, go to **Locations > Network topology > Network sites** and add sites associated with network regions, assigning internal subnets to each site, or configure them using `New-CsTenantNetworkRegion`, `New-CsTenantNetworkSite`, and `New-CsTenantNetworkSubnet`[^59]. Ensure each subnet is assigned to only one network site[^59]. ### Verify Verify under **Network sites** that each site reflects its designated region and that subnets are uniquely allocated[^59]. ### Rollback Remove the assigned subnets and delete the site on the **Network sites** tab[^59]. **Per user: assign emergency policies to users only** ### Do Skip the creation of network sites; dynamic location resolution alone requires only external trusted IPs[^11][^23]. ### Verify Confirm that your organization does not require dynamic site-based policy assignment for security desk notification or Direct Routing call routing[^11][^23]. ### Rollback Suggested rollback: no network topology configuration changes were made. ## Step 7: Populate the Location Information Service ### Do Navigate to **Locations > Networks & locations** and populate subnets, Wi-Fi access points, switches, and ports with their corresponding emergency location or place IDs, either manually, by CSV/TSV upload, or using `CsOnlineLisSubnet`, `CsOnlineLisWirelessAccessPoint`, `CsOnlineLisSwitch`, and `CsOnlineLisPort` cmdlets[^37]. - Define each subnet by its network ID (for example, client 10.10.10.150/25 belongs to network ID 10.10.10.128)[^40]. - Subnets linked to network sites must also be added here to yield dynamic locations[^39]. - The LIS evaluates identifiers in the specific order of wireless access point, switch port, switch, and finally subnet, selecting the first match[^38]. ### Verify Allow up to 4 hours for newly added network identifiers and addresses to propagate to clients[^50]. The Teams client submits network details at startup, periodically, and whenever its connection changes[^14]. ### Rollback Delete entries via the **Networks & locations** tabs or use `Remove-CsOnlineLisSubnet`, `Remove-CsOnlineLisPort`, `Remove-CsOnlineLisWirelessAccessPoint`, or `Remove-CsOnlineLisSwitch`[^37]. ## Step 8: Create the emergency call routing policy **Microsoft Calling Plan (Microsoft is the carrier)** ### Do Do not create an emergency call routing policy, as it applies solely to Direct Routing and has no effect on Calling Plan users[^31]. ### Verify Suggested check: verify that Calling Plan users remain on default routing policies. ### Rollback Suggested rollback: no call routing policies were created or assigned. **Operator Connect (a certified operator is the carrier)** ### Do Do not create an emergency call routing policy, as it does not control Operator Connect routing[^31]. ### Verify Suggested check: verify that Operator Connect users are not assigned emergency call routing policies. ### Rollback Suggested rollback: no call routing policies were created or assigned. **Direct Routing through your own SBC, with a third-party Emergency Routing Service Provider (ERSP)** ### Do In the Teams admin center, go to **Voice > Emergency policies > Call routing policies > Add**, and turn on **Dynamic emergency calling**[^32]. Add the emergency dial string (such as 911), configure any semicolon-separated dial masks, and assign a PSTN usage pointing to a dedicated emergency SIP trunk connected to the ERSP[^30][^33]. Ensure an `OnlineVoiceRoute` exists for the emergency dial string matching without a leading "+" prefix[^26][^43]. ### Verify Verify that each dial string and mask is unique within the policy[^30]. Confirm the voice route pattern matches `911` and not `+911`[^43]. ### Rollback Edit or remove custom policies using `Set-CsTeamsEmergencyCallRoutingPolicy` or the Teams admin center[^28]. The global policy can be edited but cannot be deleted[^28]. **Direct Routing through your own SBC, with an ELIN application on the SBC** ### Do In **Voice > Emergency policies > Call routing policies > Add**, create a policy with **Dynamic emergency calling** enabled[^32]. Define the emergency dial string and any semicolon-separated dial masks, assigning a PSTN usage that directs calls to an SBC ELIN gateway[^30][^33]. Ensure the matching `OnlineVoiceRoute` is configured without a leading "+"[^26][^43]. ### Verify Verify that dial strings and dial masks are unique within the policy[^30]. Check that the voice route routes to the SBC running the ELIN application[^33]. ### Rollback Modify or unassign the policy in the Teams admin center or via PowerShell[^28]. The global policy cannot be deleted[^28]. ## Step 9: Create the emergency calling policy (security desk notification) **Yes: turn on External location lookup mode so users can confirm or enter an address** ### Do In **Voice > Emergency policies > Calling policies**, add a policy and turn on **External location lookup mode**[^27]. Optionally, configure an **Emergency service disclaimer** banner of up to 250 characters[^16]. Select a notification mode: Send notification only, Conferenced in but are muted, or Conferenced in and are unmuted[^29]. If using a conferenced mode, a PSTN dial-out number may be added, which joins in a listen-only state[^56]. Configure an extended notification entry for dial string 933 to send no notification[^52]. If any extended notification uses a conferenced mode, configure a default entry with no dial string, at least one recipient, and a conferenced mode[^54]. On Windows devices, ensure Group Policy or MDM permits application access to the location service[^66]. ### Verify Verify that users on Teams desktop for Windows and Mac can confirm or enter their location[^65]. In the United States, confirmed OS-suggested or autosuggested addresses route directly to the PSAP, whereas manually typed addresses undergo screening[^63]. ### Rollback Disable External location lookup mode or update notification settings using `Set-CsTeamsEmergencyCallingPolicy`[^27][^28]. **No: users off-network rely only on the address the administrator registered on their number** ### Do In **Voice > Emergency policies > Calling policies**, add a policy and leave **External location lookup mode** disabled[^27]. Select a notification mode (notification only, conferenced muted, or conferenced unmuted) and designate the notification recipients[^29]. If conferencing is selected, add a PSTN dial-out number if required[^56]. Add an extended notification for 933 set to no notification[^52]. If any extended notification uses conferencing, ensure a default entry with no dial string is configured with a conferenced mode[^54]. ### Verify Confirm that off-network callers fall back to their registered phone number address and that US calls with static user addresses are screened prior to PSAP routing[^41][^7]. ### Rollback Modify the emergency calling policy settings in the Teams admin center[^28]. The global policy can be edited but cannot be deleted[^28]. ## Step 10: Assign the policies **Per site: assign emergency policies to network sites so a roaming user picks up the local security desk** ### Do Assign the emergency calling policy to each network site using **Locations > Network topology > Network sites > Edit** or `Set-CsTenantNetworkSite -EmergencyCallingPolicy`[^8]. For Direct Routing, also assign the emergency call routing policy to the site using `-EmergencyCallRoutingPolicy`[^8]. Note that if Shared Calling on Calling Plan or Operator Connect coexists in the tenant with Direct Routing, site-assigned call routing policies cannot be used[^57]. Additionally, assign policies directly to users with `Grant-CsTeamsEmergencyCallingPolicy` and `Grant-CsTeamsEmergencyCallRoutingPolicy` to serve as a fallback when off-site[^8][^55][^18]. ### Verify Verify on each network site that the policies are applied[^8]. When a user is at that site, the site's emergency calling policy overrides any user-assigned policy[^58]. ### Rollback Edit the network site in the Teams admin center or run `Set-CsTenantNetworkSite` with null or alternative policy values[^8]. **Per user: assign emergency policies to users only** ### Do Assign the emergency calling policy to users using `Grant-CsTeamsEmergencyCallingPolicy`[^8]. For Direct Routing users, assign the emergency call routing policy using `Grant-CsTeamsEmergencyCallRoutingPolicy`[^8]. Users without an explicit policy grant automatically inherit the global policy[^28]. ### Verify Verify that every Direct Routing user has an assigned call routing policy, as Direct Routing users cannot place emergency calls without one[^18]. ### Rollback Run `Grant-CsTeamsEmergencyCallingPolicy -Identity -PolicyName $null` or `Grant-CsTeamsEmergencyCallRoutingPolicy -Identity -PolicyName $null` to return users to the global policy[^28]. ## Step 11: Test emergency calling **Microsoft Calling Plan (Microsoft is the carrier)** ### Do Users in the United States or Canada can dial 933 from a client at each configured network location[^61]. ### Verify Listen to the bot, which 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[^61]. Verify that security personnel receive no alert when 933 is excluded via extended notifications[^52]. ### Rollback Suggested rollback: no rollback is necessary after placing a test call. **Operator Connect (a certified operator is the carrier)** ### Do Users in the United States or Canada can dial 933 from an Operator Connect endpoint located in each mapped corporate location[^61]. ### Verify Confirm that the bot 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[^61]. Ensure the security desk receives no alert when calling 933[^52]. ### Rollback Suggested rollback: no rollback is necessary after placing a test call. **Direct Routing through your own SBC, with a third-party Emergency Routing Service Provider (ERSP)** ### Do Coordinate with your Emergency Routing Service Provider to execute their recommended test procedure[^25]. ### Verify Confirm that test calls originating from mapped network identifiers present the expected dynamic location and that unlocated calls route to the ERSP screening center[^22]. ### Rollback Suggested rollback: no rollback is necessary after placing a test call. **Direct Routing through your own SBC, with an ELIN application on the SBC** ### Do WarmTransfer's reading of the sources is that Direct Routing with an SBC ELIN application lacks a Microsoft 933-style test bot, requiring a test plan arranged through your SBC vendor and PSTN carrier[^34]. ### Verify Verify that the outgoing test call reaches the test destination presenting the ELIN number associated with the caller's place, and confirm that an inbound callback to the ELIN rings back to the originating station[^20]. ### Rollback Suggested rollback: no rollback is necessary after placing a test call. ## Applicability Applies to: Microsoft Teams Phone, Microsoft Teams Calling Plan, Microsoft Teams Phone Direct Routing, and Microsoft Teams Phone Operator Connect. Deployments: multi-tenant. Sources checked 2026-09-24. Microsoft documentation covers dynamic emergency routing for Calling Plans, Operator Connect, and Teams Phone Mobile in the United States and Canada[^10]. In Survivable Branch Appliance (SBA) mode, emergency calls can still be placed but location information is not shared and emergency call routing policies are not supported, and emergency dial strings fail unless the regular voice routing policy has a matching pattern[^74]. ## What remains uncertain Sources disagree on whether Direct Routing Emergency Routing Service Providers support Canada: the configuration guide lists the United States and Canada, whereas the Direct Routing considerations guide lists them as US only[^35]. Procedures for withdrawing or modifying ELIN records directly in PSTN carrier databases are not covered by the sources below. Specific non-emergency voice routing behavior when Survivable Branch Appliances fail over is not covered by the sources below. ## Sources [^1]: For Calling Plan, Operator Connect and Teams Phone Mobile numbers the registered emergency location is set under Voice > Phone numbers > Numbers > Edit; for Direct Routing it is set optionally when assigning the number under Users > Manage users > Account > General information; in PowerShell both use Set-CsPhoneNumberAssignment. Source: [Manage emergency locations](https://learn.microsoft.com/en-us/microsoftteams/add-change-remove-emergency-location-organization), Assign an emergency location, subsections Calling Plans, Operator Connect, Teams Phone Mobile; Direct Routing; Use PowerShell. Checked 2026-09-24. [^2]: For Microsoft Calling Plans every country requires house or building number, street, city, postal code, latitude, longitude and organization name for an emergency address, with State or Province additionally required in Canada, Israel, Italy and the United States. Source: [Manage emergency locations](https://learn.microsoft.com/en-us/microsoftteams/add-change-remove-emergency-location-organization), Required information for Microsoft Calling Plans. Checked 2026-09-24. [^3]: An emergency location can be removed only when no users or phone numbers are assigned to it. Source: [Manage emergency locations](https://learn.microsoft.com/en-us/microsoftteams/add-change-remove-emergency-location-organization), Remove an emergency location. Checked 2026-09-24. [^4]: To assign an emergency location, the location, users and phone numbers must all be in the same country. Source: [Manage emergency locations](https://learn.microsoft.com/en-us/microsoftteams/add-change-remove-emergency-location-organization), Assign an emergency location. Checked 2026-09-24. [^5]: An emergency location's address can be updated only if it has not been validated; a validated address that needs changing must be deleted and re-created. Source: [Manage emergency locations](https://learn.microsoft.com/en-us/microsoftteams/add-change-remove-emergency-location-organization), Change an emergency location. Checked 2026-09-24. [^6]: An emergency address must be marked validated before it can be assigned to a user or network identifier, and addresses defined through the Teams admin center map search are validated and geo-coded automatically, which Microsoft recommends. Source: [Plan and manage emergency calling](https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing), Emergency address validation; Emergency address geo codes. Checked 2026-09-24. [^7]: In the United States, emergency calls with an administrator-defined dynamic address, or a static address on a Common Area Phone or Teams Room, go direct to the PSAP, while calls using an address statically assigned to a user or number, or with 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. [^8]: 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. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Enable users and sites, PowerShell examples. Checked 2026-09-24. [^9]: 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. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Assign emergency addresses. Checked 2026-09-24. [^10]: 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. [^11]: 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. [^12]: 47 CFR 9.16 requires a multi-line telephone system to be configured so a user can dial 911 directly from any station without any additional digit, code, prefix or post-fix. Source: [47 CFR § 9.16 - General obligations for MLTS (Cornell LII republication)](https://www.law.cornell.edu/cfr/text/47/9.16), 47 CFR 9.16(a)(1) and (b)(1). Checked 2026-09-24. [^13]: 47 CFR 9.16(b)(3) requires automated dispatchable location from on-premises fixed MLTS telephones by 6 January 2021, and from on-premises non-fixed and off-premises devices by 6 January 2022 where technically feasible, otherwise allowing end-user manual update or alternative or 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), 47 CFR 9.16(b)(3)(i)-(iii). Checked 2026-09-24. [^14]: The Teams client sends its network connectivity information to network settings and the LIS at startup, periodically afterwards, and when its network connection changes. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Plan for emergency calling, step 2. Checked 2026-09-24. [^15]: Each Calling Plan user is automatically enabled for emergency calling and must have a registered emergency address on their number; in the United States and Canada the emergency location is required when the number is assigned to the user. 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. [^16]: An emergency calling policy can carry an Emergency service disclaimer of up to 250 characters, shown as a banner that users can dismiss after confirming their address and that reappears when Teams restarts. 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. [^17]: For Direct Routing, dynamic location for routing emergency calls is supported in the United States, and in Canada in the same way except that all emergency calls are screened nationally before transfer to the PSAP. Source: [Considerations for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/considerations-direct-routing), Dynamic emergency calling for Direct Routing. Checked 2026-09-24. [^18]: For Direct Routing, a client uses the site's emergency call routing policy; it falls back to the user's policy if the site has none, the site is undefined, or the dialed number matches none of the site policy's emergency numbers; if no policy is 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. Checked 2026-09-24. [^19]: With an SBC ELIN application, the emergency addresses and associated telephone numbers are configured in the ELIN application and the ELIN records uploaded to the emergency calling database of the respective PSTN, and Teams emergency locations carrying an ELIN identifier must match those in the ELIN application. Source: [Considerations for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/considerations-direct-routing), Emergency Location Identification Number applications, first paragraph. Checked 2026-09-24. [^20]: On an emergency call with a dynamic location, the SBC ELIN application matches the location to an ELIN record, substitutes the caller's number with the ELIN number and routes to the serving PSAP; on a call-back to the ELIN it reverses the substitution to reach the original caller. Source: [Considerations for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/considerations-direct-routing), Emergency Location Identification Number applications, bulleted list and following sentence. Checked 2026-09-24. [^21]: 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. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Set up an Emergency Routing Service provider. Checked 2026-09-24. [^22]: With an Emergency Routing Service Provider integrated into Direct Routing, emergency calls carrying a dynamically acquired location are routed automatically to the serving PSAP, and calls without one are first screened to determine the caller's current location. Source: [Considerations for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/considerations-direct-routing), Emergency Routing Service Providers. Checked 2026-09-24. [^23]: 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. [^24]: 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. 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. [^25]: 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. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Test emergency calling. Checked 2026-09-24. [^26]: The emergency call routing policy references an online PSTN usage that must have Direct Routing configuration to reach the right PSTN gateways, and in particular there must be an OnlineVoiceRoute for the emergency dial string. 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. [^27]: Turning on External location lookup mode in an emergency calling policy (ExternalLocationLookupMode Enabled in PowerShell) lets users configure their own emergency address when working from a network location outside the corporate network. 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, step 4. Checked 2026-09-24. [^28]: Users automatically get the global (Org-wide default) emergency calling policy unless a custom one is assigned; the global policy can be edited but not renamed or deleted, and network sites take custom policies. Source: [Manage emergency calling policies in Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/manage-emergency-calling-policies), Introduction. Checked 2026-09-24. [^29]: An emergency calling policy's notification mode is one of: Send notification only (a Teams chat message to the specified users and groups), Conferenced in but are muted (chat plus listen-only), or Conferenced in and are unmuted (chat plus the ability to unmute and speak with the caller and PSAP). 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. [^30]: Each emergency number in a call routing policy has a dial string that the route pattern must match exactly and zero or more semicolon-separated dial masks that are translated to the dial string (for example 112 masked to 911); dial strings and masks must be unique within a policy. 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, step 5.1-5.2 and Note. Checked 2026-09-24. [^31]: 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. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Configure emergency policies; Enable users and sites. Checked 2026-09-24. [^32]: An emergency call routing policy has a Dynamic emergency calling setting; when it is on, Teams retrieves policy and location information from the service and includes it in the emergency call. 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, step 4. Checked 2026-09-24. [^33]: The PSTN usage record in an emergency call routing policy selects the route for emergency calls, and Microsoft says that route should point to a SIP trunk dedicated to emergency calls or to an ELIN gateway that routes to the nearest PSAP. 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, step 5.3. Checked 2026-09-24. [^34]: 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). Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Test emergency calling (933 bullet names only Calling Plan, Operator Connect and Teams Phone Mobile; Direct Routing bullet names only ERSPs). Checked 2026-09-24. [^35]: Microsoft's two pages disagree on where Direct Routing Emergency Routing Service Providers apply: the configuration page says the United States and Canada, while the Direct Routing considerations page labels them US only (disputed). Source: [Considerations for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/considerations-direct-routing), Emergency call routing for Direct Routing, list of two solutions ('Emergency Routing Service Providers (US only)'). Checked 2026-09-24. [^36]: 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). Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Supported clients, notes. Checked 2026-09-24. [^37]: 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. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Configure Location Information Service; Using the Microsoft Teams admin center; Using PowerShell. Checked 2026-09-24. [^38]: 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. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Plan for emergency calling, step 2. Checked 2026-09-24. [^39]: Subnets used in network sites must also be defined in the Location Information Service for them to render dynamic locations. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Configure Location Information Service, Important box. Checked 2026-09-24. [^40]: 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. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Configure network settings, note on LIS subnets. Checked 2026-09-24. [^41]: When an emergency number is dialed, Teams uses location in this precedence: an administrator-defined LIS address; a user-confirmed or edited address tied to the current network; an operating-system-suggested address; a manually entered address without service resolution; the address statically assigned to the user's phone number. Source: [Emergency addresses for remote locations](https://learn.microsoft.com/en-us/microsoftteams/emergency-calling-dispatchable-location), Location precedence. Checked 2026-09-24. [^42]: Network configuration lookups are not supported with cloud proxy 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 box. Checked 2026-09-24. [^43]: For Direct Routing, Teams clients no longer send emergency calls with a '+' before the emergency dial string (for example +911), so voice route patterns for emergency numbers must match without the '+'. 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. [^44]: Whether a tenant admin can set, change or delete the registered emergency address of an Operator Connect user depends on the capabilities the carrier assigned to the number when uploading it to the customer's inventory. 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. [^45]: For Operator Connect in the United States and Canada, emergency calls route automatically to the number's carrier and dynamic routing is part of the carrier's service, so it does not need to be procured from another provider. Source: [Considerations for Operator Connect](https://learn.microsoft.com/en-us/microsoftteams/considerations-operator-connect), Emergency call enablement for Operator Connect; Emergency call routing for Operator Connect. Checked 2026-09-24. [^46]: 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. [^47]: A place assigned to a user or phone number cannot be deleted until those users and numbers are moved to a different location. Source: [Add places to emergency locations](https://learn.microsoft.com/en-us/microsoftteams/add-change-remove-emergency-place-organization), Remove a place from an emergency location, Note. Checked 2026-09-24. [^48]: A place (building, floor or office) is added under Locations > Emergency addresses > the address > Places, and can optionally carry an ELIN. Source: [Add places to emergency locations](https://learn.microsoft.com/en-us/microsoftteams/add-change-remove-emergency-place-organization), Add a place to an emergency location, Using the Microsoft Teams admin center, steps 1-5. Checked 2026-09-24. [^49]: A place is typically a floor, building, wing or office associated with an emergency address, an address can have an unlimited number of places, and each address and each address-plus-place combination gets its own location ID, which is what 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 (Place; Emergency location). Checked 2026-09-24. [^50]: Some changes to network settings, 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. Checked 2026-09-24. [^51]: For Calling Plan and Operator Connect in the United States, if an emergency caller cannot update their location to the screening center, the call is transferred to the PSAP serving the caller's registered address. Source: [Considerations for Calling Plans](https://learn.microsoft.com/en-us/microsoftteams/considerations-calling-plan), Emergency call routing for different countries/regions, United States row. Checked 2026-09-24. [^52]: Extended notifications set notification behaviour per emergency dial string, so a separate entry for the test number 933 can be defined that sends 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. Checked 2026-09-24. [^53]: With Calling Plan or Operator Connect the emergency numbers used in notification settings are predefined (for example 911 and 933), whereas with Direct Routing they must be defined in an emergency call routing policy. Source: [Configure security desk notifications](https://learn.microsoft.com/en-us/microsoftteams/emergency-calling-security-desk-notifications), Configure extended notifications, paragraph after the Note. Checked 2026-09-24. [^54]: If any extended notification uses a conferenced notification mode, the policy must also have a default entry with no dial string, at least one user, group or PSTN number, and a conferenced notification mode. Source: [Configure security desk notifications](https://learn.microsoft.com/en-us/microsoftteams/emergency-calling-security-desk-notifications), Configure extended notifications, Note after example table. Checked 2026-09-24. [^55]: For security desk notification, a client uses the emergency calling policy of the network site it is in; if the site has none or the site is undefined it uses the user's policy; and if it cannot obtain any policy the user is not enabled for security desk notification. Source: [Configure security desk notifications](https://learn.microsoft.com/en-us/microsoftteams/emergency-calling-security-desk-notifications), Configure security desk notifications, bulleted lookup order. Checked 2026-09-24. [^56]: A PSTN number to dial for emergency notifications can be entered only when a conferenced notification mode is selected, and the PSTN party joined this way cannot unmute. Source: [Configure security desk notifications](https://learn.microsoft.com/en-us/microsoftteams/emergency-calling-security-desk-notifications), Introduction; Configure extended notifications, fourth bullet. Checked 2026-09-24. [^57]: If Shared Calling for Calling Plans or Operator Connect is configured in the same tenant as Direct Routing, site-assigned emergency call routing policies cannot be used. Source: [Manage emergency call routing policies for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/manage-emergency-call-routing-policies), Introduction, second Note. Checked 2026-09-24. [^58]: If an emergency calling policy is assigned to both a network site and a user, and the user 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 on site and user assignment. Checked 2026-09-24. [^59]: Each network site must be associated with a network region (New-CsTenantNetworkSite -NetworkRegionID) and each subnet can be associated with only one site (New-CsTenantNetworkSubnet -NetworkSiteID); external trusted IPs are added with New-CsTenantTrustedIPAddress or on the Trusted IPs tab. Source: [Manage your network topology for cloud voice features in Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/manage-your-network-topology), Define network sites; Define network subnets; Define external subnets (external trusted IP addresses); Manage external trusted IP addresses. Checked 2026-09-24. [^60]: 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. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Supported clients. Checked 2026-09-24. [^61]: 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. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Test emergency calling. Checked 2026-09-24. [^62]: 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. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Configure network settings, trusted IP paragraph and note. Checked 2026-09-24. [^63]: In the United States, an OS-suggested address confirmed by the user or an address chosen through autosuggest goes direct to the PSAP, while an OS address that is unconfirmed or manually edited, or an address typed in manually, is screened before transfer. 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. [^64]: 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. Source: [Configure dynamic emergency calling](https://learn.microsoft.com/en-us/microsoftteams/configure-dynamic-emergency-calling), Supported clients, note on Teams web client. Checked 2026-09-24. [^65]: The user-entered work-from-home address experience is for Teams desktop on Windows and Mac; Teams phones do not support it, and Teams mobile supports automatic location detection but not user entry. Source: [Emergency addresses for remote locations](https://learn.microsoft.com/en-us/microsoftteams/emergency-calling-dispatchable-location), Notes and restrictions. Checked 2026-09-24. [^66]: On Windows, whether the location service and application access to location are available to Teams can be managed with group policy or MDM, and privacy settings can conflict with automatic location detection. 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 (final paragraphs); Notes and restrictions. Checked 2026-09-24. [^67]: Dynamic emergency calling, which routes emergency calls and notifies security personnel based on the Teams client's current location, is available for Microsoft Calling Plans, Operator Connect, Teams Phone Mobile and Direct Routing. Source: [Plan and manage emergency calling](https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing), Plan and manage emergency calling, section 'Dynamic emergency calling'. Checked 2026-09-24. [^68]: To use PSTN telephony with Teams Phone, a user account must be licensed with the Teams Phone application and also be equipped with a PSTN solution from a PSTN service provider. Source: [PSTN connectivity options](https://learn.microsoft.com/en-us/microsoftteams/pstn-connectivity), PSTN connectivity options, section 'What is the Public Switched Telephone Network (PSTN)?'. Checked 2026-09-24. [^69]: Direct Routing requires a Microsoft-certified SBC, PSTN trunks to it, users homed online, a public IP, an SBC FQDN in a verified tenant domain (not *.onmicrosoft.com) with public DNS, and a publicly trusted TLS certificate. Source: [Plan Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan), Plan Direct Routing, section 'Infrastructure requirements' table and section 'SBC domain names'. Checked 2026-09-24. [^70]: Microsoft supports Teams Phone with Direct Routing only when certified SBCs are used, expects the SBC vendor to investigate first and escalate, and may decline support requests involving non-certified SBCs. Source: [Plan Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan), Plan Direct Routing, sections 'Supported Session Border Controllers (SBCs)' and 'Support boundaries'. Checked 2026-09-24. [^71]: Operator Connect requires users to have Teams Phone licenses and to be configured in Teams Only mode, and a certified operator must serve the countries or regions being deployed. Source: [Plan for Operator Connect](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-plan), Plan for Operator Connect, section 'Step 1: Verify prerequisites'. Checked 2026-09-24. [^72]: To assign an emergency location to a network identifier for dynamic emergency calling, the emergency address must be validated and carry a geo code; addresses created with the Teams admin center map search get both automatically. Source: [Plan and manage emergency calling](https://learn.microsoft.com/en-us/microsoftteams/what-are-emergency-locations-addresses-and-call-routing), Plan and manage emergency calling, sections 'Emergency address validation' and 'Emergency address geo codes', Important block. Checked 2026-09-24. [^73]: Under Operator Connect, the operator is responsible for PSTN connectivity, number provisioning and porting, calling services and PSTN-related support; Microsoft is responsible for Teams services, Teams Phone administration, the Teams admin center and the Teams-to-operator integration. Source: [Plan for Operator Connect](https://learn.microsoft.com/en-us/microsoftteams/operator-connect-plan), Plan for Operator Connect, section 'Support boundaries'. Checked 2026-09-24. [^74]: In SBA mode, emergency calls can still be placed but location information is not shared, and SBA does not support emergency call routing policies; emergency dial strings bypass normalization, so they fail unless the regular voice routing policy has a matching pattern. Source: [Survivable Branch Appliance for Direct Routing](https://learn.microsoft.com/en-us/microsoftteams/direct-routing-survivable-branch-appliance), Direct Routing SBA, section 'Known issues and considerations', 'In SBA mode, the following user actions aren't supported'. Checked 2026-09-24.