Emergency Calling in Teams: A Complete Guide for Microsoft Teams Administrators

Emergency calling in Microsoft Teams is a critical, often-regulated feature that ensures anyone in your organization can quickly connect with emergency services when it counts. This capability goes far beyond placing a simple phone call—it hinges on detailed configurations, accurate location data, and tight compliance with strict legal requirements. If you're the person the organization turns to for Microsoft Teams or SharePoint administration, it's on you to make sure every detail clicks into place.

In this guide, you’ll find straightforward explanations and actionable steps, all tailored to the unique needs of IT and compliance professionals. We’ll walk through the basics—like licensing and network setup—and dive deep into advanced topics like policy management, PowerShell automation, and dynamic location services. Along the way, we’ll highlight compliance issues such as Kari’s Law and RAY BAUM’s Act, so nothing slips through the cracks when you deploy emergency calling in Teams.

If you’re already thinking about Microsoft Teams governance—the rules, roles, and guardrails that keep your digital workplace productive and compliant—this guide will help you weave emergency call readiness right into that framework. For the broader governance story, check out how Microsoft Teams Governance turns chaos into confident collaboration. Here, though, we’re all about making your organization safe, ready, and 100% accountable in an emergency.

Getting Started with Emergency Calling Teams: Setup Essentials

Before anyone picks up Teams to call 911 or another emergency number, there’s a bit of prep work you need as an admin. This isn’t just about checking a box—it’s about ensuring you have the right foundation for both safety and compliance. Miss a piece, and you could risk misrouted calls or failing to comply with local laws.

The groundwork for emergency calling in Microsoft Teams involves understanding your existing network layout, confirming your organization’s licensing, and verifying hardware and software are all compatible. These fundamentals will help ensure that when an emergency call does happen, it gets routed quickly and accurately to the nearest emergency services provider with the right location information attached.

This section provides a big-picture look at essential steps before diving into the nitty-gritty—think of it as a guide to knowing what you don’t know. By getting set up right from the very start, you’ll avoid the classic pitfalls admins run into on emergency call projects and keep your rollout on solid ground. Next, we’ll get specific about what to check and configure—so you won’t miss a single beat.

Emergency Calling Teams: Prerequisites and Network Configuration

1. Microsoft Teams Phone Licensing: To use emergency calling in Teams, your users must be licensed for Teams Phone (formerly Phone System). This may involve an add-on license for Microsoft 365 users or be included in bundled E5 subscriptions. Double-check users are assigned the correct phone system licensing before proceeding.
2. PSTN Connectivity Setup: You'll need a way to connect Teams to the traditional phone network (PSTN). This can be accomplished with Microsoft Calling Plans, Direct Routing (via an SBC), or Operator Connect. Confirm your chosen option is in place and supported in your region before enabling emergency calling features.
3. Network Topology Mapping: Emergency calls must be routed correctly based on the user's physical location. Map your organization’s network topology—including wired subnets, Wi-Fi access points, and VPNs—to physical addresses in Teams. This step is key for accurate location detection and call routing to the right public safety authorities.
4. Supported Regions and Regulations: Emergency calling is not available everywhere. Confirm that your country and region support Teams emergency calling per Microsoft’s published lists, and verify any legal specificities (like 911 in the US, 112 in the EU, 000 in Australia).
5. Network Infrastructure and Quality: A reliable, well-configured network is crucial for emergency calls. Prioritize network readiness, including QoS settings for voice, bandwidth management, firewall rule updates for required IPs/ports, and redundant connections to prevent outages during emergencies.
6. Monitoring and Security Integration: Plan to integrate Teams with your security and monitoring tools to log emergency call events, push alerts to the security desk, and enable incident reviews. This supports audit trails and ongoing regulatory compliance.
7. Validation Checklist: Before activating emergency calling, verify all the steps above. Test with your security team to ensure technical and legal requirements are covered, reducing risks of call failure or compliance gaps.

Teams Launch: Location Detection Setup and User Onboarding

1. Initial Location Detection: During first-time Teams launch, the client attempts to detect the user’s location. This is based on the underlying network connection—using wired subnet information, Wi-Fi details (like BSSID), or device GPS (on mobile).
2. User Prompt and Data Entry: If Teams can’t auto-detect an accurate location, users are prompted to manually enter their current address. IT admins must communicate why and how to complete this step for emergency call accuracy.
3. Configuration by IT: Before onboarding users, admins should define and assign trusted network locations in Teams Admin Center or PowerShell. Users connected to these will have their emergency location set automatically, reducing friction during onboarding.
4. User Education: Prepare onboarding materials or quick guides explaining the importance of allowing Teams to access location data and regularly updating it, especially for mobile/remote staff. This boosts accuracy and compliance with emergency response regulations.

Configuring Emergency Calling Teams Policies in the Teams Admin Center

Once your organization’s infrastructure is prepped and your licensing is in place, it’s time to set up the rules and policies that govern how emergency calling will work company-wide. The Teams Admin Center is your main dashboard for this, giving you granular control over policies for different groups, locations, or scenarios.

Through Teams Admin Center, you can define not just who can make emergency calls, but what numbers trigger those calls, where alerts and notifications are sent, and the location requirements for compliance. It’s your toolkit for making sure emergency responses fit your organization’s structure, whether you’re managing a handful of users or thousands across multiple sites.

The following sections break down how to create and customize these emergency policies, and how to assign them to users, departments, or physical locations. By approaching policy management with purpose and consistency, you’ll set a strong governance baseline and enable safer, faster responses when the unexpected happens.

Creating and Managing Emergency Calling Teams Policies in Teams Admin Center

1. Create Custom Emergency Policies: In the Teams Admin Center, you can build your own emergency calling policies (like “Contoso Emergency Calling Policy 1”). This lets you specify which emergency numbers are active (e.g., 911, 112), and assign unique behaviors for different sites or user types.
2. Define Notification and Escalation Settings: You can add emergency notification emails so that, for example, security teams or front desk staff get real-time alerts when an emergency call is made. These notifications can support compliance programs and onsite incident management.
3. Set Location Requirements: Policies should mandate that users provide (or allow Teams to detect) accurate location information. Enforcing this keeps your organization compliant with regulations like RAY BAUM’s Act, which requires a precise dispatchable address for emergency responders.
4. Policy Assignment by Site or User: Assign policies at the group, user, or network location level for maximum flexibility. Multi-site organizations can use different rules for corporate, remote, and satellite offices, supporting dynamic working styles.
5. Governance and Auditing: Attach policy management to your overall Teams governance practices. For more on best practices to keep your workspace organized, compliant, and efficient, see this guide on Teams Governance.

Enable Users and Assign Emergency Addresses in Teams

1. Enable Emergency Calling for Target Users: In Teams Admin Center, select users who need emergency calling enabled. Ensure they have Teams Phone assigned and that you’ve reviewed applicable legal requirements for their locations.
2. Assign Emergency Addresses: For users on corporate networks, assign emergency addresses to appropriate network identifiers (like subnets or Wi-Fi SSIDs). For remote users, instruct them to provide their exact address in Teams client settings to ensure accurate emergency call routing.
3. Regularly Update Address Assignments: Especially for organizations with mobile or hybrid workers, create a process for users to update their location whenever they move between locations. Automate reminders or use policy enforcement as needed.
4. Verify Legal Compliance: Document all address assignments and configurations to ensure auditability and legal adherence—especially under laws like RAY BAUM’s Act and local equivalents.

Advanced Configuration with Teams PowerShell for Emergency Calling

If you manage a large or fast-changing environment, the Teams Admin Center UI may start to feel a little slow. That’s where PowerShell comes in. Using PowerShell, you can automate emergency calling setup, push changes out to thousands of users or sites, and ensure consistency across all your Teams deployments.

This approach is ideal for organizations with strict audit needs, frequent moves/adds/changes, or advanced configuration requirements not supported in the graphical interface. Through scripting, you can not only enforce policies at scale, but also perform batch updates and integrate with other IT processes. The next section shows you how to put this to work for your emergency response system.

PowerShell Scripts to Manage Emergency Settings and PIDF-LO in Teams

1. Bulk Assign Emergency Policies: Use PowerShell commands like Grant-CsTeamsEmergencyCallingPolicy to assign emergency calling policies to users or entire groups at scale. This replaces repetitive clicks in Teams Admin Center and supports automated user provisioning.
2. Configure and Update Emergency Addresses: Leverage Set-CsOnlineLisLocation and related cmdlets to manage location information tied to network regions, subnets, and WLANs. This improves location accuracy and streamlines updates as your physical footprint changes.
3. Modify PIDF-LO Data: The PIDF-LO (Presence Information Data Format-Location Object) format carries location data to emergency operators. Advanced PowerShell scripting can adjust, validate, or bulk correct PIDF-LO records—ensuring downstream systems and emergency dispatchers get accurate data every time.
4. Manage Emergency Call Routing Rules: Use PowerShell to configure call routing policies and rules that dictate how emergency calls are handled based on region, calling number, or other attributes. This is crucial in multi-site enterprises and allows for rapid response to changing regulations or business needs.
5. Audit and Export Configuration: PowerShell enables you to export policy assignments, location data, and emergency call records for compliance auditing. This supports internal reviews, post-incident analysis, and reporting to regulators or authorities as required.

Dynamic 911 Teams and Location Detection for Accurate Emergency Response

Modern workplaces aren’t just four walls—they’re coffee shops, home offices, and airport lounges. That’s why static emergency call routing no longer cuts it. With dynamic 911 in Microsoft Teams, you get real-time location updates that follow users wherever they are, supporting the safety needs of your mobile and hybrid workforce.

Dynamic 911 combines Teams’ smart location detection with policies and routing rules, ensuring every emergency call includes the caller’s latest location—even as they move between offices or connect from home. This not only improves your organization’s compliance posture but can make a real-life difference when seconds matter.

Up next, we’ll unravel how dynamic location services work, their impact on call routing and legal compliance, and exactly what end users (and their devices) need to participate in this life-saving ecosystem.

How Dynamic 911 Works in Teams: Location Updates and Emergency Routing

1. Automatic Location Updates: Teams constantly analyzes the user’s network connection—wired subnet, Wi-Fi SSID/BSSID, or even device GPS (on supported clients)—to pinpoint location. As users move, Teams attempts to update their location automatically in the background.
2. Real-Time Location Retrieval: When a user dials an emergency number, Teams pulls the latest detected or entered location and attaches it to the outbound call. This ensures emergency services receive a dispatchable address for the caller’s current site, not just a corporate HQ.
3. Integration with PSAPs (Public Safety Answering Points): The dynamically generated location data gets routed to local PSAPs, making sure that first responders know where to send help, even if the user isn’t in an expected place or is traveling between offices.
4. Fallback and Limitation Handling: If a user is off-network, Teams will prompt them to update their address manually. Admins should educate remote workers on this step to avoid inaccurate call routing.
5. Best Practices for Hybrid Organizations: Map all corporate subnets and Wi-Fi points in Teams. Encourage mobile and remote users to check and update their locations regularly for compliance and user safety.

Enabling Location on Personal Devices and Teams Supported Clients

• Windows and Mac Clients: Instruct users to enable location access in their device settings and give Teams the required permissions. This ensures automatic detection, especially when on corporate networks or using Wi-Fi.
• iOS and Android Devices: On mobile, users should enable GPS/location services for the Teams app. Remind staff to accept prompts and review app permissions after updates or OS changes.
• Supported Client Versions: Ensure that users’ Teams clients are up to date, as newer versions support more advanced location and dynamic 911 features. Outdated apps may prevent proper location handoff to emergency services.
• Troubleshooting Common Issues: Provide a support channel for users to report inaccurate location data. Most problems stem from denied permissions or outdated network mapping in Teams Admin Center.

Emergency Routing Arranging and Configuring Network for Emergency Calls

Having the right setup isn’t just about getting location data—it’s also about making sure every emergency call lands with the right local responders, no matter where your people are working. Emergency call routing in Teams hinges on detailed network and provider configurations that connect you to the right PSAP (Public Safety Answering Point), whether your staff are at headquarters or a remote corner of the country.

This section lays out the essentials for arranging both your emergency call routing and the underlying network/location mappings. The goal is to guarantee calls go exactly where they need to—even as your org grows, restructures, or sees its workforce spread out. Strong routing arrangements are the backbone of both legal compliance and practical staff safety.

The next topics break down your choices in routing providers, how to set them up with Teams, and the steps to map your physical and network locations so that nothing falls through the cracks when every second matters.

Emergency Routing Setup, Provider Choices, and Call Routing in Teams

• Select a Routing Provider: Your call routing provider (such as an Emergency Routing Service, E911 provider, or Operator Connect partner) is responsible for connecting Teams emergency calls with the right PSAP based on the caller’s location. Carefully evaluate partners for regional compliance, reliability, and integration capabilities.
• Integrate with Teams: Provision your chosen provider in Microsoft Teams using direct routing or Operator Connect. Each provider will provide steps for connecting via SIP trunk, IP addresses, or API—be sure to follow exact requirements for redundancy and compliance.
• Configure Voice Routing: In Teams, define emergency dial strings, trusted IP addresses, and region-based rules to ensure calls from different sites or locations are routed appropriately. This can be refined further with PowerShell if your needs go beyond the admin UI.
• Regional and Campus Rules: For organizations with sites across states or countries, create campus-specific or multi-region rules. These dictate where specific numbers (like 911 or 112) should go based on detected location or network segment.
• Monitor and Test Routing Reliability: Routinely test routing arrangements using safe test calls, validate all address mappings, and confirm your routing provider delivers calls to the right authorities—including backup in case of failures.

Configure Network and Location Service for Teams Emergency Calling

1. Map Physical Addresses to Network Subnets: In Teams Admin Center or via PowerShell, link your physical office addresses to specific network subnets, Wi-Fi access points, or VLANs. This mapping lets Teams automatically assign the right dispatchable address during emergency calls.
2. Configure Teams Location Service: Define locations in the Teams location service, including detailed floor, suite, or building information for larger sites. This boosts location accuracy for both compliance and faster emergency response.
3. Update Regularly: Make it a routine task to update location and network mappings whenever there are office moves, new branches, or Wi-Fi network changes. This keeps your emergency address database accurate and legal.
4. Compliance and Documentation: Maintain documentation showing all configured mappings and any recent changes, supporting both audits and post-incident reviews where required.

Testing Emergency Calling Teams Features and Monitoring Feedback

Getting your emergency calling setup together is only half the game. The other half? Making sure it really works—without accidentally sending first responders racing to your office when all you wanted was a dry run. Testing and ongoing monitoring are mission critical for emergency calling projects in Teams.

This section lays out safe ways to validate your setup, review calling logs, and make sure the right folks are notified (and kept in the loop) if anything goes amiss. It also covers how to send feedback to Microsoft when something breaks or could work better for your organization’s needs. Let’s get into how to put your system through its paces—without setting off a real-life five-alarm response.

Testing Teams Emergency Calling Without Triggering Real Emergencies

• Use Official Test Numbers: Microsoft and many emergency routing partners provide safe test numbers that confirm routing and notifications—but don’t involve live emergency response. Always use these instead of dialing 911 or actual emergency numbers for testing.
• Validate Notification Workflows: As part of your test, make sure notifications hit all the right channels—security staff, front desk, teams chat, and email. Run simulated workflows so everyone knows their role if an actual call comes in.
• Simulate Diverse Scenarios: Test from multiple user types (on-site, remote, mobile) and various network segments to ensure correct location detection and call routing are working across your organization. Each scenario can reveal hidden gaps.

Monitoring Performance and Providing Feedback on Teams Emergency Calls

• Monitor Alerts and Incident Logs: Use Teams’ built-in tools and any integrated security systems to monitor alerts and logs for emergency calls. This supports ongoing performance checks and compliance requirements.
• Report Issues in Teams Admin Center: Log operational bugs or issues directly with Microsoft, attaching call summaries and system alerts as needed. The faster you report issues, the quicker they get resolved for everyone.
• Request Enhancements: Use feedback mechanisms in Teams or Microsoft’s user voice platforms to suggest features or changes for emergency calling. That’s especially useful if your scenario isn’t covered by current documentation or UI constraints.
• Governance and Audit Trail: Tie your monitoring and reviews back to the wider governance strategy. For more structured governance tips, see this post on Teams Governance and compliance.

Emergency Calling Compliance: Kari's Law, RAY BAUM's Act, and Legal Requirements in Microsoft Teams

1. Kari’s Law Requirements: All multi-line telephone systems (MLTS) in the US, including Microsoft Teams Phone, must allow users to dial 911 directly—no prefixes. Additionally, when anyone places a 911 call, designated personnel in the organization must receive an immediate notification, like an SMS, email, or Teams chat alert.
2. RAY BAUM’s Act Compliance: This law mandates providing a “dispatchable location” for emergency calls—down to floor, suite, or room number if possible. Teams must be set up so each call includes the caller’s specific location, not just a company or campus address.
3. State and Regional Variations: Some states and municipalities add further requirements (like on-premise security desk integration, signage, or logging). Stay connected with legal counsel or compliance personnel to keep up with new mandates tied to emergency calling systems.
4. International Regulations: Outside the US, you’ll encounter other emergency numbers (like 112 in the EU, 000 in Australia) and unique country-level rules on call routing, location accuracy, and provider responsibilities. Microsoft regularly updates supported regions and their unique obligations.
5. Audit, Reporting, and Record Retention: Maintain detailed logs of emergency calls, notifications, and location data. Be prepared for compliance audits and post-incident reviews, and use Teams’ built-in export tools or integrate with your organization’s compliance platform for complete recordkeeping.

Communicating Limitations and User Responsibilities for Emergency Calls in Teams

1. Educate on Limitations: Let users know that emergency calling in Teams depends on up-to-date location data and uninterrupted internet connectivity. If they’re working from unfamiliar or unregistered locations, there might be delays or errors in getting help where it’s needed.
2. Promote Location Awareness: Instruct users to check and update their location in Teams, especially when working remotely or moving offices. Regular prompts or training sessions can reduce risk and boost compliance with legal mandates like RAY BAUM’s Act.
3. Discuss Power and Internet Outages: Make it clear—if there’s a network, Wi-Fi, or power failure, Teams emergency calling won’t work. Users should always know alternate ways to call emergency services, particularly in disaster or campus outage scenarios.
4. User Training and Reminders: Create quick-reference guides, onboarding checklists, or pop-up reminders that reinforce the importance of location permissions and entering accurate information within the Teams client. Repeat education ensures new and returning users stay informed.
5. Emergency Preparedness Drills: Incorporate virtual or physical drills to practice emergency call scenarios within Teams, verifying users know what to do—and what to expect—if they ever need to use these features for real.