Microsoft Roadmap, messagecenter and blogs updates from 08-03-2025

Coming soon for Microsoft Viva Engage: Enhanced and updated user settings.

This message is associated with Microsoft 365 Roadmap ID 472019.

This message applies to Viva Engage for Windows desktop, Viva Engage for Mac desktop, Viva Engage on the web, Viva Engage for iOS/Android, and Viva Engage in all Microsoft Teams platforms.

This message does not apply to external networks and their members.

[When this will happen:]

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

[How this will affect your organization:]

After this rollout, we will carry over the user settings from Microsoft Yammer to Viva Engage, retaining all major functionalities in a new modern design. Key settings include language customization, header theme customization, dark mode, reaction skin tone options, and customizable notification settings for each community. This new experience will provide a more user-friendly and intuitive interface, consistent with other Microsoft 365 applications.

Users can access the new settings in the same way they accessed them before the rollout: with the gear icon in Viva Engage or with the three-dot menu in Engage in Teams.

New User Settings > General:

New user Settings > Notifications:

After this rollout, users’ previous settings will remain intact and continue to be honored. These settings from the old experience will no longer be available in the modernized version:

• Changing password: Like every other Microsoft 365 application, users can manage passwords in Microsoft 365 account settings.
• Contact preferences: Like every other Microsoft 365 application, users can manage contract preferences in Microsoft 365 account settings.
• Changing language and time zone for overall Microsoft 365: Like every other Microsoft 365 application, users can manage language and time zone in M365 account settings.
• “I install a new application” and “There are new suggestions for people to follow (weekly)” notification settings will be retired.

[What you need to do to prepare:]

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.

Before rollout, we will update the below existing public documentations with revised content.

• Use diverse skin tone preferences for Viva Engage reactions – Microsoft Support
• Change my Viva Engage profile and settings (Web and Desktop) – Microsoft Support
• Accessibility in Viva Engage – Microsoft Support
• Manage Viva Engage notifications – Microsoft Support
• Manage email with Viva Engage digests – Microsoft Support
• Manage Viva Engage desktop notifications – Microsoft Support

We are excited to announce the addition of a new graph called “average time spent per user” (dwell time) to Amplify reporting. The dwell time graph will indicate the average time users spent reading a publication, providing important insights into user engagement with the Amplify campaign. Dwell time will be available at the campaign level as well as for every publication in the campaign. This metric will be supported from Microsoft SharePoint and Microsoft Outlook channels.

This message is associated with Microsoft 365 Roadmap ID 421193.

[When this will happen:]

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

[How this will affect your organization:]

This new metric will be added as a card to the Amplify reporting tab.

[What you need to do to prepare:]

This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate.

From the Microsoft Outlook for iOS and Android apps, you can request that Outlook to attempt to recall a message sent to a colleague within your organization.

This message is associated with Microsoft 365 Roadmap ID 471444.

[When this will happen:]

General Availability (Worldwide, GCC, GCC High): We will begin rolling out in early March 2025 and expect to complete by late March 2025.

[How this will affect your organization:]

Users will have the option to request a recall attempt for a sent email. This feature provides an additional layer of control for users who need to retract emails sent in error.\

Learn more: Recall emails in Outlook for Android and iOS.

[What you need to do to prepare:]

This change will happen automatically by the specified date. No admin action is required. Please notify your users about this change and update relevant documentation.

Coming soon to Microsoft SharePoint: In the Automate menu, users will be able to create customized quick steps for common tasks such as composing an email or starting a Microsoft Teams chat to specified People columns, sending an approval request, executing a flow, and setting a column value on one or more items. Users will find a simple sentence builder experience, similar to SharePoint rules.

[When this will happen:]

Targeted Release: We will begin rolling out early April 2025 and expect to complete by late April 2025.

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

General Availability (DoD): We will begin rolling out mid-May 2025 and expect to complete by late June 2025.

[How this will affect your organization:]

After this rollout, SharePoint list and library users will be able to add and configure quick steps for their common scenarios. Users can go to the Automate menu from any list or library to configure quick steps. Learn more: Create a quick step for your list or library – Microsoft Support

This feature will be available by default.

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your SharePoint admins and site owner about this change and update any relevant documentation.

Coming soon: New naming logic for Microsoft OneDrive folder shortcuts. We will add the site name or the user’s OneDrive to all new folder shortcuts. Before this rollout, OneDrive shortcuts have the same name as the folder. After this rollout, the shortcut will also include the name of site where there the original folder exists. If a colleague shares a folder with user, and the users creates a shortcut for that folder, the shortcut will include the name of the person who owns the folder. This change will help you easily identify the source of the folder shortcut and differentiate it from other content in your OneDrive > My Files.

[When this will happen:]

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

[How this will affect your organization:]

After this rollout, any new folder shortcuts you add to your OneDrive > My Files will follow the new naming convention. For example:

• If you go to a SharePoint site named Marketing Team and create a shortcut to a folder named Project File, the shortcut will appear as Marketing Team – Project Files in your OneDrive > My Files.
• If you add a shortcut to a folder named Blog post from Mona Kane’s OneDrive, the shortcut will appear as Mona Kane’s files – Blog post in your OneDrive > My Files.

Key points

• The new naming logic will apply only to new shortcuts added after this rollout.
• Existing shortcuts will retain their current names.
• This change will be reflected in OneDrive for the web, OneDrive for iOS/Android, Microsoft File Explorer, Mac Finder, and Microsoft Teams.
• This change will be available by default.

Examples of the new naming logic for folder shortcuts in OneDrive:

[What you need to do to prepare:]

This rollout will happen automatically by the specified dates with no admin action required before the rollout.

Learn more: Add shortcuts to shared folders in OneDrive for work or school – Microsoft Support (will be updated before rollout)

Coming soon for Microsoft Teams: In channels, we will rename the Files tab as the Shared tab to enable users to view content shared in posts and content in the document library in one place. Note: The Shared tab in chats will not be affected by this change.

This message applies to Teams for Windows desktop and Teams for Mac desktop.

This message is associated with Microsoft 365 Roadmap ID 470597.

[When this will happen:]

Targeted Release: We will begin rolling out mid-April 2025 and expect to complete by late April 2025.

General Availability (Worldwide): We will begin rolling out mid-May 2025 and expect to complete by mid-June 2025.

[How this will affect your organization:]

After this rollout, users can still work with files and folders in the Microsoft SharePoint document library linked to the channel. All existing functionality in the Files tab will be available in the In library view of the Shared tab in channels. The In posts view in the Shared tab will display all files and links shared in channel posts:

Users can use the order the files by date using the Recent view and then filter by Files or Links. Before this rollout, this functionality was only available in chats:

Users can use the In posts view to find links:

These changes to channels will be available by default.

Coming soon after this rollout for the In posts view of the Shared tab in channels: Keyword search

[What you need to do to prepare:]

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

Before rollout, we will update this post with new documentation.

1. Add Files as a knowledge source
2. Add Dataverse as a knowledge source
3. Virtual Agent

1. Sales Copilot
2. Customer Service Copilot
3. Contact Center Copilot
4. Field Service Copilot

1. Copilot Chat
2. Dataverse search

1. In Power Apps / Power Automate
2. In Microsoft Copilot Studio
3. Power Apps / Power Automate – Custom AI Prompts

• “DataverseSearch-StructuredIndex” for Database storage indexing
• “DataverseSearch-UnstructuredIndex” for Files storage indexing

Updated March 7, 2025: We have updated the rollout timeline below. Thank you for your patience.

Coming soon for Microsoft Outlook: If users have enabled work hours and location in Settings, their colleagues will be able to more quickly see who plans to be in the office with a new calendar feature.

This message applies to new Outlook for Windows and Outlook on the web.

This message is associated with Microsoft 365 Roadmap ID 410986.

[When this will happen:]

Targeted Release: We will begin rolling out in mid-August 2024 and expect to complete by late August 2024.

General Availability (Worldwide): We will begin rolling out early October 2024 and expect to complete by early March 2025 (previously late February).

[How this will affect your organization:]

Before this rollout: Users select the Location icon for each day in the calendar to see who plans to be in the office:

After this rollout: In addition to the Location icon, users will have a new “always on” peek in the top right of the calendar that shows who plans to be in the office for the current day:

This feature is on by default and available to all users of new Outlook for Windows and Outlook on the web.

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation.

Updated March 7, 2025: We have updated the rollout timeline below. Thank you for your patience.

Coming soon to Microsoft Outlook: Work hours and location information will be available in the My Day pane in Outlook. Users will be able to update their Work Hours and Location information from My Day and also see who is coming to Office. This message applies to new Outlook for Windows desktop and Outlook for the web.

This message is associated with Microsoft 365 Roadmap ID 412618.

[When this will happen:]

Targeted Release:  We will begin rolling out early December 2024 (previously mid-November) and expect to complete by mid-January 2025 (previously mid-November). 

General Availability (Worldwide): We will begin rolling out mid-January 2025 (previously early October) and expect to complete by early April 2025 (previously late February).

[How this will affect your organization:]

Before this rollout, users can review and update their work hours and location information in Outlook Settings > Calendar > Work hours and location. This settings page will remain in place after the rollout.

After this rollout, users will also be able to see and update their work hours and location information in the My Day pane in Outlook. Changes to the My Day pane will sync to any other work hours and location settings made in Outlook.

My Day pane with prompt to Set up your work location:

My Day pane with work location information, which can be updated:

This feature is on by default.

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation.

Updated March 7, 2025: We have updated the rollout timeline below. Thank you for your patience.

When creating a new Loop workspace, users will be able to choose an existing Microsoft 365 Group to manage the workspace’s lifetime, governance, and compliance, similar to SharePoint Team sites.

This message is associated with Microsoft 365 Roadmap ID 422728

[When this will happen:]

General Availability (Worldwide): We will begin rolling out late March 2025 (previously late February) and expect to complete by late April 2025 (previously late March).

[How this will affect your organization:]

Once available, when creating a new Loop workspace, users will be able to choose an existing Microsoft 365 Group to manage the workspace’s lifetime, governance, and compliance, similar to SharePoint Team sites.

[What you need to do to prepare:]

There is nothing you need to do to prepare. These changes will roll to your tenant automatically.

Updated March 3, 2025: We have updated the content. Thank you for your patience.

Coming soon in Microsoft Purview AI Hub: Data assessments provides a way for admins to drive data security outcomes by intersecting the sensitivity of data with actual accesses by users and providing remediation actions.

This message is associated with Microsoft 365 Roadmap ID 464997.

[When this will happen:]

Public Preview: We will begin rolling out mid-November 2024 and expect to complete by mid-November 2024.

[How this will affect your organization:]

Data assessments will be added to the left navigation in the Purview AI Hub. A default assessment is initiated on the first visit to Purview AI Hub, and admins can create custom assessments at any time:

Data assessments results show metrics like total user accesses, types of sharing links, if files are labeled, and if sensitive info types are found:

Remediation actions on the Protect tab provide guidance on how to take steps to protect the data:

This feature is on by default and available for admins to configure.

[What you need to do to prepare:]

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. You may want to notify your admins about this change and update any relevant documentation.

Learn more: Microsoft Purview data security and compliance protections for generative AI apps

Updated March 7, 2025: We are introducing Malware Threat Classes as part of our ongoing efforts to enhance threat classification. This update, once rolled out during end of March, will improve your ability to understand the malware attacks by integrating Threat Classification details across key experiences enabling better detection, analysis, and response. As the system evolves, additional threat classifications will be introduced to stay ahead of emerging attack methods.

We have updated our Threat Classification documentation on Microsoft Learn. You can now access the latest version from here.

Coming soon to Microsoft Defender for Office: We will introduce Threat classification details to enhance your ability to understand the intent behind email attacks. This update will allow you to integrate Threat classification information across key experiences, enabling better detection, analysis, and response. The Threat classification system utilizes large language models (LLMs), machine learning (ML) models, and other advanced techniques to understand the intent behind threats, providing a more accurate classification. As the system evolves, you can expect new Threat classifications to be added to keep pace with emerging attack methods.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out early January 2025 and expect to complete by late January 2025.

[How this will affect your organization:]

Threat Explorer: You will be able to filter emails by Threat classification, view the classification in the results, analyze trends using charts, and export data with the classification details included:

Advanced Hunting: The ThreatClassification column will be available in the EmailEvents table, allowing you to create custom detection rules based on classification details:

Email summary panel: Threat classification will be integrated across multiple areas, including Alerts, Incidents, Reports, AIR, Submission, Explorer, and Advanced Hunting, providing a comprehensive view of threat classifications:

Email entity page: A new Threat classification field will be added in the threat detection details, helping you understand the context and intent of the detected threat:

These changes will be available by default for admins to configure.

[What you need to do to prepare:]

Familiarize your team with the new Threat classification details available in the Threat Explorer, Advanced Hunting, email summary panel, and email entity page.

Leverage Threat classification to enhance filtering, hunting, and trend analysis in your workflows.

Prepare to update any custom detection rules or automated workflows to incorporate Threat classification for more targeted and insightful threat detection.

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. You may want to notify your team about this change and update any relevant documentation.

Before rollout, we will update this post with revised documentation.

Updated March 7, 2025: We have updated the content. Thank you for your patience.

We are thrilled to announce the upcoming rollout of custom engine agents in Microsoft 365 Copilot. These agents are specialized agentic solutions that can be built on any large language model (LLM), toolchain, or orchestration tool tailored for specific domain or tenant workflows. This feature is already supported in Microsoft Teams and will be available after this rollout in Microsoft 365 Copilot Business Chat (BizChat).

To access custom engine agents, your organization will need a Microsoft 365 Copilot license.

This message is associated with Microsoft 365 Roadmap ID 474439.

[When this will happen:]

Public Preview: We will begin rolling out early February 2025 and expect to complete in mid-March 2025.

General Availability (Worldwide): We will begin rolling out in late March 2025 and expect to complete by early April 2025.

[How this will affect your organization:]

Custom engine agents will empower your organization to create highly customized agentic experiences that leverage your own AI systems and orchestrators. This means you can design unique prompts, connect to any LLM, and integrate these custom agents with Microsoft 365 Copilot.

After this rollout, all users or specific users will be able to access the agents, provided the agents have been enabled and deployed in the Microsoft 365 admin center > Copilot tab.

Creating custom engine agents

Eligible users, or those designated by you, will have the capability to create agents using Microsoft Copilot Studio for low-code tools or the Microsoft Teams Toolkit in Microsoft Visual Studio for pro-code solutions. Users can access Copilot Studio only if you have enabled the Microsoft Power Automate free license for them.

Developers can also use the Teams Toolkit in Visual Studio and the Teams AI Library for pro-code solutions to build these agents from scratch.

Deploying custom engine agents

All the familiar admin deployment and management controls in the Microsoft 365 admin center for declarative agents will seamlessly transition to custom engine agents:

Admin controls in the Microsoft 365 admin center for a published custom engine agent:

Custom engine agents created using Copilot Studio can be deployed by users for their individual work-related tasks. Also, users have the flexibility to share these agents with internal teams, contingent on the settings you configure in the Microsoft 365 admin center > Teams applications > Shared Copilot applications. Organization-wide sharing requires admin approval through the Microsoft 365 admin center.

Custom engine agents created or updated using the Teams Toolkit in Visual Studio and the Teams AI Library requires admin approval and admin deployment in the Microsoft 365 admin center.

Provisioning a customer engine agent in the Microsoft 365 admin center > Integrated apps:

[What you need to do to prepare:]

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. You may want to notify your users about this change and update any relevant documentation.

Learn more

• Connect and configure an agent for Microsoft Teams – Microsoft Copilot Studio | Microsoft Learn (will be updated before rollout)
• Custom engine agents for Microsoft 365 | Microsoft Learn (will be updated before rollout)
• Manage Copilot agents in Integrated Apps – Microsoft 365 admin | Microsoft Learn (will be updated before rollout)
• Share agents with other users – Microsoft Copilot Studio | Microsoft Learn (will be updated before rollout)

Custom engine agents using Microsoft Copilot Studio

We are excited to announce that you can now create a Custom engine agents using Microsoft Copilot Studio. This enables you to use your own foundational model to respond to prompts without requiring any extensive coding knowledge. Eligible Users or users designated by you can deploy agents personally or share them with internal teams, depending on ‘Shared Copilot’ settings within the Admin Centre. Organization-wide sharing requires admin approval through the admin centre.

To get started please refer to the following

Key concepts – Authoring agents – Microsoft Copilot Studio | Microsoft Learn

Connect and configure an agent for Teams and Microsoft 365 Copilot – Microsoft Copilot Studio | Microsoft Learn

Stay tuned for an update on when you can start creating Custom engine agents using Teams Toolkit in Visual Studio and the Teams AI Library.

Updated March 7, 2025: We have postponed this release to ensure the proper customer experience. The rollout timeline has been updated below. Thank you for your patience.

We are pleased to inform you that we will roll out two improvements to enhance compliance and security for voicemail messages in Microsoft Exchange.

This change is related to three products: Microsoft Teams calls, Microsoft Outlook/Exchange, and Microsoft Skype for Business calls. Results will be visible in Outlook/Exchange email messages.

[When this will happen:]

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

General Availability (GCCH, DoD): We will begin rolling out mid-May 2025 and expect to complete by mid-June 2025.

[How this will affect your organization:]

1. The From: field of voicemail email messages will be updated to comply with the latest RFC standard, RFC 6854: Update to Internet Message Format to Allow Group Syntax in the From: and Sender Header Fields. According to this compliance standard, the Internet message format must always include an address in the From header field.

Example:

• Before this rollout: +44 28 7584 5695 <442875845695>
• After this rollout: +44 28 7584 5695 (Unverified) <[email protected]>

2. To strengthen trust and security in voicemails received from external PSTN calls and from federated tenants, Unverified and External tags will always be added to the From field of voicemail messages in the mailbox.

Note: This rollout applies to voicemail messages in Microsoft Exchange received from external PSTN calls and calls from federated tenants.

Example of the From field in voicemail message if PSTN caller was not found in Entra ID contacts:

• Before this rollout: +44 28 7584 5695
• After this rollout: +44 28 7584 5695 (Unverified)

Example of the From field in voicemail message if PSTN caller was found in Entra ID contacts:

• Before this rollout: John Smith
• After this rollout: John Smith (External)

Example of the From field in voicemail message for calls from federated tenant:

• Before this rollout: John Smith
• After this rollout: John Smith (External)

Example of the From field in voicemail message for anonymous Skype calls:

• Before this rollout: Anonymous
• After this rollout: Anonymous (Unverified)

Note: Both improvements will always be on by default.

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before or after the rollout. You may want to notify your users about this change and update relevant documentation.

Updated March 7, 2025: We have updated the rollout timeline below. Thank you for your patience.

We are excited to announce the upcoming People administrator role in Microsoft Entra, designed to improve and streamline administrative capabilities in Microsoft 365. Developed from customer feedback, this role will provide dedicated permissions for managing people-related settings and profile photos without needing the high privileges of Global admin or User admin roles.

[When this will happen:]

General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early February 2025 and expect to complete by late March 2025 (previously late February).

[How this will affect your organization:]

After this rollout, admins will be able to assign the new People admin role to users in:

• Entra Portal
• Microsoft 365 Admin Center

What are the capabilities of the People admin role?

1. Update profile photos for all users, including admins.
2. Update people settings for pronouns and name pronunciation, Profile card settings, and photo update settings for all users.

Why is this new role a better solution?

The People admin role allows organizations to delegate people-related tasks more effectively and securely. By limiting access to necessary settings, it reduces risks associated with higher privilege roles and aligns with user jobs focused on people administration.

The People admin role will enable organizations to:

• Delegate tasks without giving excessive permissions to other admins.
• Access new features and configurations in the People domain more easily.
• Maintain security by avoiding the use of highly privileged roles for routine tasks.

This role complements existing roles and enhances satisfaction with Microsoft administrative tools.

[What you need to do to prepare:]

We recommend admins:

1. Review the People admin role documentation to understand its capabilities.
2. Assess current roles to identify where the new role fits.
3. Communicate changes to staff if needed, highlighting improved delegation and people-related access.
4. Review your current configuration to determine the impact on your organization.

This rollout will happen automatically with no admin action required before the rollout. The People admin role will be available by default.

Learn more

• Microsoft Entra built-in roles – Microsoft Entra ID | Microsoft Learn (will be updated before rollout)
• About admin roles in the Microsoft 365 admin center – Microsoft 365 admin | Microsoft Learn (will be updated before rollout)
• Assign Microsoft Entra roles – Microsoft Entra ID | Microsoft Learn

Updated March 7, 2025: 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 is introducing a new location consent experience that gives users the choice of when and how Teams can use their location data (specifically SSID & BSSID).

Please refer to the public documentation that will be published shortly.

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 late March 2025 (previously mid-March) and expect to complete by late March 2025 (previously mid-March).

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

[How this will affect your organization:]

All new and existing Teams for Work users within 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 or troubleshooting ex via tooling such as Call Quality Dashboard or Network and Locations matching via BSSID for emergency calling location. 

Important 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 to continue working as expected, and users will not be prompted with any of the new location consent dialogs. 

The new Teams location consent changes will impact the following Teams features: 

1. Emergency Calling 
2. Location Based Routing 
3. Network and Locations matching via BSSID 
4. Call Quality Dashboard 

For all new Teams for Work users, they will first be prompted with an operating system level consent dialog, requesting location permission granting.   

• Existing Teams for Work users who had previously accepted or denied operating system level consent for location will not see this dialog a second time.
• If location access is allowed, 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 location access is disallowed, several Teams Call Quality Dashboard metrics will be impacted, and Network and Location matching via BSSID from dynamic emergency calling policies will not work.
• Users can still manually add their physical address for emergency calls via the Teams Calls app if an admin has enabled ExternalLookupMode for their users.

Immediately after consenting to allow location access at the operating system level (or for those who had previously consented to location access), both new and existing Teams for Work users will be presented with a new Teams app level location permission dialog.

Users must choose between “Allow all,” which grants Teams full location access used for emergency calls and for IT Admin insights and troubleshooting, or “Keep emergency only,” which restricts location usage to emergency calling purposes. It is important to note only end users who are configured for a dynamic emergency calling policy will see this version of the dialog. Users without ExternalLookUpMode enabled will see a slightly different version of this in-app consent dialog that excludes emergency calling. Users can modify their operating system or app level location detection preferences at any time via Teams settings under Privacy > Location. On fully managed devices, these settings will be ON by default and can only be disabled via the OS level location setting.

[What you need to do to prepare:]

Please 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 via BSSID, you may want to recommend that users allow location access for those options, otherwise a user’s location data will no longer flow through 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 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

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)
• WiFi Access Location changes – Microsoft Learn

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.