Teams Admin: Dynamic Locations

Teams Admin: Dynamic Locations

Dynamic Locations:

Dynamic Locations can be used to dynamically update a user's emergency address based on various factors such as the IP address of their machine, the wireless access point, switch, or switch port they are connected to.

How does it work?

On startup and periodically, the user's Teams Client will send the current network connection information to the Teams Environment. If a match for the current network connection is found, the user's emergency information will update accordingly.

Start by configuring an emergency location. See: Teams Admin: Emergency Locations (onecloud.us)

Once you have an emergency location set up you can proceed with the dynamic configurations.

Location Precedence

It is important to note the various ways a user's location can be defined:
  1. A dynamically acquired address defined by the tenant administer in the Location Information Service.
  2. An address the end user confirmed, edited, or manually entered which is associated to the local network the Teams client is connected to.
  3. An address automatically suggested by the operating system.
  4. An address the administrator statically assigns to the user.
The above are listed in order of precedence. For example: a location assigned by the user via the Teams client will be used instead of the emergency address statically assigned by the Teams Administrator.

Location Information Service (LIS)

This service is responsible for matching the client's network information to a physical location. This service matches against the network topology configurations in the Teams Admin Center.

Step 1 - Network Site

a: Navigate to "Locations > Network Topology"



b: Click "Add" to begin building a new network site



Enter the location name and description and a network region.
Network region: A network region contains a collection of network sites. Each network site must be associated with a network region. You can add new network regions that can be used globally for all network sites.



c: Click on "Add Subnets":




d: Enter the subnet information for your local network

example below:



IP address:
This is where you will enter the Network address.

Network range:
This is the subnet mask bit count (0-32)

Click "Apply" when done

Click "Save" to build the network site


Step 2 - Trusted IPs

Add the site's public IP address to the "Trusted IPs" section:



+ Add



Click "Apply"

Step 3 - Networks & Locations

Here we just need to confirm that the subnet is mapped to the desired emergency location.

a: Navigate to "Locations > Networks & locations"




You should be able to see your subnet with it mapped to your emergency location as show below:




If the subnet is not shown in the list, it will need to be added manually.

b: Click "+ Add" to add a new subnet




c: Enter subnet information and select desired emergency location





Click "Apply" at the bottom when finished.

Note: The network/subnet information may take up to 4 hours to provision.


Now when your user's startup their Teams client, it matches to one of the subnets entered here and updates their location accordingly. The Teams user can see their identified emergency address from within the client under the "Calls" tab:




For more information and further configuration (switch, switch port, WAP) please see Microsoft official documentation on this subject.

    • Related Articles

    • Teams Admin: Emergency Locations

      Teams Administration - Emergency Calling Configuring emergency locations in the Microsoft Teams admin portal is an essential step for ensuring that your organization is prepared for emergencies. Emergency locations are physical addresses that can be ...

    • Teams Admin: Locating Microsoft Tenant ID

      Teams Admin: Locating Microsoft Tenant ID How to find the Microsoft Tenant ID via Microsoft Partner Center If you have established your Microsoft Partner Center, the customer’s Microsoft Tenant ID can be easily accessed by signing into your Partner ...

    • Teams Admin: Build an Auto Attendant

      If not already - Navigate to the Teams Admin Center: Or navigate to: https://admin.teams.microsoft.com Like most everything else in Teams, a resource account is needed before we can build the auto-attendant itself. Step 1: Build a Resource Account ...

    • How to Update the e911 Emergency Address

      Section 506 of Ray Baum's Act Section 506 requires telephone systems to provide critical data about a 911 call's dispatchable location. Defined as "the street address of the calling party, and additional information such as room number, or similar ...

    • Teams Admin: Configure Direct Routing with OneCloud

      Login Start by checking your email for an invitation from "noreply@teams.onecloud.us": Clicking "Accept Invitation" will automatically take you to the admin portal. OR Navigate and login to https://admin.teams.onecloud.us Add Account Click the blue ...