In enterprise voice deployments with Microsoft Teams Phone, providing accurate physical location data during emergency calls is both a safety imperative and a legal requirement under regulations such as Ray Baum’s Act and Kari’s Law. While a validated civic address identifies the physical street building where an emergency call originates, large office buildings, university campuses, and multi-tenant facilities require far greater granularity. First responders must know the exact floor, suite, conference room, or wing where a distressed caller is located.
The Location Information Server (LIS) in Microsoft Teams enables administrators to define specific sub-locations linked to an approved civic address. Using the CsOnlineLisLocation cmdlets within the Microsoft Teams PowerShell module, administrators can programmatically create, manage, and validate emergency sub-locations and bind them to network identifiers such as IP subnets, BSSIDs, and switch ports.
Understanding Emergency Civic Addresses vs Sub-Locations
The Teams Location Information Server architecture separates physical addresses into a parent-child hierarchy:
- Civic Address (
CsOnlineLisCivicAddress): Represents the physical street address (street number, street name, city, state/province, postal code, and country). This address must be geocoded and validated against the Master Street Address Guide (MSAG) or provider databases. - Sub-Location (
CsOnlineLisLocation): Represents a distinct area inside the validated civic address. Examples include “Floor 4, West Wing”, “Building B – Lab 102”, or “Suite 500”. Each sub-location possesses its own uniqueLocationId(GUID) and references the parentCivicAddressId.
Once created, sub-locations are mapped to network entities (such as IP subnets via CsOnlineLisSubnet, Wi-Fi access points via CsOnlineLisWirelessAccessPoint, or Ethernet switch ports via CsOnlineLisPort). When a Teams client initiates an emergency call, Teams automatically detects the user’s network connection and passes the corresponding sub-location details to the emergency dispatch centre.
Connecting to Microsoft Teams PowerShell
Before managing emergency locations, open an elevated PowerShell terminal and establish a remote management session with your Microsoft 365 tenant:
# Import the Teams module and connect
Import-Module MicrosoftTeams
Connect-MicrosoftTeams
Retrieving Parent Civic Address Identifiers
Because every emergency sub-location must be bound to an existing, validated civic address, retrieve the CivicAddressId of your target facility:
# List all validated civic addresses in the tenant
Get-CsOnlineLisCivicAddress | Select-Object CivicAddressId, CompanyName, Description, City, StateOrProvince, CountryOrRegion
Identify the specific CivicAddressId GUID (for example, c8f49e01-2134-4b5c-a112-9c887410ebdc) that will serve as the parent for your new sub-locations.
Creating New Emergency Sub-Locations with New-CsOnlineLisLocation
To create a new emergency sub-location under the parent civic address, execute New-CsOnlineLisLocation specifying the sub-location description and parent address ID:
# Create a new sub-location for the 3rd floor marketing department
New-CsOnlineLisLocation `
-CivicAddressId "c8f49e01-2134-4b5c-a112-9c887410ebdc" `
-Location "Floor 3 - Marketing Wing" `
-CompanyName "Contoso Ltd"
You can also create multiple granular sub-locations for conference rooms or executive suites:
# Create sub-locations for specific rooms and suites
New-CsOnlineLisLocation `
-CivicAddressId "c8f49e01-2134-4b5c-a112-9c887410ebdc" `
-Location "Suite 450 - Executive Boardroom" `
-CompanyName "Contoso Ltd"
New-CsOnlineLisLocation `
-CivicAddressId "c8f49e01-2134-4b5c-a112-9c887410ebdc" `
-Location "Basement - Data Centre Operations" `
-CompanyName "Contoso Ltd"
The command outputs the created location object along with its newly generated LocationId GUID.
Querying and Inspecting Configured Sub-Locations
To inspect all configured sub-locations across the entire organization, use Get-CsOnlineLisLocation:
# List all emergency sub-locations
Get-CsOnlineLisLocation | Select-Object LocationId, CivicAddressId, Location, CompanyName
To query only the sub-locations associated with a specific civic address:
# Filter sub-locations for a specific building
Get-CsOnlineLisLocation | Where-Object { $_.CivicAddressId -eq "c8f49e01-2134-4b5c-a112-9c887410ebdc" } | Format-Table LocationId, Location, CompanyName
Updating Sub-Location Descriptions with Set-CsOnlineLisLocation
If an office department relocates or a location name requires clarification to aid first responders, update the location description using Set-CsOnlineLisLocation:
# Update the naming of an existing sub-location
Set-CsOnlineLisLocation `
-LocationId "9d8123ef-44a1-4209-b13c-789a421ef012" `
-Location "Floor 3 - Engineering & Design Lab" `
-CompanyName "Contoso Ltd"
Mapping Sub-Locations to Network Topologies
After defining sub-locations, bind them to network infrastructure so that Teams endpoints automatically inherit their physical dispatch location when connecting to enterprise switches or Wi-Fi networks:
# Map an IP subnet to the emergency sub-location
Set-CsOnlineLisSubnet -Subnet "10.140.20.0" -LocationId "9d8123ef-44a1-4209-b13c-789a421ef012"
# Map a wireless access point BSSID to the sub-location
Set-CsOnlineLisWirelessAccessPoint -BSSID "00-14-22-01-23-45" -LocationId "9d8123ef-44a1-4209-b13c-789a421ef012"
# Map a network switch chassis to the sub-location
Set-CsOnlineLisSwitch -ChassisID "00-1F-9E-AB-CD-EF" -LocationId "9d8123ef-44a1-4209-b13c-789a421ef012"
Deleting Obsolete Emergency Sub-Locations
Before deleting a sub-location, ensure that no active network subnets, Wi-Fi access points, or user accounts are assigned to its LocationId. Once unmapped, remove the record using Remove-CsOnlineLisLocation:
# Remove an unused emergency sub-location
Remove-CsOnlineLisLocation -LocationId "9d8123ef-44a1-4209-b13c-789a421ef012"
To execute deletions within automated maintenance scripts without interactive confirmation prompts, append -Confirm:$false.