How to Configure Teams Phone Emergency Wi-Fi Access Point Mapping in PowerShell Using CsOnlineLisWirelessAccessPoint

In modern enterprise office environments dominated by untethered laptops and dynamic hot-desking, employees frequently move across floors, buildings, and conference spaces while remaining connected to corporate wireless networks. Under statutory emergency regulations such as the RAY BAUM’S Act in the United States and similar public safety frameworks internationally, enterprise voice networks must provide dispatchable physical locations—including specific floor, wing, or room information—whenever an emergency 911 or 112 call is placed.

While IP subnet mapping provides coarse building-level geolocation, wireless subnets frequently span entire office towers or multiple campuses, making subnet matching insufficiently granular for emergency services. To solve this, Microsoft Teams Phone enables Wi-Fi Access Point (WAP) based location mapping within its Location Information Service (LIS). By mapping the Basic Service Set Identifier (BSSID) MAC addresses of corporate Wi-Fi radios directly to granular sub-location IDs using the CsOnlineLisWirelessAccessPoint cmdlets in PowerShell, telephony engineers achieve room-level dispatch accuracy for all wireless Teams endpoints.

Architecture of Dynamic Emergency Calling via Wireless Access Points

When an emergency call is initiated from the Microsoft Teams desktop client on Windows or macOS, the client queries the local operating system Wi-Fi stack to extract the BSSID of the currently connected radio access point. The client then matches this BSSID against the LIS topology database downloaded from Microsoft 365.

The hierarchy for emergency location resolution prioritizes network elements in descending order of physical granularity:

  1. Network Switch Port / Chassis (LLDP/CDP): Highest physical precision for wired ethernet drops.
  2. Wireless Access Point (BSSID): Highest physical precision for mobile and Wi-Fi endpoints.
  3. IP Subnet: Fallback when specific AP or switch port telemetry is unavailable.
  4. Public IP Address / Network Site: Baseline site-level fallback.

By registering individual Wi-Fi access point BSSIDs in the LIS database, each access point (which typically covers an approximate 15 to 20-metre radius) can be assigned to an exact room, zone, or floor.

Connecting to the Microsoft Teams PowerShell Module

Configuring LIS wireless access points requires administrative privileges in your Microsoft 365 tenant (Teams Administrator or Global Administrator) and the current Microsoft Teams PowerShell module.

Open an elevated PowerShell session and execute:

# Install or update the Microsoft Teams module
Install-Module -Name MicrosoftTeams -Force -AllowClobber

# Authenticate to the tenant
Connect-MicrosoftTeams

Gathering Wireless BSSIDs and LIS Location Identifiers

Before configuring WAP mappings, obtain two critical pieces of information: the wireless radio BSSIDs from your network controller (e.g. Cisco Catalyst, Aruba Central, or Meraki Dashboard) and the target LocationId GUIDs from Teams.

BSSID formatting in Microsoft Teams LIS requires standard colon-separated or hyphen-separated hexadecimal notation (e.g. 00-11-22-33-44-55 or 00:11:22:33:44:55). Note that enterprise Wi-Fi APs generate unique BSSIDs for each broadcast SSID and radio band (2.4 GHz, 5 GHz, 6 GHz). Ensure you inventory all active radio BSSIDs deployed on the physical access point.

To inspect configured sub-locations and retrieve their LocationId values, run:

Get-CsOnlineLisLocation | Format-Table LocationId, Location, CivicAddressId, CompanyName

To isolate the specific location GUID for a floor or conference wing:

$Location = Get-CsOnlineLisLocation | Where-Object { $_.Location -like "*Floor 2 - West Wing*" }
$TargetLocationId = $Location.LocationId
$TargetLocationId

Creating LIS Wireless Access Point Associations with Set-CsOnlineLisWirelessAccessPoint

In Microsoft Teams PowerShell, the Set-CsOnlineLisWirelessAccessPoint cmdlet is utilized to create new WAP records or update existing associations.

To link a single access point BSSID to the designated physical location, run:

Set-CsOnlineLisWirelessAccessPoint `
    -BSSID "00:27:90:3A:4B:C0" `
    -LocationId $TargetLocationId `
    -Description "AP-Floor2-West-ConferenceRoomA"

If an access point broadcasts multiple BSSIDs across 2.4 GHz, 5 GHz, and Wi-Fi 6E (6 GHz) radios, map each individual radio BSSID to the same LocationId:

$RadioBssids = @(
    "00:27:90:3A:4B:C0", # 2.4 GHz Radio
    "00:27:90:3A:4B:C1", # 5 GHz Radio
    "00:27:90:3A:4B:C2"  # 6 GHz Radio
)

foreach ($Bssid in $RadioBssids) {
    Set-CsOnlineLisWirelessAccessPoint -BSSID $Bssid -LocationId $TargetLocationId -Description "AP-Floor2-West"
}

Bulk Importing Wireless Access Points from CSV

In large corporate headquarters with hundreds of deployed access points, importing WAP data in bulk via a standardized CSV file eliminates manual entry errors.

Create a CSV file (e.g. C:\WapData\AccessPoints.csv) with the following headers:

BSSID,LocationId,Description
00:27:90:3A:4B:C0,a1b2c3d4-e5f6-7890-abcd-ef1234567890,Building 1 - Floor 2 - West
00:27:90:3A:4B:D0,a1b2c3d4-e5f6-7890-abcd-ef1234567890,Building 1 - Floor 2 - East
00:27:90:5E:6F:A0,b2c3d4e5-f6a7-8901-bcde-fa2345678901,Building 1 - Floor 3 - North

Execute the bulk import script in PowerShell:

$WapList = Import-Csv -Path "C:\WapData\AccessPoints.csv"

foreach ($Entry in $WapList) {
    Write-Host "Provisioning WAP BSSID: $($Entry.BSSID)"
    Set-CsOnlineLisWirelessAccessPoint -BSSID $Entry.BSSID -LocationId $Entry.LocationId -Description $Entry.Description
}

Inspecting and Auditing Registered Wireless Access Points

To view all wireless access points currently registered in the tenant LIS database, run:

Get-CsOnlineLisWirelessAccessPoint | Format-Table BSSID, LocationId, Description

To inspect a single WAP record in detail:

Get-CsOnlineLisWirelessAccessPoint -BSSID "00:27:90:3A:4B:C0" | Format-List *

To audit WAPs against their resolved civic addresses and human-readable location labels, combine query outputs:

$Locations = Get-CsOnlineLisLocation
Get-CsOnlineLisWirelessAccessPoint | Select-Object BSSID, Description, @{
    Name       = "ResolvedLocation"
    Expression = { ($Locations | Where-Object { $_.LocationId -eq $_.LocationId }).Location }
} | Format-Table -AutoSize

Updating and Removing Wireless Access Point Mappings

When access points are relocated to different floors or replaced during hardware refresh cycles, maintain database accuracy promptly.

To update the assigned location of an existing BSSID:

Set-CsOnlineLisWirelessAccessPoint -BSSID "00:27:90:3A:4B:C0" -LocationId $NewLocationId -Description "Relocated to 3rd Floor"

To remove a decommissioned access point permanently from the LIS database:

Remove-CsOnlineLisWirelessAccessPoint -BSSID "00:27:90:3A:4B:C0" -Confirm:$false

Testing Client Location Resolution on Wi-Fi Workstations

Allow up to 4 hours for LIS WAP changes to replicate to Microsoft 365 directory caches. To verify location detection on a client laptop:

  1. Connect the laptop to the corporate Wi-Fi SSID within range of the target access point.
  2. Verify your connected BSSID in PowerShell (on Windows, run netsh wlan show interfaces and observe the BSSID field).
  3. Launch or restart the Microsoft Teams desktop client.
  4. Navigate to the Calls tab. Below the dial pad, the dynamic location display should show the exact room, floor, or civic address associated with the connected BSSID.
  5. If the address remains blank or shows an older subnet fallback, click the location text to trigger a client-side LIS re-evaluation.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.