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

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

Coming soon: The Microsoft Teams Meeting add-in in classic Microsoft Outlook for Windows desktop will suggest meeting options to meeting organizers based on meeting details, helping organizers easily schedule meetings with optimized settings from the scheduling form.

This message is associated with Microsoft 365 Roadmap ID 487858.

[When this will happen:]

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

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

[How this will affect your organization:]

After this rollout, meeting organizers that have the Teams add-in installed for classic Outlook for Windows desktop will be able to see Meeting option suggestions in the new Setup pane of the scheduling form when they schedule a Teams meeting. meeting organizers can open the Setup pane from the Teams Meeting add-in ribbon in the form, or the pane will automatically open when suggestions are available.

A meeting organizer can save or accept the suggestions and easily update Meeting options from the pane.

If a user closes the ‘Setup your Teams Meeting’ pane during scheduling, then the pane will not auto-open again until the ‘Setup’ button in the Teams Meeting Add-In ribbon is clicked.

This feature 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 assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation.

Refer to documentation on how to manage, install, and troubleshoot the Teams COM add-in for Classic Outlook for Windows:

• Manage add-ins in the admin center – Microsoft 365 admin | Microsoft Learn
• Use add-ins in Outlook – Microsoft Support
• Resolve issues with Teams Meeting add-in for classic Outlook – Microsoft Teams | Microsoft Learn

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

Introducing a new content picker for Teams Mobile Android. Attach any type of content, whether files or media, from the paperclip icon in the compose overflow menu. Our unified attach flow makes it easy and intuitive to attach content from any source location.

This message is associated with Microsoft 365 Roadmap ID 488091.

[When this will happen:]

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

General Availability (GCC, GCC High, DoD) We will begin rollout on Android late June 2025 and expect to complete by late September 2025

[How this will affect your organization:]

Users will see an improved content attach flow in the Teams Android app.

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

Coming soon to Microsoft Purview | Insider Risk Management (IRM), admins will be able to select any Communication Compliance (CC) policy alerts as indicators in IRM policies. After this rollout, IRM admins can select any CC policies that they would like to bring into IRM and detect if a user has alerts for these selected CC policies. When an IRM alert is generated, admins can review if there are any alerts for the user in CC under the policies that are enabled as indicators. This feature will help admins and analysts view this information in IRM without switching to CC.

This message is associated with Microsoft 365 Roadmap ID 489838.

[When this will happen:]

Public Preview: We will begin rolling out late July 2025 (previously late May) and expect to complete by early August 2025 (previously early June).

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

[How this will affect your organization:]

After this rollout, admins will be able to enable this indicator in IRM’s global settings for policy indicators. When enabled, this indicator can be selected in any IRM policy.

Using the indicator

1. In IRM, go to Settings > Insider Risk Management > Policy indicators > Built-in Indicators. Open the Communication Compliance indicators > Detect messages matched by specific CC policies drop-down menu. Check the box and choose the CC policies to bring into IRM. Save the changes.
2. To use in a policy: In the policy wizard for any IRM policy, configure the policies as applicable until you get to the Indicators page. Open the Communication Compliance indicators drop-down menu and check the box for Sending messages flagged by selected CC policies. Configure the rest of the policy as applicable.

These changes will be available by default for admins to configure.

[What you need to do to prepare:]

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

Learn more: Configure policy indicators in insider risk management | Microsoft Learn (will be updated before rollout)

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

Coming soon for Microsoft SharePoint: A new web part for FAQs, to help assist content owners keep their content fresh and relevant. Powered by Microsoft 365 Copilot, this new web part can help content owner easily curate FAQ by working with agents and connected grounding data.

Copilot license requirements:

• Reading: All readers can view FAQ web part content without a Copilot license.
• Creating & Editing: A Copilot license is necessary for creating and editing content using Copilot features.

This feature requires a SharePoint license and a Microsoft 365 Copilot license.

This message is associated with Microsoft 365 Roadmap ID 482198.

[When this will happen:]

Public Preview (Worldwide): We will begin rolling out early August 2025 and expect to complete by late August 2025.

Public Preview (GCC): We will begin rolling out late September 2025 and expect to complete by mid-October 2025.

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

[How this will affect your organization:]

After this rollout, authors can add the web part for FAQs directly to pages or news posts during editing:

By selecting one or more grounding source files, AI will automatically generate FAQ content, reducing the time and effort needed for manual creation of FAQs. The web part currently supports FAQ types such as Event, Product, and Policy, with the option for authors to provide additional descriptions to guide more targeted content generation.

FAQs created using the web part can be indexed for search and shared via email, making it easier to distribute consistent, up-to-date information to your organization.

This change will be available by default.

[What you need to do to prepare:]

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

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

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

To improve meeting clarity and reduce confusion caused by connectivity issues, we’re adding a new Network Strength Indicator. 

This message is associated with Microsoft 365 Roadmap ID 414513

[When this will happen:]

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

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

[How this will affect your organization:]

This feature will display your current network quality using a simple 3-bar system: Good (3 bars), Poor (2 bars), and Bad (1 bar). When your connection is limited, we’ll suggest actions to help conserve bandwidth and maintain meeting performance. You’ll also be able to see when other participants are experiencing poor or bad network conditions, providing better context for disruptions in the meeting.

[What you need to do to prepare:]

You may consider updating your training and documentation as appropriate.

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

Coming soon: IT administrators will be able to run silent, synthetic Microsoft Teams call simulations to specific subnets—enabling proactive network readiness checks and early detection of issues before they affect users. This will ensure high-quality, seamless communication experiences across the organization.

This feature requires a Teams Premium license on your user’s devices.

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

This message is associated with Microsoft 365 Roadmap ID 490055.

[When this will happen:]

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

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

[How this will affect your organization:]

Silent test calls offer proactive monitoring, allowing IT teams to detect and address network issues before they affect users. By integrating silent test calls into your operational routines, you can proactively detect and resolve potential issues.

• Tests run silently in the background on the Teams client at scheduled times.
• A test runs for 60 seconds.
• Tests are targeted at a specific subnet.
• Test will run only on Desktop clients (Windows and Mac).
• Tests only run if the device is idle (user is not in an active Teams call).
• Users experience no disruption: no notifications, sounds, or visible changes.

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

[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 assess the impact on your organization. You may want to notify your users about this change and update your relevant documentation.

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

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

 We’re adding new peripheral health reporting capabilities to the Pro Management portal, enabling admins to proactively monitor device issues in bring your own device (BYOD) rooms and desks.

These reports help identify when peripherals are faulty, missing, moved, or undetectable by a PC—allowing admins to take action before users report problems. Reports for rooms require a Teams Shared Devices license. Desk reporting is currently in public preview.

This change is associated with Microsoft 365 Roadmap ID: 493319

[When this will happen:]

General Availability (Worldwide and GCC): Rollout will begin in late February 2026 (previously early November 2025) and is expected to complete by early March 2026 (previously late November 2025).

[How this affects your organization:]

Admins can now use peripheral status data to detect hardware issues in BYOD rooms and desks before they impact users. This proactive monitoring can reduce support tickets and improve meeting space reliability.

• Reports for rooms require a Teams Shared Devices license.
• Reports for desks are available in public preview and do not yet require a license.

[What you can do to prepare:]

To ensure accurate peripheral status reporting:

• Use multiple peripherals in each room or desk setup. The system compares expected device pairings (e.g., if Peripheral A and B are usually connected together, but A is missing, it will be flagged).
• Simplify connectivity for users by using a single cable solution to connect all peripherals.
• Ensure rooms and desks are bookable and have associated peripherals—this enables the Teams desktop client to send the necessary telemetry. Peripheral association can be done manually or automatically.

[Compliance considerations:]

• Does the change alter how existing customer data is processed, stored, or accessed? Maybe (device telemetry is used for reporting)

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

We’re introducing several enhancements to the modernized eDiscovery interface in Microsoft Purview to streamline workflows, improve usability, and provide greater administrative control. These updates include:

• Ability to delete searches
• Ability to delete exports created from searches
• Auto-population of the custodian field in review sets and exports
• Advanced indexing improvements, including indexing all Exchange items with attachments in scope
• A new tenant-level premium feature toggle to control eDiscovery case license toggle value during case creation.
• A new analytics process report for deeper insights into review set analytics (e.g., deduplication)
• Expanded search condition builder with support for logical operators (AND, OR, NEAR) in the keywords field
• Export packages to include user input export name for easier association with the export process
• Bulk import of data sources
• Ability to configure the maximum export package size, along with an updated default value.

These updates are designed to enhance the eDiscovery experience by offering more flexible, powerful tools and reducing administrative overhead.

This change is associated with Microsoft 365 Roadmap ID: 494160 

[When this will happen:]

General Availability (Worldwide/GCC/GCCH/DoD): Rollout will begin in late June 2025 and is expected to complete by late November 2025 (previously late September).

[How this will affect your organization:]

• The tenant-level premium toggle sets the default value for newly created cases, giving admins centralized control over premium settings without affecting existing cases.
• The ability to delete searches and direct exports introduces a change in lifecycle management, which may impact audit trails or collaboration workflows.
• Logical operators in the search condition builder will enhance query precision but may require updates to search strategies.
• Advanced indexing improvements will improve content discoverability, especially in complex or high-volume cases.

[What you can do to prepare:]

• Review and update internal documentation, training materials, and workflows to reflect these changes.
• Ensure your teams are aware of the new search and direct export deletion capability and its implications for audit and collaboration.
• Update search guidance to incorporate logical operators for more effective query construction.
• Evaluate how the new analytics report and indexing enhancements can support your review and prioritization processes.

[Compliance considerations:]

• Alters how existing customer data is processed, stored, or accessed: Yes – Advanced indexing improvement may affect how data is processed and accessed within eDiscovery.
• Modifies or disables Purview capabilities (eDiscovery, audit logging, etc.): Yes – The ability to delete searches and direct exports directly impact eDiscovery workflows and may affect audit logging.
• Alters how admins monitor/report on compliance activities: Yes – The new tenant level license toggle affects how admin control the use of eDiscovery premium features in their eDiscovery workflow. 
• Modifies how users access/export/delete/correct personal data (GDPR DSR): Maybe – The ability to delete searches and direct exports could affect how personal data is retained or accessed, depending on organizational policies and configurations.

Updated October 27, 2025: We are not releasing this feature at this time. We apologize for any inconvenience this may cause.

We’re introducing a new personalization feature in Microsoft Teams that allows users to select from a set of accent colors. This update enhances the user experience by enabling visual customization of the Teams interface and will be available on Desktop, Mac, and Web platforms. 

This message is associated with Microsoft 365 Roadmap ID 497139.

[When this will happen:]

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

[How this will affect your organization:]

Users will be able to personalize their Teams experience by choosing an accent color for the Teams shell. This change is purely cosmetic and does not impact functionality or performance. The feature will be on by default and available to all users once the rollout is complete.

Image 1. Change accent colors in Settings > Appearance:

Image 2: User selected accent color applied in Teams:

[What you need to do to prepare:]

No admin action is required. However, you may wish to inform your users about this new personalization option.

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

Introduction

We’re enhancing offline functionality in the new Microsoft Outlook for Windows. This update (Microsoft 365 Roadmap ID 496371) enables users to add file attachments while composing emails offline, improving productivity for those working without an internet connection.

When this will happen

• Targeted Release (Worldwide): Rollout begins in late October 2025 and is expected to complete by late November 2025.
• General Availability (Worldwide): Rollout begins in early January 2026 (previously mid-December 2025) and is expected to complete by early February 2026 (previously early January 2026).
• General Availability (GCC): Rollout begins in mid-February 2026 (previously mid-January 2026) and is expected to complete by late February 2026 (previously late January 2026).

How this affects your organization

Users with offline mode enabled in the new Outlook for Windows will be able to attach files to draft emails while offline. These emails, including attachments, will be sent automatically once the device reconnects to the internet.

This feature will be on or off by default based on your current configuration of the OWAMailboxPolicy-OfflineEnabledWin policy. No changes will be made to existing configurations.

What you can do to prepare

To enable this functionality, ensure the following settings are configured in the new Outlook under Settings > General > Offline:

• Enable offline email, calendar, and people
• Include file attachments

Admins can manage this feature using the OWAMailboxPolicy-OfflineEnabledWin mailbox policy. Learn more at Set-OwaMailboxPolicy.

Caption i. Offline editing can be enabled or disabled in Settings > General > Offline

Compliance considerations

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

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

Disclaimer: The original message center post was published on August 1, 2025. We previously stated that this is a new feature when it is an expanded capability of the existing feature memory in Copilot. This expanded capability requires new processing of users’ data, which is outlined below. We have edited the content below for accuracy and clarity. Thank you to the customers who provided feedback over the past few weeks. We have adjusted our roadmap to address your needs and concerns. 

Starting September 1, 2025, Microsoft 365 Copilot will start remembering key highlights from your person-to-person communications in chats, emails, and meetings. Initially these memories will be used to improve the quality of Copilot responses to people-related questions. These memories are private to the user. This feature is available to Copilot-licensed enterprise users.

This message is associated with Microsoft 365 Roadmap ID 499153

Updated October 27, 2025: We have updated the content. Thank you for your patience. 

Introduction

We’re introducing Teams Collaborative Notes (powered by Loop) in group chats across desktop and web experiences. This feature enables users to co-create and edit notes, agendas, and action items directly within the Teams chat interface, enhancing real-time collaboration without switching contexts.

This message is associated with Roadmap ID 498159.

When this will happen

• Targeted Release: Rollout begins late September (previously early September) and completes by late October 2025 (previously early October).  
• General Availability: Rollout begins early November 2025 (previously early October) and completes by mid November 2025 (previously late October).

How this affects your organization

Users will see a new Notes tab in group chats, allowing them to create and collaborate on Loop components such as agendas and action items. These components are editable inline, supporting synchronous collaboration directly within Teams.  

This feature is on by default for all tenants. Users do not need to install anything to begin using it.

What you can do to prepare

• You can manage this feature via the Teams Admin Center. If desired, Collaborative Notes can be disabled at the tenant level.
• Review internal documentation and training materials to ensure users are aware of the new Notes tab and its capabilities.
• Admins can manage the feature via the Teams Admin Center under: Messaging → Messaging Settings → Messaging Notes
  • Alternatively, it can be configured using the PowerShell cmdlet: Set-CsTeamsMessagingConfiguration

Compliance considerations

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

[Introduction]

As part of this transition, Microsoft Teams is now available at https://teams.cloud.microsoft, in parallel with its previous domain. This change enhances security by using Microsoft’s exclusive top-level domain, .microsoft, which helps prevent spoofing and builds user trust.

Learn more by reading the 2023 blog post Introducing cloud.microsoft: a unified domain for Microsoft 365 apps and services.

[When this will happen:]

[How this affects your organization:]

Who is affected: Admins managing Microsoft Teams, Teams apps, and network configurations. All users accessing Microsoft Teams.

What will happen:

• Users will be automatically redirected to teams.cloud.microsoft.
• No user action is required; existing links and bookmarks will continue to work.
• Users may notice that the new application domains are lacking the “.com” extension. This is by design, as “.microsoft” is Microsoft’s own top-level domain – and this exclusivity allows for additional security and protection against spoofing.
• Admins can disable redirects via the Teams Admin portal if needed.
• The cloud.microsoft domain has been a part of standard Microsoft network guidance on domains and service endpoints since April 2023. 

• Educate users to recognize and expect cloud.microsoft as a key domain for Microsoft cloud experiences. You can refer them to What is cloud.microsoft? – Microsoft Support for more information. 
• If your organizational websites, tools, or other materials reference the old URL, those links will be automatically redirected. However, it’s good practice to update those assets to avoid user confusion.
• Update internal documentation, websites, and tools that reference the old Teams URL.
• Partner with developers of in-house Teams apps (including those used in Outlook and Microsoft 365) to follow guidance in: Action required: ensure your Microsoft Teams apps are ready for upcoming domain changes.
• Confirm that *.cloud.microsoft is not blocked on your enterprise network. This should require no action if standard Microsoft network guidance on domains and service endpoints is being followed. 

[Compliance considerations:]

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

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

[Introduction:]

We’re introducing version history in Microsoft 365 Copilot Pages to help users confidently refine their work. This feature allows users to view and restore previous versions of a page—whether changes were made manually, through Copilot, or collaboratively. This update supports transparency and control in content creation, aligning with customer feedback.

[When this will happen:]

• Public Preview (Worldwide): Begins early October 2025 and completes by late October 2025.
• General Availability (Worldwide): Begins late October 2025 and completes by early November 2025 (previously late October).

[How this affects your organization:]

Who is affected: Users with Entra ID (work or school) accounts who have access to Microsoft 365 Copilot Pages and underlying SharePoint or OneDrive storage. 

Note: A Microsoft 365 Copilot license is not required to use version history in Copilot Pages.

What will happen:

• Users will be able to view and restore previous versions of Copilot pages:

 

• Version history will include changes made manually, via Copilot, or by collaborators.
• The feature will be enabled by default.
• No admin configuration is required.

Admin controls and licensing:

• IT admins cannot disable version history for Copilot Pages.
• Admins can manage how many versions are stored using existing versioning settings in the underlying SharePoint or OneDrive library.
• Copilot Pages are configured to save up to 50 versions per file.
• There are no Copilot Page-specific versioning controls today.
• Version history is available to users with SharePoint or OneDrive storage—even if they do not have a Microsoft 365 Copilot license.
• Copilot Pages are not currently available to personal Microsoft accounts (such as Microsoft 365 Personal or Family).

[What you can do to prepare:]

No action is required at this time.

You may choose to:

• Communicate this change to helpdesk staff.
• Update internal documentation if you reference Copilot Pages functionality.
• Review training materials to ensure users are aware of the version history feature.
• Review your SharePoint or OneDrive versioning settings if you want to adjust how many versions are retained.

Learn more: 

• [to be updated for WW General Availability rollout phase in late Oct. 2025] – How Microsoft 365 Copilot Pages works | Microsoft Support
• Summary of governance, lifecycle, and compliance capabilities for Loop | Microsoft 365 | Microsoft Learn

[Compliance considerations:]

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

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

[Introduction]

Admin activity related to agent management will now be logged in Microsoft Purview Unified Audit Logs. This enhancement improves visibility and traceability for security teams managing Copilot agents across Microsoft 365 services.

This message is associated with Microsoft 365 Roadmap ID 498227.

[When this will happen:]

General Availability (Worldwide): Rollout will begin in late October 2025 and is expected to complete by mid-November 2025.

[How this affects your organization:]

Who is affected:Admins managing Microsoft Copilot agents in Microsoft 365 environments.

What will happen:

• Admin actions such as publishing, deploying, removing, and updating agents will be logged.
• Changes to agent settings at both tenant and agent levels will be captured.
• Audit schema includes key data points such as agent name, agent type, and admin ID.
• Logs will be accessible via the Purview Portal.
• Feature is enabled by default; no configuration required.

Screenshot 1 – Search view in the new Microsoft Purview Unified Audit Log:

Screenshot 2 – Details view in the new Microsoft Purview Unified Audit Log:

[What you can do to prepare:]

• Security teams can begin searching and reviewing agent-related admin actions in the Purview Portal.
• Familiarize yourself with audit log search capabilities in Purview.
• No additional configuration is required to enable logging.

[Compliance considerations:]

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

[Introduction]

Browse your company’s approved logos, icons, and photos right inside PowerPoint—no need to search elsewhere. We’re introducing Brand Images in PowerPoint to help users easily access company-approved logos, icons, and photos directly within the app. This feature streamlines brand compliance and saves time by eliminating the need to search for assets externally.

This message is associated with Microsoft 365 Roadmap ID 509111.

[When this will happen:]

General Availability (Worldwide): Rollout will begin in late October 2025 and is expected to complete by late November 2025.

[How this affects your organization:]

Who is affected: All users of PowerPoint in Microsoft 365 tenants with an Organization Assets Library (OAL) configured.

What will happen:

• Users will be able to browse and insert approved images directly from a centralized library in PowerPoint.
• The feature will be ON by default for all tenants. Admins must set up their SharePoint OAL for employees to use this feature effectively.
• Admins can manage which images are available, ensuring brand consistency and compliance.
• Reduces the risk of using outdated or unauthorized images.
• No impact to end-user workflow unless the OAL is not set up.

[What you can do to prepare:]

• Set up the OAL: Create an organization assets library | SharePoint in Microsoft 365 | Microsoft Learn
• Use Microsoft PowerShell to specify the image OAL to be searchable: Connect organizational asset libraries to Copilot | SharePoint in Microsoft 365 | Microsoft Learn
• Upload enterprise images: Add approved logos, pictures, and other image type assets to the designated SharePoint library.
• Create folders by asset type (e.g., logos, images) to enable type-based filtering. Note: Only top-level (L1) folders are supported; subfolders cannot be used for filtering.
• Add robust image metadata for better search: Apply descriptive tags and metadata to each image. For guidance, refer to: 
  • Find and manage images using enhanced image tagging | Microsoft 365 | Microsoft Learn
  • Overview of image tagging | Microsoft 365 | Microsoft Learn

[Compliance considerations:]

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

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

[Introduction]

We’re introducing a new way to interact with your files in OneDrive: the Copilot floating button. This feature provides quick access to Copilot-powered actions, helping users work more efficiently by surfacing relevant tools and suggestions directly within the OneDrive interface.

General Availability (Worldwide): We will begin rolling out this feature starting October 15, 2025, and full rollout is expected to finish by early November 2025. During the rollout period, some users may not see the floating Copilot button in OneDrive.

Note: This is a gradual rollout, so not all users will see the feature at the same time.

• Who is affected: The floating Copilot button will automatically appear for any user who has a Microsoft 365 Copilot license.
• What will happen:
  • A new floating Copilot button will appear in the OneDrive web interface.
  • Users can ask questions about files, summarize documents, or compare content directly from OneDrive.
  • The button will offer contextual recommendations based on selected files.
  • Navigation is streamlined by surfacing relevant Copilot tools without needing to search through menus.
  • The feature is enabled by default for eligible users.

• Communicate this change to helpdesk and support teams.
• Drive internal awareness of the new Copilot experience in OneDrive.
• No configuration changes are required unless you wish to disable Copilot features for specific users.

Learn more: Get started with Copilot in OneDrive | Microsoft Support

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

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

[Introduction]

To support organizations with varying compliance and data handling needs, Microsoft Edge for Business is introducing Connected Feature Control (CFC) in Public Preview. CFC is a centralized policy that allows admins to manage cloud-powered and AI-driven features—such as Translate, Compose, and Auto Tab Grouping—based on organizational requirements.

[When this will happen:]

• Targeted Release: Rollout began in late August 2025 and is expected to complete by late September/October 2025.
• General Availability: Rollout begins in mid-November and is expected to complete by late November.

[How this affects your organization:]

Who is affected: Admins managing Microsoft Edge for Business via the Edge management service.

What will happen:

• A new policy called Connected Feature Control (CFC) will be available in Edge management.
• By default, CFC is off; no changes will be made to existing feature availability unless admins opt in.
• Admins can enable or disable specific connected experiences such as Translate, Compose, Screenshot, and Auto Tab Grouping.
• CFC offers three modes:
  • Off Mode: All connected experiences are enabled by default.
  • Level 1: Enables only experiences that are sensitive content aware.
  • Level 2: Enables only experiences that are sensitive content aware and meet strict data handling standards.

  

• Features like Translate and Screenshot are being enhanced for Level 2 compliance. Admins can choose to enable them in Level 2 via customization.

[What you can do to prepare:]

• Review your current Edge policies and connected experiences.
• Plan which features should be enabled or disabled based on your organization’s compliance needs.
• Opt in to Targeted Release in the Microsoft 365 admin center to access CFC.
• Notify users about upcoming changes and update internal documentation as needed.
• Learn more: 
  • Manage Connected Experiences in Microsoft Edge
  • Connected Feature Control in Microsoft Edge for Business

[Compliance considerations:]

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

[Introduction]

Microsoft is introducing two new ways for users to engage with Microsoft 365 Copilot:

• Sharing Copilot Notebooks on the web, enabling teams to collaborate in a single notebook with shared enterprise content
• A new Microsoft 365 Copilot mobile app update, allowing users to access Copilot experiences on the go

Sharing Copilot Notebooks enables teams to collaborate in a single notebook, combining Pages, Loops, OneNote Notebooks, SharePoint Sites, and other Microsoft 365 content with Copilot intelligence. This feature provides shared insights while maintaining data security and permissions, helping admins enable cross-functional collaboration with confidence.

These updates are designed to improve cross-functional collaboration and extend Microsoft 365 Copilot’s value across platforms.

This message is associated with Microsoft 365 Roadmap ID 506851.

[When this will happen]

General Availability (Worldwide): 

• Web: Will begin rolling out in late October 2025 and expect to complete in December 2025 based on telemetry.
• Mobile: Will begin rolling out in early November 2025 and expect to complete in December 2025 based on telemetry.

[How this affects your organization]

• Who is affected: Users without a Microsoft 365 Copilot license can be invited to a shared notebook, but they will not be able to access or interact with the content. Instead, they will see a page explaining they will need to acquire a Copilot license before they can access a shared notebook.
• What will happen:
  • Users will be able to share a notebook they created with other Copilot-licensed users: 

    

  • Users can create and collaborate on shared notebook pages.
  • Copilot responses will be grounded in shared enterprise content.
  • Chats within shared notebooks remain private to each user.
  • Access to linked files is granted only when the sharer has permission to share further.
  • Copilot ensures data sensitivity is protected when content is brought from chat into the notebook.
  • This feature improves cross-functional workflows and enables Copilot to deliver answers based on shared context.
  • Sharing is enabled by default when Copilot Notebooks is turned on via Office Cloud Policy Service (OCPS).
  • There is currently no admin control to disable sharing independently; the only way to prevent sharing is to disable Copilot Notebooks entirely via OCPS.
  • A new Copilot mobile app update will be available in November 2025, allowing users to access shared Copilot notebooks from their mobile devices.

[What you can do to prepare]

• Review your OCPS settings to manage Copilot Notebook availability.
• Notify users who will receive the feature (everyone with a Copilot license by default).
• Update user training materials to reflect the new collaboration capabilities and mobile access.
• Prepare your help desk to support questions about shared notebooks and the mobile app.
• Confirm licensing eligibility for users in EDU, GCC, and other sovereign cloud environments.
• Documentation links are being updated and will be provided when available.

[Compliance considerations]

No compliance considerations identified, all compliance capabilities will be the same as the Microsoft 365 Copilot Notebooks experience.

[Introduction]

We’re introducing the App Builder agent in Microsoft 365 Copilot, available starting October 28 through the Frontier program. This agent empowers information workers to build interactive, no-code apps directly within Copilot Chat using natural language and existing Microsoft 365 content. Designed for fast, intuitive app creation, App Builder helps users turn everyday ideas into functional apps for productivity, presentation, prototyping, and more.

The Frontier program provides early, hands-on access to experimental Microsoft 365 Copilot innovations in customer environments. Agents and AI features designated as “Frontier” are previews intended for evaluation and feedback. As these features are still in development, their availability and capabilities may change at any time.

[When this will happen:]

App Builder agent will begin rolling out in Preview to Frontier-enabled tenants starting on October 28, 2025, through the following week. The agent will be available in US only. 

[How this affects your organization:]

• Who is affected: Microsoft 365 customers with Copilot licenses who are enrolled in the Frontier program.
• What will happen:
  • Admins can manage agent access via Microsoft 365 Admin Center.

  

  • Admins can audit apps in Power Platform Admin Center.

  

  • App Builder Agent will appear in the Agent Store under “Built by Microsoft” as “App Builder (Frontier).”
  • Users can build apps using natural language prompts in Microsoft 365 Copilot Chat.

  

  • Apps are backed by created SharePoint Sites with data stored in Lists. One site per app.
  • No external data connections or custom APIs are supported.
  • Apps can be shared like documents and launched within Microsoft 365 Copilot.

[What you can do to prepare:]

• Identify users who would benefit from early access to App Builder and add them to a Microsoft Entra ID group.
• Enable Frontier features via Microsoft Admin Center > Copilot Settings > Copilot Frontier.
• Manage who can install the agent via Microsoft Admin Center > Copilot Agents > App Builder (Frontier) > Users.
• Communicate availability and usage guidance to helpdesk and end users.
• Review the Frontier program overview: Frontier program – Microsoft Adoption

[Compliance considerations:]

• This update addresses an issue where the touch keyboard does not enter characters into text fields after the device wakes from sleep.
• This update addresses an issue where external virtual switches lose their physical network interface card (NIC) bindings and convert to internal switches when the host restarts, resulting in network connectivity loss.
• This update addresses an issue that affects disk communication and causes connectivity errors during Azure Stack Hub or Azure Local cluster upgrades.

• Windows 11, version 23H2: KB5067112

• The Start menu has been redesigned to help you access your apps more quickly and smoothly. Its redesigned layout makes it easier than ever to find what you need.
• The prompt box in Click to Do* streamlines interaction with Copilot, helping you work more efficiently. You can type a custom prompt directly into the text box, which sends your prompt and selected on-screen content to Copilot.
• The new battery icons, which include color indicators and battery percentage, now appear in the lower-right corner of the lock screen.
• The “Email & accounts” section is now called “Your accounts.” You manage all your accounts under Settings > Accounts.  
• You can now configure a delay before a voice command is executed. To set this up, go to Voice access settings > Wait time before acting, and select the option that best matches your preferences.

• Windows 11, versions 25H2 and 24H2: KB5067036