Microsoft Roadmap, messagecenter and blogs updates from 04-10-2025

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

 Coming soon to the chat experience in Microsoft 365 Copilot (formerly BizChat): Users will be able to use a File type filter and People refiners in the CIQ menu to apply search criteria and find relevant files more quickly.

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 applies to the chat experience in Microsoft 365 Copilot for Windows desktop and Copilot Chat on the web.

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

This message is associated with Microsoft 365 Roadmap ID 481136.

[When this will happen:]

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

[How this will affect your organization:]

Before this rollout, in the chat experience in Microsoft 365 Copilot, users can refine search results by entering text in the search box in the CIQ menu.

After this rollout, in the chat experience in Microsoft 365 Copilot, users can enter text in the search box and also use the File type filter and People refiners in the CIQ menu’s Files tab.

The CIQ menu Files tab before this rollout:

The CIQ menu Files tab after this rollout, with the new File type filter and People refiners:

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

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

[Introduction]

Upcoming privacy-related changes in Chromium-based browsers (Google Chrome and Microsoft Edge) will increase restrictions on local network access. When enforcement begins, users accessing OneDrive for Web (and some integrated Microsoft 365 experiences such as Microsoft Lists and SharePoint Document Libraries) will encounter a browser permission prompt for local network access unless the required policy is in place. If the permission is not allowed, performance optimizations and offline capabilities powered by OneDrive and Share Point will not be available. This communication provides required administrator actions to prevent loss of functionality.

[When this will happen:]

Chrome and Edge will roll out this privacy related change as part of Chromium 141 at the end of October 2025 (previously end of September).

[How this will affect your organization:]

If no action is taken:

1. Who is affected:
   • All users accessing OneDrive for Web, Microsoft Lists, and SharePoint Document Libraries via Chrome or Edge browsers.
   • Admins managing browser policies for Windows, macOS, and VDI environments.
2. What will happen:

   If no action is taken:

   • Users will see a new browser prompt requesting permission for local network access when opening OneDrive for Web and Lists.
   • If users do not click Allow, the following results occur on that device:
     • Performance acceleration will not be available (loss of faster data access behavior).
     • Offline functionality in OneDrive Web will not be available.
   • The experience will be slower and less resilient, and helpdesk contacts will increase due to unexpected prompts and missing offline capability.

   When the recommended browser policy is deployed in advance, the prompt is suppressed for the specified trusted Microsoft 365 endpoints and existing performance, and offline behavior are preserved. The policy prevents loss of existing capability and avoids user confusion.

   [What you need to do to prepare:]

   1. Identify Required Domains
      1. Include your organization’s SharePoint Online and OneDrive endpoints, for example: https://YOURTENANT-my.sharepoint.com or https://YOURTENANT.sharepoint.com
      2. Add additional sanctioned SharePoint Online host variations if applicable (e.g., specialized cloud environments). Avoid overly broad wildcards—conform to internal security governance.
   2. Configure Browser Policy
      1. Set the Chromium policy LocalNetworkAccessAllowedForUrls (Chrome Enterprise / Edge policy) to pre-authorize the listed domains.
      2. Apply via: ADMX / JSON for Windows; plist or configuration profile for macOS (Chrome and Edge).
      3. Roll out to all managed device groups (Windows, macOS, VDI as applicable).
      4. Even if the following policies are currently enabled by policy, deploy the allow-list to prevent future prompts and avoid user confusion.
         1. DisableNucleusSync
         2. DisableOfflineMode
   3. Remediation for Users Who Already Clicked Block
      1. Deploying the managed LocalNetworkAccessAllowedForUrls policy will override any prior per-user deny state and enforce the allow setting once the policy is applied to the device/profile; no end-user action is required after policy propagation.
      2. If you need immediate remediation before policy reaches the device, have the user open the affected OneDrive site, use the site (lock) icon, reset or change the local/network device access permission to Allow, then refresh.
   4. Ensure your Sync Client is updated to v.25.164

1. Per machine SKU: The Sync client will automatically apply the required permissions and policies for existing users in Chrome and Edge—no user action is needed.

2. Per user SKU: The Sync client will prompt users via a Windows Toast notification to enable these permissions. Users should follow the notification instructions to complete setup.

[Compliance considerations:]

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

[Introduction:]

To enhance the extensibility of Microsoft 365 Copilot, we’re introducing support for Declarative Agents in Copilot Chat within classic Outlook for Windows. Declarative Agents will be available for Copilot Chat users (without a Microsoft 365 Copilot license) and Microsoft 365 Copilot users (with a Microsoft 365 Copilot license). Declarative Agents allow users to customize their Copilot experience by integrating plugins, enterprise connectors, and orchestration logic. This update aligns classic Outlook with other Copilot Chat experiences, delivering consistent agent capabilities across platforms.

This update is tracked under Microsoft 365 Roadmap ID 481559.

[When this will happen:]

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

[How this will affect your organization:]

Who is affected:

• Organizations using classic Outlook for Windows with Microsoft 365 Copilot Chat
• Admins managing Copilot extensibility and agent deployment

What will happen:

• Declarative Agents will be available in Copilot Chat within classic Outlook for Windows
• Users will see a right-side panel in Outlook showing:
  • Agents previously installed by the user
  • Agents deployed by the admin
  • Entry points to browse agents in the app store
  • Option to create a new agent
• Declarative Agents in Copilot Chat are enabled by default for Microsoft 365 tenants with Copilot licenses
• No admin opt-in is required to use agents in Copilot Chat
• Advanced agent capabilities (access to SharePoint or Graph connectors) require explicit admin opt-in and billing setup
• Admins can manage agents through the Integrated apps section of the Microsoft 365 admin center, including:
  • Enabling or disabling Declarative Agents for the organization
  • Assigning access to specific users or groups
  • Blocking or removing agents from the organizational catalog
  • Managing agent visibility and availability

Licensing tiers:

• Microsoft 365 Copilot: Requires a Microsoft 365 Copilot license. Users get full access to Declarative Agents, including those integrated with plugins, enterprise connectors, and advanced orchestration features
• Copilot Chat: Designed for users without the Copilot license. These users can still access Copilot Chat and build knowledge-only Declarative Agents, but with limited capabilities

[What you can do to prepare:]

• Review agent management settings in the Integrated apps section of the Microsoft 365 admin center
• Ensure Copilot extensibility is enabled for your organization if you plan to use agents.
• If you plan to use advanced agent capabilities (such as Graph or SharePoint connectors), configure billing and opt-in via the Microsoft 365 admin center or Power Platform admin center.
• Communicate this update to helpdesk and support teams.

Learn more: 

• Declarative agents for Microsoft 365 Copilot overview | Microsoft Learn
• Manage agents for Microsoft 365 Copilot in Integrated Apps

We’re retiring the When Sending a Message Group Policy in Classic Outlook for Windows to improve administrative flexibility and respond to customer feedback. This legacy policy grouped several mail-sending behaviors under one setting. Moving forward, these behaviors will be managed through individual policies, allowing for more granular control and easier configuration.

[When this will happen:]

• New individual Group Policies will be introduced starting October 14, 2025.
• The legacy When Sending a Message policy will be removed on January 13, 2026.

• Who is affected: Admins managing Classic Outlook for Windows using Group Policy.
• What will happen:
  • New individual Group Policies will be added to the Office admin templates (ADMX/ADML).
  • These policies will coexist with the legacy policy until January 2026.
  • After January 13, 2026, the legacy When Sending a Message policy will be removed.
  • Admins will need to configure the new policies individually.
  • No changes will occur automatically; migration is required.

• Review your current use of the When Sending a Message Group Policy.
• Plan to migrate to the new individual policies before January 13, 2026.
• Download the updated Administrative Template files (ADMX/ADML) from the Microsoft Download Center.
• Update internal documentation and helpdesk guidance to reflect the new policy structure.
• Learn more: Outlook for “When Sending a Message” Policy

No compliance considerations identified, review as appropriate for your organization.

• Risk rating will be shown for each requested permission.
• Overall privilege level will be displayed for each app or agent.
• This information will appear in:
  • Teams admin center > Teams apps > Manage apps > App details > Permissions tab
  • No changes to app enablement/blocking behavior or underlying data.

[Introduction:]

To streamline billing management and improve the admin experience, Microsoft is moving the setup of Pay-as-you-go (PAYG) billing plans for Microsoft 365 Copilot Chat from the Power Platform admin center to the Microsoft 365 admin center. While many organizations already use the existing Pay-as-you-go (PAYG) setup, starting October 3, 2025, all tenants must begin using the Microsoft 365 admin center for Pay-as-you-go (PAYG) setup for Microsoft 365 Copilot Chat, as the Power Platform method will no longer be supported.

[When this will happen:]

Starting October 3, 2025, admins will no longer be able to set up new Pay-as-you-go (PAYG) billing plans for Microsoft 365 Copilot Chat via the Power Platform admin center.

[How this affects your organization:]

Who is affected: Admins managing billing plans for Microsoft 365 Copilot Chat

What will happen:

• The PAYG billing plan setup will no longer be available via the Power Platform admin center.
• Admins will configure billing plans for Microsoft 365 Copilot Chat via the Microsoft 365 admin center.
• Existing billing plans created in the Power Platform admin center will remain active and manageable in that portal.
• Use of the PAYG billing option does not require a Microsoft 365 Copilot license.
• No impact to user experience.

[What you can do to prepare:]

• Inform your admins about the transition to the Microsoft 365 admin center.
• If your organization needs to create a new billing plan after October 3, 2025, use the Microsoft 365 admin center.

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Introduction

We’re introducing enhancements to OneDrive that simplify the process of managing files when employees leave your organization. These updates improve visibility, streamline bulk transfers, and help ensure important content remains accessible and shared appropriately.

This feature is associated with Microsoft 365 Roadmap ID 493946.

When this will happen

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

How this affects your organization

Managing OneDrive content for departing employees is now more efficient. Key improvements include:

• Redesigned notifications: Account cleanup emails are now more prominent, reducing the chance of being overlooked.
• Improved filtering: New filters help managers quickly locate shared or important files.
• Bulk file transfer with preserved sharing: The “Move and keep sharing” feature allows multiple files to be transferred while retaining existing sharing permissions.
• Consolidated alerts: When six or more files are moved, collaborators receive a single streamlined notification.

These updates help ensure a smooth handover and reduce the risk of losing critical files.

When a user account is deleted, OneDrive access is automatically granted to the manager or designated secondary owner. The recipient receives an email notification with access details and information about the OneDrive retention period. Seven days before the retention period ends, a second reminder email is sent, stating that the OneDrive will be permanently deleted in seven days.

Steps to transfer files:

1. From the email, click View files to access the departing user’s OneDrive.
   
2. Use the Shared filter to view only shared files, or All to see everything.
3. Select files using the checkbox in the table header.
   
4. Click Move to, choose a destination, and check Keep sharing with the same people.



5. Click Move to again to complete the transfer.

Collaborators will receive a single notification once the move is complete:

What you can do to prepare

No admin action is required before rollout. You may want to:

• Inform managers and secondary owners about the new experience.
• Update internal documentation to reflect the new transfer process.

Learn more: OneDrive retention and deletion – SharePoint in Microsoft 365 | Microsoft Learn

Compliance considerations

No compliance considerations identified, review as appropriate for your organization.

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

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

[When this will happen:]

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

[How this will affect your organization]

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

[What you need to do to prepare]

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

For admins

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

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

Learn more:

• Detailed support article with additional resources. 
  

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

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

[Key Points:]

• Major: Retirement
• Timeline:
  • Starting November 1st, 2024, new tenants will not be able use Azure ACS.
  • Starting April 2, 2026, Microsoft will remove the ability use SharePoint ACS for existing tenants.
• Action: Review and assess impact

[How this will affect your organization]

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

[What you need to do to prepare]

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

For admins

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

Learn more

• Support update for the retirement of Azure ACS for SharePoint Online in Microsoft 365.

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

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

[Key Points:]

• Major: Retirement
• Timeline:
  • Starting July 1st, 2024, SharePoint Add-Ins cannot be installed from the public marketplace, also referred to as store by existing tenants. Installation from a private app catalog stays possible.
  • Starting November 1st, 2024, new tenants will not be able use SharePoint Add-Ins, regardless of their origin (public marketplace, private tenant catalog).
  • Starting April 2nd, 2026, Microsoft will remove the ability use SharePoint Add-Ins for existing tenants.
• Action: Review and assess impact

[How this will affect your organization:]

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

[What you need to do to prepare]

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

For admins

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

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

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

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

Set-SPOTenant -IsSharePointAddInsDisabled $true

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

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

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

Learn more

• Support update for the retirement of SharePoint Add-Ins in Microsoft 365.

Updated October 3, 2025: This update serves as a reminder that SharePoint Framework domain isolated web parts will retire and stop working in 6 months from now (April 2, 2026).

After careful consideration and extensive review of usage data and feedback Microsoft has decided to retire the domain isolated web parts feature in the SharePoint Framework (SPFx).

[When will this happen:]

• Starting April 2, 2025, domain isolated web parts will be turned off for any newly created tenants.
• Starting April 2, 2026, Microsoft will remove the ability to use domain isolated web parts for existing tenants.

[How this will affect your organization:]

If your organization still uses domain isolated web parts, after the change has rolled out these will render an error message and stop functioning. We recommend customers to update the impacted web parts as regular web parts and redeploy them.

[What you need to do to prepare:]

To understand whether you have installed domain isolated web parts and granted permissions you can verify if the SharePoint admin center API access page contains permissions listed under the Isolated grouping. If you see permissions listed under Isolated then you can use the instructions described on the domain isolated web part retirement page to discover the solutions, their domain isolated web parts and where those web parts are used. This resource will also contain the needed steps to update the web parts to not use domain isolation.

Note: There will not be an option to extend domain isolated web parts beyond April 2, 2026.

Learn more:

• Domain isolated web part retirement page
• Retirement announcement blog post