How to Configure Teams Emergency Calling Extended Notifications in PowerShell

In enterprise unified communications and telephony, regulatory compliance frameworks (such as RAY BAUM’S Act and Kari’s Law in the United States, as well as equivalent health and safety mandates globally) require that emergency calls trigger immediate, automated notifications to on-site security personnel. When a remote or on-premises employee dials an emergency number (such as 911 or 999) from Microsoft Teams, the internal corporate security desk must be notified instantaneously with the caller’s identity and dynamic dispatchable location. To meet complex corporate requirements—such as alerting multiple security personnel, triggering automated conference bridges, notifying external security monitoring desks, and targeting distinct branch locations—Microsoft Teams supports Extended Notifications. Using the Microsoft Teams PowerShell module, administrators can define and bind CsTeamsEmergencyCallingExtendedNotification objects directly within emergency calling policies.

Understanding Teams Emergency Calling Extended Notification Architecture

Extended notifications expand standard Teams emergency calling policies by enabling multi-channel, multi-recipient alerting pipelines. Key capabilities include:

• Multiple Notification Targets: Standard policies historically allowed a single notification target. Extended notifications allow organizations to specify multiple recipients, combining internal Microsoft 365 security users, distribution groups, and external PSTN telephone numbers.
• Notification Modes: Administrators can configure different alert delivery styles:
  • NotificationOnly: Sends a silent pop-up banner and Teams chat alert to designated security desk personnel.
  • ConferencedMuted: Bridges security desk personnel into the emergency call as muted listeners to monitor the situation without interfering.
  • ConferencedUnMuted: Bridges security personnel directly into the active audio call with bidirectional audio capability to assist first responders.
• Emergency Dial String Scoping: Enables distinct notification routing rules based on the specific emergency number dialed (e.g. routing 911 calls to physical security and 988 crisis calls to confidential employee assistance teams).
• Integration with Dynamic E911: Automatically passes the caller’s verified civic address, floor, and port or wireless access point location data directly to the alerted security team.

Prerequisites and PowerShell Session Initialisation

Configuring emergency calling extended notifications requires the Microsoft Teams PowerShell module with Teams Administrator or Global Administrator privileges in Microsoft Entra ID.

Install or verify the latest Microsoft Teams module:

Get-Module -ListAvailable -Name MicrosoftTeams
Install-Module -Name MicrosoftTeams -Scope CurrentUser -Repository PSGallery -Force

Establish an authenticated remote management session:

Connect-MicrosoftTeams

Confirm the connection and verify cmdlet availability:

Get-Command *TeamsEmergencyCalling*

Inspecting Existing Emergency Calling Policies

Before attaching extended notifications, review existing emergency calling policies configured across your tenant.

Retrieve all defined emergency calling policies:

Get-CsTeamsEmergencyCallingPolicy

Inspect the specific parameters and any existing notification configurations on the Global policy:

Get-CsTeamsEmergencyCallingPolicy -Identity Global | Format-List Identity, Description, NotificationGroup, NotificationDialOutNumber, ExtendedNotifications

Review the ExtendedNotifications property, which stores the array of structured notification objects.

Creating an Extended Notification Object

Extended notifications are constructed in memory using New-CsTeamsEmergencyCallingExtendedNotification and then committed to an emergency calling policy via New-CsTeamsEmergencyCallingPolicy or Set-CsTeamsEmergencyCallingPolicy.

To configure an extended notification for on-site corporate security personnel when 911 is dialed:

$Notification1 = New-CsTeamsEmergencyCallingExtendedNotification -EmergencyDialString "911" -NotificationGroup "[email protected]" -NotificationMode "ConferencedMuted"

To create a secondary notification rule that dials an external PSTN monitoring service (e.g. an outsourced building security facility) in unmuted bridge mode:

$Notification2 = New-CsTeamsEmergencyCallingExtendedNotification -EmergencyDialString "911" -NotificationDialOutNumber "+14155550199" -NotificationMode "ConferencedUnMuted"

To configure an alert for non-emergency crisis support numbers (e.g. 988) providing chat notifications only to HR wellness coordinators:

$NotificationCrisis = New-CsTeamsEmergencyCallingExtendedNotification -EmergencyDialString "988" -NotificationGroup "[email protected]" -NotificationMode "NotificationOnly"

Binding Extended Notifications to an Emergency Calling Policy

Once the notification objects are initialized, create a new policy or update an existing one to apply the extended notifications.

To create a new policy for an enterprise corporate headquarters with multiple extended notifications:

New-CsTeamsEmergencyCallingPolicy -Identity "HQ-Campus-EmergencyPolicy" -Description "Emergency calling policy with extended multi-channel security desk alerts." -ExtendedNotifications @($Notification1, $Notification2, $NotificationCrisis)

To update an existing policy with updated extended notification objects:

Set-CsTeamsEmergencyCallingPolicy -Identity "HQ-Campus-EmergencyPolicy" -ExtendedNotifications @($Notification1, $Notification2)

Verify that the extended notifications are committed and bound properly:

(Get-CsTeamsEmergencyCallingPolicy -Identity "HQ-Campus-EmergencyPolicy").ExtendedNotifications | Format-Table EmergencyDialString, NotificationGroup, NotificationDialOutNumber, NotificationMode

Assigning Emergency Policies to Enterprise Users and Sites

Deploy the emergency calling policy to designated users, groups, or network sites.

To assign the policy directly to an individual user:

Grant-CsTeamsEmergencyCallingPolicy -Identity "[email protected]" -PolicyName "HQ-Campus-EmergencyPolicy"

To deploy the policy to all users in a specific branch location using Microsoft Entra Security Groups:

$GroupId = (Get-AzureADGroup -SearchString "HQ Facilities Personnel").ObjectId
New-CsGroupPolicyAssignment -GroupId $GroupId -PolicyType TeamsEmergencyCallingPolicy -PolicyName "HQ-Campus-EmergencyPolicy" -Rank 1

To associate the emergency policy with a physical network site defined in the Teams Location Information Server (LIS):

Set-CsTenantNetworkSite -Identity "HQ-Campus" -EmergencyCallingPolicy "HQ-Campus-EmergencyPolicy"

Clearing Extended Notifications from a Policy

To remove all extended notifications from a policy and return to standard legacy alerting behaviour:

Set-CsTeamsEmergencyCallingPolicy -Identity "HQ-Campus-EmergencyPolicy" -ExtendedNotifications @()

Verify that the ExtendedNotifications array is now empty:

(Get-CsTeamsEmergencyCallingPolicy -Identity "HQ-Campus-EmergencyPolicy").ExtendedNotifications

Troubleshooting Emergency Notification Delivery and Dial-Out

When implementing and auditing automated emergency notifications, verify these critical operational safeguards:

• Notification Group Mailbox Configuration: The email or group specified in -NotificationGroup must be a mail-enabled security group or a specific user account with an active Microsoft Teams license. Ensure the group is allowed to receive internal system notifications generated by the Teams service.
• PSTN Outbound Calling Credit: If -NotificationDialOutNumber is configured to dial an external security guard desk or third-party PSAP monitor via PSTN, ensure the tenant has sufficient Communications Credits or active Calling Plans with outbound authorization. If outbound credits are exhausted, the external dial-out will fail while the internal Teams chat alert succeeds.
• Emergency Location Information Replication: Confirm that the caller’s device is correctly mapped to a civic address via subnet, BSSID, or port mapping in CsTenantNetworkSubnet. Extended notifications include location data only if the underlying device resolved its LIS location prior to placing the call.

By configuring extended notifications in PowerShell using CsTeamsEmergencyCallingExtendedNotification, enterprise administrators fulfill statutory compliance obligations and ensure corporate security teams can respond immediately during critical emergency events.