MC1041451 - Microsoft Teams for iOS/Android: New location sharing settings for emergency calls and more

This message applies to Microsoft Teams for iOS/Android.

Microsoft is updating its policies regarding the sharing of user location data to enhance privacy, improve data security, and ensure compliance with evolving regulatory standards. To enhance transparency and user control, Teams will introduce a new location consent experience that gives users the choice of when and how Teams can use their location data specifically, the SSID (service set identifier) and the BSSID (basic service set identifier).

When this will happen:

General Availability (Worldwide, GCC): We will begin rolling out early April 2025 and expect to complete by mid-April 2025.

General Availability (GCC High, DoD): We will begin rolling out late April 2025 and expect to complete by early May 2025.

How this will affect your organization:

All new and existing Teams for Work users in your organization will be prompted to specify if they want to keep location detection on for emergency calls only or if they consent to allowing location access used for IT Admin Insights, for troubleshooting (with a tool such as the Call Quality Dashboard) or for Network and Location matching through BSSID for emergency calling location.

NOTE: The new Teams location consent flow does not apply to fully managed devices where users are restricted from user-granted location access. You can expect current policies for managed devices to continue working as expected, and users will not receive the new location consent prompts.

The new Teams location consent changes will impact these Teams features:

• Emergency calling
• Location-based routing
• Network and Location matching through BSSID
• Call Quality Dashboard

This change will be available by default.

All new Teams for Work users on iOS and Android will first be prompted to allow location permission at the operating system level:

Existing Teams for Work users who previously accepted or denied location permission at the operating system level will not see this prompt a second time.

If a user allows location access, dynamic emergency calling policies will work as configured, and users enabled for Location Based Routing will be able to make and receive PSTN calls.

If a user disallows location access, several Teams Call Quality Dashboard metrics will be impacted, and Network and Location matching through BSSID from dynamic emergency calling policies will not work. Users can still manually add their physical address for emergency calls in the Teams Calls app if an admin has enabled ExternalLocationLookupMode for their users.

Immediately after users consent to allow location access at the operating system level (and for users who previously consented to location access), both new and existing Teams for Work users will be prompted to allow location access at the Teams app level:

At the Teams level, users must choose between Allow all, which grants Teams full location access (that can be used for emergency calls, IT Admin Insights, or troubleshooting), or Allow emergency only, which restricts location usage to emergency calling. NOTE: Only users who are configured for a dynamic emergency calling policy through ExternalLocationLookUpMode will see this version of the dialog. Users without ExternalLocationLookUpMode enabled will see a slightly different version of this consent prompt that excludes emergency calling. Users can modify their location detection preferences at the operating system level or app level at any time in Teams Settings > Privacy > Location. On fully managed devices, these settings will be on by default and can only be disabled at the operating system level.

What you need to do to prepare:

We recommend that you educate your users on these selections and what works best for your tenant.

1. If you regularly use the Call Quality Dashboard or leverage Network and Location matching through BSSID, you may want to recommend that users allow location access for those options, or user location data will no longer flow to these services.
2. For emergency calling, you can communicate these changes by setting the emergency service disclaimer with a custom message that will display in the Calls app in Teams. Ensuring that users have location turned on is crucial for proper functioning of emergency calls and their safety. Learn more about sending a custom message: Manage emergency calling policies in Microsoft Teams - Microsoft Teams | Microsoft Learn

Learn more about the changes to location services and privacy policies:

• Windows location service and privacy - Microsoft Support
• Enable location sharing - Microsoft Support (will be updated before rollout)
• Changes to API behavior for Wi-Fi access and location - Win32 apps | Microsoft Learn
• User location consent experience in Microsoft Teams - Microsoft Teams | Microsoft Learn

For more detailed information and how this will affect each user in your organization, please refer to the public documentation that will be updated here shortly. Before rollout, we will update this post with links to new documentation.

This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation.