Microsoft Roadmap, messagecenter and blogs updates from 21-02-2025

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

Users will be able to summarize files with Summarize for me using Microsoft Copilot within one-on-one or group Microsoft Teams chats. This feature will work on common file types like Word and PDF initially, and other file formats will be added over time. This summarization respects the file’s security policies, ensuring that only users with access to the file receive a summary, which will carry the same sensitivity label as the original file. A Microsoft 365 Copilot license is required to use this feature.

This message is associated with Microsoft 365 Roadmap ID 418564.

 [When this will happen:] 

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

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

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

[How this will affect your organization:]

Users will be able to summarize files with Summarize for me in Copilot within Teams chats.

This feature will be available by default.  

[What you need to do to prepare:]

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

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

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

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

This message is associated with Microsoft 365 Roadmap ID 467445.

[When this will happen:]

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

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

[How this will affect your organization:]

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

Closeup view of the chat icon:

This feature will be available by default.

[What you need to do to prepare:]

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

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

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

Coming soon to new Microsoft Outlook: Newsletters in Outlook enable customers to create, distribute, and track success for their internal email newsletters. This message applies to the new Outlook for Windows and Outlook for the web.

This message is associated with Microsoft 365 Roadmap ID 328282

[When this will happen:]

Public Preview: We will begin rolling out mid-February 2025 and expect to complete by late March 2025. Rollout will begin in Targeted Release and will proceed to Standard Release.

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

[How this will affect your organization:]

After this rollout, users in your organization using the new Outlook for Windows and Outlook for the Web can create professional and engaging email newsletters with a variety of rich elements and leverage built-in tools to manage reader engagement. Readers can discover and subscribe to newsletters that interest them using the new Explore page in the Outlook Newsletters module, accessible in the left-side navigation menu. The new module also includes pages for users to view their drafts.

[What you need to do to prepare:]

Outlook Newsletters will roll out on the specified date as an opt-in preview, meaning that no users in your organization will have access to the new module without you taking additional configuration steps.

User access to Outlook Newsletters is controlled by the OwaMailboxPolicy. OutlookNewslettersAccessLevel property. The default value of this property is Undefined until you set it explicitly, which will default to NoAccess while Outlook Newsletters remains in Preview. You can use Set-OwaMailboxPolicy to update this property to ReadWrite, ReadOnly, or NoAccess. Users with ReadWrite access can create content in Outlook Newsletters while ReadOnly limits users to accessing content created by others in your organization.

For more information on using OutlookNewslettersAccessLevel, please see: Newsletters in Outlook (Preview) – Microsoft 365 Apps | Microsoft Learn

After enabling Outlook Newsletters, you may want to notify your users about this change and update any relevant documentation.

End-user help: Newsletters in Outlook (Preview) – Microsoft Support

Ongoing updates:

• Some keyboard navigation and narrator support is still being finished while in Public Preview.
• Soft delete support is still in development.
• GoLocal support is still in planning.

The Microsoft 365 (Office) app has become the Microsoft 365 Copilot app. After this rollout, users will notice changes in the Microsoft Outlook apps for iOS and Android. Also, when Outlook for iOS and Android users view their account list in Settings, they will notice a new icon for their Microsoft account.

[When this will happen:]

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

[How this will affect your organization:]

Before this rollout, Microsoft 365 (Office) app and Microsoft 365 accounts in the Microsoft Outlook apps for iOS and Android have this icon:

After this rollout, the app for iOS and Android will be called Microsoft 365 Copilot and will have this icon:

Microsoft 365 accounts will be represented by the Microsoft logo:

This change will be 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 and update relevant documentation.

Learn more: The Microsoft 365 app transition to the Microsoft 365 Copilot app – Microsoft Support

Note: If your organization uses Microsoft OneNote, please read.

As part of the Microsoft Secure Future Initiative and to address the growing number of cyber threats, we will change the authentication flow for Microsoft Graph OneNote APIs.

What is the update?

Effective March 31, 2025, we will retire support for authentication tokens with application permissions (app-only tokens) for MSGraph OneNote APIs. We will continue to support authentication tokens that have delegated permissions. While app-only tokens are easy to use, they may be more easily exploited compared to more sophisticated authorization methods. Requests to the Notes API endpoints using tokens with application permissions will return 401 unauthorized errors starting March 31, 2025.

How do I know if this update impacts my service?

1. Your service will be impacted if you have a custom third party or internal application that performs operations using app-only authentication tokens. Overview of Microsoft Graph permissions – Microsoft Graph | Microsoft Learn documents the difference between delegated access and app-only access.
2. Your service will not be impacted by these changes if you do not use a third-party or a custom internal application (an “app”) to perform operations on OneNote Notebooks.
3. Your service will not be impacted by these changes if you use an app, but it performs operations only using “delegated access” (also known as app+user) permissions.

What action is required on my part?

Before March 31, 2025, third-party applications using app-only tokens will need to migrate to using delegated authentication tokens. This update is necessary to enhance the security of your data.

To introduce a more secure form of authorization, please take these steps:

1. Share this message if you rely on a system integrator partner or other third-party solution to perform operations on OneNote notebooks so that they can take further action.
2. Transition to using a delegated authentication model if you have your own custom internal application that performs operations on OneNote notebooks and that requires each user to approve the app or an admin to approve on behalf of the user(s).
3. Transition to using a delegated authentication model with admin consent flow if you are a system integrator partner and your app uses app-only authentication. To do this you will need to make changes to your app using the links in the Learn more section. After those changes are complete, a Global tenant admin will need to approve the app for all users in their tenant through the Microsoft Entra admin center.

Learn more

• Learn how to configure delegated access for the impacted apps: Get access on behalf of a user – Microsoft Graph | Microsoft Learn
• If you have questions about user consent vs admin consent flows for delegated access, please review Microsoft Entra app consent experiences – Microsoft identity platform | Microsoft Learn

We appreciate your cooperation in making these necessary changes to ensure the security of your data.

As part of our Secure Future initiative and our commitment to safeguarding customer data, we are making important updates to the me@onenote feature in Microsoft OneNote on the web.

What is the change?

We will retire the me@onenote feature on March 26, 2025, due to low usage and the availability of an alternative feature, Send to OneNote. After the retirement, users will not be able to send Microsoft Outlook emails to OneNote using the me@onenote feature. Instead, we recommend using the Send to OneNote feature in Outlook, which allows users to send email messages and meeting invitations directly from Outlook to their OneNote notebooks and sections. The Send to OneNote feature ensures a seamless transition and continued functionality.

How will we communicate this change to users?

Users will find this banner on the me@onenote page: The me@onenote feature will be deprecated in March. To continue sending your Outlook emails to OneNote, please use the Send to OneNote feature:

Users who send use the me@onenote feature after Mach 26, 2025 will receive an auto reply about the retirement with a link to the Send to OneNote feature.

What action is required on my part?

This change will happen automatically by the specified date. No admin action is required. Please notify your users about this change, update relevant documentation as appropriate, and share the Send to OneNote alternative feature.

We thank you for your understanding and cooperation as we work to enhance our services.

Coming soon to Microsoft Purview | Insider Risk Management: We will increase policy creation limits from 20 policies per template to a maximum of 100 overall active policies. After the rollout, for example, an organization may have 50 data leak policy templates because the limit will now apply to all active policies instead of applying to each policy template.

This message is associated with Microsoft 365 Roadmap ID 477364.

[When this will happen:]

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

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

[How this will affect your organization:]

This change will be on by default.

[What you need to do to prepare:]

No impact to your organization.

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.

Learn about policy template limits in Learn about insider risk management policy templates | Microsoft Learn (will be updated before rollout)

We are excited to announce the upcoming Viva Glint Tenant Administrator role for Microsoft Viva Glint in Microsoft Entra. With this role, admins will have dedicated permissions to manage Viva Glint-related settings in the Microsoft 365 admin center, without requiring the elevated privileges of Global Admin or User Admin roles. This role is essential for users who need to read and configure Viva Glint settings in the Microsoft 365 admin center, assign Viva Glint service admins, and create or manage Microsoft Azure support tickets.

This message is associated with Microsoft 365 Roadmap ID 479414.

[When this will happen:]

General Availability (Worldwide): 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, admins will be able to assign the new Viva Glint Tenant Administrator role to users in the:

• Microsoft Entra portal
• Microsoft 365 admin center

The new role will be available by default.

[What you need to do to prepare:]

We recommend admins:

1. Review the Viva Glint Tenant Administrator role documentation to understand its capabilities.
2. Assess current roles to identify where the new role fits.
3. Communicate changes to staff if needed.

This rollout will happen automatically 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

• Microsoft Entra: Entra built-in roles | Microsoft Learn (will be updated before rollout)
• Microsoft Viva: Key Roles for Viva Glint | Microsoft Learn (will be updated before rollout)

Within Microsoft Teams, apps that are found in outlook.com and office.com will show ratings and reviews in the app store listing page and the details page.

[When this will happen:]

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

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

[How this will affect your organization:]

Users will be able to see their apps’ ratings and reviews in outlook.com and office.com.

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

A revamped Permissions section in the Microsoft Teams app details page will be available. This gives the user a better understanding of their data that the app can access. It’s broken down into categories, which makes it easier to consume all the permissions. There is now an Expand All button that allows the user to consume all the permissions at once.

[When this will happen:]

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:]

With this Teams feature update, it is easier for end-users to consume and process all the user data and information that the Teams app can access.

Prior Permissions tab

New Permissions tab

These updates will allow the Teams app to read and access information related to the user and information in the user’s chats, channels, and meetings. The app will have permission to send and receive notifications.

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

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

This message applies to Teams for Windows desktop.

[When this will happen:]

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

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

[How this will affect your organization]

After this rollout, these changes will affect all users:

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

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

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

[What you need to do to prepare]

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

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.

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

Coming soon for Microsoft Teams: When users or admins configure Microsoft Edge as the browser to open web links in Teams, then links in Teams chat will be open in Edge, and Edge launches in the profile that matches the authenticated profile. Users will benefit from a seamless browsing experience that integrates their identity and user data across Microsoft apps.&

This message is associated with Microsoft 365 Roadmap ID 414521.

[When this will happen:]

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

[How this will affect your organization:]

Before this rollout, users are asked to reauthenticate links in the browser, which slows down users.

By default, there are no changes.

By default, the feature will be on with setting System default browser and Teams links will open in the system’s default browser. System default browser refers to the default browser specified on the user’s Mac device.

Admins can control the settings and availability of this feature (and override user settings) by policy in the Microsoft 365 Apps admin center:

• If this policy is enabled, admins can go to Choose which browser opens web links and select Microsoft Edge.
• If this policy is disabled or not configured, web links will open in the system default browser.

How admins update the policy in the Microsoft 365 Apps admin center:

After admins configure the policy to open links with Edge in Teams, this banner displays to users:

How users update the browser settings in Teams:

[What you need to do to prepare:]

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

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

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

We are introducing updates that provide capabilities for managing custom fonts for Microsoft SharePoint and Microsoft Viva Connections. This includes the ability to hide the From Microsoft font packages from Change the look, the ability to apply a font package in your site templates, and updated availability for the From Microsoft font packages.

This message is associated with Microsoft 365 Roadmap ID 420933.

[When this will happen:]

Targeted Release: We will begin rolling out mid-October 2024 and expect to complete by early November 2024

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

[How this will affect your organization:]

This rollout will include new Microsoft PowerShell commands that will allow you to get information about the From Microsoft font packages and the ability to hide these font packages if desired. More details for these commands will be available in our PowerShell documentation. We will also provide an update to add an additional site script action that will allow developers and administrators to include and apply font packages as a part of a site template.

Sample action details:

{

"verb": "applyFontPackage",

"fontPackageTitle": "Amasis MT",

"fontPackageId": "1e7a7803-045d-44df-9c7a-d2f2f8562e51",

"fontPackageStore": "OutOfBox"

}

This rollout will also include a change to allow tenants that meet the requirements for custom fonts to discover the feature without needing to activate the SharePoint brand center. For tenants that are currently using the Organization Assets Library functionality with Public content delivery network (CDN), these organizations will see Fonts and the From Microsoft font packages in Change the look without any additional actions.

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

Get started with the SharePoint Online Management Shell | Microsoft Learn (will be updated)

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

Coming soon for Microsoft Outlook for iOS and Android: Minimize draft emails and quickly access them again from the message list or calendar view.

This message is associated with Microsoft 365 Roadmap ID 470304.

[When this will happen:]

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

[How this will affect your organization:]

Outlook will help you compose emails more quickly and efficiently by allowing you to minimize your draft emails and quickly access them again from the message list or calendar view. This means that while composing an email you can easily get information you need from your calendar or other emails and easily get back into the draft you are working on without ever having to go to the Draft folder.

To start, select the minimize icon in the upper right corner:

This change will be on by default.

[What you need to do to prepare:]

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

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

To maintain the best performance and reliability of our service, we are updating the page size limit for the phone number retrieval API (Get-CsPhoneNumberAssignment cmdlet) to a maximum of 1,000 numbers per query.

[When this will happen:]

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

[How this will affect your organization:]

From January 6, 2025, any request with -Top parameter exceeding 1,000 will result in a “Bad request.” Please ensure that your Get-CsPhoneNumberAssignment requests do not surpass this limit. If the intended operation is to export your numbers, please use https://learn.microsoft.com/en-us/powershell/module/teams/export-csacquiredphonenumber?view=teams-ps

[What you need to do to prepare:]

Please ensure that your Get-CsPhoneNumberAssignment requests do not surpass this limit.

Updated February 20, 2025: There are new details available regarding the Microsoft Search in Bing retirement. The FAQ is now available at Guidance for retiring Microsoft Search in Bing for your organization.

Microsoft Search in Bing, the search experience for work and school available on Bing.com, is being deprecated. The last day of its availability is on March 31, 2025. This change is being made as we streamline search experiences and focus on enhancing core productivity tools.

The Microsoft Edge for Business address bar and the Windows search box will continue to support work and school search, with some adjustments detailed below.

Details of the Change

After March 31, 2025, Microsoft Search in Bing will no longer be available, with changes as follows:

• Bing.com will no longer show work or school search results. Consequently, there will not be a dedicated page of work or school results and users’ work or school profiles will no longer appear on Bing.com. However, selecting the Work or School tab on Bing.com will redirect users to the new Microsoft Search experience on M365.cloud.microsoft (formerly Office.com and Microsoft365.com).
• Search boxes you’ve configured to point to Microsoft Search in Bing will no longer provide work or school results.
• The Edge for Business address bar and Windows search box will continue to support work and school search with some adjustments, including:
  • The Edge for Business address bar will no longer return work or school search results on a Bing.com page but will continue to provide suggested results in the address bar. In addition, the address bar will send users to work and school results on M365.cloud.microsoft rather than Bing.com. Users of the address bar can continue to find work-related documents, bookmarks, and people in suggested results—clicking on these suggestions takes users to work or school results on M365.cloud.microsoft. Users can also type “work” in the address bar, hit the tab key, then input their work- or school-related query to get results on a M365.cloud.microsoft page. Work and school search results will include documents, people, and bookmarks. Work search for documents will be available initially, with additional content types available as quickly as possible.
  • The Windows search box will no longer display organization branding nor the “Work” or “School” tab but will continue to support work and school search. Search for documents and people remains available. will be available initially, with additional content types available as quickly as possible. With these changes, users will see some UX changes in the Windows search box.

As before, the core Microsoft Search experience remains accessible through M365.cloud.microsoft (formerly Office.com and Microsoft365.com) and SharePoint Online.

• Additionally, Entra ID sign-in will no longer be available on Bing.com, since work and school search is no longer available on Bing.com.

An FAQ and further details are now available at Guidance for retiring Microsoft Search in Bing for your organization, which will be updated regularly.

[When will this happen:]

The last day of availability of Microsoft Search in Bing is March 31, 2025.

[How this affects your organization:]

For organizations using Microsoft Search in Bing, users will need to transition to using Microsoft Search through M365.cloud.microsoft (formerly Office.com and Microsoft365.com) and SharePoint Online.

Users who are accustomed to using the Edge for Business address bar and the Windows search box can continue to conduct work searches through these endpoints entry points, with the expectation that there will be some adjustment in these experiences after the deprecation date. (For details on changes, please refer to the FAQ: https://aka.ms/MSBFAQ.)

Users who click on suggestions in the Edge for Business address bar or Windows search box may be redirected to Microsoft365.com before March 31, 2025. Also, as we begin testing the retirement experience, a small set of users may find before March 31 that Bing is intermittently unavailable as an entry point for work search. We recommend that you proactively inform your users of the change and direct them to M365.cloud.microsoft (formerly Office.com and Microsoft365.com) and SharePoint Online. Adding M365.cloud.microsoft to their favorites or to the favorites bar in Edge for Business may be a helpful alternative pathway.

[What you can do to prepare:]

Customers should prepare to stop using Microsoft Search in Bing by March 31, 2025, and transition to using Microsoft Search through M365.cloud.microsoft (formerly Office.com and Microsoft365.com) and SharePoint Online. We recommend that you inform users about the upcoming change and the alternatives available.

Adding your preferred entry point from this set to favorites or favorites bar in Edge may be a helpful alternative pathway. Admins can easily set favorites in Edge for their organization, please see details here.

Additionally, users can continue to use the Edge for Business address bar and the Windows search box, with some changes expected. Please educate users that they should now type “work” in the address bar, hit the tab key, then type in their work-related query to get work results on a M365.cloud.microsoft page.

If your organization is using the AddressBarMicrosoftSearchInBingProviderEnabled policy today, you should update to the AddressBarWorkSearchResultsEnabled policy, if the policy is still needed.

The new policy, AddressBarWorkSearchResultsEnabled, will be available starting in early March, with Edge for Business version 134 (ahead of the Microsoft Search in Bing deprecation). This allows admins to configure the display of work suggestions in the address bar. If the policy is enabled or not configured, users who are signed into Edge for Business with their Entra ID can view internal work-related suggestions, such as bookmarks, files, and people results powered by Microsoft 365, in the Edge for Business address bar suggestion dropdown. If the policy is disabled, Entra ID signed-in users will not see internal workplace results in the Microsoft Edge address bar suggestion dropdown.

Admins who wish to set their own deprecation date prior to March 31, 2025, can turn off Microsoft Search in Bing by going to the Microsoft 365 admin center > Settings > Search & Intelligence.

Regarding SafeSearch settings:

• If you had set the search experience for your organization to “School search,” SafeSearch was set to Strict by default. If you’d like to ensure that your users continue to have SafeSearch set to Strict after the Microsoft Search in Bing retirement, you can map www.bing.com to strict.bing.com at a network level. See Blocking adult content with SafeSearch or blocking Chat for more details.

Note: The search history feature for work or school search is changing along with the retirement of Microsoft Search in Bing. Details are not yet determined, but they will be added to the FAQ once they’re finalized. 

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

Coming soon to Microsoft Teams: Users will be able to set their preference for how their cloud-hosted Microsoft Word, Microsoft Excel and Microsoft PowerPoint files should open when they select links for these files from Teams. The new setting (open in a browser, desktop app, or directly in Teams) will extend to links selected in other Microsoft365 apps, starting with classic Microsoft Outlook, Word, Excel, and PowerPoint, for greater consistency across apps.

This message applies to Teams for Windows desktop.

This message is associated with Microsoft 365 Roadmap ID 471000.

[When this will happen:]

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

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

[How this will affect your organization:]

After this rollout, user can set the file open preference in Teams by following instructions in Open file links directly in Microsoft 365 desktop apps from Teams and classic Outlook – Microsoft Support. Users will be still able to set separate file open preferences for Teams only.

File open preference will apply to Word, Excel and PowerPoint links selected from Word, Excel, PowerPoint, Teams for Windows desktop, and classic Outlook.

This change will be available by default.

[What you need to do to prepare:]

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

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

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

This message is associated with Microsoft 365 Roadmap ID 473887.

[When this will happen:]

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

[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

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

Coming soon for Microsoft Teams: Users will be able to share a file from a Chat conversation, a Chat Shared tab, or a channel post to 1:1 chats, group chats, or channels with fewer clicks. When files are shared, their permissions are maintained, ensuring that recipients have the appropriate access rights. Users can include a message with the shared file and @mention recipients.

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

This message is associated with Microsoft 365 Roadmap ID 475852.

[When this will happen:]

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

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

[How this will affect your organization:]

When users shares a file from a Chat conversation, a Chat Shared tab, or a channel post, a dialog box will pop up. Options available in the dialog box:

1. Mandatory: Names of the intended recipients or the channel where the user intends to share the post.
2. Optional: Add text to the message (or @mention users).
3. Optional: Modify permissions.

The new sharing icon in the file preview in a Chat conversation:

The Share option (accessed from the three-dot menu) in the Chat Shared tab:

After the user selects Send, the file will be shared with the intended recipients as a Teams message in Chat or will be posted to the intended channel.

[What you need to do to prepare:]

The feature will enabled by default. 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.