E911 location detected by Teams not is not showing accurate locations for Teams users.

Question

users who are using Microsoft Teams 1.0 or 2.1 when clicking on call button, the location detected in teams client is not accurate.

There is always a difference of 500 to 700 meters from the actual location detected by Teams client.

I have created a support request with Microsoft Teams (2309080030002511) and was informed by engineering team + support that the issue is related to Azure maps.

Engineering + support mentioned by email and call that upon checking our files and logs, no issue was detected from Teams perspective and also from TAP engineering (we are TAP customers).

Raising Azure maps issue here and requesting further assistance.

Answer 1

This isn't related to Azure Maps as it doesn't provide the location. The location information comes from your device. Devices estimate your location using one of many methods, each having different levels of accuracy. I suspect the device you are using is unable to use a high accuracy method to get your location. You also need to agree to accessing your high-resolution location (some companies who manage settings on devices disable this). This is generally set on a per app level. In Windows, search for "Location privacy settings" and ensure location services is enabled, and that Teams has access. You can also set a default location for Windows to use in these settings to fallback on.

Here is a list of the main methods devices determine a user high-resolution location and its accuracy:

1. WIFI 802.11mc FTM standard (WIFI 5 or newer, accuracy 1m-3m): One of the highest accuracy options. Requires both your device and the router to be running newer WIFI firmware. In enterprise routers this usually needs to be turned on by an administrator.
2. Traditional WIFI triangulation (accuracy 5m - 15m): How most older devices determine a device's position. I believe it is possible for this capability to be disabled in enterprise grade WIFI routers.
3. GPS location (accuracy 5 - 10m): fairly high accuracy unless you are in a building or very close to tall buildings. Requires your device to have a GPS chips (most phone, but limited computers have this).
4. Bluetooth beacon triangulation (accuracy 1-3m): Mainly used for indoor positioning. Requires Bluetooth beacons devices to be installed in building to support triangulation, so less common.
5. 5G triangulation (accuracy 3m - 25m): Similar to cell tower triangulation but uses better hardware for positioning. Requires your device to support 5G, and for there to be a 5G signal available.

If none of the above are available, high-resolution positioning disabled in computer, or required hardware or signals not available, one of the following methods are used as a fallback.

1. Cell tower triangulation (accuracy 100m - 1000m): If you have a device that connects to the cell network, and 5G isn't available/supported, 3G/4G/LTE will estimate your position based on the pings from your device to the towers. This requires your device to be in an area where cell phone signals are available.
2. Reverse IP address lookup (accuracy 5km - 50km): One of the least accurate methods of positioning, but one that is often used as a fallback when high-resolution positioning is not available, or when lower resolution positioning is preferred (e.g. user privacy/security).

All of the above said, it's also possible that the software/app or its settings are set to purposely use a lower resolution location for privacy and security reasons. However, it is most likely how your device gets your location, and if high-resolution positioning has been allowed to the software.

Answer 2

Hi @Sheetal Mahanta (WPP)

Based on our research, there are a few possible reasons why E911 location detected in Teams client is not accurate., and some steps you can take to troubleshoot and try to resolve the problem.

One reason why the location detected by Teams might not be accurate is that the location services of your operating system are not enabled or configured properly. Teams uses the location services provided by the operating system to suggest an address, if granted permission by the administrator or user. You can check and enable the location services in your OS settings, depending on whether you are using a Mac or Windows device. For more details, you may refer to the article.

Another reason why the location detected by Teams might not be accurate is that the network settings and the Location Information Service (LIS) are not configured properly by the network administrator. These settings are used to create a network/emergency location map and to return a location to the Teams client based on its network connectivity information. If there is no match between the network elements and the emergency addresses, the Teams client may not be able to obtain an accurate location. To configure the network settings and the LIS, the tenant administrator could refer to the article.

A third reason why the location detected by Teams might not be accurate is that the user has not confirmed, edited, or manually entered their emergency address in Teams. When a user moves to a new physical location, Teams will suggest an address based on the location services of the operating system. The user needs to confirm or modify this address in Teams, so that it can be used for emergency calling. The user can check and update their emergency address below the dial pad in Calls or at the bottom of the calls section in their Teams Settings.

Hope the above information is helpful for you!

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

---