Fix Teams Emergency Location Is Not Detected in Teams Admin Center

When you open the Teams admin center to assign an emergency location, the location list may appear empty or show a “Not detected” error. This blocks you from assigning a location to a user or to a network identifier. The problem usually comes from a missing or misconfigured network zone, a location that was created but not properly linked, or a caching delay in the admin portal. This article explains the root causes and gives you step-by-step fixes to make your emergency locations appear reliably.

You will also learn how to verify your network settings, re-sync the location data, and avoid common mistakes that cause the detection failure.

Why Teams Cannot Detect Your Emergency Location

The emergency location feature in Teams relies on a chain of configuration objects. You must have a network zone, a network site, and an emergency location that are all linked together. If any link is broken, the admin center shows “Not detected” or an empty list.

The most common root cause is that the emergency location was created but never assigned to a network site. In the Teams admin center, you create a location under Locations > Emergency locations. Then you must go to Network & locations > Network topology and associate that location with a specific network site. If you skip this step, the location exists but the system cannot map it to any user or network identifier.

Another cause is a caching delay. The admin center sometimes takes a few minutes to reflect newly created locations. This is especially true when you create the location through PowerShell and then check the portal immediately.

Network Zone and Site Requirement

To use emergency locations, your tenant must have at least one network zone and one network site. These are defined in Network & locations > Network topology. If you have no network sites, the emergency location cannot be associated, and the detection fails. Create a network site first, then link the location to it.

Steps to Diagnose and Fix Emergency Location Detection

Follow these steps in order. Each step verifies one part of the configuration chain.

1. Check the emergency location list
   Open the Teams admin center at admin.teams.microsoft.com. Go to Locations > Emergency locations. Look for your location in the list. If it is missing, you must create it again. If it is present but shows “Not detected,” continue to step 2.
2. Verify the network site association
   Go to Network & locations > Network topology. Select your network site and open its properties. Scroll to the Emergency location field. If it is empty, click Edit and choose the correct location from the dropdown. Save the change.
3. Confirm the network zone exists
   In the same Network topology page, check that a network zone is present. If you have no zone, create one first. Go to Network & locations > Network zones and click Add. Give it a name and description, then save. After that, assign this zone to your network site.
4. Refresh the admin center cache
   After making changes, wait at least 10 minutes. Then press Ctrl + F5 in your browser to force a full reload of the admin center. This clears the cached view and pulls the latest data.
5. Use PowerShell to verify the location
   Open Windows PowerShell as an administrator and connect to Teams with the command Connect-MicrosoftTeams. Then run Get-CsOnlineLisLocation to list all emergency locations. If your location appears here but not in the portal, the portal is showing stale data. If it does not appear, you need to create it again.
6. Re-create the location if needed
   If the location is missing, create it again in the admin center. Go to Locations > Emergency locations and click Add. Fill in the required fields: a descriptive location name, the civic address, and the country or region. Save the location. Then go back to step 2 and assign it to the network site.

If Teams Still Has Issues After the Main Fix

Emergency location list is empty after creating a location

If you just created a location and the list is still empty, wait 15 minutes and refresh. If it still does not appear, check that you filled in all required fields. The location name must be unique. If you used a name that already exists, the system may reject it silently. Try a different name.

Location appears but is not assignable to a user

When you go to Users > Manage users and select a user, the Emergency location field may be grayed out. This happens when the user has no assigned phone number. Emergency locations are only assignable to users who have a Microsoft calling plan number or an operator connect number. Assign a phone number first, then set the emergency location.

Network site shows the location but the admin center still says “Not detected”

This usually indicates a replication delay. The backend may take up to 24 hours to fully propagate the location to all services. If you need an immediate fix, use PowerShell to force a refresh. Run Set-CsTenantNetworkSite with the same parameters you already set. This re-triggers the association and often resolves the detection error.

Teams Admin Center vs PowerShell for Emergency Location Management

Item	Teams Admin Center	PowerShell
Interface	Graphical web portal	Command-line tool
Best for	Single location edits and quick checks	Bulk changes and scripting
Detection speed	May show cached or delayed data	Shows real-time backend data
Required permissions	Teams admin or global admin	Teams administrator role
Error handling	Shows friendly error messages	Returns detailed error codes

The admin center is fine for occasional changes. For troubleshooting detection issues, PowerShell gives you a direct view of the backend. Use Get-CsOnlineLisLocation to confirm that the location exists, and Get-CsTenantNetworkSite to verify the site association.

You can now diagnose and fix the emergency location detection problem. Start by checking the network site association, then refresh the cache, and use PowerShell to verify the backend data. If you manage multiple sites, consider using PowerShell scripts to assign locations in bulk. This reduces the chance of missing links. Remember to always assign a phone number to a user before setting an emergency location.