In enterprise telecommunications and Microsoft Teams Phone architectures, regulatory mandates (such as the RAY BAUM’S Act in the United States and European emergency services frameworks) strictly require organizations to deliver dispatchable caller locations whenever users dial emergency numbers (like 911 or 112). In enterprise environments utilizing Direct Routing or Operator Connect, emergency calls cannot simply be routed over generic PSTN voice trunks; they must traverse specialized Session Border Controller (SBC) gateways certified to carry Emergency Location Identification Numbers (ELIN) and dynamic civic address data directly to Public Safety Answering Points (PSAPs).
To coordinate the routing of emergency calls through certified carrier trunks and designated emergency service providers, Microsoft Teams provides Carrier Emergency Call Routing Policies. Administered via the CsTeamsCarrierEmergencyCallRoutingPolicy cmdlets in PowerShell, these policies govern the exact SIP PSTN gateways, usage records, and number substitution rules that process emergency calls when users dial public safety numbers. This guide demonstrates how to inspect, create, modify, and assign carrier emergency call routing policies across Microsoft Teams tenants.
Architecture of Carrier Emergency Call Routing in Teams Phone
When an emergency call is initiated by a Microsoft Teams user, the Teams voice routing core evaluates multiple layers of policy logic:
- Emergency Calling Policy (
CsTeamsEmergencyCallingPolicy): Dictates whether dynamic emergency calling is enabled, whether security desks are notified, and configures emergency dial strings (e.g. 911, 933 for testing). - Carrier Emergency Call Routing Policy: Defines the physical and logical telephony routes that emergency calls must follow. It maps emergency dial strings to specific PSTN carrier gateways (SBCs) configured with emergency service provider connections (such as Intrado, Bandwidth, or Sinch).
- ELIN / PIDF-LO Location Injection: As the call is routed through the designated gateway, Teams packages the caller’s dynamic physical location (resolved via subnet, Wi-Fi BSSID, or switch port) into standard SIP Presence Information Data Format Location Object (PIDF-LO) headers or ELIN numbers, ensuring the PSAP dispatcher receives real-time building, floor, and room information.
Connecting to the Microsoft Teams PowerShell Module
Configuring carrier emergency routing requires administrative credentials with Teams Administrator or Global Administrator privileges and the Microsoft Teams PowerShell module (version 4.0.0 or later).
Open an elevated PowerShell session and execute:
# Install or update the Microsoft Teams module
Install-Module -Name MicrosoftTeams -Force -AllowClobber
# Authenticate to the Microsoft 365 tenant
Connect-MicrosoftTeams
Inspecting Existing Carrier Emergency Routing Policies
Before implementing new emergency routing configurations, review the baseline policies configured in your tenant.
To inspect all provisioned carrier emergency call routing policies, execute:
Get-CsTeamsCarrierEmergencyCallRoutingPolicy | Format-Table Identity, Description
To inspect the Global tenant-wide default policy in detail:
Get-CsTeamsCarrierEmergencyCallRoutingPolicy -Identity "Global" | Format-List *
To view the specific emergency dial strings and gateway routing entries embedded within a policy, examine its EmergencyDialStrings collection:
(Get-CsTeamsCarrierEmergencyCallRoutingPolicy -Identity "Global").EmergencyDialStrings
Creating Carrier Emergency Call Routing Policies with New-CsTeamsCarrierEmergencyCallRoutingPolicy
To route emergency calls originating from a specific regional campus through local SBCs and dedicated carrier trunks, create a custom policy instance.
First, define the emergency number dial string rules using New-CsTeamsEmergencyNumberRange or by defining the route objects:
# Create route entry for 911 routing through primary emergency SBC
$Route911 = New-CsTeamsCarrierEmergencyCallRoutingEntry `
-EmergencyDialString "911" `
-PSTNGatewayFQDN "sbc-emergency01.corp.contoso.com" `
-EmergencyDialMask "911;112"
# Create test route entry for 933 (e911 address verification test)
$Route933 = New-CsTeamsCarrierEmergencyCallRoutingEntry `
-EmergencyDialString "933" `
-PSTNGatewayFQDN "sbc-emergency01.corp.contoso.com"
Now instantiate the new carrier emergency routing policy with the defined routing entries:
New-CsTeamsCarrierEmergencyCallRoutingPolicy `
-Identity "Carrier-Emergency-US-East" `
-EmergencyDialStrings @($Route911, $Route933) `
-Description "Routes East Coast emergency calls through certified carrier SBCs"
Verify that the policy and route entries were created successfully:
Get-CsTeamsCarrierEmergencyCallRoutingPolicy -Identity "Carrier-Emergency-US-East"
Modifying Existing Policy Routes with Set-CsTeamsCarrierEmergencyCallRoutingPolicy
When migrating to redundant SBC gateways or adding secondary carrier paths, update the policy to ensure high-availability failover.
To update an existing policy with secondary backup gateway routing:
# Define secondary failover route entry
$BackupRoute911 = New-CsTeamsCarrierEmergencyCallRoutingEntry `
-EmergencyDialString "911" `
-PSTNGatewayFQDN "sbc-emergency02.corp.contoso.com" `
-EmergencyDialMask "911;112"
# Apply updated route list to the policy
Set-CsTeamsCarrierEmergencyCallRoutingPolicy `
-Identity "Carrier-Emergency-US-East" `
-EmergencyDialStrings @($Route911, $BackupRoute911, $Route933)
Confirm the updated route collection:
(Get-CsTeamsCarrierEmergencyCallRoutingPolicy -Identity "Carrier-Emergency-US-East").EmergencyDialStrings | Format-Table EmergencyDialString, PSTNGatewayFQDN, EmergencyDialMask
Assigning Carrier Emergency Routing Policies to Users and Sites
Once custom carrier policies are configured, assign them to target users, common area phones, or network sites using Grant-CsTeamsCarrierEmergencyCallRoutingPolicy.
To assign the policy directly to an individual user account:
Grant-CsTeamsCarrierEmergencyCallRoutingPolicy `
-Identity "[email protected]" `
-PolicyName "Carrier-Emergency-US-East"
To verify the effective policy applied to a user:
Get-CsOnlineUser -Identity "[email protected]" | Select-Object DisplayName, UserPrincipalName, TeamsCarrierEmergencyCallRoutingPolicy
To assign the policy in bulk across an entire regional office using an Entra ID security group:
# Assign policy by Entra ID Group ID
$GroupId = "b2c3d4e5-f6a7-8901-bcde-fa2345678901"
New-CsGroupPolicyAssignment `
-GroupId $GroupId `
-PolicyType TeamsCarrierEmergencyCallRoutingPolicy `
-PolicyName "Carrier-Emergency-US-East" `
-Rank 1
To unassign a custom policy from a user, reverting them to the Global default:
Grant-CsTeamsCarrierEmergencyCallRoutingPolicy -Identity "[email protected]" -PolicyName $null
Removing Obsolete Carrier Emergency Routing Policies
When decommissioning retired branch SBCs or merging telephony profiles, remove obsolete policies.
Before deleting a policy, verify that no users or group assignments remain attached to it:
Remove-CsTeamsCarrierEmergencyCallRoutingPolicy -Identity "Carrier-Emergency-US-East" -Confirm:$false
Testing and Validating Carrier Emergency Call Routing
To verify that emergency routing policies route correctly through the SBC gateway without dialing 911 live:
- Use the standardized automated 933 test dial string (or national equivalent test number).
- Place a call to
933from the Teams client. - The call routes through the certified emergency gateway defined in the policy. The carrier automated test responder will verbally read back the phone number and the exact dispatch address transmitted via PIDF-LO, confirming end-to-end regulatory compliance.