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

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

Microsoft Teams admin center has brought security and compliance information directly into the Teams admin center app detail pages. In the security and compliance tab, users can find information on an app’s security and compliance posture to help them make more informed decisions about which apps they choose to trust. Information may include things such as assessments for data security, vulnerability scanning, Service Organization Controls (SOC), Payment Card Industry (PCI), and more. Furthermore, admins will now have the ability to view the count of apps that have completed the Microsoft 365 Certification or the publisher attestation portion of the Microsoft 365 app compliance program. Admins who may not have explored these new experiences will be notified within the Teams admin center upon the release of this feature.

This feature will bring a notification to Teams admin center that helps inform and direct admins via a click-through experience from the Teams admin center dashboard into the manage apps page. There, they will be given a quick tutorial on the fastest way to access the security and compliance info for an app. In the Manage apps page, they will also find a new tile that gives a live count of the number of Teams apps that have completed the Microsoft 365 Certification or Publisher attestation.

[When this will happen:]

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

[How this will affect your organization:]

Admins will have increased awareness of app security and compliance information in Teams admin center and a view into the current number of apps that have completed the Microsoft 365 Certification or the publisher attestation.

[What you need to do to prepare:]

This rollout will happen automatically with no admin action required.

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

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

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

This message is associated with Microsoft 365 Roadmap ID 476487.

[When this will happen:]

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

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

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

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

[How this will affect your organization:]

This change will be available by default.

[What you need to do to prepare:]

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

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

We will retire the Microsoft Feed app from Microsoft Outlook for iOS and Android starting May 1, 2025 and ending by late May, 2025.

Users of your organization will no longer be able to access the Feed tab in Microsoft Outlook for iOS and Android. The Feed app will disappear from the bottom of the screen for users who had pinned it there. The Feed app will no longer be available in the Apps list for pinning.

As an alternative to the Feed, we recommend using Copilot in Microsoft Outlook. Other alternatives that recommend content similar to the Feed:

• The Files app in Microsoft Outlook
• The Microsoft OneDrive app for iOS and Android
• The Recommended section on Microsoft365.com
• The For you section in OneDrive on web

This change will happen automatically on the specified dates and no specific actions are required. You may want to notify your users about this change and update any relevant documentation.

New LDAP query events will be added to the IdentityQueryEvents table in Advanced Hunting to provide more visibility into additional LDAP search queries running in the customer environment.

[When this will happen:]

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

[How this will affect your organization:]

This update may lead to an increase in activity within the Advanced Hunting IdentityQueryEvents table for LDAP queries. If you have custom detections related to these queries, you may see a higher number of triggered alerts.

This update is available by default. 

[What you need to do to prepare:]

We recommend that you review your existing custom detections to ensure they align with your objectives. If needed, you can adjust your query accordingly.

More information: Create and manage custom detection rules in Microsoft Defender XDR

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

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

This message is associated with Microsoft 365 Roadmap ID 89975.

[When this will happen:]

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

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

[How this will affect your organization:]

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

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

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

This change will be available by default.

[What you need to do to prepare:]

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

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

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

We will retire Microsoft Skype interoperability from Microsoft Teams on May 1, 2025. Teams users will no longer be able to communicate with Skype accounts after this change is implemented.

This retirement will happen automatically by the specified date. No admin action is required. Please notify your users about this change, update relevant documentation, and share information about continuing communication through Teams free interoperability.

Learn more: https://go.microsoft.com/fwlink/?linkid=2302203

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

[When this will happen:]

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

[Are there any recommended alternatives to the “Shared with Us” feature:]

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

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

[What you need to do to prepare:]

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

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

The Agent UX, previously available on Microsoft 365 Copilot desktop and web, is now being enabled on mobile endpoints. This new feature will allow end-users to discover installed agents, add new agents, and chat with agents in mobile Copilot on Microsoft Teams, Microsoft Outlook, and the Copilot app (formerly Microsoft 365 app).

[When this will happen:]

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

[How this will affect your organization:]

• Discover: Users can now easily find and interact with agents that are already installed from Copilot desktop and web.
• Add: The new Agent UX allows users to add new agents from the store on mobile.
• Use: Users can interact and chat with agents in mobile Copilot on Teams, Outlook, and the Microsoft 365 Copilot app.

This new feature is available by default.

[What you need to do to prepare:]

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

• September 2025: DES in Kerberos will be removed from Windows Server 2025 and Windows 11, version 24H2. 
• Alternative solutions are available to you today. 

We’re making some changes to the total number of items that can be created in a Fabric workspace. Currently, there are limits on the number of Power BI items allowed in a workspace, but no such limits for Fabric items. With this change, there will be a combined limit of 1000 Fabric and Power BI items per workspace. i.e. a workspace can have a total of 1000 Fabric and Power BI items. This would help ensure quality of service for users, by preventing capacity overload due to too many items in a Fabric workspace. For tenants where Fabric is not enabled, the existing limits of 1000 Power BI items per workspace will continue to apply. 

[When this will happen:]

This change will start rolling out from late March 2025, and will finish on mid-April 2025.

[How this will affect your organization:]

Once this change is implemented:

• For workspaces that contain fewer than 1000 items, once the limit of 1000 is reached, users will be unable to create additional items.
• For workspaces that exceed 1000 items as of April 10, 2025, a grace period of 180 days will be provided. After the expiration of this grace period, users will no longer be able to create additional items in the workspace.
• To create new items in workspaces that have reached the item limit, users will need to delete items until the total number of items in the workspace is less than 1000.

[What you need to do to prepare:]

Admins should assess the number of items per workspace in their tenant and develop a plan for managing items in both current and future workspaces. The total number of items in a workspace can be found in the Admin Monitoring workspace, within the Feature adoption and usage report under the Inventory section (documentation can be found here).

We are pleased to announce the availability of a new, centralized Microsoft 365 Copilot release notes page. This page consolidates all Copilot-related releases across the Microsoft 365 suite—such as Word, Excel, PowerPoint, Outlook, Teams, Microsoft 365 Copilot app, Copilot chat, and more—into a single, easy-to-reference resource. It also includes platform-specific filters for Windows, Web, Mac, Android, and iOS to help you quickly locate the updates most relevant to your organization.

This new page highlights features and enhancements that have reached General Availability (GA) across selected platforms, ensuring you can stay informed about the latest capabilities of Copilot across Microsoft 365.

[When this will happen]

The new Copilot release notes page is available now at Microsoft 365 Copilot release notes. We will continue to update it regularly as new Copilot features become generally available across different services and platforms.

[How this will affect your organization]

• Centralized information: Rather than visiting multiple sources, you can now view all Copilot GA releases in one location.
• Easier discovery: Filter by the specific platform(s) you use (Windows, Web, Mac, Android, iOS) for more targeted release information.
• Up-to-date insights: The page is refreshed every other week, ensuring you always have the latest Copilot updates at your fingertips.

[What you need to do to prepare]

• Bookmark the page: We recommend that admins and end users bookmark this new release notes page for quick access.
• Share internally: Distribute the link to this page within your organization so teams can stay aware of all relevant Copilot updates.
• Review and plan: Use the information in the release notes to plan for any necessary training, user documentation updates, or adoption strategies aligned with your organization’s Copilot deployment.
• Submit your feedback: Your input is important to us. Use the ‘Feedback’ button on the Copilot release notes page to share what you like and where improvements can be made so we can continue enhancing this resource to better meet your needs.

For Teams Room customers who are moving to the Intune Company Portal version 5.0.6152 or above through firmware updates or app-only updates have to ensure that Device Administrator (DA) privilege is enabled in their Microsoft Intune Portal.

This has been called out as a known issue: Known issues with Teams Rooms on Android 

Note: If your organization does not utilize Teams Room, you can safely disregard this message.

[How this will affect your organization:]

Without DA being enabled, the customers will encounter the following error message on Android based Teams devices during sign-in:

“This device isn’t enrolled in device administrator. Contact your Admin.”

[What you need to do to prepare:]

Ensure that Device Administrator (DA) privilege is enabled in their Microsoft Intune Portal as shared in the instructions given here: Intune and Conditional Access for Teams Phones 

Coming soon: Users will be able to record video clips in Microsoft Teams channels, just like users can in Teams chat.

Users can record themselves, their screen, or audio-only clips and send them in a channel as a new post or a reply. Recording in channels respects the same Video messages policy as recording in chat. As an admin, if you have already enabled or disabled this policy for recording in chat, we will respect it for recording in channels too.

[When this will happen:]

General Availability (Worldwide, GCC): Available now, since early 2025.

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

After this rollout, a new Record video clip option will appear in the compose box under the Actions and apps button for channel posts or channel replies. A similar button already exists in the chat experience.

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

Learn more: Record a video or audio clip in Microsoft Teams – Microsoft Support

Starting in March 2025, Outlook will introduce a new setting that allows users to hide Copilot entry points (e.g., “Summarize this email”) from the app. This setting can be configured per account and will apply to both organizational and personal email accounts within the app. Once set, the preference will sync across all Outlook applications. This update is in response to user feedback.

[When this will happen:]

The rollout will begin in March 2025.

[How this affects your organization:]

Users will have the option to hide Copilot entry points in the following Outlook applications:

• New Outlook for Windows
• Outlook for iOS
• Outlook for Android
• Outlook for Mac
• Outlook on the Web

Classic Outlook for Windows will not have the ability to change this setting. However, any changes made in other Outlook applications will sync with Classic Outlook for Windows.

[What you can do to prepare:]

Admins should inform users about this new setting and its availability across different Outlook applications. No additional action is required as the setting will be available by default. 

Coming soon for Microsoft OneNote: The new OneNote (Desktop) – Protected virtual printer will roll out to all OneNote Windows desktop app users on x86 (32-bit) and x64 (64-bit) devices. We will automatically install the protected printer on all eligible devices (starting with Current Channel) with OneNote Windows app versions 2410 and later and devices running Windows 11 versions 26100 or higher. As a tenant admin, to ensure the successful installation of this printer on your organization’s devices, you must configure specific group policies.

This message is associated with Microsoft 365 Roadmap ID 402540.

[When this will happen:]

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

[How this will affect your organization:]

Why is Microsoft introducing this new printer when we already have a OneNote (Desktop) printer for the OneNote Windows app?

• Since October 2024, as a part of the new Modern Print platform, Windows has introduced a secure printing capability called Windows Protected Printing (WPP), which, when turned On, will uninstall and remove all non-IPP-based (Internet Printing Protocol) printers from independent hardware vendors (IHVs) and independent software vendors (ISVs) from the list of available printers, including the OneNote (Desktop) printer. To prevent feature issues for users of the OneNote (Desktop) printer, we’re introducing the new protected virtual printer, which is based on Microsoft’s IPP class driver and is compatible with WPP. Learn more about WPP and the Modern Print platform: Modern Print Platform – Microsoft Support

Our organization has many regular users of the Print to OneNote capability using the existing OneNote (Desktop) printer. Should they expect any changes to their workflow?

• No. Like the existing OneNote (Desktop) printer, when users try to print a page, the new virtual printer will display in the list of printers as OneNote (Desktop) – Protected (refer to the screenshot in Print documents and files to OneNote – Microsoft Support). Users can switch to the printer of their choice to print to OneNote. Please note that with WPP on, only the protected virtual printer will be available for printing because the existing non-IPP based printers will be uninstalled. Learn more about WPP and eligible printers: A new, modern, and secure print experience from Windows | Microsoft Community Hub

What happens to the old OneNote (Desktop) printer already installed on user’s devices?

• On the target Windows 11 builds (>26100.0000) with WPP, turning WPP On will automatically uninstall the existing OneNote (Desktop) printer (because it is based on the v4 printer driver). When WPP is Off, the OneNote (Desktop) printer will continue to exist with the new protected printer on user devices when they upgrade to the target OneNote builds.

Can users of the OneNote app turn off or uninstall the new printer?

• Yes, if they have permission to uninstall apps on their device. The new protected virtual printer will be installed as a Print Support App (PSA) and can be completely uninstalled from the list of programs in their Windows Settings > Apps > Installed apps. The new printer can be seen installed as a separate app called OneNote (Desktop) – Protected Virtual Printer. NOTE: With WPP on, uninstalling the new protected virtual printer will break the Print to OneNote experience. To restore the protected printer, users will need to uninstall and then reinstall the OneNote app. Users should ensure their notes are synced before uninstalling to avoid losing unsynchronized changes.

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

As an admin, how can you ensure all eligible devices in your organization get the new printer installed without issues?

• The OneNote (Desktop) – Protected virtual printer will be installed by default (starting with Current Channel) in all OneNote Windows app versions 2410 and later running Windows 11 versions 26100 or higher.
• Please ensure that the group policy AllowTrustedApps is set to Enabled and the group policy BlockNonAdminUserInstall is set to Disabled. These settings are required to complete installation of the new virtual printer on your device. Learn more about other policy settings and registry keys that could prevent installation of this printer: How Group Policy works with packaged apps – MSIX | Microsoft Learn

Due to ongoing work on Microsoft Defender for Cloud Apps aimed at improving security and performance, you are required to update network information in your system’s firewall and additional third-party services by the dates noted below.

[When this will happen:]

Please follow these instructions by March 27, 2025, to ensure uninterrupted access to our services.

[How this affects your organization:]

You are receiving this message because our reporting indicates your organization may be using Microsoft Defender for Cloud Apps. Administrators may no longer be able to access Microsoft Defender for Cloud Apps services if the changes listed below are not completed by March 27, 2025, when this change is implemented.

[What you need to do to prepare:]

Please update your firewall rules to allow outbound traffic on port 443 to the new CDN endpoints before March 27, 2025:

• cdn.cloudappsecurity.com
• cdn-discovery.cloudappsecurity.com

All required outbound access URLs can also be found in Defender for Cloud Apps network requirements page under ‘Portal Access’. 

To use Defender for Cloud Apps in the Microsoft Defender Portal, make sure you add outbound port 443 for all IP addresses and DNS names listed in our documentation to your firewall’s allowlist.

To connect to third-party apps, enable Defender for Cloud Apps to connect from these IP addresses, also available in our documentation:

• US1: 23.101.201.123, 20.228.186.154
• US2: 20.15.114.156, 172.202.90.196
• US3: 20.3.226.231, 4.255.218.227
• EU1: 20.71.203.39, 137.116.224.49
• EU2: 20.0.210.84, 20.90.9.64

For US Government GCC and GCC High customers, to ensure the proper function of access controls, the following IP addresses used by our reverse proxy regions should be added to the allow list for both inbound and outbound connections:

• US Government GCC High:
  • 52.235.156.231
  • 52.235.156.197
  • 52.235.157.183
  • 52.235.156.9
  • 52.235.156.225
  • 52.235.157.175
  • 52.235.157.131
  • 52.235.157.11
  • 52.126.39.112
  • 52.235.156.151
• US Government GCC:
  • 52.126.33.153
  • 52.126.39.65
  • 52.235.138.253
  • 52.235.139.4
  • 52.235.139.36
  • 52.235.139.75
  • 52.235.139.92
  • 52.235.139.103
  • 52.235.139.134
  • 52.235.139.141

To stay up to date on IP ranges that impact the experiences in Microsoft Defender for Cloud Apps in the areas of portal experience access, access and session controls, SIEM agent connection, app connectors, mail server, and log collector, it’s recommended to refer to the Microsoft Azure service tag documentation. The latest IP ranges for Microsoft Defender for Cloud Apps services are found in the service tag ‘MicrosoftCloudAppSecurity’. For more information, Virtual network service tags. 

When this change takes effect, you will not need to take any action if you have followed the instructions above.

Learn more: Network requirements

A new Copilot feature will organize a user’s chat history by the latest interaction in each session. This will apply to a user’s existing Copilot chat history and any new chats created.

This message is associated with Microsoft 365 Roadmap ID 477358.

[When this will happen:]

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

[How this will affect your organization:]

This feature will impact users as their existing chat history list will now be grouped according to the time the chat prompts were submitted in the following categories:

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

With Copilot we are bringing the power of next generation AI to the tools millions of people use every day. Another step on that journey is automating time-consuming tasks to enhance employee productivity.

Copilot Actions provides a user-friendly way to automate and delegate common IW tasks within Microsoft 365 to Copilot. Actions combine Copilot prompts and conversations, triggers (events like file modifications or schedules like daily reminders), and user defined rules to generate artifacts. To make getting started easy, Copilot Actions offer categorized Templates such as Catch up and Gather, etc., that are tailored for common personal productivity scenarios. Actions is a Copilot feature which delivers immediate value without the need for any setup. This out-of-the-box functionality ensures that even users with minimal technical expertise can benefit from the powerful async capabilities of Copilot. Copilot Actions is accessed via the Microsoft 365 app for the Web.

This is an English only release for the UX language.

[When this will happen:]

We will begin rolling out to Targeted Release in early March 2025. 

[How this affects your organization:]

Customers, with a Copilot license, will have the ability to create automated tasks from a list of available Actions, with some of those actions backed by Copilot. Copilot Actions will have limited individual actions per user.

[What you can do to prepare:]

Educate your organization on the availability of Copilot Actions and the help article.

We will update this message when online documentation is available.

We are evolving the Feed experience in Microsoft Viva Connections for Microsoft Teams. Instead of the Feed, people in your organization will soon see a Microsoft SharePoint News experience in Viva Connections, for a fresh new look that simplifies the user experience. Learn more:

• Introducing enterprise news reader in Viva connections | Microsoft Community Hub
• Watch video (14:12 min)

This message is associated with Microsoft 365 Roadmap ID 472018.

This message applies to Viva Connections in Teams for Windows desktop, Teams for iOS/Android, and Teams for the web, with this exception: This rollout will also include a Microsoft 365 Copilot-powered summary experience initially available only in Teams for Windows desktop. Microsoft 365 Copilot licensed users will have an additional option to generate a Copilot summary of the top 10 (or fewer) items in a user’s News feed. A Microsoft 365 Copilot license is required to use this summarization feature in the news feed.

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

Due to the nature of rollout technology across various platforms, some users may see the new experience sooner than others or in one platform first before the others.

[How this will affect your organization:]

Users will see recommended SharePoint News based on the sites they follow, frequently access, posts by people they work with, and other trending sites. As always, users will only see news they have appropriate permissions for, and if a news item is audience-targeted, the News feed will honor that and filter out news items. Boosted news and news from your organization’s news sites will always be prioritized at the top of the News feed.

Users can like news items in their feed and save them for later. They will have an immersive news experience in Viva Connections, without leaving Teams to read new content for individual sites they follow.

This change will be on by default.

The new Feed experience in Viva Connections in Teams for desktop and the web:

The new Feed experience in Viva Connections in Teams for iOS/Android:

The Copilot-powered summary experience available only in Teams for Windows desktop for Microsoft 365 Copilot licensed 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. You may want to notify your users about this change and update any relevant documentation.

Copilot Agents are coming soon to both the Web and Work tabs of Microsoft 365 Copilot Chat in Outlook for the Web and the new Outlook for Windows.

This change is associated with Microsoft 365 Roadmap ID: 481558 

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

Agents extend the capability of Microsoft 365 Copilot Chat in exciting ways, letting users customize their Copilot experience.

From Copilot in Outlook, the right-side panel will show agents that the user has previously installed or that their admin has previously deployed. The panel will also provide entry points to Get Copilot agents in the app store and to Create an agent.

[What you need to do to prepare:]

Agents in Outlook will respect the same admin controls as agents in Microsoft 365 Copilot Chat.

Admins can manage agents as apps in the Integrated apps section of the Microsoft 365 admin center. Admins can also enable or disable Copilot extensibility for their org, and control who can access agents within their organization. 

Review:

• Manage agents for Microsoft 365 Copilot in Integrated Apps.

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

The latest Teams meeting experiences will be available for Teams on the web in Safari and Firefox browsers – including performance improvements, refreshed pre-join, updated meeting stage, and the updated meeting toolbar. (for anonymous join only) 

This message is associated with Microsoft 365 Roadmap ID 329253

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

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

Updated February 28, 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.

This message is associated with Microsoft 365 Roadmap ID 381643.

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

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

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

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

This message is associated with Microsoft 365 Roadmap ID 381953.

[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). Only Meet Now use cases (except Meet Now in chats and channels) will be affected in this timeframe. There will be no impact on the scheduled meetings in this phase.

General Availability (Worldwide, GCC): We will begin rolling out mid-May 2025 (previously mid-April) and expect to complete by late May 2025 (previously late April). Only Meet Now use cases (except Meet Now in chats and channels) will be affected in this timeframe. There will be no impact on the scheduled meetings in this phase. Rollout for scheduled meetings and channel Meet Now will be started in early July 2025 and expected to be completed by mid-July 2025.

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

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

1. In case the meeting organizer gets removed from the tenant, the links to the meetings scheduled by them automatically expire.
2.  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.

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

Note: If you are not using frontline worker functionality, you can ignore this message.

Coming soon to Microsoft Teams: Cross-location Shifts is a new feature in the Microsoft Shifts app for Teams that enables frontline managers to offer open shifts across multiple locations in a region so managers can share the labor pool and workers can select available shifts across different locations. This message applies to Microsoft Teams for Desktop, web, Mac and Mobile.

This message is associated with Microsoft 365 Roadmap ID 394351.

[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): We will begin rolling out early November 2024 (previously late October) and expect to complete by mid-March 2025 (previously mid-February).

[How this will affect your organization:]

Before the rollout, frontline managers are not able to not able to offer open shifts across multiple locations in a region.

After the rollout

Benefits of cross-location shifts:

• Optimize the manager’s workforce by balancing the supply and demand of labor across locations in a region.
• Empower your frontline workers by giving them the flexibility to select open shifts at a location that is convenient for them.
• Improve customer satisfaction by ensuring that you have enough staff to serve them.

The cross-location shifts feature requires the following conditions:

• An operational hierarchy must be established for the organization.
• The team should have sister locations.
• Team should have at least one matching schedule group code with other teams

Admins or frontline managers can enable these prerequisites through:

• Defining the operational hierarchy in the Teams admin center, as described in Deploy your frontline operational hierarchy – Microsoft 365 for frontline workers | Microsoft Learn
• Creating schedule group codes via the Graph API, detailed in Create scheduling Group – Microsoft Graph beta | Microsoft Learn

[What you need to do to prepare:]

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

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

For reference: Manage the Shifts app for your organization – Microsoft Teams | Microsoft Learn

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

 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 May 2025 (previously end of March) with an updated timeline for tenants that are opted out.

Starting April 15, 2025 (previously February 3), 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:]

April 15, 2025 (previously February 3)

We are delaying the rollout start date from December to April 15, 2025 (previously February 3) 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 April 15 2025 (previously 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.

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

We are rolling out enhanced app discovery for Microsoft Teams. This rollout allows users to easily discover and use apps that they have previously used in group chats, channels, and meetings, enabling users to consent to use the app everywhere in Teams with one click. This message applies to Teams on Windows and Mac desktops and to Teams on the web.

This message is associated with Microsoft 365 Roadmap ID 397089.

[When this will happen:]

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

[How this will affect your organization:]

In Teams, when one user installs an app to a group chat, channel, or meeting, others in the group can use it without installing the app. Before this rollout, it is not easy for others in the group to rediscover these apps for use everywhere in Teams.

After this rollout, users can more easily find and use apps they previously used in Teams, because these apps will appear at the top of the list of apps in Teams menus:

After this rollout, users will be able to find apps they used in a group experience, but did not install themselves. If users click such an app, a consent screen appears. If the user agrees, the app will be installed and be available everywhere in Teams, including group chats, channels, and meetings:

[What you need to do to prepare:]

Admins should ensure that their tenant’s app permission policies are configured to allow users to add and use apps in group experiences. No additional admin configuration is needed for this feature

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

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

This message is associated with Microsoft 365 Roadmap ID 401120

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

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

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

Coming soon to the Microsoft Purview compliance portal: To assist you in diagnosing issues encountered while using Microsoft Information Protection (MIP) and Data Loss Prevention (DLP), we will release a new experience where you can run diagnostics to help identify the root cause of issues and provide remediation options. Before this rollout, these diagnostics were only available as Microsoft PowerShell cmdlets.

This message is associated with Microsoft 365 Roadmap ID 418566.

[When this will happen:]

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

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

[How this will affect your organization:]

After this rollout, you can troubleshoot issues at Purview compliance portal > Data Loss Prevention > Run diagnostics.

This new feature will be on by default.

[What you need to do to prepare:]

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

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

Microsoft Purview compliance portal

Updated February 28, 2025: Reminder – this rollout is coming up soon.  

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

This message is associated with Microsoft 365 Roadmap ID 429874.

[How this will affect your organization:]

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

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

 [When this will happen:] 

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

[How this will affect your organization:]

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

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change, especially if the policy is disabled, educate them about autosave, real time user collab, and merging in the case of M365 application conflicts, and update any relevant documentation. 

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

Updated February 28, 2025: Reminder – this rollout is coming up soon.

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

This message is associated with Microsoft 365 Roadmap ID 429875.

[When this will happen:]

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

[How this will affect your organization:]

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

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

User notification to choose the file variation to keep in PowerPoint:

User notification to Save a Copy or Discard Changes in PowerPoint:

User notification to Save a Copy or Discard Changes in Word:

[What you need to do to prepare:]

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

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

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

Coming soon for new Outlook for Windows and web: Easily access your most-used folders by pinning a Favorites section at the top of the Outlook folder list on the left side of the screen. This feature streamlines navigation, ensuring your important folders are always in easy reach. Before this rollout, users can add a Favorites section that scrolls down when users navigate down the list. After this rollout, users can choose to keep the Favorites section pinned to the top of the list, and only the rest of the folders will scroll.

This message is associated with Microsoft 365 Roadmap ID 401341.

[When this will happen:]

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

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

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

[How this will affect your organization:]

After the rollout, users can pin or unpin the Favorites section in two ways.

In the Favorites section of the folder list (on the left of the screen), right-click the three-dot menu and select Pin favorites or Unpin favorites:

On the Outlook ribbon, select the View tab > Folder pane > Favorites > select Pin favorites or Unpin favorites:

This change will be available by default for users to choose to pin and unpin the Favorites section.

[What you need to do to prepare:]

Learn more: Use Favorites in Outlook – Microsoft Support (will be updated before rollout)

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.

#newoutlookforwindows

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

Coming soon, Microsoft Purview Insider Risk Management will be rolling out risky AI usage detections

This message is associated with Microsoft 365 Roadmap ID 394281

[When this will happen:]

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

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

[How this will affect your organization:]

With this update, Insider risk management will help admins identify risky AI usage. We are adding new detections of intentional and unintentional insider risk activity on generative AI apps that can pose a risk to an organization. Activities will include risky prompts containing sensitive info or risky intent and sensitive responses containing sensitive info or generated from sensitive files or sites. Coverage will span across M365 Copilot, Copilot Studio and ChatGPT Enterprise. These detections will also contribute to Adaptive Protection insider risk levels.

[What you need to do to prepare:]

Below are some of the steps admin can take

1. Get insights into risky AI usage at an organization level in an anonymized form using analytics
2. Create Risky AI usage policy to track risky prompts and sensitive responses in M365 Copilot, Copilot Studio
3. The activity explorer in alerts gives a single threaded view of prompt, response along with the sensitive information present
4. Use the new Generative AI indicators in adaptive protection for user risk score

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. 

Main Admin link: Learn about insider risk management policy templates | Microsoft Learn

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

Coming soon for Microsoft Teams: Users will be able to reduce the main Teams window, the chat window, and the meeting stage to 360px wide or 502px wide, compared to the current minimum supported dimensions of 720px wide, with no loss of functionality. We will bring this change to the rest of Teams when we release in General Availability.

Also, users can adjust the width of Teams side panels as desired.

This update enhances accessibility, creates new multitasking opportunities, supports efficient window management on Windows 11 and macOS desktops, and offers greater zooming capabilities for low-vision users when scrolling in one dimension.

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

This message is associated with Microsoft 365 Roadmap ID 470431.

[When this will happen:]

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

We will communicate the plan for General Availability in a future post.

[How this will affect your organization:]

Your organization will be able to resize down to smaller window sizes and to resize left and right panes.

Resizing windows:

Reflowing windows:

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.

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

Coming soon to Microsoft Teams: Add a Loop workspace tab to standard channels enabling your team to brainstorm, co-create, collect, and organize content—together in real time. Everyone in the Team will have access to the Loop workspace, even as Team membership changes, and the workspace will adhere to the governance, lifecycle, and compliance standards set by the Microsoft 365 group backing the team. This message applies to Teams on Windows desktop, Teams on Mac desktop, and Teams on the web.

This message is associated with Microsoft 365 Roadmap ID 472022.

[When this will happen:]

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

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

[How this will affect your organization:]

After this rollout, all users with the Loop app enabled on Teams will receive this experience by default.

To get started, users can select the plus sign (+) at the top of the Teams channel and select Loop from the list.

With this rollout, we will support these features:

• Creating a new workspace for a standard Teams channel where the workspace membership is the Channel group membership.
• Adding pages, files, and links to the workspace, collaborating with others, and sharing pages as components in Teams chats and channels. Users will be able to complete all their Loop workspace workflows in Teams.
• Recreating the Loop workspace tab in the channel, in case someone removes it by mistake.
• Deleting the Team will delete the attached Loop workspace. The workspace will be restored if the Microsoft 365 group is restored.
• If the user adding the Loop app to a channel does not have the appropriate license or permission to create a workspace, the user will be blocked from adding the app.
• The Loop workspace created in a Teams channel will automatically receive the sensitivity label of the Microsoft 365 group at creation time. With this rollout, when the label of a Microsoft 365 group changes after workspace creation, the label will not be automatically propagated to the workspace’s Microsoft SharePoint Embedded (SPE) container. Admins can update labels for these workspaces in the SharePoint admin center.
  • Coming soon in late February: When the label of the Microsoft 365 group changes, that update will automatically propagate to the SPE container for the workspace within 24 hours. We will update this message when this feature is available.

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

If you want to block the Loop app in Teams, this will remove the Loop tab applications in channels and the Loop personal app in Teams. To learn more: Overview of Loop workspaces storage and permissions | Microsoft Learn

If you want to keep the Loop application in Teams but disable to ability for users to create Loop workspaces, follow these instructions:

1. Sign in to the Microsoft 365 Apps admin center at https://config.office.com/ with your Microsoft 365 admin credentials.
2. Select Customization from the left pane.
3. Select Policy management.
4. Create a new policy configuration or edit an existing one.
5. From the Choose the scope dropdown menu, choose either All users or select the group for which you want to apply the policy. Learn more: Microsoft 365 Groups for Cloud Policy in Manage Loop components in your organization | Microsoft Learn.
6. In Configure settings, choose your desired setting for Create Loop workspaces in Loop:
   • Disabled: Users cannot create Loop workspaces in Teams. (When disabled, the Loop app will open Loop components in Teams.)
   • Enabled or not configured: Users can create Loop workspaces in Teams.
   • Not configured = Enabled
7. Save the policy configuration.
8. Reassign priority for any security group, if required. (If two or more policy configurations are applicable to the same set of users, the one with the higher priority is applied.)

Learn more

• Overview of Loop workspaces storage and permissions | Microsoft Learn
• Related message center post: MC929022 Microsoft Loop – Require Existing Microsoft 365 Group for New Loop workspaces (published November 2024)

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

Coming soon for Microsoft 365 Copilot: When writing Copilot prompts in the chat box, users will be able to use CIQ to select Microsoft SharePoint and Microsoft OneDrive folders using the existing Attach cloud files icon.

Context IQ (CIQ) is a set of AI capabilities from Microsoft that allows users to search for, select, and insert relevant enterprise or personal data directly into their prompts or conversations. This capability helps users to “ground” or anchor their prompts in specific, contextually relevant data, making responses more accurate, specific, and useful.

This message is associated with Microsoft 365 Roadmap ID 413109.

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

[When this will happen:]

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

No impact to tenant admins. This change is available by default. Users will be able to attach a OneDrive folder or a SharePoint folder to their prompt, similar to how they can select files to attach before the rollout. Users can only select folders that they own or that are shared to the user.

To add OneDrive or SharePoint folders to add to their Copilot prompt, users can select the Attach cloud files icon in the Copilot chat box:

From the new window, users can select the desired folders to add to their Copilot prompt:

[What you need to do to prepare:]

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

Learn more: Using Context IQ to refer to specific files, people, and more in Microsoft 365 Copilot – Microsoft Support (will be updated before rollout)

Updated February 28, 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.

This message is associated with Microsoft 365 Roadmap ID 470025.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out late February 2025 (previously mid-February) and expect to complete by early March 2025 (previously late 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.

Updated February 28, 2025: After further review we have decided not to proceed with this change at this time. We apologize for any inconvenience.

We are introducing the App Management Unification Impact report, a new tool that offers administrators a comprehensive preview of changes to app and tenant settings before the implementation of the unified management of Microsoft Teams apps (MC796790). This report brings awareness to the expected changes, enabling admins to adjust settings in Teams admin center or Microsoft 365 admin center before unification is applied. The report is available only in tenants that have migrated to Microsoft App Centric management (MC688930).

[When this will happen:]

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

[How this will affect your organization:]

The report will be available on the Manage Apps page in the Teams admin center to preview changes to app or tenant settings resulting from the upcoming release of unified app management.

[What you need to do to prepare:]

Administrators should run the App Management Unification Impact report from the Manage Apps page in the Teams admin center. This report will display apps and agents listed in the Teams admin center along with their tenant settings and app availability values as well as those in the Integrated Apps page of the Microsoft 365 admin center. The report will show the projected unification outcomes for each app and agent, enabling administrators to preview changes resulting from the upcoming release of unified app management (announced in MC796790, roadmap item 393931). The report will use the merge logic previously shared in public documentation. Administrators may need to make changes in either the Teams admin center or Microsoft 365 admin center and coordinate with other departments.

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

New Copilot Prompt Gallery Prompts app for Microsoft 365 available: Explore full prompt collections across Copilot and agents in the new Prompts app available on Teams, Outlook, and the Microsoft 365 Copilot app.

This message is associated with Microsoft 365 Roadmap ID 473463.

[When this will happen:]

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

[How this will affect your organization:]

Prompts app will be available for your users to install from Teams, Outlook, and Microsoft 365 Copilot app stores.

[What you need to do to prepare:]

Copilot Prompt Gallery app will be available for your users to install if:

1. Teams apps are enabled for your tenant: Customize default settings for Teams apps that work on Outlook and the Microsoft 365 app
2. Prompts app has been configured for users in your tenant to install: How to manage the availability of an app in your organization 

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

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

This message is associated with Microsoft 365 Roadmap ID 473452.

[When this will happen:]

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

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

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

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

Users familiar with keyboard shortcuts from third-party chat and meeting applications can use those same shortcuts in Microsoft Teams. To enable this, go to the Settings and more button in the upper right, access the keyboard shortcuts dialog, and select a communication or meeting layout. This allows users to apply the shortcuts they are used to from other applications.

This message is associated with Microsoft 365 Roadmap ID 472913.

[When this will happen:]

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

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

[How this will affect your organization:]

Users in your organization can now customize their keyboard shortcut layout to better suit their preferences in Teams.

[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 28, 2025: We have updated the rollout timeline below. Thank you for your patience.

Coming soon: We will introduce a new Microsoft Teams PowerShell setting in Tenant Federation Configuration to enable you to customize your federation posture. Tenant administrators will be able to define a list of external trial tenants to be whitelisted for federation, while maintaining the default block on overall federation with trial-only tenants.

[When this will happen:]

General Availability (Worldwide): The new setting is available now in Teams PowerShell. If populated, the allowed trial tenant domains list will start to take effect in mid-March 2025 (previously mid-February).

Note: This feature requires no immediate admin action, and there will be no impact if the list is not populated.

[How this will affect your organization:]

Microsoft Teams introduced a new PowerShell setting (-ExternalAccessWithTrialTenants) to the Set-CsTenantFederationConfiguration cmdlet in August 2024 that enabled blocking all external access with trial-only tenants.

Now, we’re introducing a new Tenant federation setting -AllowedTrialTenantDomains to enable more granularity in defining the federation posture for your organization. This setting will allow you to keep federation with trial-only tenants blocked, while explicitly allowing federation with trial tenant domains you trust and collaborate with for valid business needs.

Important notes

• A “trial-only” tenant is defined as a tenant with a Teams service plan that has only Trial subscriptions (0 purchased licenses).
• Cross-cloud experience: Currently, all cross-cloud communication involving trial-only tenants in public clouds is blocked by default. The AllowedTrialTenantDomains setting will not be supported for cross-cloud communication.
• This setting is only supported in PowerShell.

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

• Review your settings for external access to determine if you have a valid business need to allow federation with trial-only tenants and then prepare the whitelist.
• Download or upgrade to the latest PowerShell package (6.7 or higher): https://www.powershellgallery.com/packages/MicrosoftTeams/
• To block external communication with trial-only tenants, use: Set-CsTenantFederationConfiguration -ExternalAccessWithTrialTenants "Blocked"
• To allow external communication with specific trial-only tenants, while blocking it by default for most trial-only tenants, use:

$list = New-Object Collections.Generic.List[String]

$list.add("contoso.com")

$list.add("fabrikam.com")

Set-CsTenantFederationConfiguration -AllowedTrialTenantDomains $list

• To remove tenants from the AllowedTrialTenantDomains list, use:

$list = New-Object Collections.Generic.List[String]

$list.add("contoso.com")

Set-CsTenantFederationConfiguration -AllowedTrialTenantDomains @{Remove=$list}

• To allow external communication with all trial-only tenants, use:

Set-CsTenantFederationConfiguration -ExternalAccessWithTrialTenants "Allowed"

Learn more

• PowerShell cmdlet configuration: Set-CsTenantFederationConfiguration | Microsoft Learn
• Manage external communication: IT Admins – Manage external meetings and chat with people and organizations using Microsoft identities – Microsoft Teams | Microsoft Learn

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

Employees will soon be able to create their own link cards that connect to other tools and destinations on the Microsoft Viva Connections dashboard.

This message is associated with Microsoft 365 Roadmap ID 472021.

[When this will happen:]

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

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

[How this will affect your organization:]

After this rollout, employees can create their own cards for the Connections dashboard:

Step 1: On the Viva Connections dashboard, the user selects Customize:

Step 2: Add a Quick links card:

Step 3: Set up the card to choose a title, image, and appropriate links. Save the dashboard:

This feature will be on by default and accessible to all users in your tenant unless you turn it off.

[What you need to do to prepare:]

If your company is not ready to roll out end user customizations to employees, you can turn it off with the setting in Dashboard details:

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.

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

Coming soon to Microsoft Teams: When in a meeting that is being recorded and has content shared onscreen, Microsoft Copilot will be able to answer questions based on the shared onscreen content. Before this rollout, Copilot was only able to answer questions based on the transcript and meeting chat, and this capability will continue after the rollout. This message applies to Teams on VDI, Teams on Windows desktop, Teams on Mac desktop, Teams on the web, and Teams for iOS/Android. A Microsoft 365 Copilot license is required to use this feature.

This message is associated with Microsoft 365 Roadmap ID 325873.

[When this will happen:]

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

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

[How this will affect your organization:]

After this rollout, users will be able to ask Copilot questions about screenshare data, but only if a meeting is recorded and transcribed. If the meeting is only transcribed, users can still use Copilot, just without screenshare data.

Copilot will be able to understand slides, documents, spreadsheets, and websites, or anything else shared onscreen. Users will be able to ask simple recall questions, such as “Show me the content that was shared on the screen” or more specific questions like “what was the Sales target number” if it was shared on a previous slide. Users will also be able to combine screenshare with transcript and chat data to ask, “Show me all the slides and the feedback on each slide,” or “Rewrite the paragraph based on the comments from the audience.”

Copilot can only answer questions about content shared onscreen if the meeting is recorded and transcribed, and if the specific slide, document, spreadsheet, and website is shared for longer than 10 seconds. This will alleviate potential accidental shares being used by Copilot. For example, if a user accidentally shares the wrong content and changes it within 10 seconds, Copilot will not have access to it. However, when the meeting is recorded, the recording will still have this information. Deleting a recording will also delete all associated screen data along with it, so Copilot will no longer have access to screen data if the meeting recording was deleted.

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

Learn more: Use Copilot in Microsoft Teams meetings – Microsoft Support (will be updated before rollout)