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

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

Message ID: MC1041451

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:

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

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:

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

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:

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.

Source: Microsoft

Show 1 Comment

1 Comment

  1. Mike Rosoft

    The recent updates to Microsoft Teams for iOS and Android regarding location sharing settings are poised to create quite a stir among both admins and users. These changes aim to enhance privacy, improve data security, and ensure compliance with evolving regulations – all worthy goals that should be applauded!

    For admins, the new location consent experience means a bit more work in terms of educating users about the importance of these settings. While the rollout is automatic, it’s crucial for admins to communicate the implications of these changes, especially regarding emergency calling and tools like the Call Quality Dashboard. After all, no one wants to be the admin who overlooked a critical update that affects user safety!

    On the user side, this update offers more control over location data, which is a win for privacy advocates. Users will now be prompted to choose whether they want to share their location for emergency calls only or for broader IT insights. This added flexibility empowers users to make decisions that best suit their comfort levels. However, it also means that users need to be informed about what these choices entail; after all, it’s not every day you get to decide how much of your location to share!

    As for the impact of these changes, it’s likely to be significant. Enhanced privacy controls could lead to increased user trust in the platform. However, if users opt out of location sharing, it may limit the effectiveness of certain features, particularly those tied to emergency services. Thus, striking the right balance between privacy and functionality will be key.

    In summary, while these updates may require some adjustments on both ends, the overall trajectory is positive. Let’s embrace these changes with open arms and a sense of humor—after all, who wouldn’t want a little more control over their digital footprints?

    I encourage everyone to share their thoughts and experiences regarding these updates in the comments below! What are your expectations, and how do you think this will affect your daily use of Teams? Let’s get the conversation rolling!

    For more insights, feel free to check out other posts on mwpro.co.uk.

Leave a Reply

Your email address will not be published. Required fields are marked *