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.
Once you have an emergency location set up you can proceed with the dynamic configurations.
It is important to note the various ways a user's location can be defined:
- A dynamically acquired address defined by the tenant administer in the Location Information Service.
- An address the end user confirmed, edited, or manually entered which is associated to the local network the Teams client is connected to.
- An address automatically suggested by the operating system.
- 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
This is where you will enter the Network address.
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:
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: