Public Sector Blog

135 MIN READ

February 2025 - Microsoft 365 US Public Sector Roadmap Newsletter

Jesse_Tedoff

Microsoft

Mar 11, 2025

New location sharing settings for emergency calls in Teams, SharePoint Server 2016 and 2019 end of support July 2026, New Microsoft Volume Indicator for Teams

SharePoint

End of support for SharePoint Server 2016 and 2019 is scheduled for July 14, 2026. It's advisable to upgrade directly to SharePoint Server Subscription Edition

Purview Information Protection

New workload for Copilot in Content Explorer

Microsoft 365

New deployments of Microsoft 365 desktop client apps to include new Outlook – GCC

Unlocking Opportunities for Government Efficiency

The U.S. Federal Government stands at a critical inflection point, offering an unprecedented opportunity to redefine how it fulfills its vital missions. As leaders seek to reduce costs and enhance efficiency, much of this can be accomplished through thoughtful technology modernization applied to mission delivery.

Feb 21: Announcing M365 Community Days DC 2025 in Arlington

We are thrilled to announce M365 Community Days DC, hosted by DC area community leaders at the prestigious Microsoft Innovation Hub, Arlington VA at Rosslyn. Join us February 21st, 2025, for this in-person event featuring speakers from across North America, and headlined by elected official Roxy Ndebumadu, Councilmember for the City of Bowie, MD. Mark your calendars for a day of learning, networking, and innovation!

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

MC996585 — Microsoft SharePoint: Updated document libraries

Coming soon to Microsoft SharePoint: We will update the document library experience to improve its overall performance and enhance the functionality of Edit in grid view.

When this will happen:

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

How this will affect your organization:

After this rollout, users can expect these improvements:

Pages in document libraries will load faster.

Enhanced editing in grid view:

Choice field editing: Select or change values in Choice columns in grid view.
Person field and Group field editing: Assign users or groups to a file by selecting the Person field in grid view.
Image field editing: Add or change images in the grid, like the similar feature in Microsoft Lists.

Better scrolling with large libraries: Instead of going to the next page if there are more than 100 documents, users can scroll down and see everything.

New commands and navigation in grid view: With these improvements, grid view includes several new commands and navigational options that previously were either missing or less intuitive:

New commands: Create new items in grid view.
Clickable document titles: Document and file titles in the grid are now clickable, making it easier to open items without leaving the grid.
Folder navigation: Navigate in and out of folders from the grid view.

Details pane in grid view: Open the details pane in grid view.

Redesigned Properties pane and right-click menu:

Properties pane as a dialog: When you click or modify an item’s details, the properties pane appears as a dialog box.
Right-click context menu: Right-click any item in the grid and instantly see context-aware options such as Open, Edit, Share, or Delete.

Grouped view support while editing in grid view: Edit items in grid view even when the library is grouped by specific columns (such as grouped by a content type, department, or project).

Rating column improvements: If your document library includes a rating column (star ratings or “likes”), we improved the experience of updating and viewing these ratings.

A SharePoint document library with an item’s menu expanded (in grid view):

A SharePoint document library showing editing option in a field (in grid view):

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

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

Microsoft 365 Roadmap ID 473452

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 January 2025 and expect to complete by late February 2025.

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

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.

MC976819 — (Updated) Microsoft SharePoint: New Accessibility assistant tool for authoring Pages

Microsoft 365 Roadmap ID 470603

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

Coming soon for Microsoft SharePoint: A new Accessibility assistant tool to help content creators meet accessibility standards when authoring SharePoint Pages. This tool provides checks and brief guidance to help ensure pages are inclusive and accessible to a broad audience. This rollout reflects our ongoing commitment to fostering accessibility and inclusivity in SharePoint.

When this will happen:

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

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

How this will affect your organization:

After this rollout, authors can initiate an accessibility test while editing a page. Authors can select the Accessibility assistant icon from the right vertical toolbar. The Accessibility assistant will support five web parts: Banner, Text, Image, Hero, and Quick Links.

The Accessibility assistant identifies accessibility issues:

The Accessibility assistant guides authors to address accessibility issues in the specific web part:

The Accessibility assistant confirms the author has addressed all accessibility issues:

What you need to do to prepare:

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

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

Microsoft 365 Roadmap ID 417481

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

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

What you need to do to prepare:

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

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

MC974354 — (Updated) Microsoft SharePoint Online: Re-imagined Hero with the new carousel layout in pages and news

Microsoft 365 Roadmap ID 395214

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

We are introducing a new Carousel layout to make the Hero web part more attractive. This new layout will feature a slideshow and a selection of new styles with imagery, bold text, and a call to action, creating a more engaging page experience.

When this will happen:

Targeted Release: We will start rolling out in mid-January 2025 and expect to complete by mid-January 2025 (previously late January).

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

How this will affect your organization:

Adding a Hero web part to a page or news post has not changed. This update allows authors to create eye-catching carousel slides in any section type, with up to five slides in Carousel layout, enhancing user engagement and highlighting key content to establish page hierarchy. It offers three new styles and supports Stream videos to make the page more appealing.

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.

MC973514 — SharePoint Pages Flexible Sections

Microsoft 365 Roadmap ID 395213

Flexible sections are a new section type that allow authors to build pages without a strict column structure. Web parts can be dynamically resized and moved within flexible sections to create a fully customized section. Flexible sections unlock an endless number of design possibilities for sections.

With the introduction of flexible sections, we have reimagined section templates that are located in the content pane toolbox. The new section templates will be powered by both flexible and column-based sections with example content. All sample content from these templates is placed onto the canvas when a section template is applied.

The new flexible section type and section templates will be available in SharePoint and Viva Amplify.

When this will happen:

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

General Availability (Production, 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:

Users will see a new option when adding a section to a page, called “Flexible”. Within a flexible section, users can drag and drop web parts anywhere on the grid. Web parts will snap to the closest grid line when moved.

Users can also resize web parts. Card-based web parts, such as Quick Links, People, or Hero, only have four different width options (full width, 1/3 canvas width, ½ canvas width, and 2/3 canvas width). These web parts can only be resized to one of the four options.

Non-card-based web parts, such as Text, Image, and File & Media can be resized to any width. Web parts will snap to the closest gird line when being resized.

Users can resize flexible sections manually, change the arrangement of overlapping web parts, multi-select web parts, and group web parts.

Users can select or drag and drop a new section template from the content pane toolbox. After the template is added to the canvas, users can make adjustments to the web parts and section until ready to publish.

What you need to do to prepare:

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

MC973498 — Microsoft SharePoint: New "Editorial card" web part for Pages and News

Microsoft 365 Roadmap ID 414524

Coming soon to Microsoft SharePoint: a new web part for Pages and New posts called the Editorial card. Unlike automated web parts like News and Events, the new Editorial card allows SharePoint designers to manually tailor the content presentation to their needs.

When this will happen:

Targeted Release: We will start rolling out late January 2025 and expect to complete by mid-February 2025.

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

How this will affect your organization:

After this rollout, users can:

Showcase content in an engaging card format with advanced background and content settings
Configure content to suit varied author needs

This change will be available to users by default.

The Editorial card in the Web parts section of the Toolbox (right pane):

What you need to do to prepare:

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

Examples of Editorial card content:

MC947052 — (Updated) Microsoft SharePoint: Filter search results by "Messages"

General Availability (Worldwide, GCC, GCC High, DoD): This rollout has completed

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

The same Messages search vertical at microsoft365.com will soon be available for organization-wide search in Microsoft SharePoint. Search verticals are tabs on the search result page that show results of a specific type or from select sources. For example, the Files vertical shows results classified as files and makes it easy for users who are looking to find documents.

When this will happen:

General Availability (Worldwide, GCC, GCC High, DoD): This rollout has completed.

How this will affect your organization:

This feature will be on by default.

If you have disabled the Messages search vertical for microsoft365.com, the Messages search vertical will also be disabled in SharePoint. Learn more: Manage search verticals | Microsoft Learn

What you need to do to prepare:

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

Microsoft 365 Roadmap ID 420336

Updated January 16, 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 March 2025 (late January).

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:

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.

MC906496 — (Updated) Microsoft OneDrive and Microsoft SharePoint: New setting to disable presence in the file viewer

Microsoft 365 Roadmap ID 419814

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

Administrators can now use the Microsoft SharePoint Online Management Shell to disable the user presence feature in the Microsoft OneDrive and SharePoint file viewer on a per-site collection basis.

When this will happen:

General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late October 2024 and expect to complete by mid-January (previously December).

How this will affect your organization:

Before this rollout: When previewing a file in the OneDrive and SharePoint file viewer, users can see the presence of other users who have the file open. This behavior will not change by default.

After this rollout, if desired, SharePoint admins can use the SharePoint Online Management Shell to disable the presence feature for a given site collection. This can be done by updating to the latest version of the SharePoint Online Management Shell and running Set-SPOSite -HidePeoplePreviewingFiles $true along with a list of valid site identifiers. Learn more: Set-SPOSite (Microsoft.Online.SharePoint.PowerShell) | Microsoft Learn.

By default, this feature is available for admins to configure.

What you need to do to prepare:

MC693865 — (Updated) SharePoint Add-In retirement in Microsoft 365

Updated February 1, 2025: This update serves as a reminder that SharePoint Add-Ins will retire and stop working in 14 months from now (April 2, 2026).

Since the release of SharePoint Add-Ins in 2013, Microsoft has evolved SharePoint extensibility using SharePoint Framework (SPFx) enabling you to write applications that can be used in Microsoft SharePoint, Viva Connections and Microsoft Teams. With our continued investment in SharePoint Framework, Microsoft is retiring SharePoint Add-Ins.

Key Points:

Major: Retirement
Timeline:

o Starting July 1st, 2024, SharePoint Add-Ins cannot be installed from the public marketplace, also referred to as store by existing tenants. Installation from a private app catalog stays possible.

o Starting November 1st, 2024, new tenants will not be able use SharePoint Add-Ins, regardless of their origin (public marketplace, private tenant catalog).

o Starting April 2nd, 2026, Microsoft will remove the ability use SharePoint Add-Ins for existing tenants.

Action: Review and assess impact

How this will affect your organization:

If your organization still uses SharePoint Add-Ins, they will no longer function after April 2nd, 2026. We recommend customers to port their customizations to SharePoint Framework (SPFx) and ask their solution vendors for updated solutions.

What you need to do to prepare:

You will want to notify your Add-In users and developers. Update your user training and prepare your help desk.

For admins

Use the Microsoft 365 Assessment toolto scan your tenants for SharePoint Add-In usage.
Disable SharePoint Add-Inson your tenant using SharePoint Online Management Shell
Review the guidance for migrating from SharePoint Add-Ins to SharePoint Framework.
There will not be an option to extend SharePoint Add-Ins beyond April 2nd 2026.

New: How to disable SharePoint Add-Ins on your tenant

Admins can disable SharePoint Add-Ins with the Set-SPOTenant SharePoint Management Shell PowerShell command.

Connect-SPOService -Url https://<tenant>-admin.sharepoint.com

Set-SPOTenant -IsSharePointAddInsDisabled $true

After SharePoint Add-Ins are disabled, users will not be able to add SharePoint Add-Ins to their sites, and admins cannot add new SharePoint Add-Ins to the tenant and site collection app catalogs. SharePoint Add-Ins already added to sites will stay available and can still be used by the site's users.

New: SharePoint Add-Ins will not be available from the public marketplace

After July 1, 2024, users browsing the public marketplace (AppSource) will see SharePoint Add-In, but if they select Get it now, a message will explain that SharePoint Add-Ins are retired and cannot be added. If you still require a specific SharePoint Add-In, contact the Add-In creator to understand the possible options.

Learn more

Support update for the retirement of SharePoint Add-Insin Microsoft 365.

MC693863 — (Updated) Azure ACS retirement in Microsoft 365

Updated February 1, 2025: This update serves as a reminder that Azure ACS in Microsoft 365 will retire and stop working in 14 months from now (April 2, 2026).

Since the first use of Azure Access Control Services (ACS) by SharePoint in 2013, Microsoft has evolved the authorization and authentication options for SharePoint Online via Microsoft Entra ID (a.k.a. Azure AD). Using Microsoft Entra ID as auth platform for your SharePoint Online customizations will provide your applications the most secure, compliant and future proof model. With our continued investment in Microsoft Entra ID, Microsoft is retiring the use of Azure ACS as auth platform for SharePoint Online.

Key Points:

Major: Retirement
Timeline:

o Starting November 1st, 2024, new tenants will not be able use Azure ACS.

o Starting April 2, 2026, Microsoft will remove the ability use SharePoint ACS for existing tenants.

Action: Review and assess impact

How this will affect your organization:

If your organization still uses Azure ACS to grant custom developed or third party applications access to SharePoint Online, they will no longer have access after April 2nd, 2026. We recommend customers to update their customizations to use Microsoft Entra ID and ask their solution vendors to do the same.

What you need to do to prepare:

You will want to notify your Azure ACS users and developers. Update your user training and prepare your help desk.

For admins

Use the Microsoft 365 Assessment toolto scan your tenants for Azure ACS usage.
Review the guidance for migrating from Azure ACS to Microsoft Entra ID.
There will not be an option to extend Azure ACS usage for SharePoint Online beyond April 2nd 2026.

Learn more

Support update for the retirement of Azure ACS for SharePoint Onlinein Microsoft 365.

MC542767 — (Updated) SharePoint 2013 workflow retirement

Updated February 1, 2025: This update serves as a reminder that SharePoint 2013 workflow will retire and stop working in 14 months from now (April 2, 2026).

Since the release of SharePoint workflows, Microsoft has evolved workflow orchestration to not only encompass SharePoint, but all the productivity services you use with Microsoft 365 and beyond. With the continued investment in Power Automate as the universal solution to workflow, Microsoft is retiring SharePoint 2013 workflows.

When this will happen:

Starting April 2nd, 2024, SharePoint 2013 workflows will be turned off for any newly created tenants.
Starting April 2nd, 2026, Microsoft will remove the ability to run, or create and execute SharePoint 2013 workflows for existing tenants.

How this will affect your organization:

If your organization still uses SharePoint 2013 workflows, they will no longer function after April 2nd, 2026. We recommend customers to move to Power Automate or other supported solutions.

What you need to do to prepare:

You will want to notify your users, workflow developers and site owners. Update your user training and prepare your help desk.

For admins

Use the Microsoft 365 Assessment tool to scan your tenants for legacy workflow usage.
Review Guidance: Migrate from classic workflows to Power Automate flows in SharePoint
Review the Power Automate resourcesas a solution to legacy workflows.

Note: There will not be an option to extend SharePoint 2013 workflow beyond April 2nd 2026.

Learn more:

Detailed support articlewith additional resources.

Microsoft Copilot

MC981631 — Microsoft Teams: Microsoft 365 Copilot in Teams meetings will be generally available to GCC

Microsoft 365 Roadmap ID 476072

Coming soon for Microsoft Teams: We’re excited to announce that Microsoft 365 Copilot in Teams meetings will soon be available. This message pertains to Teams for Windows desktop, Teams for the web, Teams for Mac desktop, and Teams for iOS/Android.

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

When this will happen:

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

How this will affect your organization:

This rollout marks an important step in delivering Copilot in Teams meeting capabilities for your organization including:

Ask Copilot questions about the meeting in real-time and after meeting ends
Use out-of-the-box prompts for common tasks, such as generating a meeting recap, listing action items, capturing unresolved questions, or listing main ideas discussed in the meeting
Use Copilot during the meeting without retaining a transcript after the meeting
Generate Copilot responses based on both the spoken transcript and the written meeting chat

Here are key details to help you prepare and understand what to expect:

Teams admin center updates: Over the coming weeks, you may notice Copilot controls appearing in your Teams admin center. These controls will allow you to get familiar with how you will be able to manage Copilot in Teams in anticipation of the full rollout.
Functionality launch: We will start rolling out Copilot for Teams meetings to the Teams application in early February, but the Teams admin center controls may become visible earlier.
The Copilot in Teams setting in the Teams admin center will be ON (requiring transcript) by default.

Copilot in Teams will be available to users by default.

We appreciate your patience and understanding as we finalize this deployment. Our team is committed to ensuring a smooth experience for both admins and users.

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

Learn more

Microsoft Viva

MC989956 — Microsoft Viva: Edit and schedule polls in Viva Engage

Microsoft 365 Roadmap ID 467251

Starting in February 2025, customers with the Microsoft Viva suite or Microsoft Viva Communications and Communities premium licenses will see an option to schedule or edit a poll prior to publication.

When this will happen:

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

How this will affect your organization:

Before this rollout, users did not have a way to schedule polls in Engage.

After this rollout, premium-licensed users will have a new option in the publisher to schedule a poll post in the same location as other post types (discussion, question, praise, article). From their drafts, users can publish or edit a poll.

Users may also edit a poll prior to publication from their drafts. Users cannot edit poll posts, including voting options, after publication.

This feature will be available by default.

The new option to schedule or edit a poll prior to publication:

What you need to do to prepare:

This rollout will happen automatically by the specified date. There is no action for admins to enable or opt-in to this feature. 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: Write and schedule posts, articles, and announcements in Viva Engage - Microsoft Support

MC979826 — (Updated) Microsoft Viva Connections: Update to app name

Updated January 24, 2025: We have updated the content. Thank you for your patience.

We are renaming the Viva Connections app to Connections. This change is intended to ensure the app name fits better within Microsoft Teams, preventing it from being truncated.

When this will happen:

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

How this will affect your organization:

If you have already customized the Viva Connections app name in the Microsoft Teams app store, your customizations will remain unchanged.

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.

Microsoft Teams

MC996588 — Microsoft Teams: Adding and editing external contacts on Teams phone devices

Microsoft 365 Roadmap ID 476485

A new feature allows users to add and edit external contacts using the lightweight People app on Microsoft Teams phone devices. With this capability, you will be able to manage and interact with contacts outside of your organization on Teams phone devices.

When this will happen:

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

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

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

How this will affect your organization:

Users will now be able to add and edit external contacts from Teams phone devices.

To add an external contact:

Click Create new contact from the People app.
Add in the details of the external contact, and then click Save.

What you need to do to prepare:

Please ensure that your Teams phone devices are updated with the latest People app to get access to this new feature. This feature will only be available with the latest application update.

MC996587 — Microsoft Teams Voice: Link Voice apps without using resource accounts

We are excited to introduce a new feature in the Voice section of the Microsoft Teams admin center that allows admins to create linked Voice apps without needing to associate them with a resource account. This update simplifies the process of managing Auto attendant (AA) and Call queue (CQ) services.

When this will happen:

General Availability (Production): Available now.

How this will affect your organization:

After this rollout, in the Redirection options, you can select Voice app or Resource account to link AAs and CQs. Before this rollout, the Voice app option lets you link AAs and CQs using the resource account associated with them. If you prefer to use a resource account, you can still select Resource account:

Admins can use the using the Voice app option to create linked Voice apps without associating them with a resource account:

For example, this feature is useful when you want to create a call flow where multiple AAs and CQs are linked together. If you have an AA that needs to transfer calls to different departments, you can link it directly to multiple CQs without needing a separate resource account for each CQ.

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

Admins should review your existing AA and CQ setups and update them to take advantage of the new feature. Existing configurations will continue to work as before under the Resource account option.

Learn more

Manage resource accounts for service numbers - Microsoft Teams | Microsoft Learn(will be updated before rollout)
The Nested Auto attendants and Call queuessection in Plan for Teams Auto attendants and Call queues - Microsoft Teams | Microsoft Learn

MC994288 — Microsoft Teams: Speed dial on line keys for touch phone devices

Microsoft 365 Roadmap ID 476486

A new feature allows you to configure custom contacts and speed dial on the line key of touch phone devices certified for Microsoft Teams. It enables you to swiftly access frequently dialed numbers and contacts, incorporating one-touch/press dialing and easy management of contact lists on touch devices.

When this will happen:

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

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

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

How this will affect your organization:

Users will have the ability to use line keys on touch phone devices.

To assign line keys, tap on pre-defined placeholders and choose a contact to be added as a speed dial. Once you add a speed dial, you can make outgoing calls through one-touch/press on those line keys.

What you need to do to prepare:

Please ensure that your Teams phone devices are updated with the latest Microsoft Teams application. This feature will only be available with the latest application update. Lastly, for this feature to work, you will need to assign line keys on the device.

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

Microsoft 365 Roadmap ID 475279

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 late March 2025 and expect to complete by mid-April 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 the rollout. You may want to notify your users about this change and update any relevant documentation.

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

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

Microsoft 365 Roadmap ID 475853

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

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: Phones and Devices for Microsoft Teams - Microsoft Teams | Microsoft Learn

Before rollout, we will update this post with new documentation

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

Microsoft Teams will soon have a new location sharing setting that will allow users to grant location access to specific features. This change will affect emergency dynamic policy and the network bandwidth policy.

This message applies to Teams for Windows desktop (version 24H2 or greater) and Teams for Mac desktop. VDI clients will not be supported at this time.

When this will happen:

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

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

How this will affect your organization:

Before this rollout: Location access was governed exclusively at the operating system level. With this update, location consent will also be required from users at the individual application level. As a result, users gain more granular control over which specific application features can access their location.

After this rollout, Teams users can grant location access to certain Teams features. The setting for IT insights for admins feature are in Teams Settings > Privacy > Location. The setting for the Emergency calls feature is in the user's device's location settings. The user can find a link to their device's location settings in Teams Settings > Privacy > Location:

If a user consented to location access before the rollout, the user will be prompted to confirm their selection in this new popup that will display after the next Teams version update. If a user has not previously consented, they will not see the popup and can adjust their preferences in Settings.

What you need to do to prepare:

NOTE: After this rollout, dynamic emergency calling may not work as intended unless users allow location detection at the operating system level and app level. This dynamic emergency calling issue includes scenarios where admins have configured a network site for their users (location must be enabled by the user). To ensure emergency calls are properly routed to the nearest public safety answering point (PSAP), please advise your users to accept the new location requests from Teams. This also applies to users who may have consented to location access before the rollout.

You can communicate this requirement by setting the emergency service disclaimer with a custom message that will display in the Calls app in Teams. Ensuring that end users have location turned on is crucial for proper functioning of emergency calls and their safety. Learn more about sending a custom message: Manage emergency calling policies in Microsoft Teams - Microsoft Teams | Microsoft Learn

To continue managing video and media settings with the network roaming policy, users must enable Insights for IT admins in Teams Settings > Privacy > Location > Insights for IT admins.

Learn more about the changes to location services and privacy policies

Windows location service and privacy - Microsoft Support
Enable location sharing - Microsoft Support(will be updated before rollout)

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

MC989975 — Microsoft Teams: Occupancy status on Teams panels

Microsoft 365 Roadmap ID 474441

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 March 2025 and expect to complete by early April 2025.

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, presenting, whiteboarding, 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.

MC989974 — Microsoft Teams: New microphone volume indicator for users

Microsoft 365 Roadmap ID 468274

Coming soon for Microsoft Teams: A new Mic volume indicator on the user bar in Teams meetings. This feature will provide users with real-time visual feedback on their audio levels in the meeting, eliminating the need to ask, “Can you hear me?” This feature is designed to minimize interruptions as well as enhance user confidence and meeting effectiveness.

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

When this will happen:

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

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

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

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

How this will affect your organization:

This feature will be available to users by default and has no admin policy.

Users can select the Mic icon and review the Microphone section of the menu to find out more about their audio levels in the meeting:

What you need to do to prepare:

Learn more: Muting and unmuting your mic in Microsoft Teams - Microsoft Support

MC985484 — Microsoft Teams: Additional work information in people search results

Multi-tenant organization (MTO) users will be able to see additional work information in people search results. With this feature, MTO users will be able to see the company name and department name of a user in people search results, helping users to make sure they are communicating with the right people.

When this will happen:

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

How this will affect your organization:

Tenant admins who have MTO enabled will be able to toggle this feature on and off in the Teams admin center.

Toggle behavior:

This toggle will be off by default.
Turning on the toggle will enable the ability to see company name and department name in results.
Turning off the toggle will disable the ability to see company name and department name in results.

Instructions to toggle:

Navigate to the Teams admin center (TAC).
Navigate to the Teams Client Config page.
Using the Enable Extended Work Info in People Search toggle:

Switch the toggle to on to enable the ability to see company name and department name in results.

Switch the toggle to off to disable the ability to see company name and department name in results.

For more information, see Set up a multitenant org in Microsoft 365.

What you need to do to prepare:

Tenant admins will need to complete cross-tenant synchronization and sync the company name field in order to take advantage of this feature.

For more information, see Synchronize users in multitenant organizations in Microsoft 365.

MC981629 — Microsoft Teams: Updates to make meeting transcripts more accurate and reliable

Microsoft 365 Roadmap ID 471426

Coming soon to Microsoft Teams: Updates to make meeting transcripts more accurate and reliable. These improvements will also enhance the quality of live captions in Teams, Microsoft Copilot in Teams, and intelligent meeting recap for Microsoft Teams Premium users and users with a Copilot license, ensuring more accurate outputs and enhancing the overall experience of each feature.

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-February 2025 and expect to complete by late February 2025.

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

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

How this will affect your organization:

Key changes in this rollout:

Setting the meeting spoken language up front: Before starting features like Recording, Transcription, or Copilot that generate transcripts, users will be prompted to set the spoken language. Whether users enable these features manually or through Meeting options, this change ensures the transcription system starts with the correct language configuration.

Limiting who can change the spoken language for a meeting: When transcription is enabled, either on its own or as part of Recording or Copilot, only the meeting organizer, co-organizer, or the person who started the transcript will be allowed to change the spoken language. This ensures consistency and prevents issues caused by mismatched language settings. If transcription is not enabled, any meeting participant can change the spoken language.

Simplifying language settings: Language settings and caption customization options are on separate screens, instead of overwhelming users with all options in a single screen.

Identifying language mismatches: A Language mismatch detected notification will appear onscreen if the spoken language does not match the settings. Users can quickly resolve mismatches by confirming the system’s language suggestion directly from the notification, avoiding the need to navigate through settings.

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. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation.

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

MC980799 — Microsoft Teams: Allow presenters to moderate Q&A

Microsoft 365 Roadmap ID 469492

Coming soon for Microsoft Teams: Organizers of town halls and webinars will be able to select and assign presenters to also moderate the Q&A, allowing them to manage and publish questions asked during the event. This feature lets organizers make changes to the group of moderators at any time (before or during the event), and it is available to all users organizing a town hall or webinar.

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 late February 2025 and expect to complete by early March 2025.

How this will affect your organization:

This feature is supported for presenters with Microsoft Azure Active Directory (AAD) IDs. Presenters using consumer domains (such as live.com or gmail.com) are not supported.

Meeting organizers can enable this feature in Meeting options while setting up the event or during the event.

This feature will be available by default.

What you need to do to prepare:

Learn more: Q&A in Microsoft Teams meetings - Microsoft Support (will be updated before rollout)

MC979828 — Microsoft Teams: Cross-cloud collaboration in Virtualized Desktop Infrastructure

Microsoft 365 Roadmap ID 471434

Microsoft Teams Virtualized Desktop Infrastructure (VDI) users can join meetings with people in other Microsoft 365 cloud environments (e.g. a user in GCC High joining a meeting in Worldwide, GCC, or DoD environments) through three options:

Authenticated access via cross-cloud meeting connection.
Authenticated access using a guest account.
Anonymous access.

These scenarios require the new Slimcore-based optimization, since WebRTC-based optimization does not support meetings across different cloud environments.

For more information on the new optimization, see New VDI solution for Teams.

When this will happen:

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

How this will affect your organization:

For users who are already optimized with SlimCore in their VDI environments, after this feature is rolled out, cross-cloud anonymous and cross-cloud authenticated meetings will now open in Teams desktop client, and users with Guest Access in another cloud will be able to switch tenants via their Account picker in the Teams Settings UI.

What you need to do to prepare:

To access this new feature, enable the new VDI optimization based on SlimCore.

MC978932 — Large Events: End Session for Attendees and Return Presenters to Green Room

Microsoft 365 Roadmap ID 470432

Organizers and presenters can now end the session with this new "End Event" button for town halls, webinars, and structured meetings. After selecting this button, attendees will see a message on stage stating that the session has concluded, and presenters will return to the Green Room.

When this will happen:

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

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

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

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

How this will affect your organization:

When users join a town hall, webinar, or structured meeting with Green Room turned ON, they will now see the "End event" or "End meeting" button:

What you need to do to prepare:

This feature change will be available once it is fully released in your tenant.

MC975308 — (Updated) Microsoft Teams: iPad Multi-window support

Microsoft 365 Roadmap ID 467246

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

Teams now supports multiple windows on iPad. With this 'multi-window' feature, users can easily manage different Teams windows side-by-side, increasing productivity and flexibility.

When this will happen:

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

How this will affect your organization:

Apple's "split view" capability allows iPad users to have multiple applications and windows open side-by-side. Starting in February, Teams will now support the ability for there to be multiple Teams windows open at once. This makes it easier for users to attend a meeting and have their chat open on the other side or use Stage Manager to move windows to external displays.

This feature is available by default when users update the Teams app on iPad.

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.

MC975304 — Microsoft Teams: The Approvals app is generally available (DoD)

Microsoft 365 Roadmap ID 473448

The Approvals app in Microsoft Teams is a way to streamline requests and processes with a team or partners. Users will be able to create new approvals, view pending approvals, and see previous ones in one place.

Users with an F3 license or above can take advantage of the Approvals app in Teams:

Office 365 Government G1
Office 365 Government G3
Office 365 Government G5
Office 365 Government F3

If you do not have users that meet the licensing requirement, you may safely ignore this message.

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 (DoD): We will begin rolling out early February 2025 and expect to complete by mid-February 2025.

How this will affect your organization:

Approvals is a native Teams application that lets users easily create, manage, and share approvals from a hub for teamwork. These approvals are triggered directly with the Power Automate infrastructure and do not require a flow with an approvals action.

Users see all of their approvals in the hub, including the approvals that have been completed. Approvals show up across all of a user's systems, including Power Automate, SharePoint, and Microsoft Dynamics 365:

What you need to do to prepare:

The Approvals app is on by default if your tenant has enabled Microsoft Power Automate.

As an admin, you can manage the Approvals app in the Teams admin center on the Approvals app page, including customizing which users can access the app with permission policies. Currently, all approvals are created in your organization's default environment.

The Approvals app page in the Teams admin center:

Learn more

In October 2027, we will remove the option to specify the need for passcodes. This change will ensure that all meetings are consistently secured with passcodes. This final step will simplify the meeting creation process and provide an additional layer of protection for users. We will remove the isPasscodeRequired property on the joinMeetingIdSettings resource of the Microsoft Graph online meetings API.

MC974361 — (Updated) Microsoft Teams: Edit your display name in meetings

Microsoft 365 Roadmap ID 122934

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

In Microsoft Teams, while in a live meeting, participants will soon be able to edit their display name for the duration of the meeting. This name change is for the meeting duration only and does not affect a participant's original name on their People card.

This feature is available for participants using the Teams desktop and web apps for both Windows and Mac.

When this will happen:

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

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

General Availability (GCC High, DoD): 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:

The feature is off by default for all tenants. Admins can turn it on for their organization in the Teams admin center for all or selected tenant members. These members can then enable the feature in their private scheduled meetings.

If turned on for the tenant, a meeting organizer can turn the feature on for their meeting in Meeting options > Let people edit their display name. The feature is OFF by default in Meeting options and has to be enabled by meeting organizer.

If turned on for a meeting, participants can join the meeting and then select People at the top of the screen to edit their own display names in the Participants panel.

Example: Daniela Mandera can change her name in a meeting to Daniela M. (Before rollout, we will update this post with revised user documentation for changing the name.)

Participants who have edited their names will have an (edited) label next to their name in the meeting screens.

*Original People card names will display in some meeting features such as calendar invites, the list of people invited to meetings, group chat rosters, and so on.

Permanent meeting artifacts (such as the attendance report and transcriptions) will not reflect name changes.

What you need to do to prepare:

You can turn this feature on for your tenant users to allow the capability in the meetings they organize. You might want to notify your users about this new feature and update your training and documentation as appropriate.

MC973513 — Simplify UX flow to enable Together Mode

Microsoft 365 Roadmap ID 470427

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-March 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 — Microsoft Teams: New "Tag mentions" filter for the Activity feed

Microsoft 365 Roadmap ID 470598

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

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)

MC973497 — Microsoft Teams: The Updates app is generally available (GCC)

Coming soon to Microsoft Teams: Users can access the Updates app to streamline their daily reporting workflow and increase collaboration efficiency.

Users can use the Updates app to set up a daily or weekly reporting form and workflow to collect regular updates from others.

When this will happen:

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

How this will affect your organization:

Learn more about how to manage the app: Manage the Updates app for your organization - Microsoft Teams | Microsoft Learn.

This change is available by default.

What you need to do to prepare:

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

User documentation: Get started in Updates - Microsoft Support

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

Microsoft 365 Roadmap ID 473887

Updated January 24, 2025: We have updated the content. 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:

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

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 January 24, 2025: We have updated the content. 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:

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

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

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

Microsoft 365 Roadmap ID 423089

Updated January 24, 2025: We have updated the content. 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 mid-March 2025 (previously mid-February) and expect to complete by late March 2025 (previously late February).

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

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

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 January 28, 2025: We have updated the rollout 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 mid-March 2025 (previously mid-February) and expect to complete by late March 2025 (previously late February)

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

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

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 January 17, 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 early February 2025 (previously early January) and expect to complete by mid-February 2025 (previously mid-January).

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

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.

MC952888 — Microsoft Teams: Pop out Chat, Copilot, and Notes panes in meetings

Microsoft 365 Roadmap ID 421607

Coming soon: Users will be able to pop out the side panes for Notes, Chat, and Microsoft Copilot panes in Microsoft Teams meetings

Note: The Copilot pane is only available in Worldwide environments with a Microsoft 365 Copilot license.

When this will happen:

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

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

How this will affect your organization:

After the rollout, users will see a pop-out icon at the top of their Notes, Chat, and Copilot side panes in Teams meetings. This change will be on by default.

When users select the icon, the pane will pop out into a separate window that the user can resize and drag to their desired position, based on their screen setup and their productivity goals for the meeting. Users can view multiple meeting features at the same time, so they don’t miss the chat while they are monitoring meeting notes.

What you need to do to prepare:

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

MC950898 — (Updated) Microsoft Teams: Forwarding loop components

Microsoft 365 Roadmap ID 469507

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

There is now the ability to forward loop components in Microsoft Teams. With the addition of loop component forwarding, users have a new way to share loop components across chats and channels. To forward a message containing a loop component, simply navigate to the more actions menu of any message containing a loop component and select forward. From there, the forward this message dialog will populate, which provides users with a preview of the message being forwarded, including the loop component. In this view, users will be able to give permissions to recipients of the loop component to ensure all recipients have access to the content.

When this will happen:

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

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

How this will affect your organization:

Users will now have less restrictions when forwarding content. Previously, users were unable to forward messages that contained a loop component. With this improvement, no such restriction exists.

This update is available by default.

For additional information, see Forward a message in a Teams chat - Microsoft Support.

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.

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

Microsoft 365 Roadmap ID 468277

Updated January 28, 2025: We have updated the rollout 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 mid-March 2025 (previously mid-February) and expect to complete by late March 2025 (previously late February).

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)

MC939927 — (Updated) Microsoft Teams Premium: Decorate your background

Microsoft 365 Roadmap ID 419811

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

We will not release this feature to DoD at this moment. We are sorry for any inconvenience. We will share DoD timeline when available.

Microsoft Teams Premium users will be able to use the "Decorate your background" generative background effect in the GCC, GCC High, and DoD environments, leveraging gen-AI to augment real-life surroundings. It creates a personalized atmosphere for video calls.

When this will happen:

General Availability (GCC): We will begin rolling out in early March 2025 (previously early February) and expect to complete rollout by mid-March 2025 (previously late February).

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

General Availability (DoD): We will communicate via Message center when we are ready to proceed.

How this will affect your organization:

“Decorate your background” transforms meeting backgrounds by blending with a user’s real-life surrounding, creating a personalized atmosphere for video calls. It is available to Teams Premium users, and it is supported on Microsoft Windows and MacOS client now. There is not admin policy to disable it.

Users can access this feature in the following ways:

Before a meeting starts on the pre-join screen, select Effects and Avatars> Video effects > Decorate button. This will allow you to start generating new backgrounds.
During a meeting, select an animated background by clicking video flyout > More Video Effects and Setting > Decorate.

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.

MC932488 — (Updated) Microsoft Teams: New DVR capabilities for town halls (desktop and web)

Microsoft 365 Roadmap ID 422804

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

Coming soon for Microsoft Teams: New DVR (digital video recording) functionality for all town halls. This new feature will allow town hall attendees on Windows desktop or the web to interact with a live streaming town hall in the same way they would interact with recorded content. DVR functionality in the town hall enables event attendees to pause and move forward or back in a town hall, navigate to any previous timestamp, and other abilities, making it more convenient to interact with a town hall more and easier to digest the content being presented. This feature is available for Teams town halls from all organizers, regardless of the license assigned to the organizer.

When this will happen:

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

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

General Availability (GCC): 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:

After this rollout, the DVR controls will appear when attendees hover their mouse over the content being presented in the town hall. Attendees can:

Pause, play, and skip 10 seconds forward or backward
Control the volume of the content with the volume control
Jump to any point in time, starting from the beginning of the event
Catch up with the content and join the live event by selecting the Watch Livebutton next to the volume control

The DVR controls are at the bottom of the Teams window when the Q&A page is open on the right side.

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:

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

MC929034 — (Updated) Microsoft Teams: Best practices configuration dashboard in Teams admin center

Microsoft 365 Roadmap ID 421185

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

Coming soon to Microsoft Teams: With the Best practice configurations monitoring dashboard in the Teams admin center, Teams admins will be able to monitor the conformance of your tenant to the Microsoft recommended best practices for an optimal collaboration experience on Teams.

When this will happen:

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

How this will affect your organization:

Ensuring the quality and reliability of user's collaboration experience using Teams is crucial (specially the meeting-related experiences). Microsoft recommends best practices to ensure that organizations have an optimal environment setup for collaboration.

The Best Practice Configurations monitoring dashboard will assist admins in understanding their tenant’s non-conformance with these best practices, the overall impact, and how to comply with these recommendations.

You'll find the Best practice configurations dashboard in the Meetings section of the Teams admin center. In this release, we’ll monitor and highlight non-conformance in three key areas:

Update out-of-date client versions
Enable the right ports and protocols
Implement split tunnelling for VPNs

If a location does not adhere to these best practices, it will be highlighted on the dashboard. A widget on the main dashboard will also spotlight non-conforming practices. Also, a list of subnets/IP addresses will be displayed by city, showing the extent of non-conformance for each location. This list can be exported to share with relevant teams, and recommendations for addressing these issues will be available on the same page.

As these issues are resolved, the trend of non-conforming locations will be tracked to help monitor progress.

This new dashboard will be available by default.

What you need to do to prepare:

Administrators do not need to do anything to prepare for these changes. They will take effect automatically.

You may want to notify your admins about this change and update any relevant documentation.

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

MC923415 — (Updated) Microsoft Teams: Virtualized Desktop Infrastructure status indicator

Microsoft 365 Roadmap ID 423472

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

This new feature is designed to be a visual indicator of the optimization status in Microsoft Teams for Virtualized Desktop Infrastructure (VDI) users.

Users in VDI used to rely on the ellipsis (...) > Settings > About menu to display the optimization status for their session (AVD Media Optimized, Citrix HDX Media Optimized, VMware Media Optimized).

The new status indicator will provide the user with an easy-to-understand status message, like "Optimized" or "Not Optimized", some contextual information about the optimization mode (optimized with the WebRTC-based solution or the new SlimCore-based solution), and in the not optimized case it will provide a brief description of the problem and an error code, for better supportability.

When this will happen:

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

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

How this will affect your organization:

Once this feature is rolled out, users will be able to quickly understand whether their audio/video is optimized for virtual desktop environments (offloading to the endpoint/user's device) before joining a meeting and take actions to fix problems or report back to their IT support with an error code.

This feature is available by default.

What you need to do to prepare:

As this feature introduces new UI components, admins should update their internal documentation and communications so that end-users understand the new status indicator feature.

MC920179 — (Updated) Microsoft Teams: The new streamlined Chat and Channels experience

Microsoft 365 Roadmap ID 415249

Updated January 17, 2025: We have updated the content. Thank you for your patience.

Thank you for your engagement with the new chat and channels experience in Teams.

The new chat and channels experience has been in Public Preview and Targeted Release since November 2024 and was targeted for General Availability starting in late January 2025. Based on requests from customers to have additional time to prepare their organizations for the change, we will be postponing the rollout to General Availability from January to a later date.

The GA rollout date is updated to starting late March 2025.

We’ve been listening to user feedback on the pace of work and the challenges of keeping up with conversations, managing messages scattered across different locations, and triaging quickly. To address this, we’ve streamlined the chats, teams, and channels experience to make it easier for users to stay on top of what matters most.

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, Mac desktops, the web, and 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:

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

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

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

How this will affect your organization:

Before this rollout, users have separate Chat and Teams views (apps) with no option to unify these views; custom sections of chats and channels were not possible; and there was no view for collecting all personal mentions in one list across chats and channels.

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.

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 /go to: 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, 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.

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.

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 will be available on the adoption web page The new Microsoft Teams chat and channels experience before rollout begins.

For admins who opt in to emails for recommended Microsoft 365 training, an email for users will summarize the update when released.

MC920084 — (Updated) Microsoft Teams: Usage reports for bookable desks

Microsoft 365 Roadmap ID 421604

Updated January 28, 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 February 2025 (previously late January).

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)

MC918570 — (Updated) Microsoft Teams: Custom name on Teams panels

Microsoft 365 Roadmap ID 417153

Updated January 14, 2025: We have updated the content. Thank you for your patience.

Prior to this new feature, the display name on a Microsoft Teams panel could not be customized. It would always match the Global Adress Book (GAL) name for the account that is shown in Teams and Outlook. With this rollout, we will be providing admins with the ability to customize this display name. This feature will be supported for accounts that have a Teams panel and a Teams Rooms Pro or Teams Shared Device license.

When this will happen:

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

How this will affect your organization:

An admin must choose to use the feature. This feature is set to off as default, so there is no change to the current experience otherwise.

To change the display name on the panel, navigate to Teams Rooms Pro Management Portal > Planning > Inventory and then click on the account you’d like to customize. On the pane that opens on the right, there will be a custom name field which an admin can edit to enter in the new display name. Please note that the custom name will be displayed on the Teams panel home screen, so we recommend making sure it is clear and understandable to your users. By default, this field will be filled with the GAL name. In addition, please note that this will not change the display name shown on Microsoft Teams Rooms if you have one inside of the room.

Within 24 hours of the name being updated, the Teams panel home screen will reflect the new name. The home screen will also have a tooltip that, when selected, will show the user the GAL name.

In Teams admin settings, an admin can view the GAL name and custom name if one has been applied. It is not possible to edit the name in these admin settings. Editing can only be done in the Teams Rooms Pro Management Portal.

If you would like to remove the new custom name, you can simply remove the custom name from the field in the Pro Management Portal, and the display name on Teams panel will default back to the GAL name.

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. Please update to 1449/1.0.97.2024122401 to use this feature.

MC916866 — (Updated) Microsoft Teams: Shifts Graph APIs in beta moved to production (v1.0)

Microsoft 365 Roadmap ID 422813

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

The Shifts Graph APIs will transition from beta to production. This change brings enhanced stability and reliability to the APIs, ensuring a seamless experience for developers and users.

When this will happen:

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

How this will affect your organization:

You may continue using the API endpoints in beta. However, we recommend migrating to the production endpoints.

To refer to a list of all production (v1.0) APIs, go to the following page and navigate to Teamwork and communications > Shift management: Microsoft Graph REST API v1.0 endpoint reference - Microsoft Graph v1.0 | Microsoft Learn

This update is available by default.

What you need to do to prepare:

To update Microsoft Graph APIs from beta to production, change your API calls from the beta endpoint to the v1.0 endpoint and thoroughly test your application to ensure compatibility. Check for any differences between the versions, and update any documentation accordingly.

MC912709 — (Updated) Microsoft Teams: Bookable desks and BYOD rooms supported in GCC

Updated February 4, 2025: We have updated the content.

Coming soon for Microsoft Teams: Bookable desks and Bring Your Own Device (BYOD) rooms. To set up these two solutions, admins must have access to the Teams Rooms Pro Management portal.

Bookable desk features in Teams desktop, including plug-in-based reservations and peripheral discovery and inventory in the Teams Rooms Pro Management portal (released earlier in 2024), will be available to enhance your flexible work environments. In the future, admins will also get valuable analytics and insights for space management and planning.

Bring your own device (BYOD) meeting room features including Shared Display mode and peripheral discovery, inventory, and reports in the Teams Rooms Pro Management portal (released earlier in 2024) also will be available.

When this will happen:

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

How this will affect your organization:

Before this rollout, admins are not able to set up bookable desks and BYOD rooms in their tenant.

After this rollout, admins will have the option to set up bookable desks and BYOD rooms in their tenant. This feature is default off on Teams desktop client.

To enable bookable desks and BYOD, please see our desk and room guides. We also have a user support article for desks and rooms.

What you need to do to prepare:

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

To prepare for this feature, we recommend reviewing the published guides and documentation, discussing this new feature with your team, and share instructions if needed.

Learn more

MC912707 — (Updated) Microsoft Teams: New policy for voice and face enrollment will default to "On" (configure now)

Microsoft 365 Roadmap ID 413708

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

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 March 2025 (previously late February).

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 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-January 2025. 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-February 2025.

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.

MC908117 — (Updated) Microsoft Teams: Swap screens on Teams Rooms on Android

Microsoft 365 Roadmap ID 415243

Updated January 28, 2025: We have updated the content. Thank you for your patience.

Coming soon to Microsoft Teams Rooms on Android: As an admin, you can configure dual display mode and swap the screens of dual display devices using device settings and the Teams admin center. This feature allows you to deliberately set the display mode of your device and also to fix reversed display installations remotely and at scale, enhancing your device management capabilities. A Teams Rooms Pro license is required for this feature.

When this will happen:

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

General Availability (GCC High): We will begin rolling out early December 2024 and expect to complete by mid-February 2025 (previously mid-January).

How this will affect your organization:

Before this rollout

Teams Rooms on Android devices automatically enter dual display mode when two external displays are physically connected to a Teams Rooms on Android device. Because the display mode depends only on the physical connection to the device, rooms can be easily misconfigured when external displays are accidentally disconnected or intentionally unplugged by room users without admin approval.
If external displays are set up in reverse (with the main display on the left and the extended display on the right), admins are not able to correct the misconfiguration with remotely. Admins must send someone to each affected room to manually swap cables.

After this rollout

A Teams Rooms on Android device will only operate in dual display mode if admins physically connect two external displays to the device and explicitly set the device to run in dual display mode using Teams admin settings on the device or the Teams Rooms on Android configuration profile in the Teams admin center > General > Dual display mode.
If dual display mode is enabled for a device but only one external display signal is detected through the physical connection to the device, an error message about the disconnected display is shown on the device, prompting room users to contact IT support for resolution. This setting helps ensure that the Teams Rooms on Android app is showing the user interface configured by the admin.
Teams Rooms devices with dual displays are designed with the main display (where the calendar is shown) on the right side and the extended display (where the date, time, and room information are shown) on the left side. When dual display devices are reversely installed, you can fix display positioning errors made during device setup with minimal effort. You can swap the display using Teams admin settings on the device or the Teams Rooms on Android configuration profile in the Teams admin center > General > Dual display mode > Swap screens

NOTE: If you are deploying Teams Rooms on Android devices with dual displays, be aware that dual display mode must be explicitly enabled in the configuration profile. By default, the dual display setting is OFF, which means that using an existing configuration profile (designed for single-display devices by default) may inadvertently disable dual display mode for your existing dual display rooms. To avoid this, you must create and maintain a separate configuration profile for any devices that require dual display support.

This feature will be off by default and available for admins to configure.

What you need to do to prepare:

After updating your Teams Rooms on Android devices to the latest app version through the Teams admin center, you may notify your users about the 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.

MC907108 — (Updated) Microsoft Teams: Admin email support for "Report a problem" on Teams Rooms on Android

Microsoft 365 Roadmap ID 415247

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

Coming soon to Microsoft Teams Rooms on Android: As an admin, you can configure an email address for receiving issues submitted by users through the Report a problem feature on Teams Rooms on Android devices. The email address can be set through device settings or the Teams admin center. This feature will allow you to collect logs and feedback directly from your device Teams Rooms on Android devices, enhancing your ability to triage, respond, and escalate issues as needed.

When this will happen:

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

General Availability (GCCH): We will begin rolling out early December 2024 and expect to complete by mid-February 2025 (previously mid-January ).

How this will affect your organization:

Before the rollout: When room users encounter issues while using the conference room, there is no way for them to directly report issues to admins from the Teams Rooms on Android devices.

After the rollout

When you configure an email address in Teams admin settings > General > Logs and feedback, the Report a problem option on Teams Rooms on Android devices will be enabled, and any feedback submitted by room users using Report a problem will be sent to the email address in the device settings. You can also choose to have app logs automatically attached to the feedback you receive in email.

Users can access Report a problem from the Help button on the home screen or the More button in meetings. Report a problem can also be accessed on the pre-sign in screens.

The email you will receive will contain the feedback entered by the room user and will include information like the room account, device model, and app version. If configured, the email will also include app logs as an attachment.

NOTE: If you’re reaching out to Microsoft Support regarding an issue you receive through email, make sure to download complete device logs from the Teams admin center. For more information, see Collect Teams Android device logs | Microsoft Learn.

This feature will be off by default and available for admins to configure.

If you don’t have physical access to the Teams Rooms on Android device, you can also remotely configure an email address for log and feedback collection through the Teams Rooms on Android configuration profile found on the Teams admin center.

What you need to do to prepare:

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

After the rollout: After updating your Teams Rooms on Android devices to the latest app version through the Teams admin center, configure your devices as desired, notify your users about the change, and update your training and documentation as appropriate.

MC906501 — (Updated) Microsoft Teams: Net Promoter Score survey on Teams Rooms on Android

Microsoft 365 Roadmap ID 415245

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

Coming soon to Microsoft Teams Rooms on Android: Users can rate how likely they are to recommend Microsoft Teams Rooms from 1 to 5 and provide their comments in a Net Promoter Score (NPS) survey delivered on Teams Rooms on Android devices.

When this will happen:

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

General Availability (GCCH): We will begin rolling out early December 2024 and expect to complete by mid-February 2025 (previously mid-January).

How this will affect your organization:

Before this rollout: NPS surveys do not appear on Android devices.

After this rollout

Like Teams Rooms on Windows and other Teams platforms, NPS surveys will appear periodically after meetings end on Teams Rooms on Android devices. NPS surveys gauge the likelihood of users recommending Microsoft products and services to their peers, and the feedback gathered is used to improve Microsoft products and services.

This feature will be on by default and available for admins to allow or prevent NPS surveys. If you do nothing, the surveys will be on by default.

As an admin, you can prevent room accounts from getting NPS surveys with Microsoft PowerShell. Learn more at Manage feedback policies in Microsoft Teams - Microsoft Teams | Microsoft Learn.

What you need to do to prepare:

This rollout will happen automatically by the specified date with no admin action required before the rollout. After updating your Teams Rooms on Android devices to the latest app version through the Teams admin center, you may want to notify your users about this change and update your training and documentation as appropriate.

MC903632 — (Updated) Microsoft Teams Rooms on Android: 3x3 video gallery on dual displays

Microsoft 365 Roadmap ID 415239

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

Coming soon for Teams Rooms on Android: We will increase video participants displayed in Gallery view for dual displays from 10 to 18 video participants total, 9 (3x3) on each screen, that will be displayed when no content is being shared during meetings. This rollout aligns the Gallery experience with Teams Rooms on Windows.

When this will happen:

General Availability (Worldwide, GCC): We will begin rolling out early November 2024 and expect to complete by early November 2024.

General Availability (GCC High): We will begin rolling out late November 2024 and expect to complete by late January 2025 (previously late December)

How this will affect your organization:

Due to device capability requirements and performance implications, 3x3 video gallery support for dual displays will only be available on the following Teams Rooms on Android devices: Yealink MeetingBar A40, Poly Studio X52, and Poly Studio G62. We will include more details in the Microsoft Learn documentation that will be included in the release notes. Before rollout, we will update this message with a link to the release notes.

This change will be on by default.

What you need to do to prepare:

No action is needed to prepare for this change. Please notify your users about this new experience and update your training and documentation as appropriate.

MC889534 — (Updated) Microsoft Teams: Embed support for Teams town hall

Microsoft 365 Roadmap ID 401120

Updated January 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-February 2025 (previously mid-January).

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.

MC884018 — (Updated) Microsoft Teams: Set sensitivity labels for town halls and webinar

Microsoft 365 Roadmap ID 409226

Updated January 21, 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 January (previously late December).

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.

MC884009 — (Updated) Microsoft Teams: Start/stop recording on Teams Rooms on Windows

Microsoft 365 Roadmap ID 412072

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

Coming soon to Microsoft Teams Rooms on Windows: Users can start or stop recording meetings directly from a Teams Rooms on Windows device. This feature requires a Teams Rooms Pro license and Teams Rooms on Windows app version 5.2.

When this will happen:

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

General Availability (GCC High): We will begin rolling out early February 2025 (previously mid-December) and expect to complete by mid-February 2024 (previously mid-January).

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

How this will affect your organization:

Before the rollout: When attending a meeting using a Teams Rooms on Windows device, if users want to record the meeting, they need to also join the meeting on a companion device to initiate the meeting recording.

After the rollout

Start/stop recording is supported in any meeting where a participant belongs to the same tenant as the organizer, including scheduled meetings, ad-hoc meetings, channel meetings (only for channel members), and Teams Cast sessions. Users can select Start recording or Stop recording from the More menu, shown here at the bottom of the screen:

When users start recording 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 they can access the meeting chat on their Teams desktop or mobile app where the recording file will be available after the meeting.

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 recording meetings with the Teams meeting recording policy:

Using the Teams admin center: Learn more at Manage Teams recording policies for meetings and events - Microsoft Teams | Microsoft Learn.
Using Microsoft PowerShell: Learn more at Set-CsTeamsMeetingPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn.

NOTE: Both the meeting organizer and the recording initiator (room account) need to have recording permissions to record the meeting, or the start/stop recording button will not be available. Also, if the meeting organizer uses Meeting options to remove permissions from the room account to record the meeting, the start/stop recording button will not be available as well.

Start/stop recording is not supported in these scenarios:

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

NOTE: Avoid assigning Microsoft OneDrive for Business licenses to your room accounts to ensure that IT-managed room accounts do not become owners of the recording files.

What you need to do to prepare:

After your Teams Rooms devices are updated to the 5.2 app, configure the desired meeting recording policy, 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.

MC866447 — (Updated) CAPTCHA Verification for Anonymous Meeting Participants

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

Microsoft Teams tenants will soon be able to enable verification for anonymous meeting participants via CAPTCHA. This release of CAPTCHA Verification for Anonymous Meeting Participants will be rolling out across Microsoft Teams Desktop, Mobile and Web and will provide additional security against malicious bot and third-party app joins.

When this will happen:

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

How this will affect your organization:

Tenants can enable anonymous meeting attendee verification via CAPTCHA in the Teams Admin Center. When enabled, any users that join the meeting as an anonymous user will be required to pass a CAPTCHA verification before landing in the meeting (including the meeting lobby, if enabled).

What you need to do to prepare:

This feature is off by default and Tenant Admins will need to enable CAPTCHA verification for their tenants through Meeting policies in the Teams Admin Center.

MC818885 — (Updated) Microsoft Teams: Multiple camera view for Teams Rooms on Windows

Microsoft 365 Roadmap ID 402517

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

Microsoft Teams Rooms on Windows will be soon able to send up to four single-stream USB camera feeds to render on the receiver side, so remote meeting participants can view all cameras simultaneously. This opt-in feature requires admins to first enable the multiple camera view and map cameras to the desired order that will be displayed on the receiver side. With multiple camera view enabled, remote meeting participants will be able to follow all the action in the room and manually switch to the desired room. This message applies to Teams for Desktop (Windows, Mac).

When this will happen:

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

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

General Availability (GCC): We will begin rolling out in mid-January 2025 (previously mid-December) and expect to complete by late January 2025 (previously early January).

How this will affect your organization:

Before the rollout

Multiple camera views are not available in Teams Rooms on Windows.

After the rollout

A multiple camera view can create more visibility and coverage for large and complex spaces, such as multipurpose rooms, classrooms, and executive boardrooms. Admins can set up multiple camera views in two ways:

Admins can configure settings on a local device by turning on the Multiple camera view toggle and using the dropdown menu to map the cameras.
Admins can configure multiple camera view using Remote Accessin the Microsoft Teams Rooms Pro Management portal.

After the feature is enabled, in-room participants can disable multiple camera view with the Camera chevron button on the meeting console. This action will return the device to a single camera view, and all receiver-side participants will see a single camera view. This in-room setting will only affect that meeting and the device will revert to the admin settings for the next meeting.

Remote participants will see the multiple camera view by default. On the top right corner of the room's video tile, a remote participant can use the arrows to switch to the desired camera view. This toggle will only affect the remote participant's own view and will not affect other meeting participants.

Admin setting to configure Multiple camera view on a local device:

What you need to do to prepare:

To prepare for the change, create a plan for the rooms that may require multiple cameras in consideration of the space, meeting scenario, and the desired experience for in-room and remote participants. Then, configure the multiple camera view on the local device or in the Teams Pro Management portal and notify your users about this new experience. You may want to update relevant training documentation.

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

MC809602 — (Updated) Microsoft Teams: New skin tone settings and reactions

Microsoft 365 Roadmap ID 323766

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

With skin tone settings and reactions in Microsoft Teams, users will be able to set a preferred skin tone for relevant emojis and reactions. Each user can change their own skin tone setting in the Teams app Settings > Appearance and accessibility menu or in the emoji/reaction menu on Desktop or web. The skin tone rollout will apply to emojis and reactions in chats, channels, and meetings on all Teams platforms (Teams for Desktop, Teams for web, Teams for Mac, and Teams Mobile).

When this will happen:

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

General availability (Worldwide, GCC): We will begin rolling out early November 2024 (previously late October) and expect to complete by late December 2024.

General availability (GCC High, DoD): We will begin rolling out mid-November 2024 (previously mid-November) and expect to complete by late January 2025 (previously late December)

What you need to do to prepare:

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

We will update this post before rollout with revised documentation.

MC808828 — (Updated) Microsoft Teams: Custom background and daily restart windows for Teams panels

Microsoft 365 Roadmap ID 402183

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

We are pleased to share that you will soon have the ability to upload and apply custom backgrounds to your Microsoft Teams Panel devices to showcase your brand identity. This feature requires either a Teams Rooms Pro license or a Teams Shared Device license and will be available with the next Teams Panels app update.

The next app update will also allow you to configure a daily device restart window for every Teams panel device, regardless of license. The restart window will be set from 2:00am to 3:00am in the device's local time zone by default to keep the device healthy.

When this will happen:

General Availability (Worldwide and GCC): We will begin rolling out early September 2024 (previously early August) and expect to complete by late January 2025 (previously late December)

How this will affect your organization:

Custom backgrounds:

To set custom backgrounds for your Teams Panel devices, go to Teams admin center > Teams devices > Panels > Configuration profiles > Add or Edit > Device settings > Background > Use a custom background. You can upload one image at a time.

The image must meet these requirements:

Minimum resolution: 1280x720
Format: JPG, JPEG, or PNG
Minimum size: 100KB
Maximum size: 2MB

Note: The image may be scaled to fill the frame or center cropped to fit the display if the ratio and resolution do not match.

After the images are saved in the configuration profile and the configuration profile is assigned to one or multiple Teams panel devices, the custom background will be applied to the devices that are logged in with a properly licensed resource account.

You can also switch the background from the custom image to one of the default images or vice versa on your Teams panel (Settings > Teams admin settings > Backgrounds). To replace the custom background saved on the device, you must go to the Teams admin center and upload and save a new image in the configuration profile.

Daily device restart window:

By default, the daily device restart window will be between 2:00am to 3:00am in the device’s local time zone. You will be able to adjust this window or turn it off on the device or in Teams admin center.

To change it on the device, go to your Teams panel device settings (Settings > Teams admin settings > Device restart).
To change it remotely, go to Teams admin center > Teams devices> Panels > Configuration profiles > Add or Edit > General > Daily device restart window > save and assign the changes in configuration profiles to one or multiple devices.

What you need to do to prepare:

This rollout will happen by the specified date with no admin action required before the rollout. You may want to update any relevant documentation as appropriate and plan to design custom background images for your devices. We will update this post with a link to our learn docs with design guidelines when it is available.

MC781595 — (Updated) Microsoft Teams: Tenant-wide policy for permission to download meeting transcription

Microsoft 365 Roadmap ID 332800

Updated January 13, 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 January 2025 (previously late December).

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

MC772556 — (Updated) Microsoft Teams: Shorter meeting URLs

Microsoft 365 Roadmap ID 381953

Updated January 10, 2025: We have updated the rollout timeline below. Please note that information about meeting link expiry changes related to this rollout has been added.

We are reducing the length of Microsoft Teams meeting URLs for easier sharing. This rollout applies to all Microsoft Teams platforms (Teams for iOS, Android, Mac, Teams devices, desktop, and web).

When this will happen:

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

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

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

How this will affect your organization:

The new URL syntax is: https://teams.microsoft.com/meet/<meeting_id>?p=<HashedPasscode>

To make meeting URL shorter, we are removing several parameters such as tenant ID, conversation ID etc. This change serves two main goals: 1) improving usability of URL during sharing and 2) making the URL more secure and less susceptible to malicious attacks.

Here are some details about how meeting links work and when they expire:

In case the meeting organizer gets removed from the tenant, the links to the meetings scheduled by them automatically expire.
Every meeting link expires in 60 days after the scheduled event or in 8 hours, if it was created as Meet Now. Learn more about expiration timelines for different types of meetings.

With the Short Meeting URL release, expiration limit will be applied to all newly created links.

Once the change to Short Meeting URL is released, all newly created meetings will expire as described in the documentation: 60 days after meeting ends for scheduled meetings and 8 hours after creation for Meet Now. Once this expiry period is over, in case someone clicks the link (e.g. outside of Teams app OR in the meeting details inside Teams calendar section), they will be unable to join the meeting.

Note: Old links created before short meeting URL release will continue working as it previously was (user will be able to join even after the documented expiry limits).

The reason why we are making this change is simple: security is our topmost priority. Maintaining a high security level is essential to protect sensitive data, prevent financial losses, ensure business continuity, and meet compliance and legal obligations. It is a critical aspect of modern digital life and business operations. This adjustment is designed to enhance the security of Teams meeting links, thereby better safeguarding the customer tenant. We want to be on par with modern security standards, that’s why the new behavior is a step in the right direction that we must take. It’s not possible to keep the current behavior. If you think it breaks some of your business processes, please leave comment to the MC post and describe your case there.

Recommendations in case the meeting link has expired:

For meeting organizer: We recommend scheduling a new meeting. If the meeting organizer got removed from the tenant someone else should reschedule their meetings from scratch.

For participant: Please reach out to the meeting organizer and ask them to reschedule the meeting or send you an updated link.

What you need to do to prepare:

You may want to check if you have any integrations that use parameters from URL. After the rollout, the URL will only contain the meeting ID. Parameters such as tenant ID, organizer ID, conversation ID and message ID will not be in the URL.

You may inform meeting organizers from your tenant who use expired meeting links, or you may want to make a tenant-wide announcement about this change.

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

MC750668 — (Updated) Microsoft Teams: Access Workflows from the three-dot menu on shared file

Microsoft 365 Roadmap ID 381643

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

Coming soon: Microsoft Teams will be bringing Workflows powered by Microsoft Power Automate to the three-dot menu for files shared in Teams chat or channels.

When this will happen:

Targeted release: We will begin rolling out late October 2024 (previously mid-October) and expect to complete by early November 2024 (previously late October).

Worldwide: We will begin rolling out early November 2024 (previously late October) and expect to complete by late November 2024 (previously early November).

GCC: We will begin rolling out early December 2024 (previously late October) and expect to complete by mid-February 2025 (previously mid-January).

How this will affect your organization:

To make sure Microsoft Teams provides the best workflow experience for our users, we are making it easier to configure and run workflows for files. A user will be able to select the three-dot menu on files shared in Teams chat or channels, and then choose Workflows. From Workflows, the user will choose an instant workflow to run on a file. The user must set up the workflows in advance. A user can set up a new workflow for files by selecting See more workflows at the bottom of the three-dot menu. This launches the Workflows task module, where a user can choose a template to start setting up a new workflow. Examples of file workflows include Request approval for selected file, Get notified in Teams when a file is updated, Create a PDF copy of the file, and Add a task for this file.

If the Power Automate app is disabled in the Teams admin center, users will not see this option in the three-dot menu.

This feature will only be available in the New Teams client on the desktop and on the web.

What you need to do to prepare:

No action is needed from you to prepare for this rollout. You may want to notify your users about this change so they can find the new entry point for Workflows.

MC726122 — (Updated) Microsoft Teams: View, download, and delete Microsoft OneDrive transcript files

Microsoft 365 Roadmap ID 365720

Updated January 13, 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.

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 late January 2025 (previously late December)

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 January 21, 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 January 2025 (previously late December).

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.

MC718250 — (Updated) Microsoft Teams: Describe it to design it in Teams Workflows

Microsoft 365 Roadmap ID 382659

Updated January 23, 2025: After further review, we will not be rolling this out to GCC. We will communicate via Message center when we are ready to proceed.

Can't find a workflow template that matches what you need in Microsoft Teams? You will now be able to describe in detail how you want your automation to work and receive a workflow to match your needs. All you need to do is select the Workflow builder button at the bottom of the create dialog in the Workflows app in Microsoft Teams chat and channel overflow menu.

Workflow builder will come to the Workflows app in Microsoft Teams chat and channel overflow menu first. Other entry points to Workflows will get this feature later.

When this will happen:

Worldwide: We will begin rolling out late September 2024 (previously mid-September) and expect to complete by late October 2024 (previously late September).

GCC Release: We will not be proceeding with this change at this time.

How this will affect your organization:

All users with the ability to create workflows with the Workflows app in Teams will be able to describe the workflow they are trying to build and then receive a suggested flow.

Prerequisites

A work or school Teams account with access to a Power Automate environment in Europe or the United States.

Limitations

Power Automate supports workflow descriptions written in the English language only. Descriptions written in other languages might work but are not supported.

Cloud flows are the only type of flow that you can create from a written description.

In the version rolling out, the AI might omit some parameters, even if you provide them in the description.

What you need to do to prepare:

No action is needed to prepare for this rollout. If your tenant uses the Power Automate app within Microsoft Teams, you may want to notify your users about this change and update any relevant documentation as appropriate.

To learn more: Create a cloud flow from a description (preview) - Power Automate | Microsoft Learn

MC709270 — (Updated) Mute with Windows Taskbar available in the new Microsoft Teams on Windows

Microsoft 365 Roadmap ID 191528

Updated January 13, 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 January 2025 (previously late December)

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 January 24, 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-February 2025 (previously mid-January).

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.

MC688109 — (Updated) Co-organizer experience updates in Teams Webinars and Townhalls

Microsoft 365 Roadmap ID 168524

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

Scheduling, setting up, and managing an event is not a simple task. Which is why we allow co-organizer to be added to the event so they can work alongside or on behalf of the organizer. So far co-organizers were able to set up event theming, manage registration, meeting options, view reports and more but were not able to edit event details like title, date/time, description, event group; nor publish or cancel event. Now they can! Co-organizer can edit event details, publish, and cancel the event like the organizer can. So once the co-organizer is added they will have full parity of experience as organizer and control/manage/edit event.

When this will happen:

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

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

How this will affect your organization:

When co-organizer opens the event scheduling page, they should have the ability to edit the details page, publish, and cancel the event.

What you need to do to prepare:

Nothing required to prepare.

Microsoft Purview

MC989980 — Microsoft Purview | Insider Risk Management: Public preview of policy deletion enhancement (GCC, GCCH, DoD)

Microsoft 365 Roadmap ID 171601

Microsoft Purview Insider Risk Management will be rolling out a policy deletion enhancement.

When this will happen:

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

How this will affect your organization:

After this rollout, admins with appropriate permissions will be able to delete all associated alerts and users in scope when deleting a policy, to help quickly reset and remove inactive policies. Cases will not be impacted.

This change will be available by default.

What you need to do to prepare:

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

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: Create and manage insider risk management policies | Microsoft Learn

MC986518 — Microsoft Purview | Insider Risk Management: Updates to email scoring (GCC, GCC High, DoD)

Microsoft 365 Roadmap ID 471010

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

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:

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

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

MC985476 — Microsoft Purview | Insider Risk Management: Share user risk details with other security solutions (GCC, GCC High, DoD)

Microsoft 365 Roadmap ID 475857

Microsoft Purview Insider Risk Management is introducing the ability to share Insider Risk Management data with other Microsoft services for Government customers. When turned on, admins with the correct permissions will be able to review user risk details and alerts from Insider Risk Management in other solutions such as Microsoft Purview | Data Loss Prevention (DLP), Microsoft Purview | Communication Compliance, and Microsoft Defender.

When this will happen:

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

How this will affect your organization:

Admin can access the toggle in Microsoft Purview > Insider Risk Management settings > Share user risk details with other security solutions:

This change will be available by default.

What you need to do to prepare:

Consider assessing your organization’s needs and decide if your organization will benefit from reviewing Insider Risk Management alerts through other solutions.

Learn more: Share insider risk management data with other solutions | Microsoft Learn

MC973511 — (Updated) Microsoft Purview | Data Lifecycle Management: Separate retention policies for Copilot and AI apps

Microsoft 365 Roadmap ID 470025

Updated January 10, 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 mid-February 2025 (previously late January) and expect to complete by late February 2025 (previously mid-February).

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.

MC969449 — (Updated) Microsoft Purview | Data Loss Prevention for endpoints: Four new conditions (GCC, GCCH, DoD)

Microsoft 365 Roadmap ID 374811

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

Coming soon for Microsoft Purview | Data Loss Prevention (DLP): Four new conditions or predicates that admins can use in their policies for endpoint devices.

When this will happen:

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

How this will affect your organization:

After this rollout, DLP policies will include the capability to identify documents that are unscannable, partially scannable, exceed a specific file size, or have names matching configured patterns for Government cloud tenants on Windows endpoint devices. This functionality enables you to prevent users from accessing unscannable files on endpoints and attempting egress actions such as copying to a USB drive, copying to the clipboard, or transferring to another network share, among others.

The four new predicates are:

Document size equals or is greater than: Detects documents greater than or equal to the specified value.

Document name matches patterns: Detects documents where the file name matches specific patterns.

Document couldn’t be scanned: Applies to documents when their content wasn't scanned. Examples include password protected files, files for which text extraction failed, and files that exceed file size limit.

Document couldn’t complete scanning: Applies to documents when their content was scanned, but the entire document was not scanned. Examples include files for which extracted text exceeded the limits/thresholds.

When defining your DLP Policy, you can use these conditions across supported and applicable workloads for government cloud tenants. For example, you can extend any of the four new conditions that are available now in DLP for Exchange and scope them to Endpoint > Devices as part of your policies and rules, which enhances protection across the digital estate.

Please refer to the supported file types on endpoint, for which these predicates will provide protection.

What you need to do to prepare:

Learn more about conditions supported for endpoints
Get started with Data Loss Prevention in the Microsoft Purview compliance portal.
Learn more: Using Endpoint DLP | Microsoft Learn

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

MC966637 — (Updated) Microsoft Purview | Data Loss Prevention for endpoints: New "Document property" condition (GCC, GCCH, DoD)

Microsoft 365 Roadmap ID 417482

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

Coming soon for Microsoft Purview | Data Loss Prevention (DLP): The new Document property is condition will be available for use in policies for endpoint devices.

When this will happen:

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

How this will affect your organization:

After this rollout, DLP policies can detect and monitor egress actions for documents that match defined custom properties. The new Document property is condition detects documents with custom properties matching the specified values.

As part of DLP policy definition, this new condition can be used across supported and applicable workloads. For example, the Document property is condition in DLP for Exchange can be extended to endpoint devices as part of DLP policies and rules, which enhances protection across the digital estate.

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

What you need to do to prepare:

Get started with DLP in the Microsoft Purview compliance portal.

Learn more: Data Loss Prevention policy reference | Microsoft Learn

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

MC961761 — Microsoft Purview | Insider Risk Management: IRM alerts in Microsoft Defender XDR

Microsoft 365 Roadmap ID 422730

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

Coming soon to Microsoft Purview: Insider Risk Management (IRM) data including alerts, indicators and events will be available in these Microsoft Defender XDR experiences:

Unified alert queue: IRM alerts will appear in the unified alert and incident queue in Defender XDR for comprehensive investigation and correlation.
Advanced Hunting: IRM data will be available for advanced hunting in Defender XDR, allowing analysts to identify hidden risk patterns using KQL queries. Analytics can also create custom detections on the top of IRM data.
Graph API: IRM data will be accessible through the Microsoft Graph API, supporting bidirectional integrations with external applications.
Microsoft Sentinel: IRM alerts will be available in Microsoft Sentinel through the XDR-Sentinel connector, providing richer metadata.

When this will happen:

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

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

How this will affect your organization:

Enable this feature by turning on Share data with other security solutions in the IRM global settings.

Only users with Insider risk analysis or investigation roles in the Microsoft Purview portal can access IRM data in Defender XDR.

To access alerts, incidents, and events from Defender XDR via API, you need to provision apps with the necessary permissions. IRM data is accessible via Microsoft Security Graph APIs, allowing for reading and updating alert or incident statuses. Permissions are set at the application level, without solution-specific scoping. Any existing apps pulling data from these APIs will also access IRM data. So, if you integrate XDR alerts into external ticketing systems, IRM alerts will show up, unless you specifically filter out the alerts.

IRM alerts will appear in Sentinel if your tenant has the Defender XDR connector enabled in Microsoft Sentinel.

In Defender XDR, IRM data is not pseudonymized to allow effective correlation of IRM alerts with alerts from other solutions within the platform, such as Defender for Endpoint and Defender for Cloud apps.

These changes will be available by default for admins to configure in IRM global settings.

Admins will be able to view Insider Risk Management alerts in Defender XDR.

Harness the power of Advanced Hunting queries with two new tables that contain Insider Risk Management data: DataSecurityBehaviors and DataSecurityEvents.

What you need to do to prepare:

Opt-in to data sharing settings in IRM global settings page.
Assign necessary permissions to analysts
Review existing apps accessing Defender XDR data through Graph APIs.
If your organization is using Microsoft Defender XDR connector, please review the list of users who will gain access to this data through Sentinel.

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

MC950890 — (Updated) Microsoft Purview | Data Security Posture Management for AI

Microsoft 365 Roadmap ID 469509

Updated January 24, 2025: We have updated the content. 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 late January 2025 (previously mid-January) and expect to complete by late February 2025 (previously late January).

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.

The DSPM for AI Overview with getting started steps, two recommendations, two reports, and resources.

The Recommendations tab displays all recommendations provided by DSPM for AI.

Reports includes graphs for total interactions over time, sensitivity labels and sensitive information types found in AI interactions, user risk level, and more.

Policies displays all policies that have been created by default or AI policies created in Purview solutions.

Activity explorer shows events for AI interactions along with prompts and responses.

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 January 17, 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 early February 2025 (previously early January) and expect to complete by late February 2025 (previously late January).

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.

MC920308 — (Updated) Microsoft Purview | Information Protection: Auto-labeling policies will support "Fingerprint based SIT"

Microsoft 365 Roadmap ID 396173

Updated January 24, 2025: We have updated the content. Thank you for your patience.

Coming soon to Microsoft Purview | Information Protection: Admins will be able to use auto-labeling policies to automatically label files and emails with Fingerprint based SIT (sensitive info type).

When this will happen:

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

How this will affect your organization:

Before this rollout, admins are not able to use auto-labeling policies to automatically label files and emails with Fingerprint based SIT.

After this rollout, you can configure Fingerprint based SIT using the condition Content contains sensitive information types. Files that match Fingerprint based SIT will show in simulation.

Note: Contextual summary is not available for Fingerprint based SITs.

This change will be on by default and available for admins to configure.

What you need to do to prepare:

This rollout will happen automatically by the specified date with no admin action required before the rollout. Review use cases and set up for configuring document fingerprinting.

Learn more

MC911618 — (Updated) Microsoft Purview | Insider Risk Management: Multi-policy settings in Adaptive Protection

Microsoft 365 Roadmap ID 171735

Updated January 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, GCC High, DoD): We will begin rolling out late February 2025 (previously mid-January) and expect to complete by mid-March 2025 (previously mid-February).

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

MC892050 — Microsoft Purview | Compliance Portal: Enrich triage in Communication Compliance within Insider Risk Management context

Microsoft 365 Roadmap ID 415170

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

This feature update to Microsoft Purview Communication Compliance (CC) introduces a pivotal enhancement that integrates Insider Risk Management (IRM) alerts within CC triage flow, providing a holistic approach to compliance risk assessment. This integration empowers investigators with enriched insights by correlating communication alerts with a user's risk profile and activity history from IRM directly in the CC triage flow. This synergy between IRM and CC facilitates a more nuanced and informed decision-making process during investigations.

When this will happen:

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

How this will affect your organization:

The integration of IRM context into CC is a significant stride towards enhancing the efficacy of compliance investigations. This will allow investigators to view a user's risk profile and history alongside communication alerts, enabling a more informed and efficient triage process.

The insider risk severity (Low, Medium, or High) determined by activity detected in IRM policies helps admins prioritize and respond to user activity accordingly. A new user activity timeline will show messages and activities from IRM in one screen, simplifying the review process.

What you need to do to prepare:

To use this feature, please connect with an IRM administrator to enable data sharing from IRM settings. If you don't turn this setting on, you will see “Insider risk activity not available.”

MC808165 — (Updated) Microsoft Purview eDiscovery | Modernized eDiscovery in new Microsoft Purview portal

Microsoft 365 Roadmap ID 383744

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

A modernized new user experience (UX) for Microsoft Purview eDiscovery will be available in the Purview portal. In this new UX experience, Content Search, eDiscovery Standard, and eDiscovery Premium are unified so that users can now navigate a shared workflow that simplifies the transition between non-premium and premium features. This UX modernization also introduces features that enhance the eDiscovery process. Some of these new features include:

This new experience enhances Content Search security by placing all searches in an eDiscovery case. eDiscovery administrators and managers will have default access, with the ability to manage membership and control access to content searches. Users who are not eDiscovery administrators or managers will need to request to be added as case member in order to access content search.
Enhanced search efficiency with message ID and sensitivity labelsfor faster access to information.
Use of the improved search by Sensitive Information Type (SIT) interface for user-friendly selection without manual input.
Advanced Data Source Mappingallows linking a user's OneDrive using input such as the user's mailbox Simple Mail Transfer Protocol (SMTP) address or user’s name, streamlining data retrieval and management.
Acceleration through powerful investigation capabilities, such as user's frequent collaborators, providing a comprehensive view of the user's networks.
Data Source Sync:Stay updated with the new Data Source synchronization feature, which allows users to easily track any new or removed data locations, ensuring that eDiscovery investigations remain aligned with the latest data source landscape.
Introduction of the new visual Statisticsallows users to gain insights at a glance (such as Results containing Sensitive Information Types, top communication participants, etc.)
Monitor long-running processes with an informed and transparent progress bar with the option to cancel (for certain process types) if needed.
Obtain a full process report for all actions taken, such as statistics for holds and exports, bolstering the defensibility of your eDiscovery efforts.
Customize your exports with new settings, including the option to export as a single PST file path truncation and the use of friendly names to make exported data more accessible.

When this will happen:

Public Preview: We will begin rolling out late July 2024 and expect to complete by late September 2024.

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

GCC: We will begin rolling out mid-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 2025and expect to complete by late March 2025.

How this will affect your organization:

The unification of Content Search, eDiscovery Standard, and eDiscovery Premium into a single eDiscovery solution in the new Microsoft Purview portal will necessitate updates to your organization's training materials and documentation.

The deprecation timeline for the classic eDiscovery experience will be announced when the new modernized experience becomes generally available (GA). We will ensure that customers have ample time to transition to the new modernized experience before retiring the classic version.

What you need to do to prepare:

Update internal documentation and provide training to all eDiscovery users in your organization.

Learn more about the new Purview Portal.

Learn more about the modernized eDiscovery (preview) experience: Learn about eDiscovery (preview) solutions | Microsoft Learn

MC805721 — (Updated) Purview | Insider Risk Management: Adaptive Protection is generally available in GCC, GCCH, and DoD

Microsoft 365 Roadmap ID 335856

Updated January 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, GCC High, DoD): We will begin rolling out late February 2025 (previously mid-January) and expect to complete by late March 2025 (previously mid-February).

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

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 to manage security and compliance. 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.

MC795079 — Microsoft Purview | Insider Risk Management - Adaptive Protection - HR resignation date as a condition for risk level

Microsoft 365 Roadmap ID 124972 and 171748

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

Microsoft Purview: The feature to configure HR resignation date as a condition for risk level in Adaptive Protection will be rolling out to General Availability. We communicated the preview for this feature in MC681240 Adaptive Protection in Microsoft Purview: Public preview of HR resignation date as a condition for risk level (November 2023).

When this will happen:

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

How this will affect your organization:

When the HR connector has been configured, admins with appropriate permissions can now select the HR resignation date as a condition to assign a minor, moderate, or elevated risk level. For example, an admin can configure the elevated risk level to be assigned when an HR resignation date is sent via the HR connector.

What you need to do to prepare:

No action is required for this update. To configure user’s risk level for Adaptive Protection, admins can visit Insider Risk Management > Adaptive Protection (preview) > risk levels for Adaptive Protection.

Additional Resources:

You can access the Insider Risk Management solution in the Microsoft Purview compliance portal.

Home - Microsoft Purview

Learn more about adaptive risk mitigation:

Help dynamically mitigate risks with Adaptive Protection (preview) | Microsoft Learn

MC791110 — (Updated) Microsoft Purview | Data Lifecycle Management: New integration with Adaptive protection

Microsoft 365 Roadmap ID 392839

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

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.

MC678065 — (Updated) Microsoft Purview compliance portal: Information Protection - New cmdlet for Content Explorer

Microsoft 365 Roadmap ID 117531

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

The Content explorer Export feature has a limitation of exporting data only after drill down to specific location. This feature is now available in Public Preview and allows admins to use a new cmdlet within the Security & Compliance PowerShell, Export-ContentExplorerData, to export all rows of data for the content that are scanned and shown on the Content Explorer.

When this will happen:

This feature will begin rolling out early July 2025 (previously mid-April) and expect to complete by late July 2025 (previously mid-May).

How this will affect your organization:

This feature can be accessed through the Security & Compliance PowerShell, Export-ContentExplorerData.

What you need to do to prepare:

There are no additional settings needed for this feature.

Get started with content explorer | Microsoft Learn

Outlook

MC993229 — New Microsoft Outlook for Windows and web: New folder color feature

Microsoft 365 Roadmap ID 472921

Coming soon to new Microsoft Outlook for Windows desktop and Microsoft Outlook for the web: Users can customize folder icon colors, making it easier to visually differentiate and personalize folders.

When this will happen:

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

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

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

How this will affect your organization:

After this rollout, this feature will be available for all Outlook accounts except for shared mailboxes and shared folders. Colors work for light and dark mode. Note: Some Outlook themes will have low contrast with some folder colors.

To change the color of a folder, a user can hover over the folder name, select the three-dot menu, select Change color and then choose a color.

To turn off the color, follow the same process, and select Automatic.

The folder color will display in the list of folders and in Favorites if the colored folder is added to Favorites.

What you need to do to prepare:

#newoutlookforwindows

MC981624 — Microsoft Outlook name change: "Outlook (new)" on Windows will change to "Outlook"

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 early February 2025 and expect to complete by late February 2025.

What you need to do to prepare:

Outlook in the Windows Start menu. Left: Before the name change. Right: After the name change:

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

MC974362 — (Updated) Secure/Multipurpose Internet Mail Extensions encryption support in new Outlook for Windows

Microsoft 365 Roadmap ID 397891

Updated January 21, 2025: After further review, we will not be rolling this out to DoD during the timeline outlined below. We will communicate via Message center when we are ready to proceed. Organizations in GCC High and DoD can safely disregard this message. Thank you for your patience.

We are rolling out fundamental Secure/Multipurpose Internet Mail Extensions (S/MIME) support for primary accounts in new Outlook. With this new feature, new Outlook will start supporting sending and reading signed and encrypted emails.

In new Microsoft Outlook, this option is available in Options > More Options.

When this will happen:

General Availability (Worldwide): We began rolling out mid-December 2024 and expect to complete by late January 2025.

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

General Availability (GCC High, DoD): We will communicate via Message center when we are ready to proceed.

How this will affect your organization:

If your organization is not using New Outlook this will not impact you.

If your organization does not have S/MIME setup for your users, this will not impact you.

If your organization is currently using S/MIME, you will soon see controls to apply S/MIME encryption when signing into new Outlook. Similarly, you will be able to verify, sign, decrypt, and reply to S/MIME emails.

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.

Users with S/MIME certificates on their machine or Smart Card will be able to use this new feature in new Outlook.

Learn more: Overview of the new Outlook for Windows

MC960818 — (Updated) Microsoft Outlook for iOS/Android: New reporting buttons integrated with Microsoft Defender for Office 365

Microsoft 365 Roadmap ID 371383

Updated January 29, 2025: We have updated the content. Thank you for your patience.

Coming soon for Microsoft Outlook for iOS/Android: New built-in report buttons in version > 4.2446. Admins can control the appearance and behavior of these buttons that allow users to report emails as phishing / junk / not junk from the User Reported setting page in the Microsoft 365 Defender portal (security.microsoft.com). Admins can also customize where messages get reported to (reporting mailbox, Microsoft, or both) and what the user sees both before and after reporting messages from these buttons.

When this will happen:

General Availability (Worldwide, GCC, GCC High): We began rolling out in early December 2024 and expect to complete by late January 2025.

How this will affect your organization:

Information to keep in mind:

Microsoft OWA (Outlook on the Web) and the new Microsoft Outlook for Windows have had this functionality since November 2022. This rollout to iOS/Android does not change or affect that functionality.
Classic Microsoft Outlook for Windows client has had this functionality in current channel since August 2024. Learn more: MC841229(Updated) Classic Microsoft Outlook for Windows: New reporting buttons integrated with Microsoft Defender for Office 365 (published July 2024, updated October 2024).
Microsoft Outlook for Mac released this functionality in September 2024.
If you have turned off the reporting feature in the Microsoft 365 Defender User reported settings page or are using a third-party add-in, the report buttons in Outlook for Android/iOS won't be visible.
The Microsoft reporting add-in (the Microsoft report message add-in and Microsoft phishing add-in) will be supported till further notice. The future goal is to have a consistent button reporting experience across all Outlook platforms. If you are using Microsoft reporting add-ins in Outlook for iOS/Android, your users will see two reporting experiences: one from the built-in Outlook buttons (added by this rollout) and one from the add-in. Both options will behave the same for users (except for the newly customizable pop-ups) and the reported messages will end up in the same place, causing minimal disruption.
The selections you make on the user reported settings page will determine the reporting experience for your users (whether they choose the add-in or built-in reporting option in Outlook). Either option will report to the same place (Microsoft, custom mailbox, or both) based on your User reportedsettings.
Like OWA and new Outlook for Windows, the built-in reporting button in Outlook for iOS/Android supports reporting from shared and delegate mailboxes.

This change is available by default.

What you need to do to prepare:

No action is required form you after this rollout because your current settings in the User reported settings page will not be changed.

Learn more

Report phishing and suspicious emails in Outlook for admins - Microsoft Defender for Office 365 | Microsoft Learn(will be updated before rollout)
User reported settings - Microsoft Defender for Office 365 | Microsoft Learn(will be updated before rollout)

MC947045 — (Updated) Microsoft Outlook for iOS and Android: Attach emails while composing an email

Microsoft 365 Roadmap ID 464206

Updated January 16, 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 February 2025.

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.

MC882252 — (Updated) New Microsoft Outlook for Windows: Sharing Word, Excel, and PowerPoint local files through email

Microsoft 365 Roadmap ID 397094

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

Coming soon to new Microsoft Outlook: Users will be able to share Microsoft Word, Microsoft Excel and Microsoft PowerPoint files stored on their device (not stored in a cloud like Microsoft OneDrive) from new Outlook for Windows.

When this will happen:

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

How this will affect your organization:

Before this rollout, users are only able to see old Outlook for Windows when they try to share a Word, Excel or PowerPoint fie.

After this rollout, when users want to share a Word, Excel, or PowerPoint file that is saved to their device (not stored in a cloud like Microsoft OneDrive), the user can right-click the file name in File Explorer, select Share, and select new Outlook for Windows to email the file.

This option is on by default.

What you need to do to prepare:

MC847877 — (Updated) Microsoft Outlook for iOS and Android: Choose fonts while composing

Microsoft 365 Roadmap ID 409969

Updated January 9, 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 January 2025 (previously early December).

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 January 16, 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 early April 2025 (previously early March).

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

Exchange Online

MC982553 — Microsoft Exchange Online: Search-MailboxAuditLog and New-MailboxAuditLogSearch will retire

We will retire the Search-MailboxAuditLog and New-MailboxAuditLogSearch cmdlets in Microsoft Exchange Online starting March 1, 2025, and completing in late March 2025. After the retirement, new records will be written to Search-UnifiedAuditLog and Search-MailboxAuditLog will be accessible only as a historical record.

How this will affect your organization:

After the retirement, admins will be able to access Search-MailboxAuditLog and New-MailboxAuditlogSearch and make changes and downloads until late June 2025. After late June, Search-MailboxAuditLog and New-MailboxAuditlogSearch will become a static record only, and admins will no longer be able to make changes and downloads.

What you need to do to prepare:

This change will happen automatically by the specified dates. Please notify your users about this change, update your relevant documentation, and share the alternate capability Search-UnifiedAuditLog.

To use the Search-UnifiedAuditLog cmdlet, you must ensure auditing is enabled for your tenant.

Learn more about enabling auditing for your tenant and about the changes to these cmdlets: Microsoft Exchange Online: Search-MailboxAuditLog and New-MailboxAuditLogSearch will retire | Microsoft Community Hub

MC902782 — (Updated) Exchange Online token deprecation plan

Updated February 3, 2025: We have updated the content.

This is a reminder that starting February 17th, legacy Exchange Online user identity and callback tokens will be turned off across all Microsoft 365 tenants. This impacts all Outlook add-ins that request a legacy Exchange Online token to identify the user or make Exchange web services (EWS) calls. This change only applies to Exchange Online and doesn’t apply to Exchange on-premises.

Recommended actions

Identify any add-ins that are impacted.Determine if your tenant has any deployed Outlook add-ins that are impacted by this change. For more information, see Which add-ins in my Organization are impacted.
Contact add-in publishers.Microsoft has worked with many Outlook add-in publishers to update their add-ins to use Entra ID tokens and Microsoft Graph. If you identify any impacted add-ins on your tenant, we recommend that you reach out to the publishers of those add-ins to learn more about their plans to update.

Can I opt out of this change?

You can opt out of the February 17th change if all the following are true.

Your tenant has add-ins impacted by this change.
The impacted add-ins will not be updated to no longer use legacy Exchange Online tokens by February 17th.
The add-ins are necessary for your organization.

To opt out, run a command to set legacy Exchange Online tokens to remain on. It takes up to 24 hours for the command to take effect. If you turn tokens on before February 17th, your tenant will be exempt from the February 17th change. Tokens will remain on until June 2025 or until you explicitly turn them off.

What happens on February 17th?

Microsoft will begin deploying a change to all users worldwide in Microsoft 365 tenants that will turn off the issuance of legacy Exchange online tokens. The deployment will take several weeks to deploy to all users. If an Outlook add-in requests a legacy Exchange token, and token issuance is turned off, the add-in will receive an error. Outlook add-ins that still request legacy Exchange Online tokens will be broken by this change. Please note that even after legacy tokens are turned off, already issued legacy tokens will continue to be valid for approximately 24 hours.

Note that since the change is applied per user, and deployed over several weeks, you could see some user’s affected while others are not.

Where do I get more information?

The Outlook legacy tokens deprecation FAQ is updated regularly and contains information about tools and how to upgrade add-ins. We recommend you refer to the Q&A section for Microsoft 365 administrators. We also recommend you share the FAQ with any developers in your organization that need to update LOB Outlook add-ins using legacy Exchange Online tokens.

Additional resources

MC886603 — (Updated) Reject multiple From addresses (P2 From headers) without a Sender header

Updated January 31, 2025: We are proactively opting tenants out of the rollout that were detected as sending high volumes of emails exhibiting multiple From addresses without a Sender address header. These exempted senders will only be able to send emails exhibiting multiple From addresses without a Sender address header to recipients belonging to the same tenant as the sender. We will provide a subsequent update by the end of February with an updated timeline for tenants that are opted out.

Starting February 3 (previously December 1), we're going to start gradually dropping messages that have multiple From addresses (also known as P2 From headers) without a Sender header from being processed via Exchange Online.

If we see significant traffic exhibiting multiple From addresses (P2 From headers) without a Sender header in your tenant in the month of September, we will send you a Message Center Post by October 15th alerting you and providing some sample message IDs.

We are doing this to comply with RFC 5322 (https://www.rfc-editor.org/rfc/rfc5322#section-3.6.2) which mandates the Sender header to be present and contain a single address if the From header has more than one address. Noncompliance with this could be exploited by attackers, allowing them to impersonate a sender address by misleading the client into using the From header to determine the sender instead of the Sender header.

When this will happen:

February 3, 2025 (previously December 1st)

We are delaying the rollout start date from December to February 3rd 2025 in order to provide more time to customers for investigating messages exhibiting multiple P2 From Addresses without a Sender Address.

Most of the traffic exhibiting multiple P2 From Addresses without a Sender Address will be inbound spam destined for your tenant sent by malicious spammers on the internet.

Some customers are sending legitimate emails with this malformed header configuration. On October 15, we sent a targeted MC post to customers showing high volumes of messages exhibiting multiple P2 From Addresses without a Sender Address as they may be impacted by this change.

For investigating if you will be impacted by this change, focus your investigation on messages sent using On Premises Inbound Connectors to Exchange Online. Authenticated mail submission is not impacted because submitting messages like this using those submissions are not allowed (Graph, Outlook clients, SMTP AUTH Client Submission).

How this affects your organization:

If email clients including devices and applications that you use to send messages, do so using multiple From addresses but without a Sender address header after December 1st, you will get an NDR error code 550 5.1.20 “Multiple From addresses are not allowed without Sender address’”.

What you can do to prepare:

When this change is in effect, if you need to send a message that has more than one email address in the From field, make sure that you have a single email address in the Sender header.

If you expect this change to cause any issues for your organization, please share that feedback.

Microsoft 365

MC986516 — Microsoft Forms | Data sync to Microsoft Excel: migrating from the older solution to the new solution

We will be retiring the old data sync feature from Microsoft Forms in GCC. Instead, we recommend new live data sync to Excel solution.

Note: You may have received MC943681 (November '24) if we had identified that your tenant utilized legacy data sync between August '24 and October '24.

When this will happen:

We will begin rolling out the change on February 13, 2025, and expect to complete by February 27, 2025.

How this will affect your organization:

Users who rely on the older version to sync data from Forms to Excel will need to manually update the data sync to the new solution. After the old data sync solution has been deprecated, existing Excel workbooks using the old data sync solution will no longer receive new responses. Users can still migrate these existing Excel workbooks to the new data sync solution to receive new responses when needed.

For each form using the old syncing solution, users can migrate the form according to the instructions provided in Forms and Excel for the web. More details can be found here: Update to the new solution for syncing forms responses to Excel - Microsoft Community Hub.
If users are using the old data sync solution in a workflow that relies on the Excel workbook being updated automatically without any user action, they will be impacted by the change as the Excel file will only get updated when it’s opened in a supported Excel client. These users will have to manually update their workflow. Our suggested solution is to use Power Automate: Setting Up an Automated Workflow Between Microsoft Forms and Excel Through Power Automate - Microsoft Support

Note:

The older version of the data sync exists in group forms created with Microsoft 365 Groups.
The new data sync can only be triggered in Excel for the web. If users want to receive new Forms response data in the Excel desktop app, open the file in Excel for the web, and then wait for the desktop app file to sync from the web file. (Support for other versions of Excel is in progress.)
The new data sync solution will be on by default and available to all Forms and Excel for the web customers.

What you need to do to prepare:

Share the migration solution if users report they cannot get Forms data updated in Excel.
Learn more: Introducing Forms data sync to Excel - Microsoft Community Hub

MC980798 — Microsoft Excel: Python in Excel will be generally available in Excel for Windows (GCC)

Microsoft 365 Roadmap ID 475046

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

When this will happen:

General Availability (GCC): We will begin rolling out to Excel for Windows mid-February 2025 and expect to complete by early March 2025.

After we complete the rollout to Excel for Windows, we will send a separate message with the timeline for rolling out this change to Microsoft Excel for the web and Microsoft Excel for Mac.

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

MC833890 — (Updated) Microsoft Word, Excel, PowerPoint: Protect sensitive files with dynamic watermarking

Microsoft 365 Roadmap ID 400717

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

Update December 20, 2024: There is an issue causing users to get an access denied error when attempting to open files for which they are not the RMS owner, when the file has a sensitivity label configured for dynamic watermarking. We are working to resolve this issue.

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

Documentation - Office 365 IP Address and URL web service

January 30. 2025 - GCC

January 30. 2025 - GCC High

January 30. 2025 - DOD

Updated Feb 27, 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

February 2025 - Microsoft 365 US Public Sector Roadmap Newsletter

New location sharing settings for emergency calls in Teams, SharePoint Server 2016 and 2019 end of support July 2026, New Microsoft Volume Indicator for Teams

SharePoint

End of support for SharePoint Server 2016 and 2019 is scheduled for July 14, 2026. It's advisable to upgrade directly to SharePoint Server Subscription Edition

Purview Information Protection

New workload for Copilot in Content Explorer

Microsoft 365

New deployments of Microsoft 365 desktop client apps to include new Outlook – GCC

Unlocking Opportunities for Government Efficiency

Feb 21: Announcing M365 Community Days DC 2025 in Arlington

Where to Start with Microsoft Teams Apps in Gov Clouds

Microsoft 365 Government Adoption Resources

SharePoint Online / OneDrive for Business

MC996585 — Microsoft SharePoint: Updated document libraries

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

MC976819 — (Updated) Microsoft SharePoint: New Accessibility assistant tool for authoring Pages

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

MC974354 — (Updated) Microsoft SharePoint Online: Re-imagined Hero with the new carousel layout in pages and news

MC973514 — SharePoint Pages Flexible Sections

MC973498 — Microsoft SharePoint: New "Editorial card" web part for Pages and News

MC947052 — (Updated) Microsoft SharePoint: Filter search results by "Messages"

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

MC906496 — (Updated) Microsoft OneDrive and Microsoft SharePoint: New setting to disable presence in the file viewer

MC693865 — (Updated) SharePoint Add-In retirement in Microsoft 365

MC693863 — (Updated) Azure ACS retirement in Microsoft 365

MC542767 — (Updated) SharePoint 2013 workflow retirement

Microsoft Copilot

MC981631 — Microsoft Teams: Microsoft 365 Copilot in Teams meetings will be generally available to GCC

Microsoft Viva

MC989956 — Microsoft Viva: Edit and schedule polls in Viva Engage

MC979826 — (Updated) Microsoft Viva Connections: Update to app name

Microsoft Teams

MC996588 — Microsoft Teams: Adding and editing external contacts on Teams phone devices

MC996587 — Microsoft Teams Voice: Link Voice apps without using resource accounts

MC994288 — Microsoft Teams: Speed dial on line keys for touch phone devices

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

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

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

MC989975 — Microsoft Teams: Occupancy status on Teams panels

MC989974 — Microsoft Teams: New microphone volume indicator for users

MC985484 — Microsoft Teams: Additional work information in people search results

MC981629 — Microsoft Teams: Updates to make meeting transcripts more accurate and reliable

MC980799 — Microsoft Teams: Allow presenters to moderate Q&A

MC979828 — Microsoft Teams: Cross-cloud collaboration in Virtualized Desktop Infrastructure

MC978932 — Large Events: End Session for Attendees and Return Presenters to Green Room

MC975308 — (Updated) Microsoft Teams: iPad Multi-window support

MC975304 — Microsoft Teams: The Approvals app is generally available (DoD)

MC974361 — (Updated) Microsoft Teams: Edit your display name in meetings

MC973513 — Simplify UX flow to enable Together Mode

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

MC973497 — Microsoft Teams: The Updates app is generally available (GCC)

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

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

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

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

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

MC952888 — Microsoft Teams: Pop out Chat, Copilot, and Notes panes in meetings

MC950898 — (Updated) Microsoft Teams: Forwarding loop components

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

MC939927 — (Updated) Microsoft Teams Premium: Decorate your background

MC932488 — (Updated) Microsoft Teams: New DVR capabilities for town halls (desktop and web)

MC929034 — (Updated) Microsoft Teams: Best practices configuration dashboard in Teams admin center

MC923415 — (Updated) Microsoft Teams: Virtualized Desktop Infrastructure status indicator

MC920179 — (Updated) Microsoft Teams: The new streamlined Chat and Channels experience

MC920084 — (Updated) Microsoft Teams: Usage reports for bookable desks

MC918570 — (Updated) Microsoft Teams: Custom name on Teams panels

MC916866 — (Updated) Microsoft Teams: Shifts Graph APIs in beta moved to production (v1.0)

MC912709 — (Updated) Microsoft Teams: Bookable desks and BYOD rooms supported in GCC

MC912707 — (Updated) Microsoft Teams: New policy for voice and face enrollment will default to "On" (configure now)

MC908117 — (Updated) Microsoft Teams: Swap screens on Teams Rooms on Android

MC907108 — (Updated) Microsoft Teams: Admin email support for "Report a problem" on Teams Rooms on Android

MC906501 — (Updated) Microsoft Teams: Net Promoter Score survey on Teams Rooms on Android

MC903632 — (Updated) Microsoft Teams Rooms on Android: 3x3 video gallery on dual displays

MC889534 — (Updated) Microsoft Teams: Embed support for Teams town hall

MC884018 — (Updated) Microsoft Teams: Set sensitivity labels for town halls and webinar

MC884009 — (Updated) Microsoft Teams: Start/stop recording on Teams Rooms on Windows

MC866447 — (Updated) CAPTCHA Verification for Anonymous Meeting Participants

MC818885 — (Updated) Microsoft Teams: Multiple camera view for Teams Rooms on Windows

MC809602 — (Updated) Microsoft Teams: New skin tone settings and reactions