![Microsoft Teams: New location sharing settings for emergency calls and other features [MC993226]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-googledeepmind-17483874-1024x683.webp)
Message ID: MC993226
Microsoft Teams will soon have a new location sharing setting that will allow users to grant location access to specific features. This change will affect emergency dynamic policy and the network bandwidth policy.
This message applies to Teams for Windows desktop (version 24H2 or greater) and Teams for Mac desktop. VDI clients will not be supported at this time.
[When this will happen:]
Targeted Release: We will begin rolling out early February 2025 and expect to complete by mid-February 2025.
General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late February 2025 and expect to complete by early March 2025.
[How this will affect your organization:]
Before this rollout: Location access was governed exclusively at the operating system level. With this update, location consent will also be required from users at the individual application level. As a result, users gain more granular control over which specific application features can access their location.
After this rollout, Teams users can grant location access to certain Teams features. The setting for IT insights for admins feature are in Teams Settings > Privacy > Location. The setting for the Emergency calls feature is in the user’s device’s location settings. The user can find a link to their device’s location settings in Teams Settings > Privacy > Location:
If a user consented to location access before the rollout, the user will be prompted to confirm their selection in this new popup that will display after the next Teams version update. If a user has not previously consented, they will not see the popup and can adjust their preferences in Settings.
[What you need to do to prepare:]
NOTE: After this rollout, dynamic emergency calling may not work as intended unless users allow location detection at the operating system level and app level. This dynamic emergency calling issue includes scenarios where admins have configured a network site for their users (location must be enabled by the user). To ensure emergency calls are properly routed to the nearest public safety answering point (PSAP), please advise your users to accept the new location requests from Teams. This also applies to users who may have consented to location access before the rollout.
You can communicate this requirement by setting the emergency service disclaimer with a custom message that will display in the Calls app in Teams. Ensuring that end 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
To continue managing video and media settings with the network roaming policy, users must enable Insights for IT admins in Teams Settings > Privacy > Location > Insights for IT admins.
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)
This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. Please notify your users and admins about this change and update any relevant documentation.
Source: Microsoft
![Microsoft Teams: New location sharing settings for emergency calls and other features [MC993226]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-markusspiske-177598-150x150.webp)
![Microsoft Teams: New location sharing settings for emergency calls and other features [MC993226]](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-adrien-olichon-1257089-3709370-150x150.webp)
The upcoming update to Microsoft Teams regarding location sharing settings promises to enhance user control and improve emergency response capabilities. For both admins and users, this change will bring about a significant shift in how location data is managed and accessed.
From an admin perspective, the responsibility for communicating these changes will be paramount. Admins will need to ensure that users are aware of the new settings and the importance of granting location access for emergency calls to function correctly. This is not just a matter of compliance; it’s about user safety. Admins can take proactive steps by setting up custom messages in the Teams Calls app to remind users of the necessity of enabling location access. After all, a little reminder can go a long way in ensuring everyone is on the same page!
For users, this update offers a welcome layer of privacy and control. By allowing location access at the application level, users can now decide which features of Teams can utilize their location data. This means more granular control, allowing users to feel more secure in how their location information is shared. However, it also means users will need to be proactive in confirming their preferences and understanding the implications for emergency calling features.
The impact of these changes is likely to be substantial. With the new settings, we can expect a more efficient emergency calling process, as accurate location data will ensure that calls are routed to the nearest public safety answering point. This is a critical enhancement that could potentially save lives.
So, as we gear up for the rollout in early 2025, it’s a great opportunity for admins to engage with their users about these changes. How do you think this will affect your Teams experience? Will you embrace the new granular settings, or do you foresee any challenges? Let’s hear your thoughts! Don’t forget to check out more insights on these updates at mwpro.co.uk. Your comments could spark a lively discussion!