Remote Workers and 911: Is Your Teams Phone Ready?
December 15th, 2026
Microsoft Teams Phone follows the employee. A call placed from a kitchen table reaches the same phone system, the same number, and the same colleagues as a call placed from the office. Emergency calling is the exception that catches organizations unprepared: a 911 call from a remote worker can be routed correctly and still send responders to the wrong address.
The problem is location. When someone dials 911 from a traditional desk phone, the phone system knows which building and floor that phone sits on. A laptop running Teams at home has no such certainty. The business has to configure emergency calling so the system knows where the employee is, and the employee has to keep that information current. This article explains how Teams determines a 911 location, what to set up before employees work remotely, and where the arrangement can still fail.
Why Remote 911 Is Different
Emergency calling regulation has moved toward two requirements for multi-line telephone systems. Kari's Law requires direct dialing of 911 without an access code and a notification to a designated contact on site. The RAY BAUM'S Act requires a dispatchable location, meaning a street address and additional information such as a floor, room, or suite that helps responders find the caller.
For an office desk phone, that information is fixed and known. For a remote worker, it changes whenever the person moves. If the phone system has only the office address on file, a 911 call from a home in another city may be delivered with the office address attached. The call still reaches a dispatcher, but the dispatcher may send help to the wrong place.
How Teams Determines the Emergency Location
Teams uses a defined order of precedence when an emergency number is dialed. From highest to lowest:
- An address that the administrator defined for the network the client is connected to.
- An address the user confirmed or edited for that local network.
- An address suggested automatically by the device's operating system.
- An address the user entered manually without address validation.
- An address the administrator assigned statically to the user's phone number.
The first option is dynamic emergency calling. The administrator defines network sites and trusted network identifiers such as subnets and public IP addresses. When a Teams client connects from the office, Teams recognizes the network and supplies the address configured for that site. That is the most reliable case, and it is why offices should have their network topology documented in the Teams admin center.
For a home network, Teams usually cannot match a defined site. The client then falls back to the user-confirmed address, the operating system's location, a manually entered address, or the address assigned to the user. The exact result depends on what the organization has enabled and what the user has done.
What to Configure Before Employees Work Remotely
The technical work happens in the Teams admin center and, where the organization uses it, in PowerShell. The sequence below reflects how Microsoft documents the remote-worker setup.
- Validate emergency addresses. Create the addresses responders would need using the map search in the Teams admin center, so each address is validated and carries the correct geo code.
- Document office network sites. Add network sites, subnets, and trusted IP addresses for each location so on-site calls resolve automatically.
- Assign a static address to each user. Every user should have a registered address, even if dynamic lookup normally overrides it. This becomes the fallback.
- Enable external location lookup for remote users. In an emergency calling policy, turn on External location lookup mode. Without it, users outside the corporate network cannot confirm or edit their own emergency address.
- Add an emergency service disclaimer. A short banner in Teams reminds users to confirm their location. It reappears when Teams restarts, which is the point.
- Allow location services. Teams uses the operating system's location to suggest an address. Confirm that Windows or macOS location services are enabled and that Teams has permission to use them. Device management tools can enforce this.
- Configure notifications. An emergency calling policy can notify the security desk or another group by Teams chat, conference them into the call muted or unmuted, or dial a PSTN number. Decide who should know when an employee calls 911 from home.
- Set a test number. Microsoft provides 933 as an emergency test number in the United States. Use it to verify routing and notification behavior without calling a real dispatch center.
The policy applies to users and can also be assigned to network sites. When a user is at a network site with its own policy, the site policy overrides the user policy.
What Remote Workers Need to Do
Configuration alone is not enough. The user is part of the system, and a short training session prevents the most common failure.
- Confirm the emergency address in Teams, under the Calls tab, when working from a new location.
- Update the address after moving, and whenever Teams prompts for it.
- Keep the device's location service on, and do not block Teams from using it.
- Use a headset or a device with a working microphone, and test audio before relying on the laptop for calls.
- Know that signing out of Teams clears the address saved on that client, so confirm it again after signing back in.
- Keep a mobile phone nearby as a fallback for an internet or power outage.
Microsoft's work-from-home emergency address experience is supported on the Teams desktop app for Windows and Mac. Teams phones do not support the remote address workflow, and Teams mobile supports automatic location detection but not the user-entered address experience.
How the Call Reaches the Right Dispatcher
Teams does not send every emergency call to the same place. Addresses that are validated and associated with the network, or entered through address autosuggest and confirmed, generally route directly to the serving Public Safety Answering Point (PSAP). Addresses that are manually entered, unconfirmed, or missing may be screened by an emergency calling service and transferred to the PSAP after the location is verified. That screening adds time and depends on the caller being reachable.
The routing behavior also depends on the PSTN connection. With Microsoft Calling Plans, Operator Connect, and Teams Phone Mobile, the carrier handles much of the emergency routing. With Direct Routing, the organization or its partner must configure emergency call routing policies and make sure the address information reaches the emergency service provider. A Direct Routing deployment that works for normal calls can still have an incomplete 911 configuration.
Where Remote Emergency Calling Can Fail
These are the scenarios worth testing before they happen:
- The address is stale. The employee moved or is working from a different address and never updated Teams. This is the most common failure.
- The address is missing. No registered address, no location permission, and no user entry leave the system with nothing accurate to send.
- The internet or power is out. Teams needs a working internet connection and a reachable PSTN service. A softphone cannot place a 911 call during an outage, which is why a mobile phone fallback belongs in the policy.
- Teams is not running or not signed in. A closed laptop or an expired session means no call.
- The network blocks the call. A VPN or firewall that treats voice traffic differently can interfere. Voice traffic needs a supported path, and emergency calls should never be caught by a toll-bypass restriction.
- The user cannot speak the address. In an emergency, the caller may be panicked or unable to communicate. The location data has to do the work.
A Practical Readiness Checklist
- Every remote user has a validated registered address and knows how to confirm it.
- External location lookup is enabled for the users who need it.
- Location services are on, and Teams is allowed to use them.
- Office network sites are defined so on-site calls resolve automatically.
- Security desk notifications are configured and tested with 933.
- Direct Routing emergency routing has been reviewed by whoever manages the SBC.
- Employees know to update their address when they move and to keep a mobile phone as a fallback.
- The policy is reviewed when people, offices, or the phone platform change.
How Nova Technologies Helps
Nova Technologies designs, deploys, and manages Microsoft Teams Phone for Minnesota organizations, including the emergency calling configuration that is easy to leave until after go-live. We review the existing phone numbers and carrier setup, build the emergency addresses and network sites, configure emergency calling policies and notifications, test the result with the 933 test number, and give employees a short process for keeping their location current. For Direct Routing, we can manage the SBC and the emergency routing that goes with it.
To make sure your remote team is ready, explore our Microsoft Teams calling solutions, review our business phone systems, see our contact center call routing, or contact our team to schedule a consultation.
This article provides general information about emergency calling requirements and Microsoft Teams configuration. Regulations and product behavior change, and the right setup depends on how your organization uses Teams. Confirm current requirements with qualified counsel and with your carrier or Microsoft partner.
Posted in: Microsoft Teams