Public Sector Blog

230 MIN READ

May and April 2025 - Microsoft 365 US Public Sector Roadmap Newsletter

Jesse_Tedoff

Microsoft

May 21, 2025

The Future of AI in government / In Teams Phone assign shared lines, call queues, and call transfer key to line keys / Microsoft 365 Copilot Pages created in Microsoft 365 Copilot Chat will open in the Microsoft 365 Copilot app for the web

Purview

Labeling improvement for non-Office/PDF files using endpoint DLP

Exchange Online

Exchange Server Security Changes for Hybrid Deployments

Direct Send Control in Exchange Online – Preview GCC, GCCH, DOD

Teams

Personal Meeting Templates – GCC & GCCH June, DOD August

Microsoft 365 Copilot

Copilot Wave 2 Spring Release - GCC

Discover the Future of AI in Government

Are you ready to explore the transformative power of artificial intelligence in the public sector? Join us as we delve into the key themes discussed in the recent seminar, "Microsoft AI for Government," led by Jason Payne, Chief Technology Officer for Microsoft Federal.

What’s New in Microsoft 365 Copilot for Government | Microsoft Community Hub

The AI-powered capabilities of Microsoft 365 Copilot are expanding across government environments. Whether you’re in GCC, GCC High, or DoD, here’s what you need to know about upcoming availability, what’s changing, and how to prepare.

What’s New in Microsoft Teams | April 2025

Brand impersonation phishing protection first launched for commercial users in January, and now is available for the GCC, GCC-H, and DoD audiences. VDI users can join optimized meetings with people in other Microsoft 365 cloud environments (e.g., a user in GCC-H joining a meeting in commercial, GCC, or DOD) through three options: authenticated access via cross-cloud meeting connection, authenticated access using a guest account, or anonymous access. These scenarios require Slimcore-based optimization.

Licensing and Pricing Updates for Teams Phone and Power BI Coming July 1, 2025

On April 1, 2025, we updated pricing for commercial customers of Teams Phone and Power BI. Beginning July 1, 2025, Microsoft will implement licensing and pricing updates for new and renewing US government customers across all government cloud deployments: GCC, GCC High, and DoD.

Where to Start with Microsoft Teams Apps in Gov Clouds

Customers in our Office 365 government clouds, GCC, GCCH, and DoD, are continuing to evolve how they do business in the hybrid workplace. As Microsoft Teams is the primary tool for communication and collaboration, customers are looking to improve productivity by integrating their business processes directly into Microsoft Teams via third-party party (3P) applications or line-of-business (LOB)/homegrown application integrations.

Microsoft 365 Government Adoption Resources

Empowering US public sector organizations to transition to Microsoft 365

Microsoft 365 Roadmap
This link is filtered to show GCC, GCC High and DOD:

Stay on top of Microsoft 365 changes

Here are a few ways that you can stay on top of the Office 365 updates in your organization.

Microsoft Tech Community for Public Sector
Your community for discussion surrounding the public sector, local and state governments.

Microsoft 365 for US Government Service Descriptions

Get started with Microsoft 365 Copilot
Public Sector Center of Expertise We bring together thought leadership and research relating to digital transformation and innovation in the public sector. We highlight the stories of public servants around the globe, while fostering a community of decision makers. Join us as we discover and share the learnings and achievements of public sector communities.
Microsoft Teams for US Government Adoption Guide

Please note: This section is for informational purposes only. It is presented as is and as available with no warranty and no supportability given expressly or implied. Questions, comments, concerns and all other feedback must be presented in the comment section below the post, thank you!

SharePoint Online / OneDrive for Business

MC1062451 — Microsoft SharePoint: Customize your sites with multi-color themes

Microsoft 365 Roadmap ID 489833 and Roadmap ID 490062

Coming soon for Microsoft SharePoint: Site owners can apply a multi-color theme to the site. We will offer these multi-color themes out of the box. Site owners will create the themes using the Site branding feature, or the brand manager will use branding from your organization if you have set up a brand center in the Microsoft 365 admin center.

NOTE: The brand center app requires the use of a public content delivery network (CDN) available in the Worldwide environment. CDN is not available in the GCC, GCC High, or DoD environments.

When this will happen:

These releases will roll out to Worldwide (with brand center capability) and to GCC, GCC High and DoD (without brand center capability):

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

General Availability: We will begin rolling out early June 2025 and expect to complete by mid-June 2025.

How this will affect your organization:

This feature introduces multi-color themes that support multiple color combinations in a theme. In addition to custom themes, eight new out-of-the-box site themes will be available after this rollout.

The theme colors will show up in the site header and site footer, applied by site managers. The theme colors will also show up in section backgrounds, the rich text editor (text web part), and Design ideas, all edited by page authors.

This feature will be available by default.

Edit a multi-color theme in Site branding:

Apply an out-of-box multi-color theme in Change the look:

Apply theme colors to a header in Change the look:

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.

Learn more

MC1061109 — Microsoft SharePoint and Microsoft OneDrive: New PDF compression feature

Microsoft 365 Roadmap ID 487440

Coming soon: Users will be able to use the new Compress feature to reduce the file sizes of PDFs stored on Microsoft OneDrive for the web or Microsoft SharePoint. Users can choose from three different compression levels.

When this will happen:

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

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

How this will affect your organization:

To compress PDF files for a smaller size:

Open a PDF in OneDrive for the web (in SharePoint, go to the document library and choose Preview):
Select the Compressbutton at the top of the screen:

Select a compression level and then select Save a copyto save the compressed file:

A progress notification will appear at the bottom of the screen. After the compression is complete, select Open from the notification to view the compressed file:

FAQ

What is the quality and subsampling for each compression level?

We offer three levels of image compression. All use lossy compression and chroma subsampling to reduce file sizes while maintaining visual quality. The options are:

Light compression: Apply 4:2:0 color subsampling and reduce 25% of image pixels.
Medium compression: Apply 4:2:0 color subsampling and reduce 50% of image pixels.
Heavy compression: Apply 4:2:0 color subsampling and reduce 75% of image pixels.

Users can compress one PDF at a time. The original file must be smaller than 300 MB.

This feature is on by default.

What you need to do to prepare:

Note: Some users may see this feature before other users in your organization.

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.

MC1055557 — SharePoint Online: Content Security Policy Control in Tenant Administration

SharePoint Online Tenant Administrators can now allow script sources for modern pages in SharePoint sites. This feature is particularly useful in scenarios where modern pages have custom code that loads scripts (e.g., TypeScript code) from external sources like a content delivery network (CDN). SharePoint will now report to administrators where sources that have not been allowed are loaded from, providing a way for administrators to identify those sources and take action. Tenant Administrators can also enforce browsers to only load scripts from allowed sources. This behavior can be enabled using SharePoint Online Management Shell.

When this will happen:

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

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

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

How this will affect your organization:

Tenant Administrators will have the option to control and govern where custom code loads scripts and, if needed, enforce browsers to only load scripts from trusted sources. A new "Trusted script sources" page will give administrators control over which source can be trusted to load scripts.

What you need to do to prepare:

This rollout will happen automatically with no admin action required.

MC1055555 — Microsoft SharePoint Online: We will remove retired DISCO and WSDL web pages

ASP.NET DISCO and WSDL pages were the web service APIs for customers who wanted to create a proxy for their web services. The retirement of ASP.NET web services was announced in 2013 and should not be used. We recommend using Microsoft Graph for remote operations where possible.

We will remove these pages from Microsoft SharePoint Online starting mid-August 2025 and ending in mid-September 2025.

Learn more: Removal of deprecated DISCO & WSDL aspx pages from SharePoint Online - Microsoft 365 Developer Blog

MC1040544 — (Updated) Microsoft SharePoint: Enhancements to Restricted access control (RAC)

Microsoft 365 Roadmap ID 483028

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

Coming soon for Microsoft SharePoint: New enhancements for the restricted access control (RAC) policy for SharePoint admins to restrict access to SharePoint sites, including managing Microsoft 365 group-connected sites with Microsoft 365 groups or Microsoft Entra security groups.

Customers with SharePoint Advanced Management (SAM) capabilities in their tenants can use the RAC policy.

When this will happen:

Public Preview: We will begin rolling out late March 2025 and expect to complete by late April 2025.

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

How this will affect your organization:

Admins can go to SAM or use Microsoft PowerShell cmdlets to configure the updated RAC policy.

The enhanced policy will be available by default for admins to configure.

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.

Only awareness on how they could utilize this policy in their tenant.

Learn more: Restrict SharePoint site access with Microsoft 365 groups and Microsoft Entra security groups - SharePoint in Microsoft 365 | Microsoft Learn (will be updated before rollout)

MC1040543 — Retiring "Shared with Us" Feature in SharePoint Teams sites

We are retiring the "Shared with us" feature on SharePoint Teams sites, which provided a centralized view of files and folders shared with site members.

When this will happen:

We will begin retirement mid-April 2025 and expect to complete by mid-May 2025.

Are there any recommended alternatives to the "Shared with Us" feature:

While there is no direct replacement for this feature, users can leverage existing tools in OneDrive and SharePoint to manage shared content effectively:

OneDrive "Shared with me":Users can view files and folders that have been shared with them in OneDrive > Shared for a personalized view of shared content.
Microsoft Teams and email notifications:When files are shared via Teams or Outlook, users receive notifications and can access shared content directly from their Teams chat and email.

What you need to do to prepare:

No action is required, but we recommend informing your users about this change and guiding them on how to find shared content using the recommended alternatives above.

We understand that changes to features can impact workflows, and we appreciate your understanding as we focus on improving SharePoint’s overall experience.

MC1034592 — SharePoint Online: Table toolbar

Microsoft 365 Roadmap ID 394278

In SharePoint Online, Table toolbar is a new toolbar that allows authors to use table functionality. Table Styles was previously available on the text webpart. All the Table Styles styles are now available via the Table toolbar, including some new table features like merge, split, add space before and after, and others. With the introduction of Table toolbar, users see a menu that is always in focus when working on a table. The Table toolbar will automatically adjust by expanding or compressing based on the section layout used. When compressed, the table options move into the overflow (...) button.

The new table toolbar will be available in SharePoint and Viva Amplify.

When this will happen:

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

How this will affect your organization:

Within the text web part, users will be able to insert a table and, once the table is inserted, users will see the Table toolbar that is always in focus. Within Table toolbar, users can do all the table editing and formatting that is already available, including change layout, add/delete row/columns, and so on along with any new table features that may be added in the future.

Current experience

Future experience

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.

MC1031266 — Microsoft SharePoint: Microsoft 365 Copilot customers now have SharePoint Advanced Management capabilities

We announced at Ignite (November 2024) that SharePoint Advanced Management will be included with Microsoft 365 Copilot licenses in early 2025. We are pleased to announce that your tenant now includes all SharePoint Advanced Management (SAM) capabilities. Learn more: Get ready for Microsoft 365 Copilot with SharePoint Advanced Management - SharePoint in Microsoft 365 | Microsoft Learn

A Microsoft 365 Copilot license is required to use this feature.

When this will happen:

General Availability (Worldwide): Available now.

How this will affect your organization:

In the SharePoint admin center, the SharePoint Advanced Management page will display this message: “Your SharePoint Advanced Management subscription is now enabled:"

Important recommendations from the product team:

The oversharing baseline report using permissions is the first significant step in understanding the current oversharing status in your entire tenant and setting up an appropriate baseline. This report is available in Microsoft PowerShell onlyand is easy to miss because it is not present in SAM. We recommend using PowerShell and initiating the report as soon as possible. After you have the report, you can start to focus on clean-up and remedial actions.
Remedial actions such as Restricted access control, Restricted content discovery(to exclude content from appearing in Copilot search), and Site access review are documented in Microsoft SharePoint Premium - SharePoint Advanced Management overview - SharePoint in Microsoft 365 | Microsoft Learn

SAM is available by default for admins to configure.

What you need to do to prepare:

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.

MC1028318 — Microsoft SharePoint Online Management Shell will replace IDCRL authentication protocol with OAuth

Starting with the March 28, 2025 release of the Microsoft SharePoint Online Management Shell (SPO Admin PowerShell), we will replace the IDCRL (Identity Client Run Time Library) Authentication protocol with OAuth (modern authentication protocol). This update is part of our ongoing efforts to enhance security and adopt modern authentication practices. To enhance your security, please install the March 28, 2025 or later version of SharePoint Online Management Shell from Download SharePoint Online Management Shell from Official Microsoft Download Center.

When this will happen:

Starting with the March 28, 2025 version of SharePoint Online Management Shell, requests using the Connect-SPOService cmdlet will be automatically authenticated with the new OAuth protocol. This update does not change existing admin flows and no other admin action is required. We will also display a warning message about this change in the March 28, 2025 or later releases of SharePoint Online Management Shell.

How this will affect your organization:

How to check your current version of SharePoint Online Management Shell (SPO Admin PowerShell)

Method 1: Using PowerShell

Open PowerShell.
Run this command: Get-Module -Name Microsoft.Online.SharePoint.PowerShell -ListAvailable | Select-Object Name, Version
This will display the installed version of the SharePoint Online Management Shell module.

Method 2: Using Installed Programs List

Open the Control panelin Windows.
Go to Programs and Features.
Look for Microsoft SharePoint Online Management Shell in the installed programs list.
The version number will be displayed there.

This warning message in SharePoint Online Management Shell informs admins that we have replaced IDCRL with OAuth:

What you need to do to prepare:

Please install the March 28, 2025 or later version of SharePoint Online Management Shell from Download SharePoint Online Management Shell from Official Microsoft Download Center.

Learn more: Can't connect to SharePoint Online - SharePoint | Microsoft Learn (will be updated before rollout)

MC1026218 — (Updated) Microsoft OneDrive and Microsoft SharePoint: New annotation layout and tools for editing PDFs

Microsoft 365 Roadmap ID 483156

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

Coming soon for Microsoft OneDrive and Microsoft SharePoint: A new PDF annotation layout that features a more intuitive design. After this rollout, all annotation tools will be in a single row at the top of the screen, including a new type of eraser that can remove pen and highlighter annotations pixel by pixel.

This message applies to One Drive for the web and SharePoint Online.

When this will happen:

Targeted Release: We will begin rolling out early April 2025 (previously late March) and expect to complete by mid-April 2025.

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

How this will affect your organization:

To use the new annotation layout:

Find the PDF saved in OneDrive or Microsoft SharePoint and select the PDF to open it.
Select Edit at the top right of the screen to access the annotation tools. Note: When editing in OneDrive or SharePoint, ignore the Edit in appoption in the dropdown menu next to Edit, which will open the PDF in another PDF tool such as Adobe Acrobat.
All annotation tools are found at the top of the screen.

To erase existing pen or highlighter annotations:

Find the PDF saved in OneDrive or SharePoint and select the PDF open it.
Select Edit at the top right of the screen to access the annotation tools.
Select Eraser from the annotation toolbar and left click with the mouse to delete with precision (pixel by pixel).
Select Save changesat the top left of the screen.

To delete an entire pen or highlighter annotation, choose one of these options:

Select an existing annotation and then select the Deletekey on the keyboard.
Select the trash icon at the top left of the selected annotation.

The Eraser tool does not work for Text annotations.

This change will be available to users 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.

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

MC1025216 — (Updated) Microsoft OneDrive: New naming convention for folder shortcuts

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

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

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 Teamand 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 postfrom 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)

MC1024394 — (Updated) Microsoft SharePoint: New card animation feature for Pages, News, and Microsoft Viva Amplify

Microsoft 365 Roadmap ID 481510

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

Coming soon for Microsoft SharePoint: Cards can be animated for some web parts (Editorial cards, Images, and People) in SharePoint Pages, News, and Microsoft Viva Amplify.

When this will happen:

Targeted Release: We will begin rolling early April 2025 (previously out late-April) and expect to complete by early May 2025.

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

How this will affect your organization:

This feature will be enabled by default for new cards created after the feature is released. Users can disable card animation in the web part property pane. To add animation to existing web parts, users can enable the setting in the web part property pane. To preview the card animation, view the published page or use Preview mode.

Pages and web parts created before this rollout are not impacted by this change.

What you need to do to prepare:

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

MC1017119 — (Updated) SharePoint: OneDrive and SharePoint – Protect PDF with password

Microsoft 365 Roadmap ID 482193

Updated April 16, 2025: We have updated the title and content. Thank you for your patience.

SharePoint and OneDrive users can now secure their PDF files by adding protection that restricts unauthorized access through OneDrive Web. This feature allows you to set an open password, which is required to access the PDF, or an owner password, which sets permissions for actions such as printing or editing the document. This ensures your files remain secure and only accessible to authorized individuals

When this will happen:

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

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

How this will affect your organization:

Before this rollout: Users cannot setup passwords to protect their PDF files.
After this rollout: Users can set a User Password to protect the PDF from being opened by non-authorized users or set Owner Password to grant certain operations like printing, copying, or modifying the content.

To set up an open password:

Open a PDF you have saved in OneDrive or SharePoint document library,
Click the lock icon located at the top left of the screen

3.Under Security, enter matching passwords.

Click Save as to password protect this document,
Choose the location where you want to save the file and click Save here.
A notification will appear at the bottom of the screen, indicating that a new file has been successfully saved.

To set up an owner password:

Open a PDF you have saved in OneDrive or SharePoint document library,
Click the lock icon located at the top left of the screen,
Under Protection, check the Grant permissions box.
Under Grant permission, check the box for the permissions you want to allow on this document.
Type matching owner passwords and then click Save as to set permissions for this document,
Choose the location where you want to save the file and click Save here,
A notification will appear at the bottom of the screen, indicating that a new file has been successfully saved.

FAQ

Will password protection overwrite my current PDF?

No, we currently only allow the "Save as" option, so the original PDF will remain intact.

Can I see the same permission set on the same PDF document using other apps?

Yes, users are able to view the same permission settings, and the same restrictions are applied when they view the PDF within OneDrive and SharePoint.

What you need to do to prepare:

Note: Some users may see this feature before other users within your organization.

MC1013464 — (Updated) We will remove the EEEU sharing permission from root web and default document library in OneDrive’s

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

EEEU, which stands for Everyone Except External Users, is a permission setting used in Microsoft SharePoint and Microsoft OneDrive to manage access to content. This setting allows all internal users in an organization to access certain content while excluding external users. We discourage use of this setting due to concerns about inadvertent oversharing of user data.

What is changing

Starting April 17, 2025 (previously April 10) and ending by September 30, 2025, we will run logic to detect and remove the EEEU permission from the root site of each user’s OneDrive and the default document library in OneDrive.

How this will affect your organization:

Before this retirement, apps, processes, or users may be able to discover and access content from OneDrive because of the inadvertent presence of EEEU in the root web and default document library in OneDrive. After the EEEU permission is removed, these apps, processes, and users will lose access to the content from the affected OneDrive accounts. Users, processes, and apps that were granted direct permissions to specific files and folders of a OneDrive account will not be impacted and will continue to retain their access.

We recommend OneDrive owners and OneDrive admins give explicit permission to individual files and folders in OneDrive to be accessed by one or more users or apps.

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. If you have questions or wish to discuss more, please open a support ticket.

Learn more: The section called Use Microsoft Entra groups and dynamic membership instead of default claims in Grant Everyone claim to external users in Microsoft 365 - Microsoft 365 | Microsoft Learn

MC1005510 — (Updated) SharePoint Online: Updates to Microsoft Lists forms

Microsoft 365 Roadmap ID 124865

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

In Microsoft SharePoint Online, Microsoft Lists forms are being updated to enhance your list data collection and management. These updates include subscribing to notifications, form scheduling, conditional branching, quick form creation, and additional field-type support.

When this will happen:

Targeted Release: We began rolling out early January 2025 and expect to complete by mid-February 2025.

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

How this will affect your organization:

Updates to the Microsoft Lists forms include these key improvements:

New creation experience: Users can now create forms directly from Lists home, SharePoint, and the Lists app in Microsoft Teams. This streamlined process automatically creates the underlying list for responses, saving time and effort.
Conditional branching: Conditional branching allows you to show or hide questions based on previous answers, ensuring respondents only see relevant questions. You can branch questions to other questions or based on choices in a Choice field.
Add logo: Enhance your forms with a relevant logo, making them look more professional and reinforcing brand identity.
Support for Additional Field Types Attachments, Image, Location, Lookup. Please note that for Lookup fields respondents need at least read access to the underlying source list to see and select the options.
Get notified of new responses and Schedule form Start/End dates: Choose to be notified when someone submits a response to a form you own or have access to. Set specific start and end dates for your forms.

For more information, see Microsoft Lists forms: What's New.

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.

MC1002417 — (Updated) Microsoft SharePoint: The "spaces" feature will retire

Updated April 21, 2025: We will be rolling out the change to prevent users from activating the SharePoint spaces feature in site settings (or using PowerShell) starting May 15th. It will still be possible to disable the feature using this dialog. Users attempting to enable the feature will receive an error message indicating that the Spaces feature is being deprecated and cannot be enabled at this time. Sites with the feature already enabled will continue to function with the feature enabled.

Due to limited usage and our focus on investing in Microsoft Mesh where immersive 3D content can be created and experienced in a multi-user collaborative experience, we will retire the spaces feature from Microsoft SharePoint Online starting March 10, 2025 and ending August 11, 2025. As another alternative, you may choose to transition some existing content to SharePoint Pages.

How this will affect your organization:

Users will no longer be able to view or create SharePoint spaces after this retirement is complete. Retirement timeline details:

Starting March 10, 2025, the spacesfeature be turned off by default. After this date, users can still access the spaces feature on SharePoint sites that have used it previously and users can enable the feature for individual sites on the Site features page.
Starting May 15, 2025, users will no longer be able to enable the spacesfeature on the Site features page, but SharePoint sites with the feature already enabled will continue to function as normal.
Starting August 11, 2025, the feature will be fully disabled and users will be unable to view, edit, or create new spaces.

Learn how to identify SharePoint sites with the spaces feature enabled: SharePoint Spaces deprecation - Microsoft Support

What you need to do to prepare:

This change will happen automatically by the specified date. No admin action is required; however, existing content will no longer be usable after the feature is retired. Please notify your users about this change, update relevant documentation, and consider Microsoft Mesh for future immersive experiences in Microsoft 365.

You and your users can identify spaces content in a SharePoint site by going to the Pages library and looking for files where the Content type is Space.

Learn more: SharePoint Spaces deprecation - Microsoft Support

MC989979 — (Updated) Microsoft SharePoint: New preview mode for Pages and News posts

Microsoft 365 Roadmap ID 473452

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

Coming soon to Microsoft SharePoint: The new Preview mode can be used to understand how Pages and News posts will appear on different device types when viewed by an audience.

When this will happen:

Targeted Release: We will begin rolling out late March 2025 (previously mid-February) and expect to complete by mid-April 2025 (previously late March).

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

How this will affect your organization:

After this rollout, a Preview button will display in the command bar while users are editing Pages and News posts in SharePoint. After selecting Preview, users can see what the page will look like in view mode for the audience. When previewing Pages, users can navigate between Desktop and Mobile device types. When previewing News posts, users can also choose to view the email version as Desktop or Mobile device types.

This change will be available by default.

What you need to do to prepare:

You may want to notify users, update your user training, and prepare your help desk.

This rollout will happen automatically by the specified date with no admin action required before or after the rollout.

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

MC974358 — (Updated) Microsoft SharePoint admin center: New "App insights" feature will be in Public Preview

Microsoft 365 Roadmap ID 417481

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

Coming soon for Microsoft SharePoint Advanced Management (SAM): A new App insights feature will be available in the Microsoft SharePoint admin center for Public Preview. You can continue to manage this feature with Microsoft PowerShell cmdlets if desired.

When this will happen:

Public Preview: We will begin rolling out mid-January 2025 and expect to complete by late January 2025.

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

How this will affect your organization:

After this rollout, if you are part of SAM, you will be able to get insights in the SharePoint admin center for applications accessing SharePoint content.

This feature will be available by default to SAM licenses.

What you need to do to prepare:

Learn more: Generate App insights reports - SharePoint in Microsoft 365 | Microsoft Learn

MC922630 — (Updated) Microsoft OneDrive: We will remove the "EnableHoldTheFile" group policy

Microsoft 365 Roadmap ID 429875

Updated April 3, 2025: We have updated the rollout timeline below. We are now one month away from this change taking effect.

We will remove the EnableHoldTheFile group policy for Microsoft OneDrive from the Microsoft 365 admin center.

When this will happen:

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

How this will affect your organization:

Before this rollout, if a tenant has disabled EnableHoldTheFile and users experience file conflicts, Microsoft OneDrive automatically creates a copy of the file in conflict. When tenants disable EnableHoldTheFile, users may have to manage hundreds of conflicts because OneDrive automatically copies a file instead of allowing users to choose to merge conflicts.

After this rollout, the EnableHoldTheFile group policy will be removed and the experience associated with the EnableHoldTheFile group policy will be enabled for all tenants. If a user opens a Microsoft Word, Excel, and PowerPoint file and there is a conflict that requires user input to resolve, the user will be given the option to choose the file variation to keep. If the conflict cannot be resolved, a banner will display to either Save a Copy of the file or Discard Changes if the user doesn't care about the changes that were made.

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, especially if the policy was disabled, and update any relevant documentation.

Learn more: IT Admins - Use OneDrive policies to control sync settings - SharePoint in Microsoft 365 | Microsoft Learn (direct link to the section called Allow users to choose how to handle Office file sync conflicts)

MC921916 — (Updated) Microsoft OneDrive: The Enable OCSI for Tenants group policy is being removed

Microsoft 365 Roadmap ID 429874

Updated April 3, 2025: We have updated the rollout timeline below. We are now one month away from this change taking effect.

We're removing the EnableAllOcsiClients OneDrive group policy in the Microsoft 365 admin center. OCSI is the coordination between office and OneDrive for syncing office documents to the cloud.

How this will affect your organization:

After this rollout, the EnableAllOcsiClients group policy will be removed, and Microsoft Office and Microsoft OneDrive will be able to communicate smoothly to ensure existing Office features like autosave, version history, real time user collaboration, and merging in the case of conflicts can work properly for end users.

Before this rollout, tenants had the option to disable this feature with a GPO, and when they disable the GPO, existing Office features like autosave, version history, real time user collaboration, and merging in the case of conflicts cannot work properly.

When this will happen:

General Availability (Worldwide, GCC, GCC High, DoD): We will be rolling out in early May 2025 (previously April).

How this will affect your organization:

With OCSI enabled for all tenants, end users will be able to take advantage of features such as autosave, real time user collab, and merging in the case of conflicts of Office files. Autosave is a feature that end users will see in Word, Excel, and PowerPoint files; it is a toggle at the top left of the file header that will ensure that even if the user does not manually save a file, the file will be saved automatically to OneDrive and SharePoint. With real time user collaboration, different users can collaborate on the same file at the same time. Version history allows users to see when and who made changes to a file and provides the ability to restore to a previous version of the file within the Office app. If there are conflicts within a file that does not require user input, Office will merge the conflicts and ensure that the Office file is up to date with the latest changes. If user input is required to merge conflicts, Office will show the merge conflicts and prompt the user to choose which edits to prioritize.

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, especially if the policy is disabled, educate them about autosave, real time user collab, and merging in the case of M365 application conflicts, and update any relevant documentation.

For more information, see Allow users to choose how to handle Office file sync conflicts.

MC912181 — (Updated) Microsoft SharePoint: Add approvals to any document library

Microsoft 365 Roadmap ID 420336

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

As an extension to the previous communication MC757613 (Updated) Microsoft SharePoint: Add approvals to any SharePoint list (originally sent March 2024, updated August 2024), we will soon add approvals to document libraries in Microsoft SharePoint Online.

When this will happen:

Targeted Release: We will begin rolling out late January 2025 (previously early January) and expect to complete by early March 2025 (previously late January).

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

How this will affect your organization:

Before this rollout: Users are not able to add approvals to document libraries in SharePoint Online.

After this rollout, users will be able to configure approvals by going to the Automate dropdown menu from the command bar in SharePoint Online document libraries and then selecting the Configure Approvals option to enable and disable approvals on the library. Note: When editing files, any in-flight approvals will be cancelled if changes are saved. To discourage edits of in-progress approvals, files will open in view-only mode in Microsoft Word, Excel, and PowerPoint for the web, and the same Windows desktop applications will show that the document is Marked as final.

After approvals are enabled, a user can create a file and submit it for approval. By creating an approval request and specifying the approver, the request will appear in the Approvals app in Microsoft Teams or can be approved directly in the library in SharePoint. Once approved, the file metadata is updated.

Note: Disabling approvals will only hide the relevant columns. In-progress approvals will still be actionable in Teams. At any time, you can manually add approvals columns back into your views.

Configure approvals in SharePoint Online:

Enable configured approvals:

Approvals column:

Disable configured approvals:

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.

Inform your users of the new Approvals functionality for libraries and lists. Share the support documentation Approvals in lists, which will be updated before this rollout begins to include library support.

Microsoft Viva

MC1056267 — Microsoft Viva Connections: New Folder card in Dashboard

Microsoft 365 Roadmap ID 408536

Coming soon for Microsoft Viva Connections: A new Folder card in the Connections card gallery will provide users with a quick view of the document library files on the dashboard.

When this will happen:

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

How this will affect your organization:

After this rollout, users will find a new Folder card that provides a quick view of the document library files on the dashboard:

This feature will be available by default.

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.

Learn more: Available dashboard cards in Viva Connections | Microsoft Learn (will updated before rollout)

Microsoft Teams

MC1062452 — Microsoft Teams: Join as attendees in Microsoft events from Teams Rooms on Windows

Microsoft 365 Roadmap ID 484125

Microsoft Teams Rooms on Windows can now join Microsoft events (webinars, town halls, structured meetings) as attendees. You can attend directly from the invited Teams Room with the same features that attendees have for all events. This is available only in Teams Rooms Pro.

When this will happen:

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

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

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

General Availability (DoD): We plan begin rolling out late August 2025 and expect to complete by mid-September 2025.

How this will affect your organization:

Recently we announced official support with Teams Rooms on Windows devices as a presenter in Teams Townhall & Webinars ensuring an optimal experience for every event. Starting from app version 5.2.115.0, Teams Town halls and Webinars are exclusively available in rooms with a Teams Rooms Pro license.

Today, Teams Rooms on Windows with a Pro license can now join events as attendees, making it easier to schedule watch parties for your organization and enjoy an official supported experience. Please note that joining events from Teams Rooms with a non-Pro license will not be supported.

This feature will be enabled by default.

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.

MC1061725 — Microsoft Teams: New DVR (digital video recording) capabilities for town halls on iOS and Android

Microsoft 365 Roadmap ID 486694

Coming soon for Microsoft Teams for iOS/Android: New DVR (digital video recording) functionality for users who attend town halls.

This feature is available for town hall instances from all organizers, regardless of the license assigned to the organizer.

When this will happen:

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

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

How this will affect your organization:

This new feature will allow town hall attendees to interact with a live streaming town hall in the same way as they would interact with recorded content when viewing on desktop or web. DVR functionality in the town hall enables event attendees to pause and move forward or back in a town hall, navigate to any previously streamed timestamp, and other abilities that make it more convenient and easier for users to interact with a town hall and digest the content being presented.

To get started, attendees will touch the screen over the content being presented in the town hall and the DVR controls will appear. In this image, the live town hall is on the left, and the DVR view is on the right:

The user can pause, play, skip 10 seconds forward or backward. The user can also control the volume of the content using volume control. The user can also jump to any point of time in the past from the start of an event. The user can catch up with the content and join the live event by selecting the Watch live button. The town hall window will remain open for 24 hours after the end of the event.

We are committed to continuously improving the Microsoft Teams experience and are excited to bring this new capability to our customers.

This feature will be available by default.

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

Learn more: Plan for Teams town halls - Microsoft Teams | Microsoft Learn (will be updated before rollout)

MC1059676 — Microsoft Teams: Easily call in a presenter from the roster for town halls and webinars

Microsoft 365 Roadmap ID 485812

This feature provides the ability for organizers and presenters to quickly add a missing presenter to an ongoing Teams town hall, webinar, or structured meeting even if the missing presenter was not originally included in the event scheduling form. If the organizer or presenter realizes they've forgotten to add someone as a presenter, they can easily call them in directly from the participant roster. From the roster, organizers can choose whether to call them in as a presenter or attendee even if they are not already attending the session as an attendee. Organizers and presenters can only promote someone as a presenter if they are already in the session. With just a few clicks, the missing presenter is instantly promoted to presenter status, allowing them to join the green room, share content, control the presentation, or interact with the meeting participants.

When this will happen:

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

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

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

How this will affect your organization:

This feature will automatically be available to use once it releases.

To use this new feature, organizers and presenters must go to the roster and call in someone into the event.

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.

MC1059675 — Microsoft Teams: Pop out live captions and Real-Time Text (RTT) in Teams meetings

Microsoft 365 Roadmap ID 484113

We’re introducing the ability to pop out live captions (including live translated captions) and Real-Time Text (RTT) in Microsoft Teams meetings and calls. This new functionality gives users more flexibility and control over how they view text-based communication during meetings, supporting both accessibility and multitasking needs.

When this will happen:

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

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

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

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

How this will affect your organization:

After the rollout, users will see a pop-out icon on the live captions and RTT interface during meetings and calls. This feature will be on by default. When popped out, captions and RTT will open in separate windows that users can drag, resize, and position anywhere on their screen. This allows users to customize their meeting layout and view captions or RTT in a way that works best for their workflow or accessibility needs.

Live caption pop-out

RTT pop-out

What you need to do to prepare:

This rollout will happen automatically by the specified date with no admin action required. Please notify your users about this change and update any relevant training materials or documentation to reflect the new pop-out experience for captions and RTT.

MC1059674 — Microsoft Teams: Real-Time Text (RTT) in Teams meetings and calls

Microsoft 365 Roadmap ID 484119

We’re introducing Real-Time Text (RTT) support in Microsoft Teams meetings and calls, available on both desktop and mobile platforms. RTT is an accessible communication method that transmits text character by character as it is typed, enabling more immediate and responsive text-based conversations. This enhancement supports inclusivity by providing an alternative communication channel for users who are deaf or hard of hearing, neurodiverse, or have speech-related disabilities.

When this will happen:

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

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

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

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

How this will affect your organization:

Once this feature is enabled by your organization, users will be able to turn on Real-Time Text (RTT) during Teams meetings and calls. To access it, go to the meeting toolbar, select More > Speech and language > Enable RTT.

When RTT is turned on, it will be enabled for everyone in the meeting. As you type, your message will instantly appear on the screen - letter by letter - so others can read it in real time. This creates a faster and more natural way to communicate through text, especially compared to standard chat.

RTT is designed to improve accessibility and also supports users who prefer typing instead of speaking. It can be used together with other features like captions or chat to create a more inclusive and flexible meeting experience.

Note: Once RTT is turned on in a meeting, it stays on for the rest of the meeting and cannot be turned off unless everyone leaves and rejoins.

What you need to do to prepare:

This rollout will happen automatically, and no admin action is required. The RTT policy is enabled by default at the tenant level.

We recommend informing your users about this new feature, especially those who may benefit from enhanced accessibility options. You may also want to update any internal documentation or training materials to include guidance on how to use RTT in Teams meetings and calls.

MC1059673 — Microsoft Teams: Expanded and enhanced peripheral auto-association support for Bring Your Own Device (BYOD) spaces

Microsoft 365 Roadmap ID 486693

Updated April 23, 2025: We have updated the timeline below. Thank you for your patience.

Additional room and desk peripherals, including docking stations and webcams, are supported in BYOD spaces (including bookable desks), enabling users to seamlessly connect and utilize audio and video peripherals for a better experience. If the space is licensed, admins get an expanded view and insightful reports for peripherals associated with Bring Your Own Device (BYOD) spaces in the Pro Management portal.

When this will happen:

Targeted Release: We will begin rolling out early June 2025 and expect to complete in mid-June 2025.

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

How this will affect your organization:

Docking stations and webcams will now begin to appear in the Pro Management portal inventory device page, crowdsourced from the Teams desktop app. These peripherals can then be manually or automatically associated to BYOD rooms or bookable desks to automate and improve BYOD/Desk UX and provide admin insights into room UX quality.

BYOD auto association will begin to receive signals and auto-associate these new peripherals to BYOD rooms. This process automatically builds a full view of your inventory for you, including what peripherals are currently located in which BYOD rooms.

As a result, BYOD and Bookable Desks end user experiences will automatically activate for any user who plugs in a peripheral associated to a BYOD room or desk. These user experiences are designed to adapt the Teams desktop client to solve common user issues in rooms and desks, and includes but is not limited to the following features:

(Rooms) Auto-select Room AV peripherals so that users don't accidentally use their laptop speaker and mic in a meeting room.
(Rooms) Shared display modeto protect confidential information and present clean output without meeting controls or presenter's notes to the room display.
(Rooms) Speaker Attribution so transcript (and Microsoft 365 Copilot) know who is speaking in your meeting.
(Rooms) Disable voice isolation so others in the room can be heard.
(Rooms) Room Node in participant roster.
(Desks) Auto-booka desk upon peripheral plug in.

What you need to do to prepare:

Inform your users about the experiences that will be automatically activated for them when they plug in to a peripheral that has been associated to a room or a desk. These changes are to make their meeting room and desk experiences better.

If you do not want end user experiences to automatically activate for a user, please refer to the admin documentation for BYOD rooms or desks. If you do not want peripherals to auto associate to rooms, automatically building your inventory for you, please disable this in settings for the Pro management portal.

MC1059667 — Action required: Classic Microsoft Teams end of availability starts July 1, 2025

Starting July 1, 2025, classic Microsoft Teams on Mac and Windows desktops will be unavailable to use as mentioned in End of availability for classic Teams client - Microsoft Teams | Microsoft Learn. To avoid any business continuity issues, you must upgrade to new Teams or use Teams on the web at https://teams.microsoft.com.

How this will affect your organization:

Starting July 1, 2025, classic Teams users will be blocked from using classic Teams. Users will not be able to dismiss the blocking message or use the classic Teams desktop app.

What you need to do to prepare:

Use this scriptto find Windows devices that need to be upgraded to new Teams. While the main purpose of the script is to identify issues before installation of new Teams, it can also be used to detect devices running unsupported OS for new Teams Installation.
Upgrade users as soon as possible to the new Teams app. Learn more about switching to new Teams. Prerequisites for new Teams installation: Windowsand Mac.

Published MC posts for reference

MC783985 / Classic Teams Timelines for end of support and end of availability,published April 2024
MC791446 / Classic Microsoft Teams timelines for end of support and end of availability (GCC and GCC High),published May 2024
MC791445 / Classic Microsoft Teams timelines for end of support and end of availability (DoD),published May 2024

Thank you for being a valued Teams customer.

Learn more

MC1057717 — Microsoft Teams Phones: Users can assign shared lines, call queues, and call transfer key to line keys

Microsoft 365 Roadmap ID 486829

Coming soon for Microsoft Teams Phone devices: We are excited to announce the upcoming availability of shared line, collaborative delegation, call queues and call transfers on line keys on Teams certified phone devices.

Line keys on phone devices address the pain point of navigating through multiple menus to manager calls, offering enhanced call management where users can manage multiple calls effectively, increased productivity and improved user experience.

For shared line and collaborative delegation, this feature will enable you to assign shared lines/collaborative delegation lines to a line key and view the boss/delegates and members of the group (in case of collaborative delegation) along with their presence on Teams Phone devices. This feature allows delegates to pick up calls on behalf of the boss or members of the group (in case of collaborative delegation) by pressing the line key and join active calls. Also, users will be able to assign the transfer action to the line key, enabling them to transfer active calls to specific contacts by pressing that line key. Lastly, after assigning call queues to the line key users can view the status of call queue whether busy or available and receive calls by pressing line key.

When this will happen:

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

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

How this will affect your organization:

This change will be on by default.

Left: Shared line assignment on line keys. Right: Transfer assignment on line keys:

What you need to do to prepare:

To access the new features, ensure that your Teams phone devices are updated with the latest application. These features will only be available with the latest application update.

Learn more: Set up line keys on your Microsoft Teams phone - Microsoft Support

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

MC1057714 — Microsoft Teams: We will retire SMS invitations from Teams to external partners

Effective May 17, 2025, we will retire the option for users to invite external partners to Microsoft Teams by sending an SMS to their phone number to join Teams and continue the conversation. We are retiring this feature to provide a more consistent experience. Organizations can continue to use emails to invite partners outside of their organizations for external teamwork.

Alternatively, customers can sign up for a two-way SMS calling plan to continue inviting external partners to Teams by sending an SMS to their phone number.

This change will happen automatically by the specified date. No admin action is required. Please notify your users about this change, update relevant documentation as appropriate, and share alternatives for users to invite external partners to Teams.

Learn more

Add or invite people outside your org to a chat in Microsoft Teams - Microsoft Support(will be updated before feature retires)
About two-way SMS: Planning for SMS in Microsoft Teams - Microsoft Teams | Microsoft Learn

MC1056977 — Microsoft Teams: Streamlined unified Role-Based Access Controls (RBAC) for Teams device management

Microsoft 365 Roadmap ID 485760

We are releasing Role-Based Access Control (RBAC) enhancements in the Teams Rooms Pro management portal (PMP). As part of our ongoing efforts to improve device management across portals, we will be extending PMP's RBAC to support additional Entra built-in roles currently available in the Teams admin center (TAC). This transition aims to provide a seamless experience for admins managing Teams Rooms devices.

When this will happen:

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

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

How this will affect your organization:

With these enhancements, PMP will now support these four Entra built-in roles:

Global Administrator: Read and write access to everything in PMP. Note that the Global Administrator role will no longer be automatically assigned to the Teams Rooms Pro Manager role in PMP.
Global Reader: Read-only access with some restrictions in the settings section, such as General, ServiceNow, Signals, and Plan Management.
Teams Administrator: Read and write access in PMP, honoring Entra permissions. However, the write access to certain entities like mailbox settings may be restricted. Teams admins assigned to an Administrative Unit (AU) will need to be assigned to a PMP custom role to access PMP.
Teams Device Administrator: Read and write access in PMP except for Roles and Partner Management functionalities. Similar to Teams Administrators, any Teams Device Administrator assigned to an AU will need to be assigned to a PMP custom role to access PMP.

What you need to do to prepare:

This rollout will happen automatically with no admin action required.

MC1056268 — (Updated) Microsoft Teams Premium: Ultra-low latency (ULL) attendee experience for town halls

Microsoft 365 Roadmap ID 486535

Updated April 22, 2025: We have updated the timeline below. Thank you for your patience.

Before this rollout, Microsoft Teams town hall attendees typically watch the presentation with a 20-30 second delay. After this rollout, with ultra-low latency (ULL), attendees will be able to view and participate in a town hall at a much lower latency than before, ensuring they are in sync with content being shared by presenters and organizers.

This feature is available for town hall organizers with a Teams Premium license. This feature will only be available for tenants who use the Microsoft eCDN (Enterprise Content Delivery Network) or who do not have an eCDN provider.

This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS and Android.

When this will happen:

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

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

General Availability (GCC): We will begin rolling out late June 2025 and expect to complete by early July 2025.

How this will affect your organization:

This change will be on by default for attendees in town halls scheduled by Teams Premium organizers.

What you need to do to prepare:

This rollout will happen automatically by the specified dates with no admin action required before or after 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.

MC1052166 — (Updated) Microsoft Teams: Slide Control for PowerPoint presenters

Microsoft 365 Roadmap ID 484844

Updated April 24, 2025: We have updated the timeline below. Thank you for your patience.

A new Slide Control feature allows presenters in both meetings and events to share control of their Microsoft PowerPoint presentations. Users with control will be able to move the slides forward and backward for all users in the meeting, making it easy for each speaker to directly control their content.

When this will happen:

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

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

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

General Availability (GCC High): We will begin rolling out mid-July 2025 and expect to complete by late July 2025.

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

How this will affect your organization:

On release, Slide Control will be enabled for all internal users in the tenant and disabled for all external users.

What you need to do to prepare:

Before release, decide what feature scope you'd like to apply within your tenant, meaning which type of users are allowed to use the new Slide Control feature.

Note: Slide Control only allows for presenters to share control of their slides with the users they choose; users cannot request control themselves.

MC1052163 — Microsoft Teams: Teams button support on multiple connected peripheral devices

Microsoft 365 Roadmap ID 485714

You can now use the Teams button across personal peripheral devices without having to manually select a specific device in the Teams devices settings. This provides a more seamless experience navigating across multiple certified for Microsoft Teams personal peripheral USB devices (with a wire or a dongle) connected to the same host device (such as your laptop). For example, you can use the Teams button on headset A to bring up the meeting pre-join screen, then use the Teams button on headset B to join the meeting, and then use the Teams button on your connected speakerphone to raise hand in the meeting, and so on.

When this will happen:

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

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

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

How this will affect your organization:

The Teams button will work on all peripheral devices that are wired or with a dongle and connected to the same laptop without needing to manually switch between selected devices in the Teams devices settings.

What you need to do to prepare:

This rollout will happen automatically with no admin action required. The Teams button will work on all peripheral devices that are wired or with a dongle and connected to the same laptop without needing to manually switch between selected devices in the Teams devices settings. You may want to notify your users about this change and update any relevant documentation as appropriate.

MC1052162 — Microsoft Teams: Now available - new policy setting for Speaker Attribution in BYOD scenarios - Enabled ON by default

Microsoft 365 Roadmap ID 488301

Updated April 29, 2025: We have updated the title, timeline, and content. Thank you for your patience.

Available now: The new SpeakerAttributionBYOD setting is now available in csTeamsAIPolicy for Microsoft Teams Premium users. This gives IT admins more control over speaker attribution when users join meetings from personal (BYOD) devices. Admins can now configure this setting using PowerShell. If no action is taken, it will be enabled by default starting in early June 2025.

NOTE: If you are a Microsoft Teams customer (not a Microsoft Teams Premium customer), we are sending this message to you because this new setting will take effect automatically for any user assigned a Microsoft Teams Premium or Microsoft 365 Copilot license—even if your organization previously didn’t have these licenses. Therefore, we recommend all organizations review this message, regardless of your organization’s current license status.

This setting allows organizations to manage how speaker attribution is used in meetings where users join via personal devices, helping enhance the in-meeting and post-meeting experience with features like speaker labels (Speaker 1, Speaker 2, etc.) and Microsoft 365 Copilot in shared spaces. To access Copilot features, a Microsoft 365 Copilot license is required.

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

When this will happen:

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

How this will affect your organization:

Previously, speaker attribution was managed using the RoomAttributeUserOverrideparameter in CsTeamsMeetingPolicy. Going forward, SpeakerAttributionBYOD in csTeamsAIPolicy will determine whether attribution is used when users join from BYOD scenarios.

What you need to do to prepare:

The new setting is available now, and admins can begin configuring it using PowerShell based on their organization's preferences.

If no action is taken, the setting will be enabled by default during the rollout in June 2025.

If you prefer to modify the setting before the rollout begins, you can do so at any time starting now.

Learn more

MC1047923 — Update: Ensuring Security and Compliance - Keep you Microsoft Teams desktop clients up to date

Versions of the new Teams client that were released more than 90 days ago will be blocked. An in-app warning banner will show up 60 days before the app is blocked (30 days for VDI).

When will this happen:

Users will see blocking page

o Starting April 11th, 2025, for users using the Windows desktop app

o Starting May 6th, 2025, for users using the Teams app in VDI environment

o Starting May 15th, 2025, for users using the Mac desktop app

Users will see warning banner starting 60 days before they are blocked (for VDI environments only, users will see it 30 days before they are blocked)

How this will affect your organization:

Versions of the new Teams client that were released more than 90 days ago will be blocked. Users that are using these versions will be blocked from using the app. Users should either update to the latest version of the Teams app by downloading the latest version from the download page or use the Teams app on the web.

What you can do to prepare:

Update to the latest version of Teams.
Admins should make sure Teams is automatically updating to stay current and within the compatibility window. Common configurations to validate include:

o Teams app on macOS has Microsoft AutoUpdate (MAU) configured properly. Learn More

o Customer network settings, and any device management software e.g. antivirus, are configured properly to allow automatic updates.

o Windows Policies must not block new Teams or the Webview2 updater.

o Please visit Why it's important to keep Teams updated to learn more.

References:

MC931401, MC1034566 and MC1038442 for more details, including screenshots of the respective warning banner and blocking page in persistent and non-persistent environments.

MC1047244 — (Updated) Microsoft Teams: New town hall event access policy

Microsoft 365 Roadmap ID 483250

Updated April 30, 2025: We have updated the timeline below. Thank you for your patience.

Before this rollout, Microsoft Teams has one admin policy to control event access for webinars and town halls. After this rollout, admins can control who can attend town halls in their organization with the new policy setting TownhallEventAccessType.

This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android.

When this will happen:

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

How this will affect your organization:

After this rollout, admins can control the event access for town hall created by their users with the new policy setting TownhallEventAccessType in the Teams admin center and Microsoft PowerShell. The policy has two new attributes: Everyone and Everyone in Organization including Guests:

If Everyoneis selected, town halls will not be restricted to a certain identity type; however, your organizers can still choose to restrict their town hall as they wish. This is the default setting.
If Everyone in Organization including Guests is selected, town halls in your organization will only allow users in your organization and guest users to your tenant to attend. Town hall organizers may choose to further restrict their town halls but cannot invite users who are not part of their organization or who are not guests to attend.

If you have feedback on these attributes or have suggestions for new attributes, please send an email to EventAccessFeedback@microsoft.com

What you need to do to prepare:

By default, TownhallEventAccessType will be set to Everyone. If you would like to change the default setting before the rollout begins, you can use this Microsoft PowerShell code:

Set-CsTeamsEventsPolicy -Identity Global -TownhallEventAccessType EveryoneInOrganizationAndGuests

Learn more: Manage who can schedule and attend town halls in Microsoft Teams - Microsoft Teams | Microsoft Learn (will be updated before rollout)

MC1045226 — (Updated) Microsoft Teams: Speaker recognition and attribution in Teams Rooms on Android

Microsoft 365 Roadmap ID 480715

Updated April 8, 2025: We have updated the timeline below. Thank you for your patience.

You can now use speaker recognition, transcript attribution, and AI capabilities in Teams Rooms on Android. Intelligent speaker functionalities are brought to existing speakers via the cloud. This feature identifies and attributes people in live transcripts, utilizing a unique voice profile for each participant enabling intelligent recaps and maximum value from Microsoft 365 Copilot and Teams Premium in meetings. Users can easily and securely enroll voices via Teams Settings. This feature requires a Teams Rooms Pro license.

Users can enroll voices in the Teams Desktop. Learn more: Set up your digital voice profile

When this will happen:

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

How this will affect your organization:

With speaker recognition, Teams Rooms on Android can identify speakers during live transcription in shared meeting rooms, ensuring clear and precise voice capture for every participant. This allows you to track who said what during the meeting through intelligent meeting recap and Copilot.

What you need to do to prepare:

While this functionality is still off by default, if you have already turned it on, be aware that it will enable this feature even for hardware that did not previously support it.

To use this new capability, you need to first setup the right policies through PowerShell.

For additional information about how to set the right policies, see Manage voice recognition technology controls for an Intelligent Speaker.Participants can set up a voice profile in minutes using the Teams Desktop application. Each person gets a unique voice signature, stored securely in your organization's tenant in the Microsoft Cloud to ensure that every contribution is accurately captured in every meeting, helping you to have a more productive meeting experience.

For information about how to enable face and voice enrollment for your organization, see Overview of voice and face enrollment.

MC1045221 — Microsoft Teams: New user setting to view incoming calls in a small window

Microsoft 365 Roadmap ID 482747

Coming soon for Microsoft Teams: A new setting that allows users to view incoming calls in a small window in Teams to prevent disruptions. Users will be able to take a call in the small window and continue to see what they were working on before the call.

This message applies to Teams on Windows desktop, Teams on Mac desktop, Teams for the web, and Teams for iOS/Android.

When this will happen:

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

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

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

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

How this will affect your organization:

Before this rollout: Teams users are disrupted by the larger Teams screen when viewing an incoming call.

After this rollout: Teams users can turn on this setting to view calls in a small window. Note that both large and small windows are resizable:

This feature will be on by default.

What you need to do to prepare:

MC1045219 — (Updated) Microsoft Teams: Room Recommender

Microsoft 365 Roadmap ID 482191

Updated April 28, 2025: We have updated the timeline below. Thank you for your patience.

With this rollout, if no room is booked for the meeting, an AI-generated room suggestion will be sent in the meeting chat an hour before the meeting start time when two or more attendees are co-located in the same building, making in-person collaboration easier. The room suggestion will consider location of participants, room availability, and capacity to find the best space. You can reserve the suggested room with just one click and update the invite for everyone. The organizer must have a Teams premium license for this experience to occur, which is on Teams mobile on iOS.

When this will happen:

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

How this will affect your organization:

This will be a default on feature.

For a room suggestion to be generated, a meeting must have:

Between two to seven attendees with at least two attendees that are co-located
Teams meeting link
Organizer has Teams premium
No room is already booked for the meeting
No external attendees
Not an all-day event

Room suggestions will be generated in buildings where at least two attendees, who haven’t declined the meeting, share the same work location. For instance, if a meeting has four attendees, with two in Building X and two in Building Y, suggestions for both buildings will be sent. Distribution lists are not considered.

If a meeting is moved, canceled, or the suggested room becomes unavailable, the card will update dynamically upon clicking ‘Reserve’.

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 also want to notify your team about this change and update any relevant documentation. We recommend making sure that your rooms are properly added to Places directory with a building associated.

MC1045217 — Microsoft Teams Phone: Copilot-generated summaries for call transfers on Android devices

Microsoft 365 Roadmap ID 475855

Coming soon for Microsoft Teams Phone on Android devices: Copilot-generated summaries for call transfer. This feature is designed to streamline call transfers by providing agents receiving transferred calls with a Copilot summary of the call. This summary includes key details such as caller information, call reason, prior actions, and next steps. It supports Consult and Blind transfers to help ensure effective communication and improve efficiency.

A Microsoft 365 Copilot license is required to use this feature. Learn more: License options for Microsoft 365 Copilot | Microsoft Learn

When is this rolling out:

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

How this will affect your organization:

Copilot-generated summaries for call transfer are visible to the person to whom the call is being transferred:

These new features will be available by default.

What do I need to prepare:

Please ensure that your Teams phone devices are updated with the latest application to get access to the new features described in this message. These features will be available only with the latest application update.

Prerequisite to use these new features: Admins must enable Transcription in Calling policies for both transferor and transferee.

MC1045214 — (Updated) Microsoft Teams: New Chat and Channels experience (GCC)

Microsoft 365 Roadmap ID 485705

Updated April 30, 2025: We have updated the timeline below. Thank you for your patience.

The new, streamlined chat and channels experience makes it easier to stay on top of what matters most and organize your digital workspace. Catch up on chat, channels and teams in one place, create custom sections to organize conversations by topics, use filters to triage messages and more. For more details and screenshots, refer to Microsoft Teams announces out a new chat and channels experience | Microsoft 365 Blog

This message applies to Teams on Windows desktops, Teams on Mac desktops, Teams on the web, and Teams on iOS and Android devices.

This message excludes Education tenants. We will send a future post with an update on the plan for Education tenants.

When this will happen:

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

How this will affect your organization:

The new experience brings chat, teams, and channels into one place, in Chat, so users can easily navigate between all conversations without switching between contexts. Users start in the combined Chat view but can opt to keep chat separate from teams and channels like before.

In the Chat view, users will see these sections (in order):

Favorites containing any previously pinned chats and channels
Chats sorted by most recent
Teams and channels, organized in same order as in the Teams view

Also, users can create custom sections to organize projects and topics that can include individual, group, and meeting chats, as well as channels.

Favorites, Chats, and Teams and channels in one list in Teams for Windows:

Favorites, Chats, and Teams and channels in one list in Teams for iOS (also available for Android):

New filters for Unread, Chat, Channels, Meetings and more help users focus on relevant conversation in their list. Filters persist until turned off.

The new @mention view gathers all personal @mentions into one interactive list. Users can quickly access messages with @mentions across chats, channels, and meetings.

A quick navigation bar for teams and channels is available in Teams for Windows, Mac, and Web, at the bottom of the combined Chat view. Clicking on the bar will scroll the view to the teams and channels section for quick navigation. The bar displays in bold when there are unread messages in channels, or with indicators like "@" for unread @mentions in channels.

Use /goto: Quickly navigate to your frequently used conversation across your chat and channels with a new keyboard shortcut Ctrl+G (Cmd+G on Mac).

Customizing the experience

Users can tailor their chat and channels experience in Teams Settings. Users can choose to keep chat, teams, and channels combined in Chat (default) or switch to separate Chat and Teams views. In the combined Chat view on Windows, Mac, and Web, message previews are off by default to simplify the list. Users can turn on message previews in Settings.

When using the separate Chat and Teams views, users can still use the new filters and the @mentions view to triage and organize topics with custom sections.

Starting the new experience

A self-service guided onboarding flow in Teams will help users discover the new experience and configure it to their preferences. Users who prefer to keep chat and channels separate can easily do so during the onboarding process or later, without IT assistance.

When the new experience is available in your tenant, this screen will display to users:

The Get started button will take users to the new combined chat, teams, and channels experience in Chat, and highlight the location of settings. Users will have the option to defer the new experience up to three times over the course of approximately three days, providing flexibility while also moving an organization to the new experience overall. About a week after the new experience is available for a user, they will be presented with a final Get started screen and transition to the new experience.

This feature is on by default. The new experience has no admin policy. Each user can make choices to optimize for how they work best.

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.

To help prepare organizations for the new features, product guides for admins and users are available on the adoption web page.

MC1045213 — Microsoft Teams: New Chat and channels experience (GCC High, DoD)

Microsoft 365 Roadmap ID 485706

This message applies to Teams on Windows desktops, Teams on Mac desktops, Teams on the web, and Teams on iOS and Android devices.

This message excludes Education tenants. We will send a future post with an update on the plan for Education tenants.

When this will happen:

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

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

How this will affect your organization:

In the Chat view, users will see these sections (in order):

Favorites containing any previously pinned chats and channels
Chats sorted by most recent
Teams and channels, organized in same order as in the Teams view

Also, users can create custom sections to organize projects and topics that can include individual, group, and meeting chats, as well as channels.

Favorites, Chats, and Teams and channels in one list in Teams for Windows:

Favorites, Chats, and Teams and channels in one list in Teams for iOS (also available for Android):

New filters for Unread, Chat, Channels, Meetings and more help users focus on relevant conversation in their list. Filters persist until turned off.

The new @mention view gathers all personal @mentions into one interactive list. Users can quickly access messages with @mentions across chats, channels, and meetings.

Use /goto: Quickly navigate to your frequently used conversation across your chat and channels with a new keyboard shortcut Ctrl+G (Cmd+G on Mac).

Customizing the experience

When using the separate Chat and Teams views, users can still use the new filters and the @mentions view to triage and organize topics with custom sections.

Starting the new experience

When the new experience is available in your tenant, this screen will display to users:

This feature is on by default. The new experience has no admin policy. Each user can make choices to optimize for how they work best.

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.

To help prepare organizations for the new features, product guides for admins and users are available on the adoption web page.

MC1043473 — Microsoft Teams Rooms on Android: New local pan-tilt-zoom (PTZ) controls

Microsoft 365 Roadmap ID 482189

Microsoft Teams Rooms on Android will soon support local pan-tilt-zoom (PTZ) controls.

When this will happen:

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

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

How this will affect your organization:

After this rollout, the local PTZ controls in the camera settings will pop up for users when the Enhanced framing toggle is set to off.

Admins will have the ability to turn this feature on or off in the admin settings for each Teams Rooms on Android device. This setting will be on by default.

What you need to do to prepare:

MC1043466 — Microsoft Teams: Admins can deploy Custom Together Mode scenes (GCC, GCC High, DoD)

Coming soon for Microsoft Teams: We're delighted to introduce the ability for admins to deploy Custom Together Mode scenes. You may create a scene from developer portal and deploy it in your organization. Learn more: Custom Together Mode Scenes - Teams | Microsoft Learn

A Microsoft Teams Premium license is required to use this feature. Only Teams Premium licensed users will be able to see and apply the scenes that you've deployed.

This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web.

When this will happen:

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

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

This feature will be on by default.

What you need to do to prepare:

MC1043271 — Microsoft Teams in VDI: User uploaded custom background images for the new VDI solution

Microsoft 365 Roadmap ID 410366

With this new feature, users on the new VDI solution for Teams (SlimCore based) can now replace their background entirely with any image they want by uploading it through the "Video effects and Settings" option.

This is currently supported for Azure Virtual Desktops, Windows 365 and Citrix, when connecting from a Windows endpoint.

When this will happen:

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

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

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

How this will affect your organization:

Users need to upload the background via Teams button 'Add New' (although the file can reside on the user's device, and Teams would then rely on Client Drive Mapping / Drive Redirection in that case).

The file is subsequently uploaded to the user's OneDrive folder, fetched by SlimCore on the endpoint, and stored in the user's profile on the endpoint (e.g. for Azure Virtual Desktops or Windows 365: AppData\Local\Microsoft\TeamsVDI\avd-tfw-<guid>\downloads)

What you need to do to prepare:

Make sure you are using the new VDI solution based on SlimCore, see here for more details.

MC1041960 — Microsoft Teams: Standard and Basic licensed Teams rooms on Windows in the Teams admin center portal

Microsoft 365 Roadmap ID 482539

We will be transitioning all Teams Rooms on Windows devices, irrespective of their licenses, to the Teams Rooms Pro management portal to meet users' needs for a one-stop destination to configure, monitor, and manage Teams rooms devices. This change delivers a unified device management and admin portal experience.

Users currently using the Teams admin center (TAC) will have device management functionalities within the Teams Rooms Pro Management portal. Teams Rooms on Windows devices will not be available in Teams admin center after June 1, 2025.

When this will happen:

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

How this will affect your organization:

All Teams Rooms on Windows devices with Standard or Basic licenses will be visible in the Teams Rooms Pro management portal at https://portal.rooms.microsoft.com. Organizations that have never used the Teams Rooms Pro management portal will need to add additional URLs found in Enroll a Teams Room in the Pro management portal. Those with Teams or Teams Device administrator roles will be able to access the Teams Rooms Pro management portal and see their devices after May 1, 2025. Users with Basic and Standard Teams Rooms licenses will have device management functionalities within the Teams Rooms Pro Management portal. They will not, however, have access to the full suite of device management and space analytics features available with a Teams Rooms Pro license.

What you need to do to prepare:

For those that have used only Teams admin center and are unfamiliar with the capabilities of Teams Rooms Pro Management, we encourage you to view the short videos on Teams Rooms Pro Management - YouTube and product documentation Microsoft Teams Rooms Pro management.

MC1041461 — Microsoft Teams Premium or Microsoft 365 Copilot: New translated recap after multilingual meetings

Microsoft 365 Roadmap ID 481144

Microsoft Teams will soon add features that make it easier for Teams Premium and Copilot users to communicate in meetings where attendees speak different languages. After this rollout, each participant can choose their spoken language and a translation language, for more inclusive and productive conversations. Users will also receive an automatically translated intelligent meeting recap in the translation language they selected for live transcription and captions. For admins, these features help to ensure a more inclusive collaboration experience for multilingual teams, without requiring extra setup.

A Microsoft 365 Copilot license or a Teams Premium license are required to use this feature.

This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android.

When this will happen:

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

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

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

How this will affect your organization:

After this rollout, users will be able to:

Speak in their language: Choose from nine supported languages: Chinese (Mandarin), English, French, German, Italian, Japanese, Korean, Portuguese (Brazil), and Spanish.
Read in their preferred language: The meeting transcript will reflect conversations in each user's chosen translation language.
Get an automatic recap: After the meeting, Teams will generate an intelligent meeting recap in each user's selected translation language so they can review key discussions with ease.
Switch languages anytime: Even after the recap is generated, users can still change the translation language from the drop-down menu on the recap page.

This feature will be on by default.

What you need to do to prepare:

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

MC1041460 — Microsoft Teams Premium or Microsoft 365 Copilot: Meeting transcription supports multiple spoken languages

Microsoft 365 Roadmap ID 473434

Coming soon for Microsoft Teams Premium and Microsoft 365 Copilot users: We’re introducing new controls for organizers and users set their own spoken language during multilingual meetings, allowing each participant to communicate in their preferred language. Before this rollout, Teams meetings require a common spoken language to generate a transcript. After this rollout, Teams can generate a meeting transcript in each participant’s language of choice. For admins, these features help to ensure a more inclusive collaboration experience for multilingual teams, without requiring extra setup.

A Microsoft 365 Copilot license or a Teams Premium license are required to use this feature.

The user feature in this message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android.

The meeting organizer feature in this message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web.

When this will happen:

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

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

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

How this will affect your organization:

We will support nine languages for both spoken and translation options.

How it works

A meeting organizer with a Teams Premium or Copilot license can enable multilingual mode by turning on Enable speech recognitionin Meeting options before the meeting.
When the organizer turns on Enable speech recognition,meeting attendees can select their spoken language from the three-dot More menu in the meeting toolbar > Language settings
During the meeting, if the meeting organizer has not preconfigured multilingual mode, a Copilot user can enable the Interpreter agent, allowing all participants to dynamically select their spoken language.

In Meeting options, meeting organizers can turn on Enable speech recognition:

When Enable speech recognition is turned on, users can select Language settings from the three-dot More menu to set their spoken language and translation options:

This feature is available by default.

What you need to do to prepare:

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

MC1041451 — (Updated) Microsoft Teams for iOS/Android: New location sharing settings for emergency calls and more

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

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 late April (previously early April) and expect to complete by early May (previously mid-April).

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

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.

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.
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.

MC1040545 — Microsoft Teams: Enhanced spell checking will support multiple languages

Microsoft 365 Roadmap ID 470600

Coming soon for Microsoft Teams: Enhanced spell checking with multi-language support. This feature will help users communicate more effectively with fewer spelling errors.

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

When this will happen:

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

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

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

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

How this will affect your organization:

Users will choose their languages for spell checking in Teams settings. Before rollout, we will update this post with revised documentation.

Key features

Advanced spell checking: Improved accuracy to ensure messages are clear and professional.
Multi-language support: Seamlessly switch between up to three languages.
Custom dictionary: Users can add their own words for personalized spell checking.

This change will be available to users 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 any relevant documentation.

MC1038684 — (Updated) Prevent/Fix (Detected)Policy changes for Microsoft Teams devices using Device Code Flow Authentication

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

Microsoft is rolling out a new Microsoft Managed Policy to help further secure your tenants against potential threats to accounts using Device Code Flow (DCF) authentication. This messaging is particularly for tenants who have deployed Android based Teams devices in shared spaces as these accounts are not associated with real users, such as:

Microsoft Teams Rooms (Android) FoR and Console
IP Phones (Licensed as Teams Shared Devices)
Panels
Displays

This policy should be visible in the Entra ID Portal (https://entra.microsoft.com/), as shared in the screenshot below, and we recommend that the Global admins should create exclusion lists for excluding those accounts which sign in on these devices, so that Admins can continue to use the remote sign in and management capabilities.

Admins can customize the Microsoft-managed policy according to the tenants' specific needs. Example here: Exclude users

When this will happen:

The new policy is currently rolling out.

How this will affect your organization:

In the case where admins do not exclude these devices and enable the policy, then those devices which get signed out for any reason, will not be able to re-authenticate using DCF capability.

What you need to do to prepare:

If the new policy is visible to your tenant in the Entra ID Portal (https://entra.microsoft.com/), Global admins should create exclusion lists for excluding those accounts which sign in on these devices. The exclusion lists can be created based on the guidelines in this document: Exclude users

Click here to learn more:

Details of potential security threats to accounts using DCF Authentication: New Microsoft-managed policies to raise your identity security posture
Link to the policies list view in the Entra portal.

MC1036576 — Microsoft Teams: Share contact information for people in Microsoft Teams channels

Microsoft 365 Roadmap ID 375627

Users can now share the contact information in the Teams channel to make it easy for others to reach out to collaborators.

When this will happen:

General Availability (Worldwide, GCC High, GCC, DoD): This feature update is now available.

How this will affect your organization:

Users can now easily obtain contact information for users in Teams channels by simply hovering over the contact to view their details in the Profile Card.

For more information, see Share a contact in a chat or channel.

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.

MC1035710 — Microsoft Teams: Simplified Notes pane in meetings

Microsoft 365 Roadmap ID 482398

Coming soon to Microsoft Teams: We will update the Notes pane in meetings to streamline the design and clarify key features. Collaborative meeting notes can be added to scheduled meetings and are not supported for instant meetings or Teams calls.

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

When this will happen:

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

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

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

How this will affect your organization:

Here are the changes in this rollout:

We will change the name of the meeting pane from Meeting notesto Notes to match the Notes icon in the meeting toolbar:

Users will be able to access controls like Open in new windowand Copy componentfrom the three-dot menu at the top of the Notes pane. We will include the Open in Loopoption there, too. Before this rollout, users select the Pages icon to find the Open in Loop option.

This change will be enabled by default.

What you need to do to prepare:

Learn more: Take meeting notes in Microsoft Teams - Microsoft Support

MC1034566 — Microsoft Teams in VDI: Keep your Microsoft Teams desktop clients up to date

Microsoft Teams is governed by the Modern Lifecycle Policy which requires that the new Teams desktop client be kept up to date.

As communicated in MC931401 in December 2024, new Teams clients in VDI that are out of date will start experiencing warning banners in March 2025 and blocking pages starting from May 6th, 2025.

When a client falls out of date, the user will see:

Recurring in-app alerts, if the app is between 60d-90d out of date (see screenshot below).
A blocking page in Teams, if the app is greater than 90 days out of date. At this point, the app will show options to update, to contact their IT administrator, or continue to Teams on the web (depending on Persistent vs Non-Persistent VDI, see screenshot below).

Important: the clock for a specific version (e.g. version N) starts ticking only after the next version (N+1) is completely released, according to this calendar:

https://learn.microsoft.com/en-us/officeupdates/teams-app-versioning#windows-version-history

As an example:

Teams app 24295.x.x.x (a.k.a version N) was released on November 18th, 2024.

The next version (a.k.a version N+1), 24335.x.x.x, was released on January 9th, 2025.

Therefore, an in-app alert/warning banners would have been shown on March 9th (60 days after the January 9th update) and onwards.

An in-app blocking dialogue will be shown on April 9th (90 days after the January 9th update) and onwards.

Continuing with this example:

The next version after 24335 was 25007, released on February 4th, 2025.

Therefore, alerts/warning banners for 24335 will show on April 4th, 2025, and blocking dialogues on May 4th, 2025.

The Microsoft Teams desktop client usage report in Teams Admin Center, or similar queries in Call Quality Dashboard, gives you an overview of the Teams desktop clients in use within your organization.

What you need to do to prepare:

To avoid disruption to end-users, the admins with users on Teams versions older than the currently released versions, should update their users to the most recent version.

Admins should make sure Teams is automatically updating (or update the golden image on a frequent cadence) to stay current and within the compatibility window.

MC1028320 — (Updated) Microsoft Teams: Teams Rooms Pro Management portal will be generally available (GCC High)

Microsoft 365 Roadmap ID 482187

Updated March 27, 2025: We have updated the URL below to show as intended. Thank you for your feedback.

NOTE: This message applies to customers with Microsoft Teams Rooms Pro licenses. If you don't have this license, you can ignore this message.

After this rollout, admins will have access to the Teams Rooms Pro Management service and portal at https://devices.gov.teams.microsoft.us,where you can use remote device management and analytics features while maintaining high security and privacy standards.

When this will happen:

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

How this will affect your organization:

This portal will be available by default for admins to configure.

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 admins about this change and update any relevant documentation.

Learn more: Microsoft Teams Rooms Pro management - Microsoft Teams | Microsoft Learn (will be updated before rollout begins)

MC1026225 — Microsoft Teams admin center: We will retire Graph connector management

Due to low usage, we will retire the Graph connector management feature from the Microsoft Teams admin center starting April 14, 2025 and ending in late April 2025. Instead, we recommend admins transition their Microsoft Graph connector management activities to the Search & Intelligence feature in the Microsoft 365 admin center.

How this will affect your organization:

Before this retirement, for Teams apps with the graphConnector property in the manifest, the Teams admin center provides the Graph connector management control to enable or disable the connection to Microsoft Graph. When this control is turned on, the app content is integrated with Microsoft Graph and available for search in Microsoft 365. When this control is turned off, the app content is not integrated with Microsoft Graph. The rest of the app functionality is not impacted by this control.

For apps with the graphConnector property, the management control is in the Teams admin center > Manage apps > App details page > Graph connector tab and is available on per-app basis:

After this retirement, admins will not be able to turn on or off the connection to Microsoft Graph for Teams apps from the Teams admin center. We will maintain the existing state (on or off) for all apps that may have this property.

What you need to do to prepare:

This change will happen automatically by the specified date.

After this retirement is implemented, there is no impact on users. Any apps used in your environment with the graphConnector property will continue to function and will not be impacted.

After this retirement, to manage the graph connector for any Teams app, you can:

Delete the connection at Microsoft 365 admin center > Settings > Search and intelligence.Learn more: Monitor Microsoft Graph connectors for Microsoft Search | Microsoft Learn
Contact the owner or developer of the app to turn the graph connection on or delete it.
In the Microsoft Entra admin center, revoke the ExternalItem.ReadWrite.OwnedBy, ExternalConnection.ReadWrite.OwnedBy, and ExternalConnection.Read.Allpermissions for the app, to limit the app from reading or writing external items and external connections. Learn more: Review permissions granted to enterprise applications.

Learn more

MC1024383 — (Updated) Microsoft Teams: Update on changes to "csTeamsAIPolicy" (take action)

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

MC912707 (Updated) Microsoft Teams: New policy for voice and face enrollment will default to "On" (configure now), published October 2024.

We want to bring to your attention an issue that may have impacted your organization’s configuration of the new csTeamsAIPolicy in Microsoft Teams. As a reminder, this policy provides IT admins with greater control over voice and face enrollment settings, allowing you to manage these features based on your organization’s needs. If you made changes to this policy and settings before October 18, 2024, we recommend you verify those changes. We understand this may have caused confusion, and we sincerely apologize for any inconvenience this may have caused.

We have now resolved the issue, and you can proceed with updating your csTeamsAIPolicy settings as needed. The policy is available through Microsoft PowerShell, and any modifications you make will apply successfully.

When this will happen:

As communicated in MC912707, the PowerShell cmdlets are available now for preparation and to ensure a smooth transition. The policy takes effect starting in mid-March 2025 and is expected to be fully in effect by mid-April 2025 (previously late March).

How this will affect your organization:

Before this rollout, the current policy csTeamsMeetingPolicy has a single setting, EnrollUserOverride, that allows the administrator to enable or disable the enrollment of both face and voice profile of users.

After this rollout, the new csTeamsAIPolicy will replace the existing enrollment setting in csTeamsMeetingPolicy. The new csTeamsAIPolicy has two settings, EnrollFace and EnrollVoice, that will be set to Enabled by default.

What you need to do to prepare:

This rollout will happen automatically by the specified dates. 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.

Please review your current csTeamsAIPolicysettings to confirm they align with your intended configuration.
If you made changes before October 18, 2024, but they did not take effect, we recommend reapplying those settings now.
Ensure that updates to the policy are consistently applied across all assigned locations (global, user-level, or group-level) to avoid unintended configurations.
For guidance on configuring the policy, please refer to:

o Set-CsTeamsAIPolicy (MicrosoftTeamsPowerShell)

o Get-CsTeamsAIPolicy (MicrosoftTeamsPowerShell)

o Overview of voice and face enrollment - Microsoft Teams

We appreciate your patience and your partnership as we work to ensure a smooth transition. If you have any questions or need further assistance, please contact us.

MC1022539 — (Updated) We are making changes to the Resource Account license requirement

Updated March 5, 2025: We would like to clarify that the term "Resource Account" in this post specifically refers to the "Teams Phone Resource Account" used for Call Queue, Auto Attendant, and Shared Calling. This does not affect any Common Area Phone or Teams Rooms using the Microsoft Teams Shared Devices or Teams Rooms licenses, respectively. For more details, please refer to the following link: Microsoft Teams Phone Resource Account licenses - Microsoft Teams | Microsoft Learn

We are making improvements to how telephone numbers are managed for Teams Phone Resource Account and Teams Phone User Account in Microsoft Teams. These updates require us to streamline the license requirement and enforcement. Starting the second week of April 2025, we will require appropriate “Microsoft Teams Phone Resource Account license” to be assigned to all Teams Phone Resource Accounts. Any existing Teams Phone Resource Account without appropriate “Microsoft Teams Phone Resource Account license” may be converted to Teams Phone User Accounts. Similarly, any Teams Phone User Account with “Microsoft Teams Phone Resource Account license” may be converted to Teams Phone Resource Account.

When this will happen:

The update is planned to happen during the second week of April 2025.

How this will affect your organization:

If your organization has Teams Phone Resource Account without proper “Microsoft Teams Phone Resource Account license”, those accounts may be converted to Teams Phone User Accounts. Similarly, any Teams Phone User Accounts with “Microsoft Teams Phone Resource Account license” may be converted to Teams Phone Resource Account.

Starting second week of April 2025, any new phone number assignments to Teams Phone Resource Account will require an appropriate “Microsoft Teams Phone Resource Account license”.

More information on Teams Phone Resource Account licenses can be found at: Microsoft Teams Phone Resource Account licenses

What you need to do to prepare:

Please assign an appropriate “Microsoft Teams Phone Resource Account license” to all the Teams Phone Resource Account. If a Teams Phone User Account is desired, please remove any existing “Microsoft Teams Phone Resource Account license”.

MC1019312 — (Updated) Microsoft Teams: Meeting participants can request collaborative annotation sessions

Microsoft 365 Roadmap ID 89975

Updated April 23, 2025: We have updated the timeline below. Thank you for your patience.

Coming soon for Microsoft Teams: Meeting participants will be able to request an annotation session while someone else is sharing their screen.

This message applies to Teams for Windows desktop and Teams for Mac desktop. (Users can view and annotate in Teams on the web but cannot initiate annotations.)

When this will happen:

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

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

How this will affect your organization:

After the rollout, meeting participants who are not sharing their screens will have the ability to request an annotation session. This request will be sent to the presenter sharing their screen who can choose to accept or deny it.

If the request is accepted, the annotation session will start for everyone in the meeting.

Anonymous users in the meeting will not be able to send a request.

This change will be available by default.

What you need to do to prepare:

Learn more: Use annotation while sharing your screen in Microsoft Teams - Microsoft Support (we will update this before rollout)

Watch: How to use Collaborative Annotations in a Microsoft Teams meeting (2022)

MC1011152 — (Updated) Microsoft Teams: Updates to the Teams system tray icon and menu

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

We are improving the Microsoft Teams app icon and menu in the Microsoft Windows system tray (taskbar notification area) for ease of use and to reduce the number of steps to perform routine tasks.

This message applies to Teams for Windows desktop.

When this will happen:

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

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

How this will affect your organization

After this rollout, these changes will affect all users:

Updates to how your account presence is displayed. Instead of seeing My status in the system tray menu, users will now see their current presence status and can quickly change their status.
We removed the Openoption from the system tray menu. Users can launch the Teams app by selecting their account name in the system tray.

Changes that will impact users who are signed into both personal and work accounts:

Before this rollout, if a user is signed into both personal and work Teams accounts, the system tray will display two Teams icons and corresponding menus. After this rollout, users will have one Teams icon in the system tray for personal and work accounts.

What you need to do to prepare:

No action is required, as users will automatically receive these changes by default.

MC1009932 — (Updated) Microsoft Teams: Add CVI (Cloud Video Interop) coordinates to town hall and webinar invitations

Microsoft 365 Roadmap ID 476487

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

Coming soon to Microsoft Teams: Meeting organizers and schedulers will be able to add CVI (Cloud Video Interop) coordinates to Teams town hall and webinar meeting invitations. With CVI coordinates in invitations, non-Teams users—such as external customers or partners—can easily join town hall and webinar meetings using a third-party teleconferencing device. This message applies to Teams on Windows desktop, Teams on Mac desktop, and Teams on the web.

CVI is a Microsoft Qualified third-party solution that enables third-party SIP and H.323 video room devices (VTCs) to join Microsoft Teams meetings. As an admin, you can set CVI for your org. Learn more: Manage and set up Cloud Video Interop for Microsoft Teams - Microsoft Teams | Microsoft Learn

When this will happen:

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

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

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

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

How this will affect your organization:

This change 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 or after 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: Plan for Teams town halls - Microsoft Teams | Microsoft Learn (will be updated before rollout)

MC1009930 — (Updated) Microsoft Teams: Distinguish invites among Attendee, Presenter, and Co-organizer emails

Microsoft 365 Roadmap ID 476488

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

Microsoft Teams Events invite emails will be separated based on the role of the participant. Event organizers will get an email explaining the specific roles of participants in the event. Similarly, each presenter will get a separate calendar invite, allowing the organizers of town halls to maintain separate invites for attendees.

When this will happen:

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

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

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

How this will affect your organization:

This feature update allows the organizers of town halls to maintain separate invites for attendees.

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.

MC1009929 — (Updated) Microsoft Teams: Join town halls using dial-in options and join codes

Microsoft 365 Roadmap ID 476489

Updated April 11, 2025: There was an error previously published that we have corrected. Previously we mentioned that the Microsoft Teams town halls dial-in options would be available to attendees and presenters, and that it would appear as separate email invited. This is not correct.

Presenters and Organizers can now, with this update, join a Teams town hall using the dial-in options and code displayed on the Event Scheduling page after publishing. This code should only be used for Organizers and Presenters, not attendees.

Presenters and attendees can now join Microsoft Teams town halls using dial-in options and join codes.

When this will happen:

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

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

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

How this will affect your organization:

With the release of this feature, Teams town hall presenters and organizers may join a Town hall using the dial-in option. Teams town hall does not support dial-in Attendees at this time.

This update is available by default.

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.

MC1006624 — (Updated) Microsoft Teams: Access chats while sharing a screen

Microsoft 365 Roadmap ID 467445

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

Coming soon to Microsoft Teams: We will add a control to the meeting presenter toolbar so presenters can more easily access the meeting chat while sharing a window or a screen.

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

When this will happen:

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

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

How this will affect your organization:

After this rollout, a compact view of the meeting chat (visible to presenter only) will open when the presenter selects the Chat icon on the presenter toolbar.

This feature will be available by default.

What you need to do to prepare:

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

MC1005513 — (Updated) Microsoft Teams: Direct routing call troubleshooting with the new "SIP call flow" diagram tool

Microsoft 365 Roadmap ID 479413

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

We are launching the SIP call flow diagram tool in the Microsoft Teams admin center to enable admins to troubleshoot their Direct Routing calls in a self-serve way.

This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web.

SIP refers to session initiation protocol.

When this will happen:

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

How this will affect your organization:

This feature will be available in the Teams admin center on the Usage reports page. The feature will also enable admins to view the SIP requests, responses, and associated SDP (Session Description Protocol) data between Microsoft Teams proxy and the SBC (session border controller) through which the call was routed. This data will be available for all calls made more than 30 minutes and less than 30 days ago. In order to access the SIP call flow diagram, admins will need to:

Sign in to the Teams admin center.
In the left menu, go to Analytics & reportsand select Usage reports.
Create and run a new PSTN and SMS (preview) usagereport. (PSTN refers to public switched telephone network and SMS refers to short message service.)
After the report is generated, to the Direct Routingtab and select the call you want to analyze.
Select the SIP call flow button in the report to view the detailed diagram.

Watch a short video on using the SIP call flow diagram (00:19 min)

What you need to do to prepare:

Additional resources:

SIP call flow for Direct Routing in Microsoft Teams - Microsoft Teams | Microsoft Learn

MC1000269 — (Updated) Microsoft Teams: New keyboard shortcut for adding emojis

Microsoft 365 Roadmap ID 369345

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

Coming soon: We are excited to announce a new feature in Microsoft Teams that allows users to insert emojis in the compose box by typing a word surrounded by colons. For example, :smile: will turn into the smiling face emoji. Users can soon add any emoji, including custom ones, for faster and easier personal expression.

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

When this will happen:

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

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

General Availability (GCC): We will begin rolling out late June 2025 and expect to complete by early July 2025.

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

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

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

General Availability (USSec, USNat): We will begin rolling out mid-July 2025 and expect to complete by late July 2025.

How this will affect your organization:

This feature will be available by default.

Watch the video: Use colons to insert emojis (0:04 minutes)

What you need to do to prepare:

Learn more: Send an emoji, GIF, or sticker in Microsoft Teams - Microsoft Support (will be updated before rollout)

MC997581 — Windows 10 End of Support for Microsoft Teams Rooms on Windows

Support ends soon for Window 10 on October 14, 2025, and devices will no longer receive security and feature updates. Upgrade your Teams Rooms on Windows devices now to Windows 11 for a smooth transition and get the latest productivity, security, and management features.

When this will happen:

October 14, 2025

How this affects your organization:

Until October 14, 2025, Teams Rooms and Teams Rooms Pro Management software will continue to support and test on Windows 11 and Windows 10 version 22H2. After the Windows 10 end of support date, Teams Rooms and Teams Rooms Pro Management will no longer update, support, or test apps on Windows 10.

What you can do to prepare:

Please utilize the Windows 11 readiness checker and Teams Rooms Pro Management portal Room Inventory export to identify devices that will need action. OS version 10.0.19045 or below devices will need to be upgraded.

Most Teams Rooms devices running Windows 10 can be upgraded to Windows 11. There are some devices from makers such as Lenovo, HP, Yealink, and Crestron that are not able to be upgraded due to the processor used. Please contact your device manufacturer for specific models impacted.

Find additional details on the Teams Rooms app OS support at Teams Rooms app and Windows versioning support - Microsoft Teams | Microsoft Learn. Please see the Microsoft product lifecycle notices for Windows 10 Enterprise and Windows10 IoT Enterprise.

MC994287 — (Updated) Microsoft Teams: Webinars will be generally available (DoD)

Microsoft 365 Roadmap ID 475279

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

Webinars in Microsoft Teams will soon be generally available. After this rollout, users will be able to schedule webinars with internal audiences and use capabilities such as creating an event page, sending attendee registration automated emails, and more.

This message applies to Teams on Windows desktop, Teams on Mac desktop, and Teams for the web. Teams for iOS/Android users can attend webinars but not schedule them.

When this will happen:

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

How this will affect your organization:

This change will be available by default.

What you need to do to prepare:

User documentation: Get started with Microsoft Teams webinars - Microsoft Support

MC993227 — (Updated) Microsoft Teams: Native Bluetooth call controls using hands-free protocol for multiple peripheral devices

Microsoft 365 Roadmap ID 475853

Updated April 25, 2025: We have updated the timeline below. Thank you for your patience.

Coming soon for Microsoft Teams: When you have several peripheral devices connected to Teams, the one you use to answer a call will temporarily become the main device that will sync with Teams when using the device's buttons. After the call, the original device selected in Teams settings will take over again as the main device. After this rollout, users can use multiple native Bluetooth devices can be confident that call controls will function correctly with all of them.

This message applies to Teams for Windows desktop.

When this will happen:

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

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

How this will affect your organization:

After this rollout, users will be able to switch between their connected peripheral devices when answering a call without manually changing the selected device in Teams settings.

This change will be available by default.

What you need to do to prepare:

Learn more:

MC993226 — (Updated) Microsoft Teams: New location sharing settings for emergency calls and other features

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

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

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

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:

Emergency Calling
Location Based Routing
Network and Locations matching via BSSID
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 isallowed, 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 isdisallowed, 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.

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.
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

MC989975 — (Updated) Microsoft Teams: Occupancy status on Teams panels

Microsoft 365 Roadmap ID 474441

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

Before this rollout, Microsoft Teams panels indicate a room availability based only on reservation data. After this rollout, Teams panels can smartly utilize signals from Teams Rooms devices and occupancy sensors paired with Teams panels to indicate when a room is in use, so users are not surprised to find an available room is actually occupied. This feature will be supported for accounts with a license for Microsoft Teams Rooms Pro or Microsoft Teams Shared Devices.

When this will happen:

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

How this will affect your organization:

After this rollout, this feature will be set to on by default, so the current experience will change. The room is in use when the room is not currently reserved and a user is in a call or casting with a Teams Rooms device, or the room is detected as occupied through a paired occupancy sensor.

When the room is in use, the panel's LED will adjust to the color selected by the admin for the busy state. In addition, the panel's home screen will reflect that the room is occupied. Note: The room can still be reserved on the device itself, through Microsoft Outlook, or through Microsoft Teams.

If the device is paired with a Microsoft Teams Rooms on Android, after a user reserves the occupied room from the device, a message will appear on the room display to let the user inside of the room know that the room has been reserved and to exit. This notification will be off by default, and the admin will need to enable it after pairing the device.

An admin can choose to turn off these features in Teams admin settings > Device settings > Occupied state. The two settings are Allow occupied state and Allow booking notifications. If Allow occupied state is turned off, the booking notifications also will be turned off.

What you need to do to prepare:

This rollout will happen by the specified date with no admin action required. You may want to update any relevant documentation as appropriate and plan to update your devices to the latest Teams app when it becomes available.

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

MC973513 — (Updated) Simplify UX flow to enable Together Mode

Microsoft 365 Roadmap ID 470427

Updated April 3, 2025: After further review, this feature continues rolling out. We apologize for any inconvenience.

Together mode will get a new simplified flow which will take the user from the beginning to the end through the steps of setting up the scene, assigning the seats and applying for everyone in the call in a transparent and easy-to-understand way.

When this will happen:

Targeted Release: We will begin rolling out mid-February 2025 and expect to complete by early March 2025.

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

How this will affect your organization:

With the improved experience, the function itself does not change but there will be more transparency thanks to the icons on the meeting toolbar for an easy access for each next step in the familiar Together mode flow.

What you need to do to prepare:

You may consider updating your training and documentation as appropriate.

MC973502 — (Updated) Microsoft Teams: New "Tag mentions" filter for the Activity feed

Microsoft 365 Roadmap ID 470598

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

Coming soon to Microsoft Teams: Users will have a new Tag mentions filter in the Activity feed to see their tag mentions in their chat and channel messages. The existing @Mentions filter allows users to catch up quickly on personal mentions.

When this will happen:

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

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

How this will affect your organization:

This change will be available by default. There are no tenant level settings. Defaults will not change.

What you need to do to prepare:

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

User documentation: Explore the Activity feed in Microsoft Teams - Microsoft Support (will be updated before rollout)

MC971032 — (Updated) Microsoft Teams: New recording policies for town halls and webinars

Microsoft 365 Roadmap ID 473887

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

Coming soon to Microsoft Teams: New admin policies in the Teams admin center and Microsoft PowerShell that govern the recording behavior for town halls and webinars. Before this rollout, the same policies control the recording behavior for town halls, webinars, and meetings. After this rollout, separate recording policies for town halls and webinars will be available to more finely control event behavior. This message applies to Teams for Windows desktop, Teams for the web, and Teams for iOS/Android.

When this will happen:

Targeted Release: We will begin rolling out late April 2025 (previously early April) and expect to complete by mid-May 2025 (previously mid-April).

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

How this will affect your organization:

This change will be available by default.

What you need to do to prepare:

Before the rollout, we encourage you to use PowerShell commands to update the default values of the recording policies for webinars and town halls. After the rollout, you can use Teams admin center or PowerShell commands to update the values.

Examples of PowerShell commands to set the town hall or webinar recording policy:

Set-CsTeamsEventsPolicy -Identity Global -RecordingForTownhall Enabled

Set-CsTeamsEventsPolicy -Identity Global -RecordingForWebinar Enabled

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: New-CsTeamsEventsPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn

MC971031 — (Updated) Microsoft Teams: New transcription policies for town halls and webinars

Microsoft 365 Roadmap ID 473886

Updated April 28, 2025: We have updated the timeline below. Thank you for your patience.

Before this rollout, for a Microsoft Teams town hall or webinar, the transcription behavior respects the current Teams meeting transcription policies. After this rollout, new transcription policies will be available for town halls and webinars to allow finer control over transcriptions. The policies may be changed in the Teams admin center or with Microsoft PowerShell commands. This message applies to Teams for Windows desktop, Teams for the web, and Teams for iOS/Android.

When this will happen:

Targeted Release: We will begin rolling out late April 2025 (previously early April) and expect to complete by mid-May 2025 (previously mid-April).

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

How this will affect your organization:

These new transcription policies for webinars and town halls will determine whether transcription is allowed for a town hall or webinar. Town halls and webinars will no longer respect the Teams Meeting transcription policies.

The new policies will be available by default for admins to configure.

What you need to do to prepare:

Before the rollout, we encourage you to use PowerShell commands to update the default values of the transcription policies for webinars and town halls. After the rollout, you can use Teams admin center or PowerShell commands to update the values.

Examples of PowerShell commands to set the town hall or webinar policy:

Set-CsTeamsEventsPolicy -Identity Global -TranscriptionForTownhall Enabled

Set-CsTeamsEventsPolicy -Identity Global -TranscriptionForWebinar Enabled

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: New-CsTeamsEventsPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn

MC966633 — (Updated) Microsoft Teams: Meeting recap can be shared as a link

Microsoft 365 Roadmap ID 471430

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

Coming soon to Microsoft Teams: Meeting participants will be able to share a link to the Meeting recap from the meeting thumbnail in chat and the Recap tab, making it easier to reference and share Meeting recap insights with others. Meeting participants can share the meeting recap link with anyone in their organization. Users who don't have access to the recording or transcript must request access before they can access the Meeting recap.

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

When this will happen:

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

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

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

How this will affect your organization:

This change will be available by default.

What you need to do to prepare:

Learn more: Meeting recap in Microsoft Teams - Microsoft Support (will be updated before rollout)

MC960811 — (Updated) Microsoft Teams: Enhanced captions for Teams Rooms on Windows

Microsoft 365 Roadmap ID 423089

Updated April 25, 2025: We have updated the timeline below. Thank you for your patience.

Coming soon to Microsoft Teams Rooms on Windows: We are excited to announce that captions will soon support additional languages and translation capabilities. This enhancement aims to improve meeting accessibility and inclusivity for non-English speaking users using Teams Rooms on Windows.

When this will happen:

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

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

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

How this will affect your organization:

Before the rollout: Captions in Teams Rooms on Windows only support the English language, which limits usability for non-English speaking users as the captions will result in gibberish if the actual spoken language in the meeting is non-English. There is also no way for admins to set default caption settings.

After the rollout

Additional languages: Users can select from a list of supported languages for captions, ensuring that captions are accurate and meaningful for non-English speakers. Users can change the meeting spoken language directly from Teams Rooms devices by selecting More > Captions > Meeting spoken language.

Real-time translation: Users can translate the meeting's spoken language if the room account has a Teams Rooms Pro license or if the meeting organizer has a Teams Premium license, allowing for real-time translation of captions. Users can translate captions by selecting More > Captions > Translation language.

Admin controls: For room accounts with Teams Rooms Pro license, admins can change system defaults, turn on captions by default for calls and meetings, and turn off filtering of profanity in captions and transcripts as necessary with these XML settings:

<CaptionsDefault>true</CaptionsDefault>
<FilterProfaneWords>false</FilterProfaneWords>

As an admin, you can allow or prevent users (including room accounts) from having access to this feature by configuring calling and meeting policies in the Teams admin center. Learn more: Enable call captions - Microsoft Teams | Microsoft Learn and Manage live captions - Microsoft Teams | Microsoft Learn.

This feature is available by default.

What you need to do to prepare:

After your Teams Rooms on Windows devices are updated to the latest version, configure the desired policy and settings, notify your users about this change, and update your training and documentation as appropriate. This rollout will happen automatically by the specified date with no admin action required before the rollout.

MC960809 — (Updated) Microsoft Teams: Live transcription for Teams Rooms on Windows

Microsoft 365 Roadmap ID 423088

Updated April 25, 2025: We have updated the timeline below. Thank you for your patience.

Coming soon to Microsoft Teams Rooms on Windows: We are excited to announce that users can soon start and stop transcription as well as view the meeting transcript directly from Teams Rooms on Windows devices. This feature requires a Teams Rooms Pro license.

When this will happen:

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

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

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

How this will affect your organization:

Before the rollout: When joining a meeting on Teams Rooms on Windows, users must also join the meeting on a companion device to start transcription. Also, even when transcription has been started, users can't view the transcript from the front of room display.

After the rollout: Users can select More > Record and transcribe > Start transcription or Stop transcription directly from the Teams Rooms on Windows device. Start/stop transcription is supported in any meeting where a participant belongs to the same tenant as the organizer.

When users transcribe a Meet now or Whiteboard session initiated from a Teams Rooms on Windows device, users must ensure that they invite themselves to the meeting so that they can access the transcript after the meeting through the meeting chat on their Teams desktop or mobile app.

After transcription is started, users can show/hide the transcript panel on the front of room display in any meeting layout:

Select More> Record and transcribe > toggle On/Off Show transcript.
Select View> Front row > open the left/right panel dropdown > select/unselect Transcript.

Users can also set the meeting spoken language, translate the transcript, and choose to show the original language and translated language side by side, ensuring accurate and meaningful transcription.

This feature will be on by default and available for admins to configure. As an admin, you can allow or prevent users (including room accounts) from transcribing meetings with a policy in the Teams admin center. Learn more: Manage transcription for Teams meetings | Microsoft Learn.

NOTE: Both the meeting organizer and the transcription initiator (room account) need to have permissions to transcribe the meeting. If the meeting organizer uses Meeting options to remove the room account's permissions, the start/stop transcription button will not be available.

For room accounts with a Teams Rooms Pro license, you have the option to turn off the filtering of profanity in transcripts using this XML setting: <FilterProfaneWords>false</FilterProfaneWords>

Start/stop transcription is not supported in these scenarios:

Teams calls including P2P, group, and PSTN calls
External and cross-tenant Teams meetings and calls
Third-party meetings and calls including Direct Guest Join and SIP

What you need to do to prepare:

After your Teams Rooms on Windows devices are updated to the latest version, configure the desired policy and setting, notify your users about this change, and update your training and documentation as appropriate. This rollout will happen automatically by the specified date with no admin action required before the rollout.

MC956699 — (Updated) Microsoft Teams: Forward messages with app cards

Microsoft 365 Roadmap ID 469506

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

We are introducing the ability to forward app cards. With the addition of app card forwarding, users now have a new way to share app cards across chats. To forward a message containing an app card, simply navigate to the More Actions menu of any message containing an app card and select forward. From here, the forward message dialog will populate, which provides users with a preview of the message being forwarded, including the app card.

Please note: Forwarding of bot cards is excluded from this release.

When this will happen:

Targeted Release: We will begin rolling out mid-February 2025 (previously early February) and expect to complete by late February 2025 (previously mid-February).

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

How this will affect your organization:

Users will now have less restrictions when forwarding content. Previously, users were unable to forward messages that contained app cards. With this improvement, this restriction does not exist.

What you need to do to prepare:

Users must have the latest Microsoft Teams build to receive these updates. You may want to notify your users about this change and update any relevant documentation as appropriate.

MC952889 — (Updated) Microsoft Teams admin center: Non-disruptive device operations for Microsoft Teams devices

Microsoft 365 Roadmap ID 418120

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

We are excited to announce a new capability in the Microsoft Teams admin center designed to ensure that device operations are non-disruptive for Android-based Teams devices.

This new feature allows software updates, restarts, and configuration updates to occur only when the device is idle (not busy), preventing any disruptions during meetings or calls. Device admins will now have the ability to manage these operations without affecting end-user experience, ensuring smoother and uninterrupted device usage.

When this will happen:

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

How this will affect your organization:

This change will significantly enhance the user experience by ensuring that device operations such as software updates, restarts, and configuration updates are carried out only when the device is idle. This means meetings or calls will no longer be interrupted by these operations. This change will be applicable for Teams Rooms on Android, Panels, Phones, and Displays.

This change will require an update for Teams app and the Teams admin agent app to take effect. We will update this message closer to the release date with details about the required versions.

With this change, the following device operations will automatically function in a non-disruptive way:

Software update
Device restart
Configuration update

This change will be applicable for operations created by administrators manually from Teams admin center or the Teams Rooms Pro Management Portal, as well as those being carried out automatically.

How this will work:

At the time of execution, the device status is checked. The execution goes forward only if the device is free (no ongoing meeting or call) and has no upcoming scheduled event on the calendar.

A few minutes before the execution starts, the device shows a notification for the end-users, informing them that the operation is about to start. The device users get an option to Postpone the execution if they want to use the device.

The execution of the operation does not start if the device is busy, or has upcoming scheduled events on the calendar, or the end-user has opted to postpone the execution. The device status is checked at regular intervals for a safe window for execution.

The status of the operation is available in Teams admin center. Admins can view the details on the device page under the History tab.

This ensures that the end-users do not face any disturbance while they are using Teams devices.

Additional aspects

There could be scenarios where the devices are extremely busy thus delaying the execution of the operation. Administrators will have an option to decide the execution approach if the execution is unable to start even after 24 hrs. There are two options:

The operation is cancelled after having tried for 24 hrs.There will be no impact on the device. If the administrator created this operation, they can come back can create it again. This is the default behavior.
The operation is force-executed after having tried for 24 hrs. This option will execute the operation, but the status of the device will not be checked at this point. This may cause some disruption if the device is in use.

The option to cancel or force the execution of the operations after the 24-hr search of a safe-execution window can be configured from Teams admin center through the Configuration profiles.

What you need to do to prepare:

The changes will take effect automatically after updating the devices to the required Teams app and Teams admin agent versions. The updates will happen automatically, but admins can choose to update manually also. The details about the required versions will be announced closer to the release date. Refer to Update Microsoft Teams devices remotely - Microsoft Teams | Microsoft Learn for more details about updating devices.

Admins should familiarize themselves with the new controls available in the Teams admin center. They should ensure that they configure the settings appropriately to suit their organization's needs. Additionally, it's recommended to communicate these changes to end-users, so they are aware of the improved experience and new notifications they might receive regarding device operations.

We believe this feature will greatly improve the reliability and user experience of Teams devices in your organization.

For any clarification, feel free to reach out to Microsoft Support.

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

MC948994 — (Updated) Microsoft Teams: Collaborative Notes support for GCC High and DoD environments

Microsoft 365 Roadmap ID 418119

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

Teams Collaborative Notes (powered by Loop), and Loop components in chat and channels, is now available for Microsoft 365 GCC High and DoD environments across desktop and web experiences. Users can create components in meetings to collaborate on their meeting agenda, notes, and action items, create components in compose, share with others and edit inline in Chats and Channels to collaborate synchronously on ideas without leaving the context of Teams. No matter where people are editing, the component will always show the latest updates. You can also share Loop components between chats, channels, and meetings as well as the rest of M365 where Loop is supported.

When this will happen:

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

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

How this will affect your organization:

Users within your tenant will see a Notes button during meetings that invokes these new capabilities. The meeting notes will be shown on the right pane of the meeting window with the ability to open them in the browser for more room or on a second monitor. Participants can collaborate in real time, create an agenda, take notes, and add tasks. When participants are assigned a task in the meeting, they will also receive an email notification, and it will be synced with the Planner and To Do apps.

Meeting organizers and participants will also see an option to add Collaborative Notes before meetings to prepare by adding agendas or other materials in one place. The meeting organizer can also choose to hide the meeting notes prior to the meeting through the Teams scheduling form. If Collaborative Notes are not created ahead of the meeting in the scheduling form, users can create the file by opening the Notes pane in the meeting.

After the meeting, Collaborative Notes will remain accessible for all participants on the Teams calendar meeting details page and through the meeting recap. The experience is a Loop component, so they can be copied easily out of the meeting and into chats, group chats, emails, and other documents. This makes prepping and follow-up even more seamless.

Clicking on the meeting note title or the icon in the upper left corner of the note launches the Loop app in browser. If the meeting is part of a series, meeting notes from previous instances can be conveniently found in the Loop app as well.

This feature is available by default.

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. Public documentation is available here: Take meeting notes in Microsoft Teams.

Note: The Loop Components will generate a Company Shareable Link (CSL), unless you have set People Specific Link (PSL) as the default. If PSL is the default, only specific users who were sent the original component invite will be able to access the component. Users who were forwarded the meeting or nudged into a meeting will need to request access to the components.

Known issues: Users external to an organization will not be able to view or edit the Loop component. Loop meeting notes will generate a Company Shareable Link (CSL) regardless of your organization’s default sharing link type if you use the Teams New Calendar.

You can manage this in Teams Calendar and Loop components in chats and channels by following the instructions here. You can manage this in Teams New Calendar by following the instructions here.

Known limitations: Collaborative Notes are currently supported for scheduled meetings and channel meetings and are not available for instant meetings or Teams calls.

MC946818 — (Updated) Microsoft Teams: Updates to Gallery in Teams Rooms on Windows

Microsoft 365 Roadmap ID 468277

Updated April 25, 2025: We have updated the timeline below. Thank you for your patience.

Coming soon to Microsoft Teams Rooms on Windows, the updated Gallery view introduces these changes to enhance your meeting experience:

All participants will appear in consistent tile sizes
By default, video participants have priority and appear first on the meeting stage by default (audio participants appear on the side or bottom of the screen)
Ability to disable priority on video participants to create a mix of audio participants and video participants in the Gallery
Optimized view of up to 25 participants on a single display and up to 50 participants on dual displays
Preview video is part of the Gallery, appearing next to the rest of the participants
Ability to hide the preview video across all layouts

When this will happen:

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

How this will affect your organization:

The updated Galleryprovides a unified meeting experience across both Teams Rooms and desktop. A more consistent and predictable layout can drive meeting efficiency and visibility for remote participants in hybrid meeting scenarios.

In 1:1 meetings, the preview video will be positioned at the bottom right, overlapping the other participant.

In group meetings, the preview video will be on the last available tile in the Gallery, next to the rest of the participants.

Admins can use two new settings to adjust the default view:

Prioritize vide0;< PrioritizeVideoParticipantsGallery> – Default value is True. The default experience will show video participants on the main stage with audio participants on the side or bottom rail. If you would like to display all audio and video participants mixed in the Gallery, change the value to False.
Hide me <HideMeForAllLayout> – Default value is False. If you would like to hide preview video across all layouts in Teams Rooms on Windows, change the value to True.

In-room users can adjust these settings on the console during a meeting, if desired.

Lastly, when another Teams Room joins the meeting, the video of the room automatically enlarges if there are more than two in-room users, providing a clearer view and better connection, and so users can focus on the person speaking.

These changes will be available by default.

What you need to do to prepare:

Please notify your users about this change and update any training documentation, as appropriate.

Learn more

Remotely manage Microsoft Teams Rooms device settings - Microsoft Teams | Microsoft Learn(will be updated before rollout)
Microsoft Teams Rooms (Windows) - Microsoft Support(will be updated before rollout)

MC942831 — (Updated) Microsoft Teams Phones: Remotely manage contacts in Teams admin center

Microsoft 365 Roadmap ID 81379

Updated April 25, 2025: We have updated the timeline below. Thank you for your patience.

Coming soon to the Microsoft Teams admin center: Admins will be able to remotely manage contacts to ensure crucial contacts are available for users on their Teams Phone devices. This feature is only available for common area phones.

When this will happen:

General Availability (Worldwide, GCC): We will begin rolling out this feature in mid-June 2025 and expect to complete by late June 2025.

General Availability (GCC High): We will begin rolling out this feature in late June 2025 and expect to complete by mid-July 2025.

General Availability (DoD): We will begin rolling out this feature in late July 2025 and expect to complete by mid-August 2025.

How this will affect your organization:

IT admins can access the Manage contacts feature from Teams admin center > Teams Devices > Phones > Common area phones. Select the applicable devices and then select Manage contacts.

In the right panel, use the Search box to search for and select contacts to add to selected devices. You can upload a CSV file for contacts not found through Search. Newly added contacts will be synchronized to the Calls app and People app on the Teams phones devices under the group name Company contacts within 24 hours.

For any device, admins can review or delete the added contacts from the Manage contacts right panel.

Track the progress and status of contact operations with the Activity log in the Teams phone inventory.

This new 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. If you have questions or need further assistance regarding this feature, please reach out to our support team.

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

MC942829 — (Updated) Microsoft Teams admin center: Activity log for Teams Phone device management

Microsoft 365 Roadmap ID 420326

Updated April 25, 2025: We have updated the timeline below. Thank you for your patience.

We’re excited to announce the rollout of a new feature in the Teams admin center: Activity log for Teams Phone device management. This feature empowers Teams administrators to actively monitor and track device operations, providing greater control over remote operations on Teams devices.

Updated December 3, 2024: We have updated the rollout timeline below. Thank you for your patience.

Currently, the Activity log supports only the remote management of contacts on Teams Phones; however, we’re working to expand this feature to other device types and additional operation categories.

When this will happen:

General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out this feature in mid-June 2025 and expect to complete by late August 2025.

How this will affect your organization:

Admins can access the new Activity log by navigating to the Teams admin center > Teams Devices > Phones > Activity log

Because only remote management of contacts for Teams Phones is currently supported, admins will be able to track operations such as Add contacts or Delete contacts and details like created time, impacted users, operation status, and more. By selecting an operation name, admins can view status updates at a granular level for each device involved in that operation.

The Activity log will be available by default.

What you need to do to prepare:

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

MC939924 — (Uploaded) Microsoft Teams: Start Whiteboard from Teams Rooms on Android in GCC and GCC-H

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

Microsoft Whiteboard storage is moving from Azure to OneDrive for Business to deliver greater compliance, governance, and retention capabilities. This improvement allows us to offer the Start Whiteboard feature in additional cloud environments (GCC and GCC High) that support OneDrive for Business. The enhanced Whiteboard experience, includes:

Features unique to whiteboards stored in OneDrive, such as Follow me, Commenting, Collaborative cursor, and more.
Improved performance on whiteboards now stored in OneDrive.
Improved compliance and security associated with whiteboard being stored in OneDrive.

When this will happen:

General Availability (GCC, GCC High): We will begin rolling out late January 2025 (previously November) and expect to complete rollout by late June 2025 (previously late March).

How this will affect your organization:

Outside of a meeting

Whenever you want to brainstorm in the office, just start whiteboarding using the new Whiteboard button on the home screen. With one touch, you can quickly launch Microsoft Whiteboard and start collaborating outside of a Teams meeting.

Since a resource account does not have OneDrive, it will launch a temporary whiteboard. The Save button will guide you to invite your work account to a meeting with your Teams Room so that the temporary whiteboard can be saved in your OneDrive for Business. You will see a saving failure error if you invite a non-room participant who does not have OneDrive.

Switch from local to online collaboration by selecting Start meeting on the local whiteboard screen. This initiates an ad-hoc meeting and presents the temporary whiteboard. From there, you can add participants into the meeting and contribute across the same whiteboard in real time. The temporary whiteboard will be saved in OneDrive for the first non-room user who joins the meeting.

In a meeting

During a meeting, click the Share button and select Microsoft Whiteboard to initiate a whiteboard. The whiteboard will be shared in the meeting and saved in OneDrive for Business for one of the non-room participants at the meeting automatically.

What you need to do to prepare:

Please verify that your tenant setting meets the requirements described in this documentation: Manage sharing for Microsoft Whiteboard - Microsoft Whiteboard | Microsoft Learn.

The Start Whiteboard feature will be turned on by default. Your Home screen (outside of the meeting) will show the Whiteboard button, and the in-meeting share tray will show the whiteboard option.

If you want to disable the Start Whiteboard feature, please turn it off via the admin setting on your device or apply the configuration profile in Teams admin center using the 'Allow room to use Microsoft Whiteboard' setting under the 'Meeting settings' section.

Even if the Start Whiteboard feature is disabled for your Teams Rooms on Android device, you can see a whiteboard that remote participants share in a meeting.

MC934727 — (Updated) Microsoft Teams: File Interactive Previews

Microsoft 365 Roadmap ID 421188

Updated March 20, 2025: We would like to inform you that the general availability and other releases of this feature will be delayed. New timelines for release will be communicated in due course. In the meantime, this feature will be rolled back for about a month from the current target releases.

Now users can quickly review files in Microsoft Teams chat and channel conversations using the file preview option. Using preview, users will be able to consume the file within the flow of work, minimizing the context switch and potentially enhancing the efficiency for the users.

When this will happen:

Targeted Release: We will communicate via Message center when we are ready to proceed.

General Availability (Worldwide): We will communicate via Message center when we are ready to proceed.

General Availability (GCC): We will communicate via Message center when we are ready to proceed.

General Availability (GCC High): We will communicate via Message center when we are ready to proceed.

General Availability (DoD): We will communicate via Message center when we are ready to proceed.

How this will affect your organization:

The stage 1 release of this feature will enable previews for single file attachments in Teams messages, starting with PDF files and gradually extending the support for other popular formats such as Microsoft PowerPoint, Microsoft Word, and later Microsoft Excel. The preview option for files in messages with multiple files will be supported in subsequent releases.

This new feature is available by default.

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.

MC920084 — (Updated) Microsoft Teams: Usage reports for bookable desks

Microsoft 365 Roadmap ID 421604

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

With this rollout, admins will have access to reports and insightful usage analytics for desk pools (workspace resource accounts) that have at least one associated peripheral. These capabilities will be available in the Teams Rooms Pro Management portal. This message applies to tenants with Teams Rooms Pro or Teams Shared device licenses.

When this will happen:

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

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

How this will affect your organization:

The Teams Rooms Pro Management portal will have a new tab under Reports called Desk usage. Desk pools that have at least one peripheral associated will appear under this tab.

Admins will be able to review overall metrics about their desk pools such as the number of total associated desks, the number of desks that are unused, and the percentage of reservations that were unplanned. For each desk pool, they will be able to review more analytics such as utilization, total reservations, reservation occupancy (percentage of time that desk pool was utilized during reservations), and more.

Admins will also be able to select a specific desk pool to review specific metrics, such as a peak utilization matrix.

This change 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 also want to notify your admin team about this change and update any relevant documentation. Also, we recommend setting up desk pools with up to 8 seats in each pool. We will show analytics for up to 8 desks per desk pool.

Reports for desk pools will be in public preview and available with no licensing requirement until July 2025. More information on licensing requirements will be provided prior to that date.

Learn more: Setting up Bookable Desks in Microsoft Teams - Microsoft Teams | Microsoft Learn (will be updated soon after rollout)

MC912707 — (Updated) Microsoft Teams: New policy for voice and face enrollment will default to "On" (configure now)

Microsoft 365 Roadmap ID 413708

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

Updated February 6, 2025: Please verify that all previously set values remain unchanged and as intended.

A new csTeamsAIPolicy policy for Microsoft Teams (available now via Microsoft PowerShell and taking effect in mid-March 2025 (previously mid-February) will give IT admins more control over voice and face enrollment settings, allowing organizations to manage these features based on their needs. After rollout, voice and face profile enrollment will be enabled by default, and users can benefit from voice isolation, speaker recognition, and attribution in meeting rooms, resulting in smarter meeting recaps and enhanced functionality for Microsoft 365 Copilot in meetings. To access Copilot features, a Microsoft 365 Copilot license is required. This message applies to Teams for Windows desktop and Mac desktop.

NOTE: Microsoft doesn't use the voice and face profiles of users to train any models or for any other purposes other than providing the voice and face enrollment feature in Microsoft Teams.

When this will happen:

The new Microsoft PowerShell cmdlets are available now for admins to configure, to ensure a smooth transition.

General Availability (Worldwide, GCC): The new Microsoft PowerShell cmdlets are available now for preparation and to ensure a smooth transition. The policy takes effect starting in mid-March 2025 (previously mid-February) and is expected to be fully in effect by late April 2025 (previously late March).

How this will affect your organization:

What you need to do to prepare:

This rollout will happen automatically by the specified date. 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.

If your organization prefers to disable voice and face enrollments, review and update your settings before mid-March 2025 (previously mid-January). To help you get started, review:

Learn more: Overview of voice and face enrollment - Microsoft Teams | Microsoft Learn

If your organization prefers to disable voice and face enrollments, review and update your settings before mid-March 2025 (previously mid-February).

Important: The EnrollUserOverride setting can be assigned globally, directly to users, or to groups in PowerShell.

Admins must ensure that changes are applied consistently across all these locations to avoid unintended configurations.

MC889534 — (Updated) Microsoft Teams: Embed support for Teams town hall

Microsoft 365 Roadmap ID 401120

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

As a part of Team’s ongoing effort to enable our customers to create, manage, and run large scale events, end users can now embed Teams town hall in sites they manage. This capability allows town hall attendees to watch the event instance within a particular website.

Embed for town hall introduces embeddable support for town hall engagement features on release. Attendees will have the same engagement feature access within the embed player as they do in client such as Q&A, Captions, Reactions and more.

To implement embed for town hall, organizers can access their town hall events unique embed code from the town hall scheduling template upon publish. Organizers can then take that code and inject it to their SharePoint or Microsoft 365 site as desired. On event start, attendees will be able to view and engage with the embed stream on the published site.

When this will happen:

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

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

How this will affect your organization:

Users will be able to copy embed code directly from town hall scheduling form on event publish. After the embeddable code is placed in the website, the town hall player will be accessible to attendees who have access to the URL.

Note: Attendee access to the embedded video player is driven by the town hall event access.

What you need to do to prepare:

Organizers with SharePoint or Microsoft 365 site who want to utilize embed support for town hall can begin implementing the embeddable code upon release.

MC898391 — (Updated) Microsoft Teams: Performance improvements for meetings in Edge web browser for guests

Microsoft 365 Roadmap ID 401117

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

Anonymous users (guests) who join Microsoft Teams meetings in the Microsoft Edge for Business web browser will soon experience performance improvements. They will be able to join meetings faster.

When this will happen:

Targeted Release: We will begin rolling out early November 2024 and expect to complete by mid-November 2024.

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

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

How this will affect your organization:

Before this rollout, anonymous users (guests) may experience longer wait times when attempting to join a Teams meeting.

After this rollout, anonymous users (guests) will be able to join meetings faster, even on low-end devices.

What you need to do to prepare:

This rollout will happen automatically with no admin action required.

MC894581 — (Updated) Microsoft Teams: Performance improvements for meetings in Chrome web browser for guests

Microsoft 365 Roadmap ID 401116

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

Anonymous users (guests) who join Microsoft Teams meetings in the Chrome web browser will soon experience performance improvements.

When this will happen:

Targeted Release: We will begin rolling out early November and expect to complete by mid-November 2024.

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

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

How this will affect your organization:

Before this rollout, anonymous users (guests) may experience longer wait times when attempting to join a Teams meeting.

After this rollout, anonymous users (guests) will be able to join meetings faster, even on low-end devices.

What you need to do to prepare:

You may want to update your internal documentation to inform your users about this improvement. However, because the improvement is for external users and does not change the look of Teams, you can skip this step.

MC892646 — (Updated) Microsoft Teams: New policy for voice and face enrollment defaulting to 'On'

Microsoft 365 Roadmap ID 413708

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

We're introducing a new policy that gives IT admins enhanced flexibility with distinct settings for voice and face enrollment. This adjustment provides greater control over managing these features, allowing organizations to tailor to their needs. Voice and face biometric enrollment will be enabled by default, enabling voice isolation and speaker recognition in meeting rooms and enhancing intelligent meeting recaps and Microsoft Copilot for meetings.

When this will happen:

General Availability (Worldwide, GCC):

We will begin rolling out the new policy in early October 2024 and expect complete by mid-October 2024.
The policy will be enabled beginning in mid-March 2025 (previously early February) and expect to be complete by late April 2025 (previously late March).

How this will affect your organization:

These changes will provide your organization with increased flexibility in managing voice and face enrollments. By using separate settings, you can customize for your organization's specific needs. The enrollment policy will be enabled by default. Once enabled, these enrollments will activate features like Voice Isolation and enhanced speaker recognition, leading to more efficient and productive meetings.

What you need to do to prepare:

To ensure you have enough time to prepare for this change, you have until mid-January 2025 to configure everything to best suit your needs. If your organization requires keeping face and voice enrollments off, be sure to review the new policy and adjust the settings during this time. This period provides an opportunity to optimize how you manage voice and face data, enhancing your team's control over the process.

The new csTeamsAIPolicy will replace the current csTeamsMeetingPolicy, introducing two separate settings for face and voice enrollment: EnrollFace and EnrollVoice. Each can be set to Enabled or Disabled.

To help you get ready, review:

For more information about voice and face enrollment, visit Overview of voice and face enrollment - Microsoft Teams | Microsoft Learn

MC884018 — (Updated) Microsoft Teams: Set sensitivity labels for town halls and webinar

Microsoft 365 Roadmap ID 409226

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

Coming soon for Microsoft Team Premium customers: Event organizers will be able to set sensitivity labels for town halls and webinars. Sensitivity labels allow organizations to protect and regulate access to sensitive content created through collaboration in Teams. Sensitivity labels are available only for Teams Premium users on Mac and Windows desktops.

When this will happen:

Targeted release: We will begin rolling out in mid-October October 2024 (previously early October) and expect to complete by late October 2024 (previously mid-October).

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

How this will affect your organization:

Before this release: Sensitivity labels were not available for town halls and webinars.

After this rollout, events created or updated by an organizer with a Teams Premium license can apply a sensitivity label to their event. Organizers will be notified if their configured settings are not valid for the selected sensitivity. Specific options under Event access may be enabled or disabled based on the sensitivity label set for the event:

For upcoming events that have already been scheduled prior to rollout, the sensitivity of the event will be set to None. If an event organizer chooses to modify the sensitivity for a scheduled event after the rollout, this action may affect event settings that were previously configured.

What you need to do to prepare:

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

MC856756 — (Updated) Microsoft Teams Rooms on Windows: Native PTZ controls

Microsoft 365 Roadmap ID 409534

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

Microsoft Teams Rooms on Windows will soon support native PTZ (pan-tilt-zoom) controls for cameras capable of supporting PTZ controls. The PTZ controls will appear in the Camera settings pop-up menu when the Enhanced Framing toggle is set to off.

When this will happen:

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

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

How this will affect your organization:

Before this rollout: Native PTZ controls are not displayed in Camera settings pop-up menus for PTZ-capable cameras.

After this rollout: Admins will be able to toggle this feature for each Teams Rooms on Windows in the device's Admin Settings for Peripherals. This setting will be on by default.

Users in a Teams Rooms on Windows with a PTZ-capable camera connected will see PTZ controls in the Camera settings pop-up menu.

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 new capability and update any supporting documentation for your users.

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

MC854652 — (Updated) Microsoft Teams: Meeting participants can choose a breakout room from a list

Microsoft 365 Roadmap ID 121269

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

Coming soon: Microsoft Teams meeting organizers can make the list of breakout rooms visible to all meeting participants and allow them to choose which room to join. Enabling this setting in breakout rooms allows participants to move freely from one room to another, simplifying breakout room coordination for meeting organizers and participants. This message applies to Teams for Windows, Mac, and the web.

When this will happen:

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

General Availability (Worldwide, GCC): We will begin rolling out mid-January 2024 (previously mid-December) and expect to complete by late January 2025 (previously early January).

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

How this will affect your organization:

Before this rollout: Only the meeting organizer can assign meeting participants to breakout rooms. Participants cannot move between rooms.

After this rollout: Meeting participants can select their breakout rooms of choice if the meeting organizer selects this option during setup.

Organizers can look for the new feature under the breakout rooms panel when setting up breakout rooms:

This feature is on by default and accessible to all meeting participants on the affected platforms if enabled by meeting organizers.

What you need to do to prepare:

MC804771 — (Updated) Microsoft Teams: Hiding inactive channels

Microsoft 365 Roadmap ID 325780

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

Note: Users with EDU licenses assigned will not receive this change.

Based on Admin feedback, we are updating the behavior for automated hiding of inactive channels to be opt-in (suggestions) only. With this update, Teams will offer users suggestions on channels that are inactive, and the user is prompted to review their inactive channels and hide them only if they choose. The settings are also updated to reflect this opt-in workflow. There are no changes to the on-demand hiding process.

This feature is enabled for Targeted Release, and we will roll out to General Availability later this year in 2025.

In the interim, we are disabling the current generally available version of the feature which requires users to opt-out as well as the settings, for all users. Please note that all users in the public or general ring will not see the setting or have any of their channels hidden automatically. We will re-introduce the updated feature later this year in 2025.

When this will happen:

Targeted Release: We will begin rolling out mid-July 2024 and expect to complete later in 2025.

General Availability (Worldwide) and all clouds: We will begin rolling out later in 2025.

How this will affect your organization:

Before this rollout: Users had to manually manage their relevant channels list by hiding inactive and irrelevant channels.

After this rollout in 2025: Manage preferences for automated suggestions via Teams Settings

If users prefer to manage channels manually, they can opt out of the auto-suggestions process. Simply go to Teams settings, select General, and toggle off "Suggestions for hiding inactive channels."

Hide inactive channels on demand when needed

Users can manually view which channels are inactive and choose to hide some or all of them whenever you need. This can be done from Settings, under General, by clicking the "Get Suggestions" button. Note that this action can be performed once every 24 hours.

Automated suggestions of inactive channels

With this, Teams will suggest channels that have been inactive for the user. Once the inactive channels are identified, the user is notified with the coach mark message, "Looks like you haven’t visited some channels lately. Hide them to help you focus."

The user can select Review and Hide to see the details and decide which channels they would like to hide. The user can choose not hide any channels by selecting Not Now.

If a user has less than or equal to 25 shown channels, no channels will be suggested for that user. This feature is on by default and all Teams users on the affected platforms will have access to it.

What you need to do to prepare:

Admins need to be aware of this feature, but no additional action is needed.

MC795750 — (Updated) Microsoft Teams: Custom emojis and reactions

Microsoft 365 Roadmap ID 80659

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

In Microsoft Teams, users will be able to add their own custom emojis and reactions by uploading an image or GIF file, and their emojis and reactions will be accessible to all users in the tenant alongside the standard Teams emojis and reactions. Up to 5,000 custom emojis can be added per tenant.

When this will happen:

Targeted Release: We will begin rolling out early July 2024 (previously late June) and expect to complete by mid-July 2024 (previously early July).

Worldwide: We will begin rolling out early August 2024 (previously mid-July) and expect to complete by early September 2024 (previously late July).

GCC: We will begin rolling out early March 2025 and expect to complete by mid-March 2025.

GCC High: We will begin rolling out mid-March 2025 and expect to complete by late March 2025.

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

How this will affect your organization:

This new custom emojis and reactions feature will be turned on by default. Users in the tenant will be able to upload emojis that are visible to the whole tenant. You can pre-emptively turn this feature off or restrict users who can create new emojis via the Teams Admin Center controls described below.

How do I use this feature?

Custom emojis and reactions will be found in the emoji and reaction menus in the Custom category. Users with upload abilities can add new content through the plus (+) button. Users with delete abilities can right-click any custom emoji to delete. Please note that deleted emojis may take up to 24 hours to reflect for all users in the tenant. Deleted emojis may take up to 24 hours to reflect for other users.

How do I manage this feature?

This feature can be managed through the Teams Admin Center. Admins will have access to the following controls:

Turn the feature on/off for the whole tenant via the Messaging Settings page (on by default).
Set which users can create new emojis via the Messaging Policy groups (on for all users by default).
Set which users can delete emojis via the Messaging Policy groups (off for all users except admins by default).

The Teams Admin Center controls will be made available in early June. We recommend adjusting your settings as needed prior to the Targeted and Worldwide Releases in late June 2024 to ensure that they are in place when the feature rolls out.

What you need to do to prepare:

This feature is on by default. If you would like to turn the feature off, please use the provided setting in the Messaging Settings page:

Messaging Settings

This feature allows all users to create new emojis by default and only allows admins to delete emojis by default. If you would like to adjust emoji creation and deletion permissions, please make the appropriate changes through the Messaging Policy groups:

MC781595 — (Updated) Microsoft Teams: Tenant-wide policy for permission to download meeting transcription

Microsoft 365 Roadmap ID 332800

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

Coming soon for Microsoft Teams: A new policy for IT admis to restrict permissions to download new meeting transcript files (stored in Microsoft OneDrive) for all users in the tenant. Admins can exempt people from the policy who are members of specified security groups such as governance or compliance specialists who require download access to meeting transcripts. This rollout applies to Teams for Mac and Teams for desktop.

When this will happen:

Targeted Release: We will begin rolling out early June 2024 (previously mid-May) and expect to complete by mid-June 2024 (previously late May).

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

General Availability (GCC High): We will begin rolling out late August 2024 (previously mid-July) and expect to complete by mid-September 2024 (previously late July)

General Availability (DoD): We will begin rolling out late September 2024 (previously mid-August) and expect to complete by complete by late April 2025 (previously late March).

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 admins about this change and update any relevant documentation as appropriate.

Learn more: Block the download of Teams meeting recording files from SharePoint or OneDrive - Microsoft Teams | Microsoft Learn (We will update this comm before rollout with revised documentation.)

MC726122 — (Updated) Microsoft Teams: View, download, and delete Microsoft OneDrive transcript files

Microsoft 365 Roadmap ID 365720

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

We are beginning the process to standardize all transcript storage to OneDrive, starting with the storage of transcripts for meetings that only have transcription enabled. Previously, meetings with only transcription enabled saved the transcript file to the meeting organizer’s Exchange Online, while meetings with both recording and transcription enabled saved two transcript copies—one that is coupled with the recording saved to OneDrive and another transcript copy saved to the meeting organizer’s Exchange Online.

Now with this feature, meetings that have only transcription enabled will also save two copies (one in OneDrive and one in Exchange Online), but all meeting transcript entry points in Teams app will point to the OneDrive copy only, no entry points for meeting transcripts will source from the Exchange Online copy. At the same time, meeting transcripts will stop saving in Exchange Online altogether and all transcript storage will be standardized on OneDrive only.

The rollout of this feature also improves both the experience of meeting organizers to manually delete the transcript, as well as the ability for IT administrators to apply retention policies to the transcripts from meetings that only had transcription enabled.

A summary of the deletion experience for meeting transcripts is captured in the following table:

When this will happen:

Targeted release: We will begin rolling out early June 2024 (previously mid-May) and expect to complete by mid-June 2024 (previously late May).

General Availability (Worldwide, GCC): We will begin rolling out mid-June 2024 (previously late May) and expect to complete by late August 2024 (previously mid-August).

GCC High: We will begin rolling out late August 2024 and expect to complete by mid-September 2024.

DoD: We will begin rolling out late September 2024 and expect to complete by early April 2025 (previously late April).

How this will affect your organization:

There is no change to the end user experience for viewing and downloading Teams meeting transcripts. The only change for meeting organizers and co-organizers is for any meetings that are held after this feature rolls out, they can delete all copies of the meeting transcript directly from the Teams app, instead of having to manually delete all copies of the transcript from two places (Teams app and Stream). For IT administrators, they can start applying retention policies for the copy of the transcript saved in OneDrive, including scenarios where a meeting only had transcription enabled. This retention policy won’t affect the copies saved in Exchange Online, to bulk delete transcript files saved in Exchange Online—please refer to this documentation.

We will also update the default transcript permissions. After the rollout, when the new policy is not applied, only meeting organizers and co-organizers will have permission to download or delete the transcript file, and meeting participants can only view the transcript in Teams or Microsoft Stream. Regardless of whether the new policy is applied, the meeting organizer will be able to select in Stream the participants who are restricted from downloading, viewing, and editing the transcript in Stream.

What you need to do to prepare:

There is no action needed to prepare for this change. You may want to notify your users about this change and update any relevant documentation as appropriate.

MC718553 — (Updated) Microsoft Teams: Change background while recording on phone

Microsoft 365 Roadmap ID 380852

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

Users can now record themselves anywhere and share it with coworkers in the Microsoft Teams chat or channel without worrying about the background. Users can now change their background to any image they want or make the background blurry while recording using their Microsoft Teams camera on iOS devices.

When this will happen:

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

How this will affect your organization:

Users will get an option to change their background to any image they want or make the background blurry while recording using their Microsoft Teams camera on an iOS device. To use this feature:

Press and hold the camera icon next to the Compose box and then tap the blur icon to the right of the shutter button.
You can then choose either an image to replace the background or choose to mildly or heavily blur your background.

What you need to do to prepare:

No action is needed to prepare for this change. You may want to notify your users about this change and update any relevant documentation as appropriate.

MC709270 — (Updated) Mute with Windows Taskbar available in the new Microsoft Teams on Windows

Microsoft 365 Roadmap ID 191528

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

The Muting Teams with Windows Taskbar is now available. This feature, available in the new Teams experience on Windows, enables you to mute and unmute your audio by clicking the mic icon in Windows taskbar.

To control your call mic from the taskbar, do the following:

Select the mic icon on your taskbar or press Windows logo key + Alt + K to mute or unmute your microphone while using a calling app.

-OR- Click the volume icon in the hardware indicator for volume in Windows taskbar.

When this will happen:

Targeted release: We will begin rolling out early June 2024 (previously mid-May) and expect to complete by mid-June 2024 (previously late May).

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

How this will affect your organization:

This enables a feature previously available in older version of Teams on Windows.

What you need to do to prepare:

To prepare, distribute updates on this rollout with your organization if applicable for your users.

MC705760 — (Updated) Teams: Latest meeting experiences with performance improvements on web for Safari and Firefox (for guests)

Microsoft 365 Roadmap ID 329253

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

The latest Teams meeting experiences will be available for Teams on the web in Safari and Firefox browsers - including performance improvements, refreshed pre-join, updated meeting stage, and the updated meeting toolbar. (for anonymous join only)

When this will happen:

Worldwide: We will begin rolling out early September 2024 (previously mid-August) and expect to complete by early October 2024 (previously late August).

GCC, GCC High and DoD: We will begin rolling out mid-October 2024 (previously mid-September) and expect to complete by mid-April 2025 (previously mid-March).

How this will affect your organization:

We make constant steps to improve Teams performance irrespective of the platform – this time we are making the experience of Teams meetings on web (in Safari and Firefox browsers) better for anonymous users (guests). That’s crucial because it improves external collaboration. For example, if participants from your tenant would like to have meetings with non-Teams users (who are often joining as guests) it’ll become simpler as guests joining meeting from Safari/Firefox web browsers won’t have to wait significant amount of time for the meeting experience to load.

You may also notice that currently meeting UI in Chrome and Safari/Firefox is different, but with this update it won’t be a case anymore and you’ll enjoy all the benefits of modern UI (such as meeting toolbar on top of the screen, etc).

What you need to do to prepare:

You may want to update your internal documentation to inform your users about this improvement.

Microsoft Purview

MC1061103 — Microsoft Purview | Data Loss Prevention: Ability to rename policy and rules

Microsoft 365 Roadmap ID 370535

Coming soon for This feature gives the ability for the DLP admin to rename the existing policy/rule without having to create the entire the rule or policy again

When this will happen:

Public Preview: We will begin rolling out mid-July 2025 and expect to complete by late July 2025.

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

General Availability (GCC, GCC High, DOD): We will begin rolling out mid-October 2025 and expect to complete by late October 2025.

How this will affect your organization:

This feature is currently supported for major workloads: Microsoft Exchange Online, Microsoft Teams, Microsoft SharePoint, Microsoft OneDrive, and Microsoft Endpoint.

With this rollout, we will also introduce a new field called DisplayName that you can edit in DLP and in Microsoft PowerShell. For all practical purposes the display name can be used as the name for all the operations.

Renaming an existing policy:

Editing a rule to rename it:

All DLP experiences (such as Incident Reports, User Notifications, Email Alerts, DLP Alerts, MTP Alerts, and Activity Explorer) will start showing the policy/rule names at the point of record generation. For example: If a policy is named P1 at T0 and updated to P2 at T1, all records generated between T0 and T1 will have the name as P1 and all the records from T1 will have the name as P2.

This feature will be available by default for admins to configure.

What you need to do to prepare:

This is a non-invasive feature. The tenant admin will not see any changes unless the admin uses the feature.

Learn more: Create and deploy a data loss prevention policy | Microsoft Learn

MC1059679 — Microsoft Purview | Insider Risk Management: Policy tuning analysis for priority content only policies

Microsoft 365 Roadmap ID 378409

In Microsoft Purview | Insider Risk Management (IRM), policy tuning analysis provides admins with a real-time prediction of the number of users in a tenant that could potentially match a given set of policy conditions. After this rollout, policy tuning analysis will support insider risk policies that are scoped for priority content.

MC786326 (about the preview for this feature that started in May 2024).

When this will happen:

General Availability (WW, GCC, GCC High, DoD): We will begin rolling out mid-June 2025 and expect to complete by mid-July 2025.

How this will affect your organization:

After this rollout, admins can use real-time analytics for policies scoped for priority content to help predict the number of users that could potentially match a given set of policy conditions. This feature enables admins to quickly adjust the selection of indicators and thresholds of activity occurrence so they can efficiently translate their insider risk strategies into pragmatic controls and keep from having too few or too many alerts.

In IRM, Navigate to Settings > Insider Risk Management > Analytics,turn on Analytics, and then select Save.

Create/edit a policy scoped to all users in the organization.
When you get to Content to prioritizein the policy wizard, select the priority content types you want to prioritize:

Select the items for each priority content type as applicable.
On the scoring page, select Get alerts only for activity that includes priority content:

Configure the rest of the policy as applicable and save it.
1-2 days after the policy is saved, edit the policy again and navigate to the indicator thresholds page where insights on user activity containing the scoped priority content for each indicator will be visible under Choose your own thresholds:

What you need to do to prepare:

This change will be available by default for admins to configure. To use this feature, admins will need to enable Analytics in Insider risk management > Settings. After Analytics is enabled and insights are populated, admins will be able to see real-time predictions in policies scoped to all users/groups and scored only for priority content.

Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage and security violations. Insider Risk Management enables customers to create policies based on their own internal policies, governance and organizational requirements. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy.

You can access the Insider Risk Management solution in the Microsoft Purview compliance portal.

Learn more: Configure policy indicators in insider risk management | Microsoft Learn

MC1058262 — Microsoft Purview | Insider Risk Management: Enhancements to global exclusions in IRM settings

Microsoft 365 Roadmap ID 486826 and Roadmap ID 483485

Coming soon for Microsoft Purview | Insider Risk Management (IRM): Enhancements to IRM exclusions to reduce alert noise.

When this will happen:

Public Preview: We began rolling out mid-April 2025 and expect to complete by late April 2025.

General Availability (Worldwide, GCC, 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:

Customer can use this feature to tune down the noise

Keyword logic update for email: An email will be excluded from scoring only when all the attachments match the keyword exclusions or email subject matches the keyword exclusions. This will be helpful to reduce the email signature noise that commonly contains keyword "image."
Keyword exclusions on both target and source file paths: For signals like File copied to removable media, keyword exclusions apply on both target and source file paths.
File path exclusions for removable media: We will start supporting file path exclusions for removable media.
Exclusion support for browser: Domain exclusions will be supported for browsing indicators.

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

What you need to do to prepare:

To get the most out of this feature, admins need to update the exclusion settings at IRM Settings > Global exclusions.

This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization.

Microsoft Purview | Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage, and security violations. Insider Risk Management enables customers to create policies based on their own internal policies, governance, and organizational requirements. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy.

MC1046161 — Microsoft Purview | Data Loss Prevention: New inline protection controls for AI apps in Microsoft Edge for Business

Microsoft 365 Roadmap ID 486368

Coming soon for Microsoft Purview | Data Loss Prevention (DLP): We will introduce new inline protection capabilities for Microsoft Edge for Business that prevent data leakage for the various ways that users interact with sensitive data in the browser, including typing text directly into a web application or sending a prompt to a generative AI app. Inline protection is built natively into Edge for Business, meaning it can be enabled even without deploying Endpoint DLP, and the inline protection complements existing Endpoint DLP protections for uploading or pasting sensitive content to the browser. This capability will be available starting with several top consumer generative AI apps (ChatGPT, Google Gemini, and DeepSeek), and will expand to support a growing list of unmanaged apps over time.

Learn more in our blog: Building layered protection: New Microsoft Purview data security controls for the browser & network | Microsoft Community Hub

When this will happen:

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

We will update this message when the plan for General Availability is finalized.

How this will affect your organization:

After this rollout, admins can block prompts typed by users containing sensitive data, starting with ChatGPT, Google Gemini, and DeepSeek. Inline protection can also leverage Adaptive Protection policy conditions for activities in generative AI apps. This rollout enables data security admins to tailor the level of enforcement to the risk level of the user interacting with the data, minimizing disruption to day-to-day AI usage.

This change will be available by default for Admins to configure in Purview. Features aren't activated by default.

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 assess the impact on your organization. We recommended informing Security admins and Edge admins at your organization about this change to DLP features. You may want to update any relevant documentation.

MC1045278 — Microsoft Purview | Data Loss Prevention: New data protection in Microsoft Edge for Business on unmanaged devices

Microsoft 365 Roadmap ID 486366

Coming soon: Microsoft Purview | Data Loss Prevention (DLP) will be integrated in the Microsoft Edge browser to offer DLP protections that apply directly in the Edge browser and target scenarios where users on unmanaged (or bring-your-own/BYO) Windows desktop devices and Mac desktop devices are sharing data to or exfiltrating data from organization-managed cloud apps (apps that use Microsoft Entra authentication for user sign-in).

When this will happen:

Public Preview: We will begin rolling out late May 2025 and expect to complete by mid-June 2025.

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

How this will affect your organization:

After this rollout, admins can apply protections from Purview DLP that apply directly in the Edge browser to target user activities sharing data to or from Entra-managed apps, when the user is using Edge for Business on an unmanaged device.

Admins can configure Purview DLP to block or audit users when they perform activities including uploading or downloading files with sensitive information.

Admins can configure policies in Purview DLP to apply protections in the Edge browser and view outcomes for investigation in the Microsoft Defender portal.

This change will be available by default for Admins to configure in Purview. Features aren't activated by default.

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 assess the impact on your organization. We recommended informing Security admins and Edge admins at your organization about this change to DLP features. You may want to update any relevant documentation.

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

MC1045212 — Microsoft Purview compliance portal: Insider Risk Management user analytics

Microsoft 365 Roadmap ID 475058

Microsoft Purview Insider Risk Management will be rolling out a new user analytics feature to help Microsoft Defender, Microsoft Purview Data Loss Prevention, and Communication Compliance analysts access an insider risk summary of user activities.

When this will happen:

Public Preview: We began rolling out in late March 2025 and expect to complete by mid-April 2025.

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

How this will affect your organization:

With this new feature, Microsoft Defender, Microsoft Purview Data Loss Prevention, and Communication Compliance analysts with the right permissions can access an insider risk summary of user activities that may lead to potential data security incidents as a part of the alert investigation experience in Microsoft Purview and Microsoft Defender. This feature can help analysts gain insider risk context for a specific user and make more informed decisions about responses to potential incidents related to the user.

Insights are generated by Insider Risk Management for potentially risky behaviors of every user and are surfaced across the following experiences:

User activity summary in Microsoft Purview Data Loss Prevention alerts
User activity summary in Microsoft Defender alerts and user entity pages
User activity summary in Communication Compliance policies

What you need to do to prepare:

Insider Risk admins can enable user-level insights from Insider Risk Management Settings > Analytics. During the initial rollout, user analytics will be enabled for all customers who have enabled Insider Risk Management Analytics and will include an option to opt-out. Insider Risk admins should ensure data sharing is also enabled from Insider Risk Management Settings > Data Sharing.

Additional information is available here: Enable Analytics in Insider Risk Management.

MC1036579 — (Update) Microsoft Purview | Data Loss Prevention: A new Diagnostics experience in the new portal

Microsoft 365 Roadmap ID 469504

Updated April 23, 2025: We have updated the timeline below. Thank you for your patience.

Coming soon for Microsoft Purview | Data Loss Prevention: Admins will be able to view and manage Diagnostics in the new Purview portal. Before this rollout, diagnostics are only available through Microsoft PowerShell cmdlets.

When this will happen:

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

How this will affect your organization:

Admins can find the new experience at:

Purview portal> Information Protection > Diagnostics
Purview portal> Data Loss Prevention > Diagnostics

The PowerShell cmdlets will continue to be available after this rollout.

This new experience will be on by default.

What you need to do to prepare:

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

MC1035707 — Microsoft Purview | Endpoint Data Loss Protection (DLP): Blanket protections for unscannable file types (GCC, GCCH, DoD)

Microsoft 365 Roadmap ID 473460

Coming soon for Microsoft Purview | Endpoint Data Loss Protection (DLP): A new feature to apply blanket protection to unscannable file types. After you turn on this policy, you will apply this policy to files that cannot be scanned.

When this will happen:

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

How this will affect your organization:

With this new capability, Microsoft Purview DLP is now providing blanket protection for unscannable files. Learn more: Apply controls to all unsupported files

In Microsoft Purview, you can access this feature in Policy settings > Create policy > Create rule > Apply restrictions to only unsupported file extensions:

This feature is available by default for admins to configure.

What you need to do to prepare:

Learn more

MC1035703 — Microsoft Purview | Endpoint Data Loss Prevention: New Allow and Off modes for each activity (GCC, GCCH, DoD)

Microsoft 365 Roadmap ID 481356

Before this rollout, Microsoft Endpoint data loss prevention (Endpoint DLP) supports Audit only, Block, and Block with override on the Create policy page in Microsoft Purview | Endpoint DLP. This rollout will add two new modes: Off and Allow.

When this will happen:

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

How this will affect your organization:

The two new modes are:

Off: Endpoint DLP will not trigger events or Alerts and will not trigger notifications. You can use this enforcement mode to configure restrictions for a specific group.
Allow: Endpoint DLP will not trigger Alerts and will not trigger notifications but will trigger events in Activity explorer.

In Microsoft Purview, the new Allow and Off enforcement modes on the Create policy page for Endpoint DLP:

The new modes will be available by default for admins to configure.

What you need to do to prepare:

You will need these prerequisites to use the new modes:

All prerequisites in Onboard Windows devices into Microsoft 365 overview | Microsoft Learn
A Defender Antimalware client version higher than 4.18.25010. To find the version of Microsoft Defender (Windows Defender) Antimalware, follow these steps:
Open Windows Security.
Click on the Settings gear icon.
Look for the About link.
The About page contains the version information for the Windows Defender components.

MC1034582 — Microsoft Purview compliance portal: Endpoint Data Loss Prevention: "Paste to browser" prevention on macOS devices

Microsoft 365 Roadmap ID 483491

Microsoft Purview | Endpoint Data Loss Prevention (DLP) will soon add support for restricting users from pasting sensitive content into web browsers on macOS devices using Microsoft Edge, Safari, Chrome, and Firefox.

When this will happen:

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

How this will affect your organization:

After this rollout, if you have already configured DLP policies to prevent users in your organization from pasting sensitive content into a supported web browser on a Windows device, the policies will automatically apply to a supported web browser on macOS devices also.

This change will be available by default.

What you need to do to prepare:

Learn more: Learn about Endpoint data loss prevention | Microsoft Learn

MC1034577 — (Updated) Microsoft Purview compliance portal: Endpoint Data Loss Prevention: Full file evidence parity for macOS

Microsoft 365 Roadmap ID 483492

Updated April 22, 2025: We have updated the timeline below. Thank you for your patience.

Microsoft Purview | Endpoint Data Loss Prevention (DLP) will soon add support for copying an item that matches a DLP policy from onboarded macOS devices to a Microsoft Azure storage account. This rollout creates full file evidence parity for macOS.

When this will happen:

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

How this will affect your organization:

After this rollout, if you have already configured DLP policies for users in your organization to collect file evidence in Azure storage to protect Windows devices, the policies will automatically apply to macOS devices also.

This change will be available by default.

What you need to do to prepare:

Learn more: Learn about collecting files that match DLP policies from devices | Microsoft Learn

MC1031293 — Microsoft Purview | Endpoint Data Loss Prevention: New Allow and Off modes for each activity (GCC, GCC High, DoD)

Microsoft 365 Roadmap ID 481356

Before this rollout, Microsoft Endpoint data loss prevention (Endpoint DLP) supports Audit only, Block, and Block with override on the Create policy page in Microsoft Purview | Endpoint DLP. This rollout will add two new modes: Off and Allow.

When this will happen:

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

How this will affect your organization:

The two new modes will be:

Off:Endpoint DLP will not trigger events or Alerts and will not trigger notifications. You can use this enforcement mode to configure restrictions for a specific group.
Allow:Endpoint DLP will not trigger Alerts and will not trigger notifications but will trigger events in Activity explorer.

In Microsoft Purview, the new Allow and Off enforcement modes on the Create policy page for Endpoint DLP:

The new modes will be available by default for admins to configure.

What you need to do to prepare:

You will need these prerequisites to use the new modes:

All prerequisites in Onboard Windows devices into Microsoft 365 overview | Microsoft Learn
A Defender Antimalware client version higher than 4.18.25010. To find the version of Microsoft Defender (Windows Defender) Antimalware, follow these steps:
From your PC, open Windows Security
Click on the Settings gear icon.
Look for the About link.
The About page contains the version information for the Windows Defender components.

MC1028323 — Microsoft Purview | Insider Risk Management: New reporting capabilities (GCC, GCC High, DoD)

Microsoft 365 Roadmap ID 470027

Coming soon: Microsoft Purview | Insider Risk Management will introduce a central location for all reports, including analytics and user activity reports. New Alerts and Cases operational reports will summarize trends in alerts generated and cases created. Sample reports include alerts and cases generated over time, alerts actioned over time, alerts and cases generated by region and department, top triggering events of alerts generated, and average time to triage alerts and cases. Users with the admin, analyst, or investigator role will be able to access the new Alerts and Cases operational reports.

When this will happen:

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

How this will affect your organization:

To access the Alerts and Cases reports

In Insider Risk Management, go the new Reports page at https://purview.microsoft.com/insiderriskmgmt/reportingpage
Select Alerts or Cases
To drill deeper into each report, select View details

Access the new unified Reports page at https://purview.microsoft.com/insiderriskmgmt/reportingpage

To view new reports, Select Alerts or Cases on the Reports page:

Example of an Alerts report:

This feature is available by default to be configured by admins, analysts, or investigators.

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 and investigators about this change and update any relevant documentation.

Learn more: Use reports in insider risk management | Microsoft Learn

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

Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage, and security violations. Insider Risk Management enables customers to create policies based on their own internal policies, governance, and organizational requirements. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy.Post Coming soon: Microsoft Purview | Insider Risk Management will introduce a central location for all reports including analytics and user activity reports. New Alerts and Cases operational reports will summarize trends in alerts generated and cases created. Sample reports include alerts and cases generated over time, alerts actioned over time, alerts and cases generated by region and department, top triggering events of alerts generated, and average time to triage alerts and cases. Users with the admin, analyst, or investigator role will be able to access the new Alerts and Cases operational reports.

MC1026220 — Microsoft Purview | Endpoint Data Loss Prevention: Support for Just-in-time protection on MacOS devices

Microsoft 365 Roadmap ID 483354

Coming soon for Microsoft Purview | Endpoint Data Loss Prevention (DLP): You will be able to use just-in-time (JIT) protection to block all egress activities on monitored files while waiting for policy evaluation to successfully complete.

This message applies to macOS devices. For any organizations that have already configured DLP settings with JIT to protect Windows device, the policies will automatically apply to macOS devices also.

When JIT protection is enabled, and while policy evaluation is processing, Endpoint DLP blocks all egress activities for each user whose account is in the selected scope. Endpoint DLP audits the egress activities for all user accounts that have been excluded (via the Exclude setting) or are otherwise not in scope.

When this will happen:

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

How this will affect your organization:

This feature will be available by default for admins to configure. If your organization has already enabled JIT on your Windows device, your macOS devices will start getting the same protection.

What you need to do to prepare:

No change is required to your existing DLP settings.

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 on macOS devices about this change and update any relevant documentation.

Learn more: Using Endpoint DLP Just-in-time protection | Microsoft Learn

MC1025209 — Microsoft Purview compliance portal: New capabilities for Microsoft 365 Copilot

Microsoft 365 Roadmap ID 479082

Introducing a set of capabilities in Microsoft Purview designed to enhance data security and support compliance management for Microsoft 365 Copilot. These capabilities will be available once Microsoft 365 Copilot is deployed.

Copilot phased rollout:

Phase 1: Features already available with Purview capabilities as of December 2024, including Copilot Chat, Microsoft 365 App Copilot (Word, Excel, PowerPoint), Outlook Mail and Calendar, and Teams Chat/Channel Copilot.
Phase 2: Purview capabilities will be available once Teams Meeting Copilot, OneNote, Stream, Loop, SharePoint agents, and OneDrive for Business are deployed.

Purview capabilities - strengthening data security:

Copilot will honor sensitivity labels and content encrypted by Microsoft Purview Information Protection, including sensitivity label inheritance, citation, and honoring Extract usage rights.

Purview capabilities - supporting compliance management:

Capture events for Copilot prompts and responses using Microsoft Purview Audit.

Select and retrieve Copilot interactions when a user mailbox is selected as the source for a search query using Microsoft Purview eDiscovery. You can also perform existing reviewing actions and choose to export the review set or put them on hold.

Manage retention and deletion policies for Copilot prompts and responses using Microsoft Purview Data Lifecycle Management.

Analyze potentially risky communications in Copilot prompts and responses using Microsoft Purview Communication Compliance. This tool helps organizations detect business conduct and regulatory compliance violations (e.g., SEC or FINRA), such as sensitive or confidential information, harassing or threatening language, and sharing of adult content. Built with privacy by design, usernames are pseudonymized by default, role-based access controls are built in, investigators are opted in by an admin, and audit logs are in place to help ensure user-level privacy.

When this will happen:

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

How this will affect your organization:

These capabilities are meant to help you strengthen data security and compliance for Copilot.

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.

Licensing information:

Learn more:

Protect and manage Microsoft 365 Copilot interactions with Microsoft Purview

MC1024388 — (Updated) Microsoft Purview compliance portal: Modern eDiscovery enhancements

Microsoft 365 Roadmap ID 482558

Updated April 16, 2025: We have updated the content. Thank you for your patience.

We are excited to announce several enhancements to the recently launched modernized eDiscovery experience. These updates include:

Case Level Data Source View: Users can now access the case level data source view, which allows them to add data sources to the current case. These sources can be utilized in any searches or holds within the case.
Enhanced Search and Hold Capabilities: Users will have the ability to duplicate a search, create a search from an existing hold, or create a hold from an existing search within the current case.
Retry Failed Locations: The search statistics view now includes the option to retry failed locations, providing a more comprehensive search estimate.
Detailed Process Reports: We are adding information related to compliance boundaries, case/export/search names, and decryption settings into the relevant process report CSVs.

When this will happen:

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

How this will affect your organization:

eDiscovery users will start to see the relevant enhancements in the product, so internal documentation updates may be needed.

What you need to do to prepare:

Evaluate how this feature will impact your organization’s eDiscovery process and, if needed, modify your internal documents accordingly.

For more information, see Learn about eDiscovery solutions | Microsoft Learn.

MC1024387 — Microsoft Purview | Data Loss Prevention: New predicates for email DLP to detect number of domains or recipients

Microsoft 365 Roadmap ID 483158

Customers have expressed a significant pain point in managing and controlling the distribution of sensitive information in email. The lack of predicates to monitor the number of recipients or domains in outgoing emails poses a risk of data leaks and non-compliance with regulatory requirements. We are addressing this issue in Microsoft Purview | Data Loss Prevention by rolling out new predicates that will enable organizations to set precise policies that trigger alerts or actions when emails exceed a specified number of recipients or domains. This feature is essential for enhancing data security, ensuring compliance, and providing peace of mind to organizations concerned about unauthorized data dissemination.

When this will happen:

Public Preview: We will begin rolling out late April 2025 and expect to complete by mid-May 2025.

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

How this will affect your organization:

After this rollout, admins can use the new predicates in Data Loss Prevention > Policy settings > Create rule > Unique recipients greater than and Unique domains greater than to take action on emails based on the number of recipients or domains in the email:

This change will be available by default for admins to configure.

What you need to do to prepare:

Learn more: New-DlpComplianceRule (ExchangePowerShell) | Microsoft Learn (will be updated before rollout)

MC1006621 — (Updated) Microsoft Purview | Insider Risk Management: New compromised user context in Microsoft Entra

Microsoft 365 Roadmap ID 420938

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

Coming soon to Microsoft Purview | Insider Risk Management: IRM analysts will be able to identify if a user being investigated has any compromised user alerts in Microsoft Entra. The new visibility will help the analyst formulate the right response action, such as escalating the Incident to SOC teams for quick remediation.

When this will happen:

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

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

How this will affect your organization:

Microsoft Entra offers two types of compromised user detections:

Sign-in risk detections: Compromise risk associated with a specific sign-in
User risk detections: Compromise risk associated with a specific user

After this rollout:

Risk detections will be available in the indicator timeline in the alert investigation experience.
Risk detections will not impact the risk score or severity of Insider Risk Management alerts.

To access the new risk detections, go to Microsoft Purview portal > Settings > Insider Risk Management > Policy indicators > Built-in Indicators. Scroll down to Microsoft Entra ID Protection indicators, open the dropdown menu and select the applicable indicators.

When you create a policy, you will find Microsoft Entra ID Protection indicators on the Indicators page.

This change will be available by default.

What you need to do to prepare:

Insider risk management admins can opt into risk detections from Insider Risk Management global settings.
Insider risk management admins need to opt into risk detection in Insider Risk Management policies.

Learn more

MC1004410 — Microsoft Purview | Endpoint Data Loss Prevention - Classification improvements on file read access in macOS devices

Microsoft 365 Roadmap ID 478930

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

Data classification on files stored in macOS devices will be triggered automatically when handing files on read access to improve classification operations.

When this will happen:

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

How this will affect your organization:

Files that are stored locally on macOS devices will improve data classification whenever files are accessed and read. This system-level change is automatically happening for those macOS devices that have endpoint Data Loss Prevention (DLP) deployed and will not be visible to the end user.

For more information about items on targeted devices being automatically reevaluated the next time they're accessed or modified, see Best practice for endpoint DLP policies.

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.

MC999442 — Microsoft Purview | Data Lifecycle Management: Retention based on “last accessed” for OneDrive and SharePoint files

Microsoft 365 Roadmap ID 472030

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

Coming soon for Microsoft Purview | Data Lifecycle Management: Admins will be able to apply a retention policy or retention label in Microsoft OneDrive and Microsoft SharePoint for files that have not been accessed by anyone in your organization for a specified period of time. This message applies to retention for Microsoft 365 file types. We will support other file types (non-Microsoft 365) in a future rollout.

When this will happen:

Public Preview: We will begin rolling out mid-September 2025 and expect to complete by late September 2025

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

How this will affect your organization:

This feature will help delete obsolete data, which will improve the quality and relevance of Microsoft 365 Copilot responses.

This feature will be available by default.

After the rollout, admins can use the retention control When items were last accessed when configuring labels and policies.

What you need to do to prepare:

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

MC986518 — (Updated) Microsoft Purview | Insider Risk Management: Updates to email scoring (GCC, GCC High, DoD)

Microsoft 365 Roadmap ID 471010

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

Coming soon: Microsoft Purview | Insider Risk Management (IRM) will be rolling out updates to email scoring.

When this will happen:

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

How this will affect your organization:

Insider Risk Management email scoring logic is being updated. With current logic, a single email to multiple recipients is counted multiple times, and this is creating noise by increasing the risk score. In the new logic, a single email to multiple recipients is counted once, and this new principle is applicable to the email containing multiple unallowed domains or priority content. After this rollout, all email insights in Alerts will display the new count and score.

This change will be available by default.

What you need to do to prepare:

You can access the Insider Risk Management solution in the Microsoft Purview compliance portal.

Learn more: Configure policy indicators in insider risk management | Microsoft Learn

MC971035 — Microsoft Purview | Data Lifecycle Management: New secure workflow to bypass legal holds and retention policies

Microsoft 365 Roadmap ID 392838

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

This new feature enables data governance administrators to expedite the permanent deletion of sensitive content from Microsoft Exchange mailboxes, overriding any existing retention settings or eDiscovery holds. This process may be required for security or privacy, such as after a data spillage incident or for compliance and regulatory requirements.

When this will happen:

Public Preview: We will begin rolling out late February 2025 (previously early February) and expect to complete by mid-March 2025 (previously mid-February).

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

How this will affect your organization:

Priority Cleanup administrators can now set up a Priority Cleanup policy for Exchange to create exceptions to retention principles and e-Discovery holds for specific scenarios. Once administrators are within the Data Lifecycle Management (DLM) Solution on Microsoft Purview, they can visit the Priority Cleanup tab and follow the wizard to set-up this policy. Like auto-apply retention labels, Priority Cleanup supports policy simulation mode, so administrators can check the returned samples in case the policy configuration needs any fine-tuning before enabling the policy. Once set-up, because the deletion by a priority cleanup policy is irreversible and can override existing holds, the process requires multiple approvals, specific roles, and is audited. Thus, respective reviewers must be mandatorily added during policy creation to allow for disposition of items under a retention or e-Discovery hold.

What you need to do to prepare:

Because of the built-in safeguards, the feature itself is enabled by default at the tenant level. However, Priority Cleanup can be turned off on the Priority Cleanup settings page. If you can't create new Priority Cleanup policies, refer to your Data Lifecycle Management documentation for necessary roles and permissions requirements. A new role permission "Priority cleanup administrator" is now added to Purview role permissions to enable data governance administrators to use this feature.

MC950890 — (Updated) Microsoft Purview | Data Security Posture Management for AI

Microsoft 365 Roadmap ID 469509

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

Generative AI (GAI) is being adopted at an unprecedented rate. AI fuels innovation and productivity but also poses risks – organizations are concerned about the risky AI use and sensitive data loss through AI apps. Microsoft Purview Data Security Posture Management for AI (DSPM for AI) is a central location in Microsoft Purview that helps organizations secure data in AI, including Microsoft AI applications such as Microsoft 365 Copilot and non-Microsoft AI applications. With the DSPM for AI capabilities in Purview, organizations can safely adopt AI without having to choose between productivity and protection.

DSPM for AI also supports admin units and displaying AI policies that were created in Purview solutions. A version of DSPM for AI is available to additional licensing, specifically Microsoft 365 E3 and Microsoft 365 Copilot licenses.

When this will happen:

We will begin rolling out mid-March 2025 (previously late February) and expect to complete by mid-March 2025 (previously late March ).

How this will affect your organization:

DSPM for AI use cases

Viewing insights and analytics into AI activity in your organization.
Using policies to protect data and prevent data loss in AI prompts
Implementing compliance controls to apply optimal data handling and storing policies

Microsoft Purview DSPM for AI will be in the Microsoft Purview portal and will consist of 5 tabs: Overview, Recommendations, Reports, Policies, and Activity explorer.

This feature will be enabled by default.

What you need to do to prepare:

Get ready for this change by reviewing the admin documentation:

MC949003 — (Updated) Microsoft Purview | Data Loss Prevention: Gain policy insights with Microsoft 365 Copilot for Security

Microsoft 365 Roadmap ID 466740

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

As part of Microsoft 365 Copilot for Security in Data Loss Prevention (DLP), Policy Insights helps admins understand DLP policies and its constructs. This enhancement enables DLP admins to gain insights on coverage of policies on pivots like location, classifiers, and notifications.

DLP admins can get these insights on all the policies or on a few selected policies. They will be able to use prompts to gain a deeper level view of how a policy is configured for their digital landscape. This helps them align their data posture on a regular basis and make corrections to policy posture as needed.

When this will happen:

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

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

Currently, Copilot for Security is not designed for use by customers using US government clouds, including but not limited to GCC, GCC High, DoD, and Microsoft Azure Government. For more information, consult with your Microsoft representative.

How this will affect your organization:

Administrators can invoke the policy insights to understand the insights from all their policies or selected polices. The insights offered start with a higher-level view of how their policies:

are effective across locations.
detect the presence of sensitive information types throughout their digital estate.
notify administrators of violations.
educate users while they perform activities they should not.

These insights are offered with different pivots by location, classification, and by administrative scopes. This is offered to give the security policy administrators different views for deeper understanding of policy constructs and their impact.

Step 1:

Select the policies you wish to get insights/quick summaries about.

Step 2:

Click on the Get Insights with Copilot button. You will see the prompt is already pushed into the Copilot Experience in the side panel.

Step 3:

Copilot responds with insights on the selected policies.

What you need to do to prepare:

Admins can prepare by having Security Computer Units (SCUs). Copilot for Security is sold in a provisioned capacity model and is billed by the hour.

Get more information about SCUs: Get started with Microsoft Copilot for Security | Microsoft Learn.

MC937158 — (Updated) Microsoft Purview | Insider Risk Management: New scenario-based policy templates

Microsoft 365 Roadmap ID 409966

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

Coming soon to Microsoft Purview | Insider Risk Management: Two new preconfigured quick policy templates for Crown jewel protection and Email exfiltration. These templates are for admins who want to deploy scenario-specific policy templates with less configuration, to get started faster. The existing quick policies for Data leak and Data theft will continue to be available. You can find all four scenario-based quick policies in Insider Risk Management at Policies > Create Policies. Admins can expect additional turning after deploying these policies to meet individual alert volume needs.

When this will happen:

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

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

How this will affect your organization:

Sign in to Insider Risk Management with the admin role permissions
Go to the Policiespage at https://purview.microsoft.com/insiderriskmgmt/policiespage
Select Create policy
Select Quick policies
Select either the Crown jewel protectionpolicy or the Email exfiltration policy
Configure policy as applicable (add users to scope, optional priority content, and so on)

The new policies will be on by default.

What you need to do to prepare:

Learn more: The Quick Policies section in Create and manage insider risk management policies | Microsoft Learn

MC911618 — (Updated) Microsoft Purview | Insider Risk Management: Multi-policy settings in Adaptive Protection

Microsoft 365 Roadmap ID 171735

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

Protection is a feature in Microsoft Purview | Insider Risk Management that allows organizations to identify risky users and create dynamic policies in Data Loss Prevention, Conditional Access, and Data Lifecycle Management.

After this rollout, admins will be able to select multiple Insider Risk Management policies in the Risk levels for Adaptive Protection settings.

When this will happen:

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

GCC is complete.

How this will affect your organization:

Before this rollout, admins can select single Insider Risk Managment policies in the Risk levels for Adaptive Protection settings.

This new feature will be on by default and available for admins to configure.

What you need to do to prepare:

No action is required for this update. To configure user risk level for Adaptive Protection, admins can go to the Microsoft Purview compliance portal > Insider Risk Management > Adaptive Protection (preview) > Risk levels for Adaptive Protection

Learn more: Help dynamically mitigate risks with Adaptive Protection (preview) | Microsoft Learn

MC833890 — (Updated) Microsoft Word, Excel, PowerPoint: Protect sensitive files with dynamic watermarking

Microsoft 365 Roadmap ID 400717

Updated April 22, 2025: We have recently implemented the necessary fixes to expand the GA scope, enabling support for dynamic watermarking on labels with both user-defined and admin-defined permissions (the original scope).

Dynamic watermarking is a new sensitivity label setting that will add watermark text containing the consuming user’s information onto content in files created in Microsoft Word, Excel, and PowerPoint. This setting is supported for labels with admin-defined protection. Sensitivity labels from Microsoft Purview Information Protection help you classify and protect your organization's data. Learn more: (Preview) Dynamic watermarking for sensitivity labels in Word, Excel, and PowerPoint - Microsoft Community Hub

This message applies to Word, Excel, and PowerPoint on the web, Desktop/Windows, Mac, Android, and iOS platforms.

When this will happen:

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

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

The rest of the channels will follow in line with their normal cadence.

How this will affect your organization:

Before the rollout: Admins are not able to configure dynamic watermarking though sensitivity labels in Word, Excel, and PowerPoint.

After the rollout, refer to the admin documentation to configure dynamic watermarks in your tenant. This feature is off by default. Admins must configure the feature before it is accessible to users.

What you need to do to prepare:

Learn more

MC805721 — (Updated) Purview | Insider Risk Management: Adaptive Protection is generally available in GCC, GCCH, and DoD

Microsoft 365 Roadmap ID 335856

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

Coming soon: Adaptive Protection integrates the breadth of intelligence in Microsoft Purview Insider Risk Management with the depth of protection in Microsoft Purview Data Loss Prevention, to continuously and automatically fine-tune policies and protect data where and when it matters the most. The capability is built into the Microsoft platform with no endpoint agents required so organizations can get started using this as soon as it rolls out.

When this will happen:

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

GCC is complete.

How this will affect your organization:

Before the rollout: Admin are not able to configure custom definitions for insider risk levels in Insider risk managements or use insider risk levels as conditions in Data Loss Prevention (DLP) policies to apply dynamic controls to risky users.

After the rollout: Adaptive Protection is a capability of Microsoft Purview that enables organizations to dynamically optimize the balance between data protection and productivity. By leveraging the machine learning-driven analysis in Insider Risk Management, Adaptive Protection detects potentially risky user actions that may result in a data security incident and automatically adds the user to a stricter Data Loss Prevention (DLP) policy. The protection policies are adaptive based on user context, ensuring low-risk users can maintain productivity and high-risk users have appropriate protection in place.

What you need to do to prepare:

To begin using this capability, configure risk levels for Adaptive Protection in Insider Risk Management and add a new condition for risk levels for Adaptive Protection in new or existing DLP policies for Exchange, Teams, or Devices.

You can also set up Adaptive Protection using the one-click activation option from the home page of Microsoft Purview compliance portal. With one click, Adaptive Protection will create an Insider Risk Management policy based on aggregated risk insights of anonymized user activities in your organization, set your risk levels for Adaptive Protection, and create a DLP policy in test mode.

The default state of this feature is off.

Get started with Adaptive Protection in the Microsoft Purview compliance portal > Insider risk management > Adaptive Protection:

References

MC791110 — (Updated) Microsoft Purview | Data Lifecycle Management: New integration with Adaptive protection

Microsoft 365 Roadmap ID 392839

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

Coming soon for Microsoft Purview: We are announcing the public preview of the integration of Adaptive protection with Data Lifecycle Management (DLM) to help you find the right balance to protect against data sabotage while enabling productivity. This new integration leverages DLM features to provide an additional control for Adaptive protection that automatically preserves items deleted by a user with an elevated risk level, so items can be restored if needed.

When this will happen:

Public preview: We will begin rolling out in late June 2024 (previously early May) and expect to complete by late July 2024 (previously mid-July).

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

How this will affect your organization:

After the rollout, and after you enable Adaptive protection for your tenant, the retention label and auto-apply policy for data lifecycle management will be automatically created for you. This policy will automatically include elevated risk users identified by Microsoft Purview | Insider Risk Management solution. If these users delete content from Microsoft SharePoint, Microsoft OneDrive, or Microsoft Exchange, a retention label is automatically applied to that content to retain it for 120 days. Retention labels are automatically applied to unlabeled content deleted by these users. When these users are no longer at the elevated risk level, they are automatically removed from the DLM policy, and the system will no longer keep a copy of content they delete. Any content copies previously retained when the user had an elevated risk level will be kept for the 120 days as specified by the retention label.

Unlike other retention labeling scenarios, users do not see the retention label, and you do not need to create or manage the retention label or policy. At this time, you can't change the retention period or assign different policies based on the different risk levels, or for different locations. The single retention label and auto-labeling policy for your tenant is not visible in the Microsoft Purview compliance portal.

What you need to do to prepare:

Learn more: Learn about retention policies & labels to retain or delete | Microsoft Learn

If you're using Adaptive protection and want to automatically retain content deleted by elevated risk users, follow these steps to turn on this new integration.

Sign in to the Microsoft Purview compliance portal.
Navigate to Data lifecycle management > Microsoft 365 > Adaptive protection settingsin the top right corner.
Turn the setting ON and select Save.

If you’re not using Adaptive protection already, turn on Adaptive protection and the new feature will be enabled along with Adaptive protection.

MC788980 — (Updated) Microsoft Purview | Insider Risk Management: Granular trigger throttling

Updated March 28, 2025: After further review we have decided not to proceed with this change at this time. We apologize for any inconvenience.

Coming soon, Microsoft Purview Insider Risk Management will be rolling out public preview of granular trigger throttling limits.

When this will happen:

Public Preview: We will begin rolling out late October 2024 (previously late August) and expect to complete by late January 2025 (previously late October).

General Availability: We will communicate via Message center when we are ready to proceed.

How this will affect your organization:

With this update, we are introducing more granular trigger throttling limits to isolate the impact of a surge in noisy trigger volumes and prevent other policies from being affected. This ensures that organizations can receive critical alerts without being throttled by these limits. By default, these throttling limits will be applied:

All sensitive triggers, including HR signals, Azure AD leavers, and custom triggers, will be limited to 15,000 per day per trigger.
All other triggers will be limited to 5,000 per day per trigger.

Additionally, the policy health warning messages will be enhanced to assist admins with appropriate permissions in effectively identifying and addressing noisy triggers.

What you need to do to prepare:

No action is needed from you to prepare for this rollout. You may want to notify your admins about this change and update any relevant documentation as appropriate.

You can access the Insider Risk Management solution in the Microsoft Purview compliance portal.

Learn more: Insider risk management | Microsoft Learn

MC690178 — (Updated) Information Protection - Keyword highlight support for document trainable classifiers

Microsoft 365 Roadmap ID 170738

Updated April 28, 2025: To ensure the best customer experience, we have decided to rollout until October 2025. Thank you for your patience.

The keyword highlighting feature for Trainable Classifiers emphasizes the top 10 distinct keywords/phrases that influence the classification, showcasing up to 10 occurrences of each keyword.

The feature is being enabled through:

Content Explorer:

Viewing the classified document through Content explorer will highlight the keywords that match the Trainable classifiers detected.

Test Trainable classifier:

Uploading a document and testing it for a specific classifier OR selecting the document in the classifier’s matched item will highlight the keywords that match the Trainable classifier detected.

Note:

This feature will only work on the new/edited documents after the date “keyword highlight” has been enabled.

When this will happen:

Rollout will begin in early October 2025 (previously early June 2024) and will complete by late October 2025 (previously late June 2025).

How this will affect your organization:

The keyword highlight feature enables you to:

Quickly locate text that caused the positive outcome in the classifier.
Establish trust in the effectiveness of trainable classifiers.
Reduce the time to decide and take further actions.

What you need to do to prepare:

This feature will only work on new/edited documents after the date “keyword highlight” has been enabled.

Defender XDR

MC1048617 — Introducing new Advanced Hunting Tables to hunt on Teams messages and URLs

Microsoft 365 Roadmap ID: 487411

We are happy to introduce three new Advaned Hunting tables designed to facilitate hunting of Teams messages containing URLs within your organization.

The MessageEvents table enabled hunting across Teams messages containing URLs within your tenant. This includes both, known malicious messages blocked immediately after delivery and messages with no malicious content. Each message is uniquely identified by the TeamsMessageId, which can be utilized to establish joins across tables. As there is only a single copy of each message, even in instances of delivery to multiple recipients, only one instance of the message will be accessible for viewing in Advanced Hunting.
The MessagePostDeliveryEvents table provides the capability to analyze Teams messages containing URLs within your tenant, that have been identified as malicious after message delivery. If you have Zero-hour Auto Purge (ZAP) enabled for Teams, messages blocked post-delivery will be observable within this table. Each message is uniquely identified by the TeamsMessageId.
The MessageURLInfo table support the ability to hunt across URLs embedded within Teams messages in your organization.

The tables can be found under the Email & Collaboration in Advanced Hunting.

When this will happen:

Public Preview (Worldwide): We will begin rolling out late April 2025 and expect to complete by mid-May 2025.

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

How this will affect your organization:

You will now have the ability to hunt on Teams messages from Advanced Hunting.

What you need to do to prepare:

No additional action will be needed to prepare for this rollout. The new hunting tables will be available in your tenant and can be viewed with the right security permissions.

More information on these new tables can be found here:

MessageEvents: MessageEvents table in the advanced hunting schema - Microsoft Defender XDR | Microsoft Learn
MessagePostDeliveryEvents: MessagePostDeliveryEvents table in the advanced hunting schema - Microsoft Defender XDR | Microsoft Learn
MessageURLInfo: MessageUrlInfo table in the advanced hunting schema - Microsoft Defender XDR | Microsoft Learn

Microsoft 365 Copilot

MC1056992 — Pages created in Microsoft 365 Copilot Chat will open in Microsoft 365 Copilot app

Coming soon: Microsoft 365 Copilot Pages created in Microsoft 365 Copilot Chat will open in the Microsoft 365 Copilot app for the web. This change is designed to reinforce the Microsoft 365 Copilot app as the center for all content created with Copilot.

When this will happen:

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

How this will affect your organization:

After this rollout, users who search for Copilot Pages or select links to Copilot Pages will be taken to m365.cloud.microsoft where the link will open. For example, if a user shares a Copilot Pages link with another user in Microsoft Teams, that link will open in the Microsoft 365 Copilot app for the web.

Screen recording:

We will also update the Copilot Pages icon in this rollout. Left: The old icon. Right: The new icon:

This rollout applies to files created in Copilot Chat and files created by the user in My Workspace in Loop. This rollout will not change or affect Loop files created in Team chat, email, or in Loop workspaces.

Sensitivity labels for Copilot Pages are available now for Worldwide customers and will be available to GCC customers for Copilot Pages by late April 2025. Learn more about new Copilot capabilities coming soon:

Copilot Pages service description
What’s New in Microsoft 365 Copilot for Government

These changes will 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 the rollout. You may want to notify your users about this change.

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

MC1056264 — (Updated) Microsoft PowerPoint: Reference a TXT file when creating a presentation with Microsoft 365 Copilot

Microsoft 365 Roadmap ID 488795, Roadmap ID 488796, and Roadmap ID 488794

Updated April 18, 2025: After further review we have decided not to proceed with GCC at this time. We also have updated the rollout timeline below. We apologize for any inconvenience

When creating a presentation in Copilot for Microsoft PowerPoint, users will be able to reference TXT files in addition to Microsoft Word files.

A Microsoft 365 Copilot license is required to use this feature.

This message applies to PowerPoint for Windows desktop, PowerPoint for Mac desktop, and PowerPoint on the web.

When this will happen:

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

How this will affect your organization:

After this rollout, users can see TXT files when searching for files that Copilot can use to create a presentation. Select the Copilot icon from the PowerPoint ribbon, choose Create a presentation from [file], and search for TXT files by file name or paste the URL of your TXT file from Microsoft OneDrive or Microsoft SharePoint:

This feature will be available by default.

What you need to do to prepare:

Learn more: Create a new presentation with Copilot in PowerPoint - Microsoft Support (will be updated before rollout)

MC1052912 — (Updated) Microsoft Teams - Copilot Summary for Transferred Calls

Microsoft 365 Roadmap ID 484123

Updated April 28, 2025: We have updated the timeline below. Thank you for your patience.

Copilot enabled users will now be able to share the summary of the call from within the transfer panel and the context will be shown in the toast notification and within the call.

This feature requires a Copilot license to be enabled.

When this will happen:

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

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

How this will affect your organization:

Once available and if transcribe is enabled, users will be able to share a summary or a call from the transfer panel.

What you need to do to prepare:

You may consider updating your training and documenation. No admin configuration required other than allowing users to transcribe their calls.

MC1040542 — (Updated) Microsoft 365 Copilot and Microsoft 365 Copilot Chat: Increased transparency for web queries (GCC)

Microsoft 365 Roadmap ID 483965

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

Users with licenses for Microsoft 365 Copilot and Microsoft 365 Copilot Chat will soon be able to see the exact web search queries used by Copilot to generate its response with relevant web data. Users will see this feature if you enable web search.

Before this rollout, Copilot provided a list of websites that it used to generate its response. After this rollout, a user will also be able to review the exact queries sent by Copilot, which will enhance the user's awareness of how Copilot sourced the websites used to generate its response. Learn more: Introducing greater transparency and control for web search queries in Microsoft 365 Copilot and Microsoft 365 Copilot Chat | Microsoft Community Hub

This feature will be available for both Web and Work chats in Microsoft 365 Copilot and in Microsoft 365 Copilot Chat. For more information on Microsoft 365 Copilot Chat availability, please refer to MC1036580 Microsoft 365 Copilot Chat for GCC customers (published March 2025).

A Microsoft 365 Copilot license or an eligible Microsoft 365 license for Microsoft 365 Copilot Chat is required.

When this will happen:

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

How this will affect your organization:

This feature will be available by default if you have enabled web search. Learn more about managing web search in Copilot for your organization

What you need to do to prepare:

MC1036580 — (Updated) Microsoft 365 Copilot Chat for GCC customers

Microsoft 365 Roadmap ID 464984

Update April 25, 2025: We are currently preparing for availability. However, in a change to our original communication, we do not expect to complete the rollout of Copilot Chat in the GCC cloud until mid-May 2025. We will share more details as we can.

Beginning mid-May 2025, Microsoft 365 Copilot Chat (“Copilot Chat”) will be available by default at no additional cost for Entra account users with an eligible Microsoft 365 subscription:

Microsoft 365 F1, F3, G3, or G5
Office 365 F1, F3, G3, or G5

Copilot Chat will be available by default from the web. It will also be available and pinned by default in the Microsoft 365 Copilot app (web, desktop), Teams (web, desktop), and Outlook (web, desktop). If Copilot Chat availability for any of these entry points changes, we will inform you.

Web grounding in Copilot Chat will be off by default unless you have explicitly allowed for web grounding using the “Allow web search in Copilot” policy.

Note: This only applies to GCC cloud. Copilot Chat availability for GCC High and DoD will be communicated later.

When this will happen:

General Availability (GCC): We will begin rolling out mid-May 2025 (previously mid-April).

How this will affect your organization:

Users will be able to access Copilot Chat from the web, and in the Microsoft 365 Copilot app, Outlook, and Teams.

Copilot Chat offers:

Secure, enterprise-ready AI chat powered by models like GPT-4o.

o Note: Web grounding will be off by default unless you have explicitly allowed for web grounding using the “Allow web search in Copilot” policy. When web grounding is off, users will be alerted via a notification in the UI and Copilot will only use the LLM to provide a response.

IT controls for data governance, including enterprise data protection.

Note: Agents will not be available initially. Agent availability will be communicated later.

What you need to do to prepare:

Once Copilot Chat rolls out and is available in your tenant, you will be able to manage user access across entry points. To block access to Copilot Chat, refer to the documentation: Removing access to Copilot Chat.

To block access from the web, and in the Microsoft 365 Copilot app and Outlook, refer to Step 2.

To block access in Teams, refer to Step 3.

Note: As Copilot Chat will be pinned by default in the Microsoft 365 Copilot app, Outlook, and Teams once available, you do not need to implement Step 1. Additionally, Copilot Chat will not be available initially through the Microsoft Edge sidebar, so you do not need to implement Step 4.

Web grounding in Copilot Chat is off by default unless you have explicitly allowed for web grounding using the “Allow web search in Copilot” policy. To manage web grounding in Copilot Chat, please refer to our documentation here.

To help your organization get the most out of the Microsoft 365 Copilot Chat, we have updated the Copilot Success Kit and added the new Copilot Chat and Agent Starter Kit. This includes:

Copilot Chat user training guideto help your users get started with Copilot Chat and understand how to access it.
Copilot Chat and agent IT set up and controls guideto plan, deploy, manage, and measure Microsoft 365 Copilot Chat in your organization.
User engagement templatesin a variety of formats—including email, Viva Engage, and Teams—that you can leverage to communicate updates and new features to your users.

Note: You can customize these assets to remove content about agents since agents are not available initially.

Please also refer to documentation for Copilot Chat here: Overview of Microsoft 365 Copilot Chat

MC1036562 — (Updated) Microsoft 365 Copilot: Web chat access for GCC Tenants

Update April 16, 2025: We are currently preparing for availability. However, in a change to our original communication, we do not expect to complete the rollout of Web chat for Microsoft 365 Copilot-licensed users in GCC tenants until mid-May 2025. We will share more details as we can.

Starting mid-April 2025, Microsoft 365 Copilot-licensed users in GCC tenants will gain access to Web chat, alongside the existing Work chat, as part of their chat experience. Web grounding in Web chat will be off by default unless you have explicitly allowed for web grounding in Microsoft 365 Copilot using the “Allow web search in Copilot” policy.

When this will happen:

General Availability (GCC): We will begin rolling out mid-April 2025.

How this will affect your organization:

Microsoft 365 Copilot-licensed users will have access to Web chat starting mid-April. When web grounding is off, users will be alerted via a notification in the UI and Copilot will only use the LLM to provide a response in Web chat.

What you need to do to prepare:

Web grounding in Web chat will be off by default unless you have explicitly allowed for web grounding using the “Allow web search in Copilot” policy.

Learn more about the “Allow web search in Copilot” policy here.

MC1031286 — (Updated) Microsoft PowerPoint: Suggestions for slide templates

Microsoft 365 Roadmap ID 475053, 475054

Updated April 24, 2025: We have updated the timeline below. Thank you for your patience.

Updated April 8, 2025: We have updated this message to show as intended. The Roadmap items associated with this message have been updated. Additionally, we have determined that we will not be rolling out this change to GCC at this time. We apologize for any confusion this may have caused.

A new set of suggestions will soon be shown in Designer for Copilot users when creating a new PowerPoint presentation and adding a new slide.

Non-Copilot users will retain access to the standard Designer layouts provided to all Microsoft 365 users. Users with a Microsoft 365 Copilot license will see those standard Designer layouts and additionally, these new Copilot suggestions.

This message applies to Microsoft 365 Copilot in PowerPoint on Windows desktop and Mac desktop and to Microsoft PowerPoint on Windows desktop and Mac desktop.

When this will happen:

General Availability (Worldwide): This change will happen automatically with these three builds:

Microsoft 365 Copilot for Windows desktop build 16.0.18526.20000 (planned for release April 7, 2025)
Microsoft 365 Copilot for Mac desktop build 16.95.25030315 (planned for release April 21, 2025)
This feature will also be coming to Microsoft 365 Copilot for the web in early May 2025 (previously April).

How this will affect your organization:

Copilot users will gain access to new narrative-driven layout suggestions within the Designer pane when adding new slides.

Furthermore, a selection of new templates designed specifically for Copilot functionality will be available in Designer when starting a new blank presentation. Non-Copilot users will retain access to the standard Designer layouts provided to all Microsoft 365 users.

This change will be available by default for those with a Copilot license. Designer will continue to be available for non-Copilot users in PowerPoint as described in this message.

What you need to do to prepare:

Learn more

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

MC1031280 — (Updated) Microsoft 365 Copilot: Pages feature (GCC)

Microsoft 365 Roadmap ID 485177

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

The Pages feature enables users to add their Microsoft 365 Copilot responses to a page where they can edit and share with others for collaboration. This happens within the Microsoft 365 Copilot app.

For more information, see Introducing Microsoft 365 Copilot Pages - Microsoft Support.

When this will happen:

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

How this will affect your organization:

Users need to have Copilot Pages enabled for this feature update to work. Enabling this feature allows users to create Loop Page files via Copilot.

What you need to do to prepare:

For more information, see Copilot pages for IT Admins.

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.

MC1020327 — (Updated) M365 Copilot for GCC Environments: Wave 2

Microsoft 365 Roadmap ID 483357

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

Bringing Microsoft 365 Copilot GCC your AI assistant for work in the GCC environment. It combines the power of Large Language Models with your work content and context, to help you draft and rewrite, summarize and organize, catch up on what you missed, and get answers to questions via open prompts. Copilot generates answers using the rich, people-centric data and insights available in the Microsoft Graph.

We are excited to announce the release of the second wave of apps for M365 Copilot into the GCC environment. This release includes Stream, OneNote, SharePoint, and Pages in Copilot Pages, enhancing your organization's productivity and collaboration capabilities.

When this will happen:

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

How this will affect your organization:

As with the other M365 Copilot experiences released in December, the web grounding policy default is OFF for GCC. Web grounding in these new apps will follow the settings of the existing web grounding policy.

What you need to do to prepare:

A toggle is available in your admin center to enable and disable web grounding for M365 Copilot experiences. Please review your settings and make any necessary adjustments to align with your organization's needs.

For more information and resources, please visit: Data, privacy, and security for web search in Microsoft 365 Copilot and Microsoft 365 Copilot Chat.

MC1003344 — (Updated) Microsoft Copilot: File summary in Microsoft Teams chat

Microsoft 365 Roadmap ID 418564

Updated April 23, 2025: We have updated the timeline below. Thank you for your patience.

Users will be able to summarize files with Summarize for me using Microsoft Copilot within one-on-one or group Microsoft Teams chats. This feature will work on common file types like Word and PDF initially, and other file formats will be added over time. This summarization respects the file's security policies, ensuring that only users with access to the file receive a summary, which will carry the same sensitivity label as the original file. A Microsoft 365 Copilot license is required to use this feature.

When this will happen:

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

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

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

How this will affect your organization:

Users will be able to summarize files with Summarize for me in Copilot within Teams chats.

This feature will be available by default.

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.

Outlook

MC1058261 — New Microsoft Outlook: Changes to how shared mailboxes are displayed in the folder pane

Microsoft 365 Roadmap ID 486837

Coming soon for new Microsoft Outlook for Windows desktop: To align with the behavior of classic Outlook for Windows, we will display shared mailboxes in the same way accounts are displayed and add a Shared icon to give users a visual distinction between standard mailboxes and shared mailboxes.

When this will happen:

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

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

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

How this will affect your organization:

After this rollout, shared mailbox users and delegates will no longer have a Shared with me section in the folder pane on the left of the screen. Shared mailboxes and shared folders will display at the same level as accounts in the folder pane. Users will also see a teaching message pointing to the new shared mailboxes and shared folders, so users are not surprised by the change. Users will not lose any shared mailboxes or shared folders.

Left: The Shared with me section before the rollout. Right: After the rollout:

This change will be on by default.

What you need to do to prepare:

Learn more: Open and use a shared mailbox in Outlook - Microsoft Support (will be updated before rollout)

#newoutlookforwindows

MC1057715 — Outlook mobile: Edit a recurring event from a chosen date going forward by selecting 'This and all following events'

Microsoft 365 Roadmap ID 486835

Users can now edit a recurring event from a chosen date going forward by selecting This and all following events on Android or Edit this and all following events on iOS.

When this will happen:

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

How this will affect your organization:

Users can now bulk edit all future instances of a recurring event from a chosen date going forward. Anytime a user chooses to edit or cancel an event, they will see the This and all following events option on Android or Edit this and all following events on iOS. Previously, users would only see the option to Edit this event only or Edit all events in the series.

Android:

iOS:

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.

MC1056989 — Microsoft Outlook: New "Shared with me" page in Settings for shared email accounts and folders

Microsoft 365 Roadmap ID 486836

The new Microsoft Outlook for Windows and Microsoft Outlook for web will soon have a new Settings page called Shared with me where users can view and manage all shared email accounts and folders that they have been granted permission to access. Before April 30, 2025, we will update this post with new documentation.

When this will happen:

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

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

General Availability (GCC): We will begin rolling out early July 2025 and expect to complete by early August 2025.

How this will affect your organization:

After this rollout, users will be able to access the new page in Outlook Settings > Accounts > Shared with me:

If users have permission to access shared mailboxes or folders before this rollout, they will appear on this page. After this rollout, users can add new shared mailboxes and folders if their colleague has given them permission to access the mailbox and/or folders. User can remove shared mailboxes and folders from this page, but this action does not revoke permission granted by a colleague. If a colleague revokes a permission, the email account will remain on this page in a disabled state and will say that the user no longer has permission.

If your organization uses shared mailboxes, the Shared with me page will give users more insight into the permissions they have for shared mailboxes without needing to ask an admin or mailbox owner.

If your organization does not use shared mailboxes, this rollout will not impact you. The Shared with me page will be available for users, but it will stay empty if they do not add shared mailboxes or folders.

This change will be available to users by default.

What you need to do to prepare:

#newoutlookforwindows

MC1047925 — Outlook: open attachments while offline in the new Outlook for Windows

Microsoft 365 Roadmap ID 472026

We are adding more functionality to offline mode in the new Outlook for Windows. You will now be able to open and save attachments from your emails without an internet connection.

Please note that this is only scoped to classic file attachments. OneDrive and SharePoint links in the body of the emails will still need a connection to be opened.

For this functionality to work you need to make sure Offline is enabled and offline attachments are enabled.

At the user level you can verify this by checking two settings in new Outlook Settings - General - Offline:

Enable offline email, calendar and people
Include file attachments

This functionality will also be enabled or disabled based on the True/False behavior of the already existing Mailbox Policy: OWAMailboxPolicy- OfflineEnabledWin.

Attachments from emails within the timeframe and folder scope selected in the "Settings - General - Offline" will be synced and available locally for users to open without an internet connection.

When this will happen:

Targeted Release (Worldwide): We will begin rolling out on mid-May 2025 and expect to complete by late May 2025.

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

General Availability (GCC): We will begin rolling out on mid-July 2025 and expect to complete by late July 2025.

How this will affect your organization:

Classic attachments from emails within the timeframe and folder scope selected in the "Settings - General - Offline" will be synced and available locally for users to open without an internet connection:

What you need to do to prepare:

The default on or off of this feature will depend on your existing Offline configuration in the new Outlook via the following policy: OWAMailboxPolicy- OfflineEnabledWin. This feature will not change the default of this Policy. You can find more information about this Policy here: Set-OwaMailboxPolicy

If you have not made any changes to this Policy, then the default of this feature will be on.

MC1041465 — (Updated) New Microsoft Outlook for Windows and Outlook on the web: Optimized hover actions in the message list

Microsoft 365 Roadmap ID 429868

Updated April 28, 2025: We have updated the timeline below. Thank you for your patience.

In new Outlook for Windows and Outlook on the web, the hover actions in the message list will be moved to the Sender/From column to be more space-efficient and minimize unnecessary mouse travel for users with their Reading Pane set to Hide or Bottom. The large width occupied by the DateTime Received column will thus be reduced. For all users, a one-time shortcut to change/set your hover actions will be provided. After the changes to the hover actions, the first action will be replaced by a quick button (gear button) to change/set your hover actions. After that button has been triggered once, it will disappear, and your hover action settings will kick in fully.

When this will happen:

Targeted Release: We will begin rolling out mid-May 2025 (previously early April) and expect to complete by late May 2025 (previously late April).

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

How this will affect your organization:

For new Outlook for Windows and Outlook on the web, hover actions in the message list will be moved to the Sender/From column to reduce the large width occupied by the DateTime Received column.

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.

#newoutlookforwindows

MC1041456 — New Microsoft Outlook and Outlook for the web: New setting to enable two-click view for encrypted emails

Microsoft 365 Roadmap ID 483883

New Outlook for Windows desktop and Outlook for the web will soon support a two-click view for encrypted emails, which requires user confirmation before allowing access to encrypted emails. As an admin, you can enable the two-click feature for your users.

When this will happen:

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

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

How this will affect your organization:

With this two-click feature enabled, users will be required to select View message for every encrypted email, and then the email will render. This feature ensures that users deliberately access encrypted email content, reducing the risk of accidental exposure, especially in unsecured environments like public spaces or during screen sharing:

Admins can find the TwoClickMailPreviewEnabled setting in the Microsoft Azure directory. This setting is a Boolean type with default = 0, which means the experience is disabled by default. To enable the feature for all users in your tenant, set value = 1.

Alternatively, you can access and set the value for this setting using the Microsoft PowerShell cmdlet -Set-OrganizationConfiguration in the Microsoft Exchange Online PowerShell. Learn more: Exchange Online PowerShell | Microsoft Learn

By default, the two-click setting is off.

What you need to do to prepare:

No action is required from admins unless you want to enable this feature.

#newoutlookforwindows

MC1025213 — (Updated) Microsoft Outlook: Message recall in the Outlook app for iOS and Android

Microsoft 365 Roadmap ID 471444

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

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.

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 April 2025 (previously late March).

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.

MC997576 — Microsoft Outlook for iOS: Open the previous email with email auto-advance

Microsoft 365 Roadmap ID 477362

Note: If your organization does not support iOS users, you can ignore this message.

Coming soon to Microsoft Outlook for iOS: A new Open the Email Above setting to automatically open the message above the current one in the message list after performing actions like moving or deleting the current message.

When this will happen:

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

How this will affect your organization:

After this rollout, users can find the new setting in Outlook at Settings > Mail > Email Auto-advance > Open the Email Above.

We will also remove the Move to the Next Email setting.

Before the rollout:

Go back to the Inbox
Move to the Next Email

After the rollout:

Go Back to the Message List
Open the Email Below
Open the Email Above

What you need to do to prepare:

Learn more: Email Auto-Advance Setting - Microsoft Support

MC981624 — (Updated) Microsoft Outlook name change: "Outlook (new)" on Windows will change to "Outlook"

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

We are delaying this change until mid-March to allow time to for customer experiencing issues with classic Outlook shortcuts to use this workaround. Some customers may still see classic Outlook shortcuts listed as just "Outlook", which could lead to confusion when new Outlook's installed name changes. The workaround for this issue is documented here.

Coming soon: The installed name for new Microsoft Outlook for Windows will change from "Outlook (new)" to "Outlook."

This rollout comes after a change to the classic Outlook in version 2407, previously announced in MC803006 (Update) Outlook for Windows display name change (published June 2024, updated August 2024), which added "(classic)" to the installed name to differentiate the two apps.

When this will happen:

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

What you need to do to prepare:

This change will be on by default. This part of the app identity is not customizable for organizations.

As always, we recommend planning your organization's migration to the new Outlook using the resources at https://aka.ms/newOutlookAdoption

#newoutlookforwindows

MC962527 — Updated: New Microsoft Outlook for Windows and web: Delegates can create new categories for the account owner's Calendar

Microsoft 365 Roadmap ID 473997

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

Coming soon for new Microsoft Outlook for Windows and Outlook on the web: Delegates can create new categories on behalf of the account owner who granted them delegate permissions. Delegates can also apply categories to the Calendar of the account owner.

When this will happen:

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

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

How this will affect your organization:

To access the new capability, the account holder assigning the permissions should open:

Open their Calendar > Hover over a calendar name and select the three-dot More optionsmenu. Then, select Sharing and permissions.
Enter the email address of the desired delegate.
Select Delegate from the dropdown menu and check the box forLet delegate manage categories.Select Share.

After the account holder applies the necessary permissions, delegates can view the list of the delegator's categories in their Settings > Accounts > Categories and select the delegator's account from the dropdown menu.

This change will be available by default. The new checkbox for Let delegate manage categories will not be selected by default.

What you need to do to prepare:

Learn more: About delegates: Allow someone to manage your mail and calendar in Outlook - Microsoft Support (will be updated before rollout)

#newoutlookforwindows

MC947045 — (Updated) Microsoft Outlook for iOS and Android: Attach emails while composing an email

Microsoft 365 Roadmap ID 464206

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

Coming soon for Microsoft Outlook for iOS and Android users: In response to customer requests, we are rolling out the ability to attach emails directly in the compose window. This enhancement allows users to include individual emails as attachments in new messages, facilitating seamless sharing and providing more context for recipients.

When this will happen:

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

How this will affect your organization:

Before this rollout, users can forward emails as attachments but cannot attach emails while composing.

After this rollout, users will notice a new Attach email option when they select the paper clip attachment icon in the compose window. Users can select this option to browse for, choose, and attach individual emails to their new message.

This change is available by default.

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, update relevant documentation.

MC946791 — (Updated) Microsoft Outlook for iOS and Android: Minimize the compose window to multitask in the Outlook app

Microsoft 365 Roadmap ID 470304

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

Coming soon for Microsoft Outlook for iOS and Android: Minimize draft emails and quickly access them again from the message list or calendar view.

When this will happen:

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

How this will affect your organization:

Outlook will help you compose emails more quickly and efficiently by allowing you to minimize your draft emails and quickly access them again from the message list or calendar view. This means that while composing an email you can easily get information you need from your calendar or other emails and easily get back into the draft you are working on without ever having to go to the Draft folder.

To start, select the minimize icon in the upper right corner.

This change will be on by default.

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.

MC926892 — (Updated) Microsoft Outlook: Sync folder order

Microsoft 365 Roadmap ID 422816

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

The order of folders in Microsoft Outlook mobile will now sync to match the folder order on Outlook web, Mac, and Windows platforms.

When this will happen:

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

Users will now see an updated folder order on their mobile devices that reflects the folder order on Outlook web and desktop platforms. If users want to re-order the folders, they must do so on Outlook for the web, Mac, and Windows devices, as folder re-ordering is currently not supported on mobile devices.

This feature is on by default and cannot be turned off.

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.

MC917748 — (Updated) Microsoft Teams and Microsoft Outlook: Name pronunciation on the profile card

Microsoft 365 Roadmap ID 420329

Updated April 29, 2025: We have now shipped the admin control, the name pronunciation feature is OFF by default so admins will need to toggle it ON. The instructions in this support document explain how to turn the feature on.

Important! Starting from April 29, 2025, if you haven't turned the name pronunciation feature ON, any existing recordings on profile cards will be deleted. Your users will need to re-record their name pronunciation.

The admin toggle for Name Pronunciation is rolling out to Production starting this week. Admins will be required to configure in the admin center to avoid loss of data. Instructions to configure are in this support article. Please expect the admin toggle in the admin center starting the week of April 14th through April 18th, 2025.

We will be shipping to preview without the admin toggle however an admin toggle will be available before general availability. If there are concerns or your organisation wants to opt out, please raise an incident to address this.

Coming soon to Microsoft Outlook and Microsoft Teams: A name pronunciation feature on the profile card in Microsoft Teams and Microsoft Outlook. This new feature helps promote diversity by giving working colleagues relevant information about each other. Names are a crucial part of a person’s identity. The incorrect pronunciation of a person’s name can lead to anxiety and offense in some cases. Correctly pronouncing a person’s name helps to create an inclusive environment.

Pronunciation data is stored in each user's mailbox until the user deletes the recording. Learn more: Data Residency for Exchange Online - Microsoft 365 Enterprise | Microsoft Learn

This message applies to Teams for Windows desktop, Teams for Mac desktop, new Outlook for Windows desktop, and new Outlook for web.

When this will happen:

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

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

How this will affect your organization:

After this rollout, users can record and share the correct pronunciation of their name on their profile card. With a click, users can play and listen to name pronunciations recorded by their colleagues.

To open a profile card in Outlook, double-click a name in the To or From field in any sent or received email.

To open your profile card in Teams, select your profile photo in the upper right corner of the screen, and then select your name.

To listen to a colleague's recorded pronunciation, select the speaker icon on their profile card.

To record the pronunciation of a name, open your profile card in Outlook or Teams, and select the microphone icon.

What you need to do to prepare:

This feature is off by default. As an admin, you can enable the feature in Microsoft Graph using these instructions: namePronunciationSettings resource type - Microsoft Graph beta | Microsoft Learn

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

You may want to notify your users about this change and update any relevant documentation.

#newoutlookforwindows

MC901831 — (Updated) New Microsoft Outlook for web and Windows: Organize and reorder folders

Microsoft 365 Roadmap ID 378775

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

Coming soon: We will automatically import the folder order from classic Microsoft Outlook for Windows to new Microsoft Outlook for Windows and Outlook for the web. If users have not customized their folder order, the default view will continue to display folders alphabetically in the new Outlook.

When this will happen:

Targeted Release: We will begin rolling out late November 2024 (previously early October) and expect to complete by late December 2024 (previously early November).

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

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

How this will affect your organization:

Before this rollout: If a user enabled custom folder order in classic Outlook, the custom order is preserved in the new Outlook for Windows and Outlook on the web. This may result in changes to the folder structure for affected users, as the new Outlook supports only alphabetical ordering.

After this rollout: users will see the custom folder order they previously enabled in classic Outlook. Special folders such as Inbox, Drafts, Sent Items, and others will still remain at the top of the folder list, even when the rest of the folders are arranged alphabetically.

This change is on by default.

To change folder order, go to the new Outlook ribbon, and select View > Layout > Folder pane. Choose one of these options:

Order folders A to Z order: This will organize folders alphabetically
Custom order

Users can hover next to each folder name to see the three-dot menu where they can move folders with drag-and-drop or the move up/move down options:

What you need to do to prepare:

Learn more: Change the order of folders in the Folder Pane - Microsoft Support (will be updated before rollout)

MC847877 — (Updated) Microsoft Outlook for iOS and Android: Choose fonts while composing

Microsoft 365 Roadmap ID 409969

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

Coming soon for Microsoft Outlook for iOS and Android: We will add support for choosing fonts while composing emails. We will also improve support for fonts while reading emails.

When this will happen:

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

How this will affect your organization:

When this update rolls out, users will be able to select fonts to use in emails, signatures, automatic replies, and calendar invitations.

What you need to do to prepare:

You might want to notify your users about this new capability and update your training and documentation as appropriate.

MC799635 — (Updated) Microsoft Outlook: Add shared folders to Favorites

Microsoft 365 Roadmap ID 388913

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

Coming soon for new Microsoft Outlook for Windows and Outlook for web: Users will be able to add shared folders to their Favorites list in the top left corner of the screen. This message does not apply to Outlook for Mac or Outlook for mobile devices.

When this will happen:

Targeted Release: We will begin rolling out early February 2025 (previously early January) and expect to complete by early March 2025 (previously early February).

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

How this will affect your organization:

This new functionality will enable users to add shared folders and individual folders from shared mailboxes to their Favorites. This means that users can easily access important folders from shared resources or individual colleagues, directly from their Favorites. Users can share calendars, or folders that contain mail, contacts, tasks, or notes.

What you need to do to prepare:

Learn more: Open and use a shared mailbox in Outlook - Microsoft Support

MC714520 — (Updated) Apps for the web: Grid view for tasks in Microsoft To Do web version and To Do inside Microsoft Outlook

Microsoft 365 Roadmap ID 381749

Updated April 23, 2025: We have updated the timeline below. Thank you for your patience.

In Microsoft 365 apps for the web, users can see their tasks in a grid view and can update details inline in To Do on web and To Do app inside Microsoft Outlook.

When this will happen:

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

How this will affect your organization:

When users open To Do on web within Microsoft Outlook, they will see their tasks in a tabular format or grid. They can continue to have the list view if preferred.

What you need to do to prepare:

There is no action needed to prepare for this change. You may want to notify your users about this change and update any relevant documentation as appropriate.

Exchange Online / Defender for Office 365

MC1061102 — Microsoft Defender for Office 365: Auto-remediation of malicious URL and file clusters identified through AIR (preview)

Microsoft 365 Roadmap ID 186576

Coming soon: The automated investigation and response (AIR) capability in Microsoft Defender for Office 365 (MDO) will allow admins to configure auto-remediation of malicious entity clusters (for URL clusters and file clusters) identified by AIR. Auto-remediation expands on the existing capability provided through AIR by equipping customers to further expedite remediations through automation, to increase protection and reduce SOC workload. Auto-remediation will not be on by default and admins desiring to use the new automation will need to turn on auto-remediation for each cluster type in the new MDO automation settings page in Defender.

When this will happen:

Public Preview: We will begin rolling out early May 2025 and expect to complete by mid-May 2025.

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

How this will affect your organization:

After this rollout, admins will have a new MDO automation settings page in the Defender portal in Settings > Email & collaboration > MDO automation settings where you can turn on auto-remediation for malicious URL clusters and file clusters identified through MDO AIR:

After you have enabled the new feature, AIR will automatically execute the soft deletion of messages identified in malicious URL clusters and file clusters that remain in mailboxes.

Auto-remediated clusters will appear directly in Action center history for review. Also, messages remediated through AIR auto-remediation will be designated as attributed to automation in Explorer, in Advanced hunting and on the email entity page.

What you need to do to prepare:

Auto-remediation will be off by default. If desired, turn on as described in this message.

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

Learn more: Automated remediation in AIR - Microsoft Defender for Office 365 | Microsoft Learn.

MC1024399 — (Updated) Microsoft Exchange Online: New limit for dynamic distribution groups (DDGs)

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

We will soon introduce a new limit on dynamic distribution groups (DDGs) in Microsoft Exchange Online. Each organization will be limited to a maximum of 3,000 DDGs. After this limit is reached, admins will need to remove existing DDGs before creating new ones. Learn more: Exchange Online limits - Service Descriptions | Microsoft Learn

When this will happen:

General Availability (Worldwide, GCC): We will begin enforcing this limit in mid-April 2025 (previously early April).

How this will affect your organization:

If your organization has fewer than 3,000 DDGs, this change will not impact you. However, after your organization reaches this limit, you will not be able to create new DDGs until some existing DDGs are removed.

This change will be on by default and cannot be turned off by admins.

What you need to do to prepare:

The enforcement of the DDG limit will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your admins about this change and update any relevant documentation.

We recommend reviewing the usage of Dynamic Distribution Groups (DDGs) in your organization and removing any DDGs that are no longer needed. You can use the Dynamic distribution groups report in the Exchange admin center (EAC) to see the number of DDGs in your organization and insights into their usage. To access this report, go to the EAC > Reports > Mail flow > Dynamic distribution group report. Learn more: Dynamic Distribution Groups report in the new EAC in Exchange Online | Microsoft Learn

MC1023294 — (Updated) New Exchange Online Tenant Outbound Email Limits

Updated April 21, 2025: We have updated the timelines below. Thank you for your patience.

To reduce the risk of misuse and abuse of Exchange Online resources and ensure service availability for all users, we’ll soon introduce new tenant-level outbound email limits, known as the Tenant External Recipient Rate Limit or TERRL. The TERRL restricts the number of external recipients a tenant can send email to per day. If the limit is exceeded further messages sent to external recipients from the tenant will be blocked until the volume for the last 24 hours drops below the quota. A tenant’s TERRL quota is calculated based on the number of email licenses a tenant has purchased. Here is the formula used to calculate a tenant’s quota:

500 * (Purchased Email Licenses^0.7) + 9500

To help admins plan and track their outbound email volume, you’ll find a new report in the Exchange admin center: EAC > Reports > Mail flow > Tenant Outbound External Recipients Rate. This report shows the current volume of external recipients, your tenant’s daily quota, how much of the quota is used, and the number of recipients that were blocked if the limit was exceeded. The report will also show if enforcement for the limit is enabled or disabled. For example, for tenants who have more than 500 email licenses it will show “Disabled” until May 1st, the day we’ll start to enable enforcement for tenants who have more than 500 licenses.

When this will happen:

This change will roll out in progressive stages over the month of March as per the following rollout schedule:

How this will affect your organization:

If your tenant exceeds its daily outbound sending limit further messages sent to external recipients will be blocked and senders will receive one of the following bounce messages (also known as Non-Delivery Receipts or NDRs):

Trial tenants: 550 5.7.232 - Your message can't be sent because your trial tenant has exceeded its daily limit for sending email to external recipients (tenant external recipient rate limit)
Non-trial tenants: 550 5.7.233 - Your message can't be sent because your tenant exceeded its daily limit for sending email to external recipients (tenant external recipient rate limit)

What you need to do to prepare:

Check the report in the EAC to see your tenant’s quota and current daily outbound email volume and whether or not any messages will be blocked once the TERRL is enabled for your tenant. If your current outbound email volume is well below the quota, you don’t have to do anything. If your outbound email volume is near or exceeding your quota, consider using Azure Communication Services email for high-volume email to external recipients instead. ACS email which offers significant advantages and features for high-volume email, especially for external recipients. Messages sent using ACS email are not counted against your Tenant External Recipient Rate Limit quota.

For more information about the Tenant External Recipient Rate feature and report please see this blog post:

Introducing Exchange Online Tenant Outbound Email Limits

MC676299 — (Updated) Retirement of Exchange Web Services in Exchange Online

Updated April 18, 2025: We have updated the content. Thank you for your patience.

In 2018, we announced that we were no longer making feature updates to Exchange Web Services (EWS) in Exchange Online, and we advised developers to move to Microsoft Graph.

In September 2023, we announced that on October 1, 2026, we will start blocking EWS requests to Exchange Online.

We are now less than 18 months from October 1, 2026. We have made progress on closing several parity gaps with more changes in development to be released in the coming quarters. Please refer to Deprecation of Exchange Web Services in Exchange Online for up-to-date guidance and roadmap information.

If you haven't already, start the process of working with your application development organization and your application vendors to migrate active EWS applications on your tenant to the Graph API.

When this will happen:

October 1, 2026

How this affects your organization:

While the EWS components of the service will continue to receive security updates and certain non-security updates, product design and features will remain unchanged. This change also applies to the EWS SDKs for Java and .NET, as well.

Despite this announcement, EWS is still available and supported for use in production environments. But we strongly suggest migrating to Microsoft Graph to access Exchange Online data and gain access to the latest features and functionality.

Today’s update and the retirement of EWS apply only to Microsoft 365 and Exchange Online (all environments); there are no changes to EWS in Exchange Server. Further, the changes in Exchange Online do not affect Outlook for Windows or Mac, Teams, or any other Microsoft product.

In our original blog post, we said this change would affect only third-party (non-Microsoft) applications. We have expanded our effort and are now also removing EWS dependencies from Microsoft apps and services, and we’re going to complete that work well before October 2026. We intend to do this as quickly as possible without affecting the quality of service or product.

There may be applications running on your tenant created by your organization or 3rd parties that use EWS. We recommend reviewing your application portfolio now to get an understanding of which apps need to be updated by your organization and which applications require updates from vendors.

It is important to get started with this effort as soon as possible as the Graph API patterns are quite different from EWS. Equivalent Graph API operations may exhibit subtle differences that affect your use cases and application designs in unanticipated ways.

Migrating Applications to Microsoft Graph

We know there are several feature gaps between EWS and Microsoft Graph, and though the list below is not exhaustive, these are the gaps most frequently reported to us by developers:

Access to Archive Mailboxes – We are working on delivering access to archive mailboxes via Microsoft Graph and will provide an updated timeline in the coming months.
Folder Associated Information / User Configuration – We are working on these features and will provide an updated timeline in the coming months.
Exchange Online Management – We are investigating solutions for this and will provide an updated timeline in the coming months.
Access to Public Folders – After evaluating the usage of public folders, we have decided to restrict programmatic access to public folders to supported Outlook clients only, and for bulk import/export purposes. We will not provide APIs for programmatically creating, reading, updating and deleting public folders after October 2026 (also see Security Related Updates in Exchange Online).

We know there are other gaps not listed above, and we continue to work on closing them, but it’s possible some functionality will not make it to Microsoft Graph. We encourage you to refer to Deprecation of Exchange Web Services in Exchange Online for up-to-date guidance and roadmap information.

Next Steps

The retirement of these APIs follows our Modern Lifecycle Policy. We understand changes like this may cause some inconvenience, but we are confident it will ensure more secure, reliable, and performant experiences.

We will publish regular communications as we progress towards this deadline to aid affected tenants in identifying EWS usage. We encourage all customers to monitor Message Center and the Exchange Blog and Deprecation of Exchange Web Services in Exchange Online for related content.

Thank you in advance for updating and opening your apps to a wider range of useful and intelligent features on Microsoft Graph. We are extremely excited about the growing opportunities that Microsoft Graph offers to developers, and we remain fully committed to our journey to empower developers to access Microsoft 365 data with the most modern features and tools.

Microsoft 365

MC1060472 — (Updated) The new Microsoft Planner for the web (GCC High)

Microsoft 365 Roadmap ID 490567

Updated April 23, 2025: We have added the roadmap information. Thank you for your patience.

The new Microsoft Planner for the web brings together the simplicity of Microsoft To Do, the collaboration of Planner, and the power of Project for the web into a simple, scalable solution that spans individual task management to professional project management.

With this rollout, we will update the existing web version of Planner to the new Planner.

A Microsoft 365 license is required to use the new Planner. A Project Plan 3 license, Project Plan 5 license, or a premium Planner trial license is required to create premium plans.

When this will happen:

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

How this will affect your organization:

As part of our efforts to simplify Planner, these existing features are not available in the new Planner due to low usage:

Charts for pinned plans in Planner Hub
While you were awaynotifications
Activity log of a task’s creation, assignments, and completion date in the task comments
Links to group members, Microsoft Outlook conversations, and Microsoft OneNote notebook (you can still access these links in Outlook)
Menu option to Leave plan
Suggested attachments
Charts view and Schedule view on the Assigned to me page

Lastly, after the new Planner for the web is rolled out, users can still access Project for the web. For this rollout, we will merge notification settings in the new Planner and Project for the web. Users will see identical notification options in the two apps, and the settings they choose will be reflected across both apps. Until a user reviews their notification settings, we will maintain what the user had set before the notifications are merged.

The new Planner for the web:

What you need to do to prepare:

The new Planner is on by default for users with the required licenses. 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.
Please review our Planner blog announcementto update any internal documentation. We will update Planner help documentation in the coming weeks.
Supporting adoption resources: The new Microsoft Planner.

MC1060466 — Microsoft Excel: Python in Excel will be generally available in Excel for Mac (GCC)

Microsoft 365 Roadmap ID 489216

Python in Excel allows you to bring the capabilities of Python directly into the Microsoft Excel grid. With this rollout, Python in Excel with standard compute will be generally available in Excel for Mac.

MC980798 (Updated) Microsoft Excel: Python in Excel will be generally available in Excel for Windows (GCC) (published January 2025, updated February 2025).

When this will happen:

General Availability (GCC): We will begin rolling out to Excel for Mac mid-May 2025 and expect to complete by late May 2025.

How this will affect your organization:

After this rollout, eligible users will be able to add Python formulas to their workbooks without any installation required. These Python formulas will be run by Excel in a secure container on the Microsoft Cloud with enterprise-level security and with standard compute. With this release, eligible Excel users with a Microsoft 365 Copilot license will also be able to use the Copilot in Excel with Python feature, enabling them to leverage the capabilities of AI and Python in Excel for deeper data analysis.

Note: Some premium Python compute will be included with each user’s Microsoft 365 subscription each month, giving them limited access to faster calculation speeds. After they have used all their premium compute, they can continue to use the Python in Excel feature with standard Python compute. To get more premium compute, admins will be able to purchase the Python in Excel add-on license for their users after it becomes available later this year for GCC. We will send a separate message with the timeline for the rollout of the Python in Excel add-on license.

The Python in Excel feature will be enabled by default.

What you need to do to prepare:

To learn more about Python in Excel, please review the Python in Excel documentation. To learn more about data security: Data security and Python in Excel - Microsoft Support

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 relevant documentation.

MC1058303 — Reminder: Support for the Word Mobile, Excel Mobile, and PowerPoint Mobile UWP applications will end on October 14, 2025

Reminder: Support for the mobile Universal Windows Platform (UWP) apps (Microsoft Word, Microsoft Excel and Microsoft PowerPoint) will end on October 14, 2025. After that date, no further updates, security fixes, or technical support will be available for these applications.

We communicated this retirement in MC921113 Support for the Word Mobile, Excel Mobile, and PowerPoint Mobile UWP applications will end on October 14, 2025 (published October 2024)

When this will happen:

This retirement will occur on October 14, 2025.

How this will affect your organization:

If Microsoft Windows-based devices within your organization are running Word Mobile, Excel Mobile, or PowerPoint Mobile, we recommend that the applications be removed before the October 14, 2025, end of support date. While they may continue to function, using unsupported software could lead to potential security risks and other issues.

If you’re using Microsoft Intune, you can run a report to identify devices running these applications. In the Microsoft Intune admin center, go to All services > Apps | Monitor > Discovered apps and search for "office.word", “office.excel”, or “office.powerpoint”. The application version will start with "16001.14326.xxxxx.x".

What you need to do to prepare:

To mitigate these risks and ensure your organization remains secure and compliant, we recommend removing these three UWP applications and switching to alternatives:

Microsoft 365 Copilot mobile appfor iOS or Android phones and tablet devices
Word, Excel, and PowerPoint on the web. Learn more.
Windows desktop versions of Word, Excel, and PowerPoint in a Microsoft 365 plan. Compare Microsoft 365 Enterprise Plans.

Learn more about the end of support for the OneNote UWP application (OneNote for Windows 10): Moving to OneNote on Windows - Microsoft Support.

Planning ahead will help you avoid potential disruptions and keep your organization’s software environment secure and up to date.

MC1056996 — (Updated) Microsoft Excel: Extending support for Insights Services (GCC High, DoD)

Microsoft 365 Roadmap ID 488142

Updated April 28, 2025: We have updated the timeline below. Thank you for your patience.

Coming soon for Microsoft Excel: Support for the Analyze Data feature, which will be found on the Data tab

This message applies to Excel for Windows desktop, Excel for Mac desktop, and Excel for the web.

When this will happen:

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

How this will affect your organization:

Analyze Data can generate charts and graphs that may provide insights and answer questions you may have about your data:

This change will be available by default.

What you need to do to prepare:

Learn more: Analyze Data in Excel - Microsoft Support

MC1056260 — Support for Office 2016, Office 2019, and additional apps will end on October 14, 2025

As previously c ommunicated, support for Office 2016 and Office 2019 will end on October 14, 2025. After that date, no further updates, security fixes, or technical support will be available for these versions of Office. While the applications may continue to function, using unsupported software could lead to potential security risks, compliance risks, system incompatibilities, and other issues.

Support for Visio 2016 and 2019, Microsoft Project 2016 and 2019, and several other products will also end on October 14, 2025. Organizations using these products should upgrade as soon as possible to maintain security, compliance, and performance.

When this will happen:

Support for Office 2016, Office 2019, and additional apps will end on October 14, 2025.

How this will affect your organization:

After end of support, Office 2016 and Office 2019 suites, standalones, and servers will no longer receive security updates or other fixes, and no technical assistance will be available for devices still running them. Continuing to run unsupported software may expose your organization to security vulnerabilities and compliance risks, and may affect the reliability and performance of services.

What you need to do to prepare:

To mitigate these risks while maintaining access to desktop Office apps, we recommend upgrading devices to a Microsoft 365 or Office 365 suite that includes Microsoft 365 Apps (for enterprise or for business). Microsoft 365 Apps provides always-up-to-date versions of familiar apps like Word, Excel, and PowerPoint for desktop, mobile, and web with continuous support under the Modern Lifecycle Policy, and is eligible for use with the Microsoft 365 Copilot add-on.

For scenarios that require a fully disconnected solution, we recommend upgrading to Office LTSC 2024. Office LTSC 2024 includes a subset of the value in Microsoft 365 Apps and will be supported until October 2029 under the Fixed Lifecycle Policy.

Take steps to prepare for this transition with the following resources:

Read the upgrade guidancefor an overview of how to move from Office 2016 or Office 2019 to Microsoft 365 Apps.
Consider engaging Microsoft FastTrack, a Microsoft support service, for moving to Microsoft 365.

Plan ahead to avoid potential disruptions and keep your organization’s software environment secure and up to date.

MC1051092 — Microsoft 365 web app: Updated experience (DoD)

Coming soon: An updated experience for the Microsoft 365 web app at https://www.ohome.apps.mil

When this will happen:

General Availability (DoD): We will begin rolling out late May 2025.

How this will affect your organization:

This rollout includes these key changes:

Microsoft 365 apps that were pinned to the left navigation will be available in the Apps tab.
Profile and Settings buttons will move from the top right to the bottom left corner.
New content types and templates will be added to the Create tab.
Search bar will move from the top header to the Home tab.
Organization branding will be removed along with the top header.

The upgraded Microsoft 365 web app home page:

This change will be on by default.

What you need to do to prepare:

MC1051087 — Microsoft 365 web app: Updated experience (GCC High)

Coming soon: An updated experience for the Microsoft 365 web app at https://www.office365.us

When this will happen:

General Availability (GCC High): We will begin rolling out late May 2025.

How this will affect your organization:

This rollout includes these key changes:

Microsoft 365 apps that were pinned to the left navigation will be available in the Apps tab.
Profile and Settings buttons will move from the top right to the bottom left corner.
New content types and templates will be added to the Create tab.
Search bar will move from the top header to the Home tab.
Organization branding will be removed along with the top header.

The upgraded Microsoft 365 web app home page:

This change will be on by default.

What you need to do to prepare:

MC1047236 — Cloud Policy Service available to GCC-H and DoD customers

The Cloud policy service will begin rolling out for Microsoft 365 GCC-H and DoD customers early June 2025. The Cloud Policy service allows Microsoft 365 administrators to configure policies for Microsoft 365 apps and assign these policies using Microsoft 365 or Entra ID groups.

When this will happen:

General Availability (GCC High): We will begin rolling out on early June 2025 and expect to complete by early June 2025.

General Availability (DoD): We will begin rolling out on early June 2025 and expect to complete by early June 2025.

How this will affect your organization:

Once configured, these policies are automatically enforced as users sign in and use Microsoft 365 apps and services. The initial release will support policies for Microsoft 365 Apps for enterprise on Windows and future updates will bring support for additional applications and platforms.

What you need to do to prepare:

Review online documentation and implement as appropriate for your organization.

For additional information about the Cloud Policy service, refer to Overview of the Cloud Policy service for Microsoft 365 Apps for enterprise.

MC1041965 — Microsoft Excel: Python in Excel will be generally available in Excel for the web (GCC)

Microsoft 365 Roadmap ID 485764

MC980798 (Updated) Microsoft Excel: Python in Excel will be generally available in Excel for Windows (GCC) (published January 2025, updated February 2025).

When this will happen:

General Availability (GCC): We will begin rolling out to Excel for the web early May 2025 and expect to complete by mid-May 2025.

How this will affect your organization:

Note: Some premium Python compute will be included with each user’s Microsoft 365 subscription each month, giving them limited access to faster calculation speeds. After they have used all their premium compute, they can continue to use the Python in Excel feature with standard Python compute. To get more premium compute, admins will be able to purchase the Python in Excel add-on license for their users after it becomes available later this year for GCC. We will send a separate message with the timeline for the rollout of the Python in Excel add-on license.

An example of a Python formula in an Excel workbook:

The Python in Excel feature will be enabled by default.

What you need to do to prepare:

To learn more about Python in Excel, please review the Python in Excel documentation. To learn more about data security: Data security and Python in Excel - Microsoft Support

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 relevant documentation.

MC973511 — (Updated) Microsoft Purview | Data Lifecycle Management: Separate retention policies for Copilot and AI apps

Microsoft 365 Roadmap ID 470025

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

This new feature provides the capability for admins to configure separate retention policies for various Microsoft 365 Copilot and AI apps. As a result, admins will have the option to configure policies that can delete Copilot and Generative AI interactions faster.

When this will happen:

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

How this will affect your organization:

Organizations will now have controls to configure different retention policies for Microsoft Teams Chat, Copilot, Copilot studio, and ChatGPT Enterprise.

This feature is available by default.

What you need to do to prepare:

For more information, see Create and configure a retention policy.

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.

MC961557 — (Updated) Microsoft Search in Bing Deprecation

Updated March 10, 2025: There are additional details available regarding the Microsoft Search in Bing retirement.

Some Microsoft Search answers will no longer be available after March 31, 2025, including Q&As and location answers. Recommended bookmarks will also be retired; you can keep them by manually publishing or exporting them by April 30, 2025. Please see the FAQ for more information.
Work or school search history on Bing.com will be available through March 31, 2025. Individuals who wish to keep their recent search history must download it by March 31 by signing in with their Entra ID, going to Options on Bing.com, and selecting “Search history.” There is no control available for IT admins to download search terms on behalf of users.
To help users on Bing.com, a banner to redirect to M365.cloud.microsoft will be shown in Edge if search terms are high likelihood of being work-related. For more details, please see the FAQ available at Guidance for retiring Microsoft Search in Bing for your organization.
Note: Microsoft Edge version 134.0.3124.51+ is required for the work search functionality described below.

Microsoft Search in Bing, the search experience for work and school available on Bing.com, is being deprecated. The last day of its availability is on March 31, 2025. This change is being made as we streamline search experiences and focus on enhancing core productivity tools.

The Microsoft Edge for Business address bar and the Windows search box will continue to support work and school search, with some adjustments detailed below.

Details of the Change

After March 31, 2025, Microsoft Search in Bing will no longer be available, with changes as follows:

Bing.com will no longer show work or school search results. Consequently, there will not be a dedicated page of work or school results and users’ work or school profiles will no longer appear on Bing.com. However, selecting the Work or School tab on Bing.com will redirect users to the new Microsoft Search experience on M365.cloud.microsoft (formerly Office.com and Microsoft365.com).
Search boxes you’ve configured to point to Microsoft Search in Bing will no longer provide work or school results.
The Edge for Business address bar and Windows search box will continue to support work and school search with some adjustments, including:

o The Edge for Business address bar will no longer return work or school search results on a Bing.com page but will continue to provide suggested results in the address bar. In addition, the address bar will send users to work and school results on M365.cloud.microsoft rather than Bing.com. Users of the address bar can continue to find work-related documents, bookmarks, and people in suggested results—clicking on these suggestions takes users to work or school results on M365.cloud.microsoft. Users can also type "work" in the address bar, hit the tab key, then input their work- or school-related query to get results on a M365.cloud.microsoft page. Work and school search results will include documents, people, and bookmarks. Work search for documents will be available initially, with additional content types available as quickly as possible.

o The Windows search box will no longer display organization branding nor the “Work” or “School” tab but will continue to support work and school search. Search for documents and people remains available. will be available initially, with additional content types available as quickly as possible. With these changes, users will see some UX changes in the Windows search box.

As before, the core Microsoft Search experience remains accessible through M365.cloud.microsoft (formerly Office.com and Microsoft365.com) and SharePoint Online.

Additionally, Entra ID sign-in will no longer be available on Bing.com, since work and school search is no longer available on Bing.com.

An FAQ and further details are now available at Guidance for retiring Microsoft Search in Bing for your organization, which will be updated regularly.

When will this happen:

The last day of availability of Microsoft Search in Bing is March 31, 2025.

How this affects your organization:

For organizations using Microsoft Search in Bing, users will need to transition to using Microsoft Search through M365.cloud.microsoft (formerly Office.com and Microsoft365.com) and SharePoint Online.

Users who are accustomed to using the Edge for Business address bar and the Windows search box can continue to conduct work searches through these endpoints entry points, with the expectation that there will be some adjustment in these experiences after the deprecation date. (For details on changes, please refer to the FAQ: https://aka.ms/MSBFAQ.)

Users who click on suggestions in the Edge for Business address bar or Windows search box may be redirected to Microsoft365.com before March 31, 2025. Also, as we begin testing the retirement experience, a small set of users may find before March 31 that Bing is intermittently unavailable as an entry point for work search. We recommend that you proactively inform your users of the change and direct them to M365.cloud.microsoft (formerly Office.com and Microsoft365.com) and SharePoint Online. Adding M365.cloud.microsoft to their favorites or to the favorites bar in Edge for Business may be a helpful alternative pathway.

What you can do to prepare:

Customers should prepare to stop using Microsoft Search in Bing by March 31, 2025, and transition to using Microsoft Search through M365.cloud.microsoft (formerly Office.com and Microsoft365.com) and SharePoint Online. We recommend that you inform users about the upcoming change and the alternatives available.

Adding your preferred entry point from this set to favorites or favorites bar in Edge may be a helpful alternative pathway. Admins can easily set favorites in Edge for their organization, please see details here.

Additionally, users can continue to use the Edge for Business address bar and the Windows search box, with some changes expected. Please educate users that they should now type "work" in the address bar, hit the tab key, then type in their work-related query to get work results on a M365.cloud.microsoft page.

If your organization is using the AddressBarMicrosoftSearchInBingProviderEnabled policy today, you should update to the AddressBarWorkSearchResultsEnabled policy, if the policy is still needed.

The new policy, AddressBarWorkSearchResultsEnabled, will be available starting in early March, with Edge for Business version 134 (ahead of the Microsoft Search in Bing deprecation). This allows admins to configure the display of work suggestions in the address bar. If the policy is enabled or not configured, users who are signed into Edge for Business with their Entra ID can view internal work-related suggestions, such as bookmarks, files, and people results powered by Microsoft 365, in the Edge for Business address bar suggestion dropdown. If the policy is disabled, Entra ID signed-in users will not see internal workplace results in the Microsoft Edge address bar suggestion dropdown.

Admins who wish to set their own deprecation date prior to March 31, 2025, can turn off Microsoft Search in Bing by going to the Microsoft 365 admin center > Settings > Search & Intelligence.

Regarding SafeSearch settings:

If you had set the search experience for your organization to “School search,” SafeSearch was set to Strict by default. If you’d like to ensure that your users continue to have SafeSearch set to Strict after the Microsoft Search in Bing retirement, you can map www.bing.com to strict.bing.com at a network level. See Blocking adult content with SafeSearch or blocking Chat for more details.

Documentation - Office 365 IP Address and URL web service

April 30, 2025 - GCC

April 30, 2025 - GCC High

April 30, 2025 - DOD

Updated May 13, 2025

Version 1.0

Microsoft

Joined January 03, 2020

View Profile

Public Sector Blog

Follow this blog board to get notified when there's new activity

Blog Post

May and April 2025 - Microsoft 365 US Public Sector Roadmap Newsletter

The Future of AI in government / In Teams Phone assign shared lines, call queues, and call transfer key to line keys / Microsoft 365 Copilot Pages created in Microsoft 365 Copilot Chat will open in the Microsoft 365 Copilot app for the web

Purview

Exchange Online

Teams

Microsoft 365 Copilot

SharePoint Online / OneDrive for Business

MC1062451 — Microsoft SharePoint: Customize your sites with multi-color themes

MC1061109 — Microsoft SharePoint and Microsoft OneDrive: New PDF compression feature

MC1055557 — SharePoint Online: Content Security Policy Control in Tenant Administration

MC1055555 — Microsoft SharePoint Online: We will remove retired DISCO and WSDL web pages

MC1040544 — (Updated) Microsoft SharePoint: Enhancements to Restricted access control (RAC)

MC1040543 — Retiring "Shared with Us" Feature in SharePoint Teams sites

MC1034592 — SharePoint Online: Table toolbar

MC1031266 — Microsoft SharePoint: Microsoft 365 Copilot customers now have SharePoint Advanced Management capabilities

MC1028318 — Microsoft SharePoint Online Management Shell will replace IDCRL authentication protocol with OAuth

MC1026218 — (Updated) Microsoft OneDrive and Microsoft SharePoint: New annotation layout and tools for editing PDFs

MC1025216 — (Updated) Microsoft OneDrive: New naming convention for folder shortcuts

MC1024394 — (Updated) Microsoft SharePoint: New card animation feature for Pages, News, and Microsoft Viva Amplify

MC1017119 — (Updated) SharePoint: OneDrive and SharePoint – Protect PDF with password

MC1013464 — (Updated) We will remove the EEEU sharing permission from root web and default document library in OneDrive’s

MC1005510 — (Updated) SharePoint Online: Updates to Microsoft Lists forms

MC1002417 — (Updated) Microsoft SharePoint: The "spaces" feature will retire

MC989979 — (Updated) Microsoft SharePoint: New preview mode for Pages and News posts

MC974358 — (Updated) Microsoft SharePoint admin center: New "App insights" feature will be in Public Preview

MC922630 — (Updated) Microsoft OneDrive: We will remove the "EnableHoldTheFile" group policy

MC921916 — (Updated) Microsoft OneDrive: The Enable OCSI for Tenants group policy is being removed

MC912181 — (Updated) Microsoft SharePoint: Add approvals to any document library

Microsoft Viva

MC1056267 — Microsoft Viva Connections: New Folder card in Dashboard

Microsoft Teams

MC1062452 — Microsoft Teams: Join as attendees in Microsoft events from Teams Rooms on Windows

MC1061725 — Microsoft Teams: New DVR (digital video recording) capabilities for town halls on iOS and Android

MC1059676 — Microsoft Teams: Easily call in a presenter from the roster for town halls and webinars

MC1059675 — Microsoft Teams: Pop out live captions and Real-Time Text (RTT) in Teams meetings

MC1059674 — Microsoft Teams: Real-Time Text (RTT) in Teams meetings and calls

MC1059673 — Microsoft Teams: Expanded and enhanced peripheral auto-association support for Bring Your Own Device (BYOD) spaces

MC1059667 — Action required: Classic Microsoft Teams end of availability starts July 1, 2025

MC1057717 — Microsoft Teams Phones: Users can assign shared lines, call queues, and call transfer key to line keys

MC1057714 — Microsoft Teams: We will retire SMS invitations from Teams to external partners

MC1056977 — Microsoft Teams: Streamlined unified Role-Based Access Controls (RBAC) for Teams device management

MC1056268 — (Updated) Microsoft Teams Premium: Ultra-low latency (ULL) attendee experience for town halls

MC1052166 — (Updated) Microsoft Teams: Slide Control for PowerPoint presenters

MC1052163 — Microsoft Teams: Teams button support on multiple connected peripheral devices

MC1052162 — Microsoft Teams: Now available - new policy setting for Speaker Attribution in BYOD scenarios - Enabled ON by default

MC1047923 — Update: Ensuring Security and Compliance - Keep you Microsoft Teams desktop clients up to date

MC1047244 — (Updated) Microsoft Teams: New town hall event access policy

MC1045226 — (Updated) Microsoft Teams: Speaker recognition and attribution in Teams Rooms on Android

MC1045221 — Microsoft Teams: New user setting to view incoming calls in a small window

MC1045219 — (Updated) Microsoft Teams: Room Recommender

MC1045217 — Microsoft Teams Phone: Copilot-generated summaries for call transfers on Android devices

MC1045214 — (Updated) Microsoft Teams: New Chat and Channels experience (GCC)

MC1045213 — Microsoft Teams: New Chat and channels experience (GCC High, DoD)

MC1043473 — Microsoft Teams Rooms on Android: New local pan-tilt-zoom (PTZ) controls

MC1043466 — Microsoft Teams: Admins can deploy Custom Together Mode scenes (GCC, GCC High, DoD)

MC1043271 — Microsoft Teams in VDI: User uploaded custom background images for the new VDI solution

MC1041960 — Microsoft Teams: Standard and Basic licensed Teams rooms on Windows in the Teams admin center portal

MC1041461 — Microsoft Teams Premium or Microsoft 365 Copilot: New translated recap after multilingual meetings

MC1041460 — Microsoft Teams Premium or Microsoft 365 Copilot: Meeting transcription supports multiple spoken languages

MC1041451 — (Updated) Microsoft Teams for iOS/Android: New location sharing settings for emergency calls and more

MC1040545 — Microsoft Teams: Enhanced spell checking will support multiple languages

MC1038684 — (Updated) Prevent/Fix (Detected)Policy changes for Microsoft Teams devices using Device Code Flow Authentication

MC1036576 — Microsoft Teams: Share contact information for people in Microsoft Teams channels

MC1035710 — Microsoft Teams: Simplified Notes pane in meetings

MC1034566 — Microsoft Teams in VDI: Keep your Microsoft Teams desktop clients up to date

MC1028320 — (Updated) Microsoft Teams: Teams Rooms Pro Management portal will be generally available (GCC High)

MC1026225 — Microsoft Teams admin center: We will retire Graph connector management

MC1024383 — (Updated) Microsoft Teams: Update on changes to "csTeamsAIPolicy" (take action)

MC1022539 — (Updated) We are making changes to the Resource Account license requirement

MC1019312 — (Updated) Microsoft Teams: Meeting participants can request collaborative annotation sessions

MC1011152 — (Updated) Microsoft Teams: Updates to the Teams system tray icon and menu

MC1009932 — (Updated) Microsoft Teams: Add CVI (Cloud Video Interop) coordinates to town hall and webinar invitations

MC1009930 — (Updated) Microsoft Teams: Distinguish invites among Attendee, Presenter, and Co-organizer emails

MC1009929 — (Updated) Microsoft Teams: Join town halls using dial-in options and join codes

MC1006624 — (Updated) Microsoft Teams: Access chats while sharing a screen

MC1005513 — (Updated) Microsoft Teams: Direct routing call troubleshooting with the new "SIP call flow" diagram tool

MC1000269 — (Updated) Microsoft Teams: New keyboard shortcut for adding emojis

MC997581 — Windows 10 End of Support for Microsoft Teams Rooms on Windows

MC994287 — (Updated) Microsoft Teams: Webinars will be generally available (DoD)