Source record · tier 2 current vendor documentation
Configure security desk notifications
- Publisher
- Microsoft
- URL
- https://learn.microsoft.com/en-us/microsoftteams/emergency-calling-security-desk-notifications
- Published
- 2026-03-25
- Updated
- unknown
- Accessed
- 2026-09-24
- HTTP status
- 200
- License
- Microsoft Learn terms of use; no-redistribution; short excerpts and locators only
Source notes citing this source
- A Teams emergency calling policy can define an extended notification for 933, and because it is a test number no notifications are sent to the security desk for those calls. in context
- If any Teams extended notification uses a conferenced-in notification mode, a default entry with no dial string must be set with at least one user, group or PSTN number and a conferenced-in mode. in context
- Teams security desk notification modes are chat only, conferenced in and muted, or conferenced in muted with the ability to unmute; an external PSTN number can be conferenced in but is not allowed to unmute. in context
- With Teams Calling Plan or Operator Connect the emergency numbers (911 and 933 in Microsoft's US example) are predefined, whereas Direct Routing admins must define them in an emergency call routing policy. in context
- For Teams security desk notification, a policy on the network site where the client is located is used first, otherwise the user's policy, and a client that obtains no emergency calling policy is not enabled for security desk notification. in context
- 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. in context
- 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. in context
- 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. in context
- 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. in context
- 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. in context
- An extended notification can be defined for the test number 933 so that test calls send no notification to the security desk. in context
- 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. in context
- 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. in context
- Microsoft documents security desk notifications as available with Calling Plans, Operator Connect and Direct Routing; the pages do not list Teams Phone Mobile. in context
Cite this source record
APA
WarmTransfer. (2026, March 25). Configure security desk notifications. WarmTransfer. https://warmtransfer.net/knowledge/sources/ms-learn-emergency-security-desk-notifications
BibTeX
@misc{warmtransfer-ms-learn-emergency-security-desk-notifications,
title = {Configure security desk notifications},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/sources/ms-learn-emergency-security-desk-notifications},
note = {Microsoft, accessed 2026-09-24}
}