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

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

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

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

This latest version of Copilot on Edge includes several important updates that enhance functionality and resolve known issues.

[When this will happen:]

The update is available now, and organizations should ensure they are using Edge version 134.0.3124.51 or newer.

[How this affects your organization:]

• Independence from Bing authentication: Authentication is now retrieved via the Edge work profile, resolving known issues.
• Support for file upload on the ‘Web’ tab: This feature is now in parity with Copilot on M365.cloud.microsoft. File upload on the ‘Work’ tab remains unchanged.
• Independence from Microsoft Search in Bing policies, service plans, and licenses: All eligible enterprise tenants can now access Copilot on Edge.

These updates apply only to Copilot on the Edge sidebar. Copilot access on M365.cloud.microsoft is not impacted by these changes to Edge.

[What you can do to prepare:]

Ensure your organization updates to Edge version 134.0.3124.51 or newer to continue using Copilot on the Edge sidebar. The same M365 Copilot license requirements still apply for Copilot on Edge sidebar as M365.cloud.microsoft.

Beginning mid-April 2025, or soon after, admins will be required to have the ‘Intune Service Administrator’ role-based access control (RBAC) permission to configure device limit enrollment restrictions policy.

[How this will affect your organization:]

Admins managing these policies will be required to have the ‘Intune Service Administrator’ RBAC permission to update the device limit enrollment restrictions policy. (Devices > Enroll devices > Device limit restrictions). If they do not have this permission, these policies will be read-only.

[What you need to do to prepare:]

Review your RBAC assignments and update as needed to allow admins permission to update device limit restrictions.

[Additional information:]

Create device limit restrictions – Microsoft Intune | Microsoft Learn

Role-based access control (RBAC) with Microsoft Intune 

As announced in MC454504, Viva Engage no longer supports multiple networks associated with a single tenant. Tenants received notice of automatic network consolidation 30 days prior to the start of the consolidation process. Going forward, tenants will receive notice 15 days prior.

[How this will affect your organization:]

You are receiving this message because we have a legal requirement to announce any change to notice periods for automatic network consolidation.

Admins will not be able to pause or cancel the automatic network consolidation.

[What you need to do to prepare:]

If you would like to control the timing of your network consolidation, go to the Engage Admin Center and begin the network consolidation process as soon as possible.

Learn more 

Coming soon to Microsoft Viva Engage: Community admins will have an upgraded experience for viewing, creating, and editing text in the full Community information section. The new experience will use a simplified version of the same publisher used for creating posts in Viva Engage and will limit the length of the Community information section to 32k characters (the same as the limit for articles).

This message applies to:

• Engage app on the desktop (as a progressive web app)
• Engage app in Microsoft Outlook (new Outlook for Windows desktop, Outlook for the web, and new Outlook for Mac desktop)
• Engage app in Microsoft Teams (Teams for Windows desktop, Teams for Mac desktop, and Teams for the web)
• Engage on the web (www.engage.cloud.microsoft.com)

This message is associated with Microsoft 365 Roadmap ID 479405.

[When this will happen:]

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

[How this will affect your organization:]

The updated Community information experience in Viva Engage:

This change will be on by default.

[What you need to do to prepare:]

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

#newoutlookforwindows

As communicated in 168828 (Updated) SharePoint eSignature electronic signature service (published November 2024, updated March 2025), SharePoint eSignature is Microsoft’s first party electronic signature service which allows users to easily request eSignatures on a PDF document via SharePoint online. Signers can easily add their electronic signature. Signed documents are saved securely back to SharePoint.

Before this rollout, when users request an eSignature using the native SharePoint eSignature capability on a PDF, users must wait for their request to complete processing before creating an additional request.

After this rollout, users will be able to create additional requests without needing to wait for the previous request to complete sending.

[When this will happen:]

General Availability: We will begin rolling out mid-April 2025 and expect to complete by late May 2025 to these regions.

[How this will affect your organization:]

After this rollout, new toast notifications will inform users of the processing state of requests. Users can access the in-progress PDF through the toast notification.

This change will be on 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. Please notify your users about this change and update any relevant documentation.

Learn more: Create a signature request using SharePoint Signature – Microsoft Syntex | Microsoft Learn (will be updated before rollout)

We want to announce an update to the behavior of an existing tenant setting in Fabric that allows Fabric admins to enable SQL databases in their Fabric tenant. By making SQL databases in Fabric a default option, we aim to help organizations leverage its full potential from the start. This change aligns with our commitment to improving user experience and operational efficiency.

Although the infobox displays March 8, 2025 as the enablement date, the actual change will occur on March 28, 2025, providing additional time for tenant admins to review and make selections before the setting is enabled by default.

[When this will happen:]

February 28, 2025: The checkbox for enabling SQL databases in Fabric was made available to tenant admins.

March 28, 2025: Even though the infobox displays March 8th, the actual enablement will take effect for tenants that have not opted out on March 28th.

[What you need to do to prepare:]

1.Review and Decide on Settings:

• Enable SQL database in Fabric by Default: This setting is ON by default. Please review its implications and determine if it should remain enabled for your organization.

2.Action for M365 and Fabric Admins:

• If no action is taken, SQL databases in Fabric will remain active for all users, with the default enablement occurring on March 28, 2025.
• If your organization prefers not to have this setting enabled by default, tenant admins must manually turn OFF this setting before March 28, 2025.
• We encourage you to assess these new settings and make any necessary changes to align with your organization’s compliance and data storage policies.

If you have any questions or need further assistance, please do not hesitate to contact our support team.

The API access page in the Microsoft SharePoint admin center will soon display a set of additional permissions that have been automatically pre-authorized by Microsoft. These permissions are required for SharePoint Online to function properly.

Tenant admins can remove the permissions (and add them back to the API access page), but these actions could compromise some out-of-the-box functionalities provided by SharePoint.

[When this will happen:]

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

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

[How this will affect your organization:]

This change will be on by default and will have no impact on customers.

The API access page is only available if you have provisioned the application catalog for your tenant.

[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 update any relevant documentation.

Learn more: Manage access to Microsoft Entra ID-secured APIs – SharePoint – SharePoint in Microsoft 365 | Microsoft Learn (will be updated before rollout begins)

Coming soon for Microsoft Viva Engage premium users: We will add existing creation options for Question and Article posts to the Create new button.

An Engage premium user is licensed for Microsoft Viva Suite or the Microsoft Viva Employee Communications and Communities Suite.

This message applies to:

• Engage app on the desktop (as a progressive web app)
• Engage app in Microsoft Outlook (new Outlook for Windows desktop, Outlook for the web, and new Outlook for Mac desktop)
• Engage app in Microsoft Teams (Teams for Windows desktop, Teams for Mac desktop, and Teams for the web)

This message is associated with Microsoft 365 Roadmap ID 484852.

[When this will happen:]

General Availability (Worldwide): 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, the Create new button displayed options for Post, Community, Campaign and Event, or a subset of these depending on the user’s assigned license and role permissions.

After this rollout, premium licensed Engage users will find new options to more easily create Question and Article posts from the Create new button:

This rollout does not include new types of content creation. Users will inherit their current creation settings, so they can create content types based on their permissions and license type .

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. 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 about the nuances of licensing and permissions for Viva Engage and for each post type:

• Seeded and premium licensing: Set up Viva Engage | Microsoft Learn
• Post types: Write and schedule posts, articles, and announcements in Viva Engage – Microsoft Support

#newoutlookforwindows

This message is associated with Microsoft 365 Roadmap ID 380187.

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

Before this rollout: Users may not see a standardized date format across the app, nor do they have the option to change how dates are displayed depending on their language preference.

After this rollout: A Date Format feature is added under Settings so users can select a date format that suits their preference. Additionally, depending on the language selected, the numeral values across Viva Learning will also change.

When a user lands on Viva Learning for the first time, they will be able to see the default language and date format set. However, if they wish to change it, they can navigate to the Settings option in the application where they can see a Language & Date setting option. When they select the Language & Date setting, they get two options:

• Language: A dropdown menu containing all language options a user can select, which will apply to all static data content on the Viva Learning app.
• Date Format: A dropdown menu of all the date formats that are available for the user. All occurrences of dates in the app will follow the format selected here.

The date formats available are dependent on the language selected and may vary from language to language.

Once the date format and/or language are selected, the user can click on the Save and Refresh button to reload the application, then the language, date, and numeral changes will be applicable across the application.

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

Coming soon for Microsoft Teams: We have improved user options for sharing a link for a Teams app or an agent in a chat.

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

A Microsoft 365 Copilot license is not required to share agent links but may be required to install and use the agent.

This message is associated with Microsoft 365 Roadmap ID 483254 and Roadmap ID 483356.

[When this will happen:]

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

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

[How this will affect your organization:]

After this rollout, links to apps and agents will have a new preview card with

• User ratings for users to consider before installing apps or agents in Teams.
• Clear actions like Add (which installs the app or agent) and View details.

This change will be on by default.

[What you need to do to prepare:]

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

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

Coming soon: The Microsoft Copilot Studio agent report template in the Microsoft Viva Insights advanced insights app will be available in public preview for all Viva Insights customers. This Microsoft Power BI template provides Viva Insights analysts an aggregated view of Microsoft Copilot Studio agent adoption and impact across the organization over time with flexibility to explore details for specific agents.

This feature will be enabled for tenants who meet either of these eligibility criteria:

1. Tenant must have Viva Insights licenses (either minimum 50+ assigned Viva Insights licenses or 50+ Microsoft 365 Copilot licenses)
2. Tenants must have Copilot Studio licenses, either standalone, pay-as-you-go, or bundled with Microsoft 365 Copilot, and have created at least one agent* and published the agent in a Production environment.

*The Copilot Studio agents report covers usage and impact metrics for agents built using Copilot Studio that are published outside of Microsoft 365 Copilot or Microsoft 365 Copilot Chat. This version of the reports excludes agents that enhance Microsoft 365 Copilot and autonomous agents.

This message is associated with Microsoft 365 Roadmap ID 472020.

This message applies to Viva Insights for Windows desktop and Viva Insights for the web.

[When will this happen]

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

In May 2025, we will update this message with the plan for the General Availability (Worldwide) of this feature.

[How will this affect your organization]

After this rollout, your organization will see these changes

• In the Microsoft Power Platform admin center (PPAC), a new M365 Services toggle will control the cross-boundary flow of agent performance and usage data for generative AI features from Power Platform to Microsoft 365.
  • This toggle is on by default for non-Federal Risk and Authorization Management Program (non-FedRAMP) environments. Learn more: Move data across regions for Copilots and generative AI features – Power Platform | Microsoft Learn
  • For all other environments, if the M365 Services toggle is on, data from Copilot Studio will flow to Viva Insights by default.
  • If desired, Power Platform admins can turn off the data flow to Viva insights using Microsoft PowerShell. Learn more: Move data across regions for Copilots and generative AI features – Power Platform | Microsoft Learn
• For tenants with Power Platform environments across multiple geos, Copilot Studio agent usage data is sent to and stored in the base location of the tenant in Viva Insights. IMPORTANT: To avoid unintentional data sharing across geographies, cross-geo sharing is off by default, so agent usage data will not be sent to Viva Insights for those tenants. Power Platform admins can turn on cross-data sharing with a PowerShell script, which will allow agent usage data to be stored in base location of the data in Viva Insights. Learn more: Move data across regions for Copilots and generative AI features – Power Platform | Microsoft Learn
• The Viva Insights admin has the flexibility to delete the Copilot Studio agent data for the entire tenant using PowerShell. Learn more: Introduction to advanced insights | Microsoft Learn
• Viva Insights analysts will be able to set up and view the Copilot Studio agent Power BI report in the Viva Insights advanced insights app. Learn how to generate the report in the Viva Insights advanced insights: Introduction to advanced insights | Microsoft Learn

Users with the Insights Analyst role will be able to generate the Copilot Studio agent report in the Viva Insights advanced insights app. The report output will include:

1. Ability to review Copilot Studio agent adoption trends across the organization:

2. Ability to understand agent key performance indicators (KPIs) of top agents across your entire tenant:

3. Ability to explore details of specific KPIs of Microsoft Copilot Studio agents:

[What do you need to do to prepare:]

Review and assess the impact of introducing these features for your organization. You might consider reviewing these features with your works council and updating your training and documentation as appropriate. This rollout will happen automatically by the specified date with no action specifically required from Microsoft Viva Insights admin or Microsoft Power Platform admin unless needed for any specific action described in this message. You may want to notify your admins about this change and update any relevant documentation.

Learn more

These articles will be updated before rollout:

• Learn more about the Copilot Studio custom agents report and the advanced insights app: Introduction to advanced insights | Microsoft Learn
• Learn how to generate Power BI report templates: Introduction to Power BI templates in Microsoft Viva Insights | Microsoft Learn
• Learn more about Copilot Studio and how to create an agent: Overview – Microsoft Copilot Studio | Microsoft Learn
• Learn more about Microsoft Power Platform admin center: Administer Microsoft Power Platform – Power Platform | Microsoft Learn

More AI capabilities are coming soon to conversation analytics in Microsoft Viva Engage. With this rollout, leaders and their delegates in premium licensed tenants will have access to AI themes and summaries in their Engage conversation analytics. In alignment with Microsoft Responsible AI guidelines (What is responsible AI? – Microsoft Support), these AI features will be controlled with the AI Summarization setting in Feature Access Management in Viva.

This feature will be available to customers with a license for Engage premium, Microsoft Viva Suite, or Microsoft Viva Employee Communications and Communities.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out late March 2025 and expect to complete by early April 2025. The AI summarization control is available now in Feature Access Management in Viva for you to configure your setting preferences.

[How this will affect your organization:]

As communicated in MC719651 Microsoft Viva Engage premium: Introducing Viva Feature Access Management (February 2024), global admins or Engage admins can use Feature Access Management in Viva to create these granular access policies for AI summarization:

• Tenant policy: Automatically includes all users in the tenant.
• Group-level and user-level policy: Admins can choose individual users and groups that should be part of the access policy.
• Admins can use tenant and group policies to restrict or enable access to Microsoft 365 Copilot and AI summarization.

These granular access policies provide admins with the ability to turn the features On, Off, or On with user opt out. Learn more: Microsoft Viva – Feature access management | Microsoft Learn

Before this rollout: AI Summarization or themes are not available in conversation analytics in Viva Engage.

After this rollout, themes and summaries will be available for conversations that meet the minimum criteria of 5 unique repliers or equivalent content available for summarization. The AI Summarization features will be on by default and available for tenants with the specified licenses.

An example of how themes and summaries will be displayed in conversation analytics:

To access conversation analytics, select the number of views:

[What you need to do to prepare:]

Tenant admins: Review your AI Summarization settings and confirm that your latest preferences are represented.

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

• View and manage analytics in Viva Engage | Microsoft Learn (will be updated before rollout)
• Monitor engagement in Viva Engage with analytics – Microsoft Support (will be updated before rollout)

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

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

This message is associated with Microsoft 365 Roadmap ID 394278.

[When this will happen:]

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

[How this will affect your organization:]

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

Current experience

Future experience

[What you need to do to prepare:]

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

Updated March 18, 2025: Based on Admin feedback, we are updating the behavior for automated hiding of inactive channels to be opt-in (suggestions) only. With this update, Teams will offer users suggestions on channels that are inactive, and the user is prompted to review their inactive channels and hide them only if they choose. The settings are also updated to reflect this opt-in workflow. There are no changes to the on-demand hiding process.

This feature is enabled till Targeted Release and we will roll out to General Availability later this year in 2025.

In the interim, we are disabling the current generally available version of the feature which requires users to opt-out as well as the settings, for all users. Please note that all users in the public or general ring will not see the setting or have any of their channels hidden automatically. We will re-introduce the updated feature later this year.

Note: Users with EDU licenses assigned will not receive this change. 

Microsoft Teams will detect and hide inactive channels users have not interacted with recently. Users can choose to have Teams run this automatically as well as initiate the hiding process on demand when needed. They can review the list of channels and choose none, some or all of the inactive channels to be hidden. Users can opt out of automated hiding anytime from Teams Settings. This message applies to Microsoft Teams for Desktop, web, and Mac. 

This message is associated with Microsoft 365 Roadmap ID 325780.

[When this will happen:]

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

General Availability (Worldwide): We will begin rolling out mid-November 2024 (previously mid-August) and expect to complete by mid-January 2025 (previously mid-September)

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

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

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

[How this will affect your organization:]

Before this rollout: Users had to manually manage their relevant channels list by hiding inactive and irrelevant channels.

After this rollout: 

Manage preferences for automated hiding via Teams Settings 

If users prefer to manage channels manually, they can opt out of the auto-hiding process. Simply go to Teams settings, select General, and toggle off “Hide Inactive Channels.”  

Hide inactive channels on demand when needed

Users can manually view which channels are inactive and choose to hide some or all of them whenever you need. This can be done from Settings, under General, by clicking the “Hide Now” button. Note that this action can be performed once every 24 hours.

Automated hiding of inactive channels 

With this, Teams will hide channels that have been inactive for the user. Inactive channels are identified based on the following criteria: if the user has not been active in the channel in the last 120 days – meaning there is no new messaging in the channel that the user has read or reacted to – the channel is considered inactive. Once the inactive channels are identified, the user is notified with the coach mark message, “We’re hiding some inactive channels for you.” 

The user can select View changes to see the details. The user can keep the channels hidden or show them again. 

If a user has less than or equal to 25 shown channels, no channels will be hidden for that user. 

[What you need to do to prepare:]

Admins need to be aware of this feature, but no additional action is needed. The feature will roll out starting in November 2024. Users will first see their settings enabled to manage their preferences for automated hiding; additional to the ability to manually hide inactive channels. 

Users will start to see the automated hiding of inactive channels, a few weeks after the feature has rolled out.  

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

Coming soon for Microsoft Outlook: Major design improvements to our draft with Copilot experience. This message applies to new Outlook on Windows and Mac desktops, on the web, and on Android/iOS. This feature requires a Microsoft Copilot for Microsoft 365 license.

This message is associated with Microsoft 365 Roadmap ID 397092.

[When this will happen:]

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

[How this will affect your organization:]

Before this rollout: Users have the original Copilot Compose design:

After this rollout: Users will have the same Copilot Compose features, with an updated design (as shown in the screenshot). We are not changing the functionality:

This change is on by default for all users with a Microsoft Copilot for Microsoft 365 license.

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

#newoutlookforwindows

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

Coming soon: We will automatically set your Home site as the default experience for Microsoft Viva Connections app in Microsoft Teams.

Note: This change will only apply to customers who have not yet set a Viva Connections experience in their tenants. Customers who already have a Viva Connections experience (either standalone or backed by a Home site) will not be affected by this change.

This message is associated with Microsoft 365 Roadmap ID 422815.

[When will this happen:]

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

[How this will affect your organization:]

Before this rollout, end users could access the Homesite through the SharePoint website. With this rollout, end users are now able to also access the Homesite through the Viva Connections app in Teams.

This change will be on by default.

[What you need to do to prepare:]

If you are okay with this change:

• No additional admin action is required.
• We recommend creating awareness about this feature with your users by sending a new post, sharing the link to the Viva Connections app in Teams, or configuring and pinning Viva Connections in Teams. Learn more about how to access Viva Connections in the Microsoft admin center.

If you want to turn off this change, you have two options:

• Use Microsoft PowerShell with Set-SPOHomeSite: Set-SPOHomeSite -VivaConnectionsDefaultStart:$false
• Disable the Viva Connections app from the Teams admin center. Learn how to allow or block apps.

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 update any relevant documentation.

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

As part of Microsoft 365 Copilot for Security in Data Loss Prevention (DLP), Policy Insights helps admins understand DLP policies and its constructs. This enhancement enables DLP admins to gain insights on coverage of policies on pivots like location, classifiers, and notifications.

DLP admins can get these insights on all the policies or on a few selected policies. They will be able to use prompts to gain a deeper level view of how a policy is configured for their digital landscape. This helps them align their data posture on a regular basis and make corrections to policy posture as needed. 

This message is associated with Microsoft 365 Roadmap ID 466740.

[When this will happen:]

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

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

Currently, Copilot for Security is not designed for use by customers using US government clouds, including but not limited to GCC, GCC High, DoD, and Microsoft Azure Government. For more information, consult with your Microsoft representative.

[How this will affect your organization:]

Administrators can invoke the policy insights to understand the insights from all their policies or selected polices. The insights offered start with a higher-level view of how their policies:

• are effective across locations.
• detect the presence of sensitive information types throughout their digital estate.
• notify administrators of violations.
• educate users while they perform activities they should not.

These insights are offered with different pivots by location, classification, and by administrative scopes. This is offered to give the security policy administrators different views for deeper understanding of policy constructs and their impact.

Step 1:

Select the policies you wish to get insights/quick summaries about.

Step 2:

Click on the Get Insights with Copilot button. You will see the prompt is already pushed into the Copilot Experience in the side panel.

Step 3:

Copilot responds with insights on the selected policies.

[What you need to do to prepare:]

Admins can prepare by having Security Computer Units (SCUs). Copilot for Security is sold in a provisioned capacity model and is billed by the hour. 

Get more information about SCUs: Get started with Microsoft Copilot for Security | Microsoft Learn.

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

This new feature provides the capability for admins to configure separate retention policies for various Microsoft 365 Copilot and AI apps. As a result, admins will have the option to configure policies that can delete Copilot and Generative AI interactions faster.

This message is associated with Microsoft 365 Roadmap ID 470025.

[When this will happen:]

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

[How this will affect your organization:]

Organizations will now have controls to configure different retention policies for Microsoft Teams Chat, Copilot, Copilot studio, and ChatGPT Enterprise.

This feature is available by default.

[What you need to do to prepare:]

For more information, see Create and configure a retention policy.

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