Microsoft Roadmap, messagecenter and blogs updates from 25-09-2025

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

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

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

This message is associated with Microsoft 365 Roadmap ID 89975.

[When this will happen:]

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

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

[How this will affect your organization:]

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

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

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

This change will be available by default.

[What you need to do to prepare:]

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

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

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

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

Microsoft Teams will soon add features that make it easier for Teams Premium and Copilot users to communicate in meetings where attendees speak different languages. After this rollout, each participant can choose their spoken language and a translation language, for more inclusive and productive conversations. Users will also receive an automatically translated intelligent meeting recap in the translation language they selected for live transcription and captions. For admins, these features help to ensure a more inclusive collaboration experience for multilingual teams, without requiring extra setup.

A Microsoft 365 Copilot license or a Teams Premium license are required to use this feature.

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

This message is associated with Microsoft 365 Roadmap ID 481144.

[When this will happen:]

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

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

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

[How this will affect your organization:]

After this rollout, users will be able to:

• Speak in their language: Choose from nine supported languages: Chinese (Mandarin), English, French, German, Italian, Japanese, Korean, Portuguese (Brazil), and Spanish.
• Read in their preferred language: The meeting transcript will reflect conversations in each user’s chosen translation language.
• Get an automatic recap: After the meeting, Teams will generate an intelligent meeting recap in each user’s selected translation language so they can review key discussions with ease.
• Switch languages anytime: Even after the recap is generated, users can still change the translation language from the drop-down menu on the recap page.

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.

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

Updated September 24, 2025: We have updated the content. 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 late September 2025 (previously late August) 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 September 24, 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 early November 2025 and is expected to complete by 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 September 24, 2025: We have updated the timeline. Thank you for your patience. 

Coming soon to Microsoft Purview | Information Protection: To help improve label usability and configuration, the sensitivity labeling scheme will be simplified to only consist of labels and label groupings.

This move to a dynamic architecture will make it easier to move a child label into label groups, out of label groups, and between label groups without losing referential integrity, allowing customers to better scale and reorganize their labels across their entire data estate.

Tenants in scope for manual migration to the new label scheme will see a message on the Sensitivity labels page in the Purview portal, where the tenant admin can access a simple manual migration wizard to opt in to the migration, which should complete in less than a few minutes or even seconds, depending on the label configuration.

If you do not see this message, your tenant does not meet the criteria for manual migration (your tenant lacks applicable parent labels). This new label scheme will be rolled out to your tenant in the coming months. (and we will send a separate MC post in advance).

This message is associated with Microsoft 365 Roadmap ID 386900.

[When this will happen:]

Public Preview (Worldwide): Modern labels have been in Public Preview since July 7th 2025. This post announces the rollout of modern label scheme to new tenants and tenants with applicable parents.

General Availability (Worldwide): We will being rolling out early December 2025 and expect to be completed by late December 2025

[How this will affect your organization:]

During migration, to ensure label scoping integrity, any applicable parent label will be converted to a child label under a new label group, and then both parent and child label will have the same display name as the original parent label. Non-applicable parent labels will automatically be converted to label groups.

A parent label is deemed applicable if it has a different scope from any of its children, has label actions, or is published separately from its children.

The manual migration wizard provides a preview of the migrated scheme so admins can better understand how their sensitivity label scheme will change after the migration.

After migration, admins are free to make changes to their migrated label scheme, including unpublishing applicable parent labels that were converted to children during migration.

Users will not notice any change in how labels are viewed or applied. This change will be on by default.

Example of a migrated label scheme:

[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 tenant’s label scheme to ensure it is up to date. You may want to notify your admins about this change and update any relevant documentation.

Optionally, before you migrate your production tenant, consider migrating a test tenant configured with a label scheme that is representative of your production tenant, to become familiar with the migration process and the modern label scheme.

Learn more: Learn about sensitivity labels | Microsoft Learn

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

Introduction

We’re streamlining the Know Your Customer (KYC) requirements for acquiring Microsoft telephone numbers in all markets. Teams administrators will need to submit general business information and supporting documents via Teams Admin Center before provisioning new telephone numbers. This is a one-time process that will allow Microsoft to validate businesses and fulfill regulatory requirements, helping protect our phone services from misuse, such as spam calls and voice phishing (vishing).

When this will happen

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

How this will affect your organization

This change updates the existing telephone number provisioning workflow. Teams administrators must now complete a KYC onboarding process in the Teams Admin Center before provisioning new telephone numbers.

• Admins will be required to submit business information and supporting documentation.
• The vetting process typically takes a few hours but may take up to two business days.
• No new telephone numbers can be acquired until the submitted information is validated.
• Existing telephone numbers are not affected.

These requirements apply globally and are consistent across all Calling Plans markets.

What you need to do to prepare

Ensure your Teams administrators are ready to provide the following information via the Teams Admin Center:

• Company name
• Tax ID, DUNS number, or Business Registration Number
• Business address
• A copy of the Business Registration, Registry Extract, or Articles of Incorporation

This process applies to all tenants, including those on free trials. No specific license tier is required to complete the KYC onboarding.

Learn more: Teams Phone Know Your Customer overview – Microsoft Teams | Microsoft Learn  

Compliance considerations

• Does the change store new customer data, if so, where, and is the data cached or permanently stored? – Yes. The KYC onboarding process requires submission of business information and supporting documentation, which will be stored by Microsoft to fulfill regulatory requirements.
• Does the change alter how existing customer data is processed, stored, or accessed? – Maybe. While existing telephone numbers are not affected, the process introduces new data collection and validation workflows that may interact with existing tenant metadata.
• Does the change include an admin control and, can it be controlled through Entra ID group membership? – Yes. The KYC onboarding process is managed through the Teams Admin Center, which supports role-based access control via Entra ID group membership.

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

Beginning mid-August 2025, we’re introducing a new Tools feature in the Copilot Chat prompt box. Tools acts as a lightweight entry point into high-value, task-specific Copilot features and capabilities directly from the prompt box. By selecting Tools, users get a menu where they can easily discover and trigger the right Copilot feature or capability for their current task, while also providing consistent interactions across tools. Based on the user’s license, Tools provides easy access to features and capabilities like Researcher, Analyst, Pages, and image generation.

This message is associated with Microsoft 365 Roadmap 497298.

When this will happen

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

How this affects your organization

Once this update is rolled out, users will see a new Tools button in the Copilot Chat prompt box. Selecting this button opens a menu of AI-powered features tailored to the user’s license. This enhancement improves discoverability and usability of Copilot capabilities, helping users complete tasks more efficiently.

This feature is on by default and does not require admin configuration.

What you can do to prepare

No admin action is required. However, you may want to:

• Inform users about the new Tools experience in Copilot Chat.
• Update internal documentation or training materials if needed.

Compliance considerations

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

Updated September 24, 2025: After further review, this has been delayed to a later date. We apologize for any inconvenience.

Introduction

We’re introducing a new Service health dashboard in the Microsoft Purview compliance portal. This feature provides a detailed view of service health for Microsoft Purview and the Microsoft 365 services and Azure Cloud Services that affect Purview—helping administrators monitor outages, advisories, and service issues without switching portals.

This message is associated with Microsoft 365 Roadmap ID 497944.

View real-time status across Purview, Microsoft 365, and Azure:

Reported issue summary:

When this will happen

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

How this affects your organization

Administrators will gain direct access to service health insights from within the Purview portal. This includes the ability to:

• View real-time service health status for Microsoft Purview, including related Microsoft 365 and Azure Cloud services. 
• Submit potential emerging issues for review by Microsoft support teams.

This feature will be enabled by default and does not require manual configuration.

Submit a service issue:

 What you can do to prepare

No action is required to prepare for this change. However, we recommend informing your compliance and IT operations teams about the new dashboard to streamline monitoring workflows.

Compliance considerations

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

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

Introduction

Starting September 15, 2025, the Reporting Labels feature in Teams Admin Center will be retired. It will be replaced with a new unified upload page that streamlines the management of building and endpoint data for Teams reporting. This update simplifies data handling by consolidating inputs for both Call Analytics and Call Quality Dashboard (CQD).

This message is associated with Microsoft 365 Roadmap ID 495830.

When this will happen

• General Availability (Worldwide): Rollout begins early September 2025 and completes by mid-September 2025.
• General Availability (GCC): Rollout begins early September 2025 and completes by mid-October 2025.

MSIT Deployment: Begins early June 2025.

How this affects your organization

This change eliminates the need to maintain separate building files in Reporting Labels and CQD. You will now manage building and endpoint data through a single page in Teams Admin Center, enriching call reports with customized tenant information.

What you can do to prepare

If you currently use the building and endpoint file upload feature in CQD, no action is required. Your existing files will automatically appear in the new upload page.

If you use Reporting Labels but not CQD, ensure you have an updated building file ready for upload. You can continue uploading building and endpoint data in CQD at any time.

Compliance considerations

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

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

Updated September 5, 2025: Access to emails by typing ‘/’ in the prompt box will only be available when using Copilot Chat in Outlook. This applies to both the full app and side pane experience.

We’re enhancing Copilot Chat for users with a Microsoft 365 Copilot license with new capabilities that make it easier for them to include work content—such as files and emails—in their prompts when using Chat in Web scope. By typing ‘/’ in the prompt box, users can quickly search and reference relevant files or emails, streamlining prompt creation and improving Copilot responses. Additionally, some suggested prompts beneath the input box will now include relevant files or emails to help users get started quickly.

Note: Web scope in Copilot Chat is still grounded only in the web. Users can also choose to include additional content in the prompt for Copilot to reason over, such as with the methods described above. Users must switch to Work scope to have Chat automatically grounded in content from their organization’s graph or their personal graph.

This message is associated with Microsoft 365 Roadmap ID 500377.

When this will happen:

• Files: Currently available (Roadmap ID 497112)
• Emails: Rollout begins early October 2025 (previously mid-September) and completes by late October 2025 (previously late September).  Roadmap ID 500377.

[How this will affect your organization:]

This update improves usability and prompt relevance in Copilot Chat by allowing users to reference files and emails in their prompts (without uploading them manually) or as part of suggested prompts under the input box. Users will only see content they have access to, based on interaction signals (such as accessed, modified, or shared) and properties (such as creation or last update date).

No changes to default settings or user permissions are required.

What you can do to prepare:

No admin action is required. You may want to inform your users of these changes.

Learn more: Using Context IQ to refer to specific files, people, and more in Microsoft 365 Copilot and Copilot Chat

Compliance considerations

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

Updated September 5, 2025: Access to emails by typing ‘/’ in the prompt box will only be available when using Copilot Chat in Outlook. This applies to both the full app and side pane experience.

We’re enhancing Microsoft 365 Copilot Chat with new capabilities that make it easier for users to include work content—such as files and emails—in their prompts. By typing ‘/’ in the prompt box, users can quickly search and reference relevant files or emails, streamlining prompt creation and improving Copilot responses. Additionally, some suggested prompts beneath the input box will now include relevant files or emails to help users get started quickly.

Note: For users without a Microsoft 365 Copilot license, Copilot Chat is still grounded only in the web. Users can also choose to include additional content in the prompt for Copilot to reason over, such as with the methods described above. Chat is not automatically grounded in the organization’s graph or the user’s personal graph – this is only available for users with a Microsoft 365 Copilot license when using Chat in Work scope.

This message is associated with Microsoft 365 Roadmap ID 500377.

When this will happen:

• Files: Currently available (Roadmap ID 497112)
• Emails: Rollout begins early October 2025 (previously mid-September) and completes by late October 2025 (previously late September). Roadmap ID 500377.

How this affects your organization:

This update improves usability and prompt relevance in Copilot Chat by allowing users to reference files and emails in their prompts (without uploading them manually) or as part of suggested prompts under the input box. Users will only see content they have access to, based on interaction signals (such as accessed, modified, or shared) and properties (such as creation or last update date).

No changes to default settings or user permissions are required.

What you can do to prepare:

No admin action is required. You may want to inform your users about the new reference capabilities.

Learn more: Using Context IQ to refer to specific files, people, and more in Microsoft 365 Copilot and Copilot Chat

Compliance considerations

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

To better reflect the identity and functionality of the Microsoft 365 Copilot app, we are updating the executable name on Windows devices. This change improves clarity for IT admins, developers, and users managing diagnostics or process monitoring.

When this will happen:

This update will roll out to affected users with the next app update after late September 2025 (previously September 20).

How this affects your organization:

With the change, the executable name for the Microsoft 365 Copilot Windows app will change from Webviewhost.exe to M365Copilot.exe. For users who installed the app via the Microsoft Store, the update will happen automatically on September 20 if their device settings allow for automatic updates. For users who installed the app through other platforms or have settings that do not allow automatic updates, the change will happen once users update their app.

This update does not affect app functionality or user experience.

What you can do to prepare:

No action is required unless your organization has dependencies on Webviewhost.exe. If so, update those references to M365Copilot.exe to ensure continued functionality.

Compliance considerations:

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

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

Introduction

We’re introducing new output control features in the Researcher Agent within Microsoft 365 Copilot. These enhancements allow users to customize the length of generated reports and select preferred output formats, improving flexibility and usability.

When this will happen: General Availability (Worldwide):

Rollout will begin in late September 2025 (previously mid-September) and is expected to complete by late October 2025 (previously late September).

How this affects your organization

This update gives users greater control over how research reports are generated and exported.

• Before generating a report, users can now select a desired length (short, comprehensive):

   

• After generation, users can choose from multiple output formats, including exporting to Word:

   

What you can do to prepare

• No action is required at this time.
• Admins may wish to inform users of the new customization options available in the Researcher Agent.

Compliance considerations

Updated September 24, 2025: After further review, we will announce a revised GA date after we have had an opportunity to collect feedback from the public preview. Thank you for your patience.

Introduction

We’re introducing a new feature: M365 Copilot Chat adoption metrics in the Microsoft Copilot dashboard. This feature provides organizations with enhanced visibility into how users who are not licensed for Microsoft 365 Copilot are engaging with Copilot Chat. These insights include usage trends, retention and intensity metrics, app-level breakdowns, and filtering by organizational attributes—helping organizations better understand adoption patterns and tailor support strategies.

This feature will be available to tenants with at least 50 assigned Viva Insights licenses or 50 assigned Microsoft 365 Copilot licenses (includes Viva Insights service plan).

This message is associated with Microsoft 365 Roadmap ID 499899.

When this will happen

Public Preview: We will begin rolling out at the end of October 2025 and expect to complete by end of November 2025.

General availability (Worldwide): After further review, this has been delayed to a later date. We apologize for any inconvenience.

How this affects your organization

Users with access to the Microsoft Copilot dashboard will see new analytics cards and visualizations focused on Microsoft 365 Copilot Chat adoption for unlicensed users. These insights will appear in the dashboard’s adoption tab and include:

• Usage trends over time: Track active users and adoption growth.
• Adoption by group: Compare usage across departments or roles.
• Usage intensity and retention: Understand recurring usage and engagement levels.
• App-level breakdowns: Identify which apps and entry points drive adoption.
• Filtering and drilldown: Segment data by organizational attributes to tailor change management strategies.

This feature will be on by default for existing dashboard users. No additional administrator action is required to enable it.

What you can do to prepare

Review the impact of this feature on your organization’s reporting and privacy practices. You may also want to update internal training and documentation to reflect the new insights available.

Starting in September 2025:

• A new administrator control will be available for Global administrators, Viva Insights administrators, and AI administrators to turn off this feature at the tenant level. To disable this feature, use Viva Feature Access Management (VFAM) in Microsoft admin center or PowerShell.
• These same roles will also be able to exclude specific users or groups from being included in aggregated insights using the updated exclusion list feature.

Administrators should read the communication regarding the detailed scope and availability of this exclusion feature here (Roadmap ID: 500161).

Administrators should review any existing exclusions, assess their impact, and take appropriate action to exclude or include additional users or groups as needed.

Learn more:

• Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Viva Insights | Microsoft Viva | Microsoft Learn
• Control access to features in Microsoft 365 | Microsoft Viva | Microsoft Learn
• Copilot for all: Introducing Microsoft 365 Copilot Chat | Microsoft Blog
• Manage settings for the Microsoft Copilot Dashboard and Viva Insights web app | Viva Insights | Microsoft Viva | Microsoft Learn
• Microsoft 365 Copilot overview | Microsoft 365 Copilot | Microsoft 365 | Microsoft Learn

Compliance considerations

Updated September 24, 2025: We have updated the content. Thank you for your patience.

Introduction

We have identified that some tenants are using DLP rules in which alert generation has been enabled using the Microsoft Purview portal policy configuration page but the corresponding Alert Policy (Protection Alert) was disabled or deleted using “Set-ProtectionAlert” PowerShell cmdlet (Learn more). Due to this the alert generation gets turned off for the associated DLP rule – even though the alert it appears active on Purview portal policy configuration UX.

If you wish to continue receive alerts for these rules, please take one of the following actions:

• Open the rule in the Purview portal, make any update, and save the configuration.
• Use the PowerShell cmdlets to re-enable alert generation for the rule. (Learn more)

When this will happen

This change will begin rolling out on September 26, 2025.

How this affects your organization

To ensure consistency we will update the DLP rule to remove Generate Alert as an action. Since alerts were disabled using Protection Alert PowerShell cmdlets there will be no change in alert generation behavior for corresponding DLP rule and policy. We are only ensuring there is consistency between DLP rules (with Generate Alert as an action) and their corresponding Alert policies (protection alert)

What you can do to prepare:

If you wish to receive alerts for these rules, please take one of the following actions:

• Open the rule in the Purview portal, make any update, and save the configuration.
• Use the PowerShell cmdlet “Set-DlpComplianceRule” to re-enable alert generation for the rule. (Learn more).

Compliance considerations

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

Introduction

We’re introducing a new capability in Copilot in Word that allows users to view key document statistics directly within the Dynamic Document Snapshot. This enhancement helps users quickly understand document activity and ownership, improving transparency and collaboration.

When this will happen

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

How this affects your organization

Users will be able to access important document metadata—such as author, last modified date, and number of times opened—by selecting the Activity tab in the Copilot Dynamic Document Snapshot. This feature is designed to improve document awareness and collaboration by making insights easily accessible.
This feature will be on by default and requires no admin configuration.

What you can do to prepare:

No action is required. This update will roll out automatically as part of Copilot in Word.

Compliance considerations

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

Coming soon for Microsoft Teams Rooms Pro: The Teams Pro Management service and portal will be generally available. You will be able to use the remote device management and analytics features of the solution while meeting high security and privacy standards.

This message is associated with Microsoft 365 Roadmap ID 493323.

[When this will happen:]

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

[How this will affect your organization:]

After this rollout, you will be able to access the Pro Management Portal in your organization at https://devices.dod.teams.microsoft.us/

The new portal 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 your relevant documentation.

Please follow the set up process detailed in Enroll a Teams Room device into Pro Management – Microsoft Teams | Microsoft Learn

[Introduction:]

We’re updating Memory in Microsoft 365 Copilot to improve personalization and enhance the user experience. With this update, Copilot will personalize responses using chat history, helping users receive more relevant and contextual replies. We’re also introducing refreshed user controls in Copilot settings to make it easier to view and manage what Copilot remembers.

[When this will happen:]

• Targeted Release: Begins rolling out early October 2025 and expected to complete by mid-October 2025.
• General Availability: Begins mid-October 2025 and expected to complete by late October 2025.

[How this affects your organization:]

All users of Microsoft 365 Copilot in tenants where Memory is enabled.

What will happen:

• Copilot will use chat history to personalize responses, making interactions more tailored and helpful:

 

• Users will see a redesigned Memory settings page that improves visibility and control over what Copilot remembers.
• Existing admin and user-level Memory settings are respected. If Memory is toggled off, it will remain off.
• No changes to admin controls or policy enforcement.

[What you can do to prepare:]

• Review the updated Memory settings experience with your users once available.
• No admin action is required unless you wish to update internal documentation or training materials.

Learn more:

• Enhanced personalization control overview | Microsoft Graph | Microsoft Learn 
• enhancedPersonalizationSetting resource type | Microsoft Graph | Microsoft Learn

[Compliance considerations:]

[Introduction]

We’re introducing a major update to organizational data ingestion in Microsoft 365 that enhances flexibility, control, and destination support. This release includes attribute access and mapping, new connector availability, and a new admin role. It also expands ingestion support to Viva Insights and Viva Glint, helping organizations streamline data flows across Microsoft Viva experiences.

• Public Preview: Began in early September 2025; completed in mid-September 2025.
• General Availability (Worldwide): Begins late September 2025; completes by early October 2025.

Who is affected: Admins managing organizational data ingestion and Microsoft Viva scenarios.

What will happen:

• Microsoft 365 will support connectors with custom attribute ingestion, allowing organizations to choose automated workflows that best suit their needs and ingest data from multiple distinct sources in parallel.
• Attribute mapping and access controls will be enhanced to streamline the source-to-destination mapping process and enable selective sharing of attributes by app, helping protect sensitive and custom data.
• Ingestion support will be unified across Viva scenarios, with a single ingestion point now serving Viva Insights and Viva Glint, in addition to existing support for Profile, Viva Amplify, and Viva Engage.
• No new licenses are required to access the platform. However, a Viva Insights and Viva Glint license is required to access the extended features.

Screenshot 1 – Decide which Microsoft 365 and Viva applications will be able to use imported data:

Screenshot 2 – Map reserved attributes to your imported data:

Screenshot 3 – Choose access for custom attributes:

• Assign the new Organizational Data Source Admin role as needed.
• Review documentation for more information.
• Ensure your organization has the appropriate Viva Insights and Viva Glint licenses to access extended ingestion features.

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

[Introduction]

Cloud IntelliFrame, an AI-powered video enhancement feature for Microsoft Teams Rooms, is now available on Teams Rooms for Android with a Teams Rooms Pro license. This feature transforms the traditional wide-angle room view into a dynamic gallery of individual video tiles, improving visibility and engagement in hybrid meetings.

This message is associated with Microsoft 365 Roadmap ID 499614.

[When this will happen:]

• General Availability (Worldwide): Begins in mid-October 2025 and is expected to complete by late October 2025.

[How this affects your organization:]

Who is affected:

This change affects administrators who manage Microsoft Teams Rooms on Android devices that are licensed with Teams Rooms Pro.

What will happen:

• Cloud IntelliFrame will become available for Teams Rooms on Android.
• Administrators will be able to manage the feature through the Teams admin console. 
• The feature will not be enabled by default; administrators must turn it on manually.
• Existing admin policies will remain unchanged and are respected by this feature.

[What you can do to prepare:]

• Enable Cloud IntelliFrame in small to medium-sized meeting rooms where hybrid collaboration is common.
• Review the Teams admin console settings to ensure you can manage the feature as needed.
• Communicate the feature’s availability to your helpdesk or AV support teams to prepare for potential questions.
• Update your internal documentation if it includes details about Microsoft Teams Rooms features.

Learn more: Cloud IntelliFrame | Microsoft Teams | Microsoft Learn

[Compliance considerations:]

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

Introduction

We’re introducing a major upgrade to the AI video creator in Microsoft 365 Copilot. This next-generation experience makes it easier than ever to create professional-quality videos from a text prompt, PowerPoint, PDF, or Word document. Key enhancements include:

• Transcript-based editing
• Ability to replace stock media with your own from OneDrive
• Updated natural-sounding voice options
• Brand Kit integration for applying brand colors
• New scene structure for improved storytelling
• Redesigned editing interface for faster, more intuitive workflows

These updates enable smoother video creation, richer customization, and more professional outputs—helping your organization produce videos that look and sound like they were made by experts.

This message is associated with Microsoft 365 Roadmap ID 501560.

When this will happen

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

How this will affect your organization

What you can do to prepare

• No action is required at this time.
• No preparation required.

Learn more: Create a video with the Microsoft 365 Copilot app | Microsoft Support

Introduction:

We’re expanding model choice in Microsoft 365 Copilot Researcher and Microsoft Copilot Studio to include Anthropic models. You can read more about this announcement in our blog: Expanding model choice in Microsoft 365 Copilot.

This update gives organizations more flexibility to tailor AI experiences to their needs. Researcher can now be powered by either OpenAI’s deep reasoning models or Anthropic’s Claude Opus 4.1. Claude in Researcher is rolling out today via the Frontier Program to Microsoft 365 Copilot licensed customers who opt in. In Copilot Studio, Claude Opus 4.1 and Sonnet 4 models are now available as optional model options in addition to existing options from OpenAI. Makers with Microsoft Copilot Studio licenses who opt in can now experiment with creating custom agents using Claude. Claude models in Microsoft Copilot Studio are currently in preview and not intended for production use.

When this will happen:

• Rollout begins September 24, 2025. Admin opt-in required.
• Claude Opus 4.1 in Researcher is available today via the Frontier Program.
• Claude Opus 4.1 and Claude Sonnet 4 in Copilot Studio are in preview.

How this affects your organization:

Who is affected:

•  Admins managing Microsoft 365 Copilot, Researcher, and Microsoft Copilot Studio.
• Microsoft 365 Copilot licensed customers participating in the Frontier Program.

What will happen:

• Researcher can now use:
  • OpenAI deep reasoning models
  • Anthropic Claude Opus 4.1 (opt-in required)
• Microsoft Copilot Studio now supports:
  • Claude Opus 4.1 and Claude Sonnet 4 models (opt-in required; external preview)
  • Existing OpenAI models remain available
• Anthropic models are disabled by default until admins opt-in
• Admins must opt-in via: 
  • Microsoft admin center (MAC)
  • Once turned on in MAC, additional management controls for Microsoft Copilot Studio can be used in Power Platform admin center (PPAC)

Learn more about admin opt-in controls:

• Connect to Anthropic’s AI models | Microsoft Learn
• Allow external large language models (LLMs) for generative responses | Microsoft Learn

Additional documentation:

• Choose an external model as the primary AI model | Microsoft Learn

Important: Claude models are hosted by Anthropic outside Microsoft-managed environments. Data used with Claude is processed outside Microsoft’s compliance and audit boundaries. This means Microsoft’s Product Terms, Data Protection Addendum, data residency commitments, data processing commitments (EUDB) do not apply to use of Anthropic models. Instead, your use is governed by Anthropic’s Commercial Terms of Service and Data Processing Addendum. 

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

Coming soon to Microsoft Purview: Insider Risk Management (IRM) data including alerts, indicators and events will be available in these Microsoft Defender XDR experiences:

• Unified alert queue: IRM alerts will appear in the unified alert and incident queue in Defender XDR for comprehensive investigation and correlation.
• Advanced Hunting: IRM data will be available for advanced hunting in Defender XDR, allowing analysts to identify hidden risk patterns using KQL queries. Analytics can also create custom detections on the top of IRM data.
• Graph API: IRM data will be accessible through the Microsoft Graph API, supporting bidirectional integrations with external applications.
• Microsoft Sentinel: IRM alerts will be available in Microsoft Sentinel through the XDR-Sentinel connector, providing richer metadata.

This message is associated with Microsoft 365 Roadmap ID 422730.

[When this will happen:]

Public Preview: We will begin rolling out mid-January 2025 and expect to complete by end of January 2025.

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

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

[How this will affect your organization:]

Enable this feature by turning on Share data with other security solutions in the IRM global settings.

Only users with Insider risk analysis or investigation roles in the Microsoft Purview portal can access IRM data in Defender XDR.

To access alerts, incidents, and events from Defender XDR via API, you need to provision apps with the necessary permissions. IRM data is accessible via Microsoft Security Graph APIs, allowing for reading and updating alert or incident statuses. Permissions are set at the application level, without solution-specific scoping. Any existing apps pulling data from these APIs will also access IRM data. So, if you integrate XDR alerts into external ticketing systems, IRM alerts will show up, unless you specifically filter out the alerts.

IRM alerts will appear in Sentinel if your tenant has the Defender XDR connector enabled in Microsoft Sentinel.

In Defender XDR, IRM data is not pseudonymized to allow effective correlation of IRM alerts with alerts from other solutions within the platform, such as Defender for Endpoint and Defender for Cloud apps.

These changes will be available by default for admins to configure in IRM global settings.

Admins will be able to view Insider Risk Management alerts in Defender XDR:

Harness the power of Advanced Hunting queries with two new tables that contain Insider Risk Management data: DataSecurityBehaviors and DataSecurityEvents. In this query, 54 confidential files were exfiltrated through mail.google.com by 2 unique users:

[What you need to do to prepare:]

• Opt-in to data sharing settings in IRM global settings page.
• Assign necessary permissions to analysts
• Review existing apps accessing Defender XDR data through Graph APIs.
• If your organization is using Microsoft Defender XDR connector, please review the list of users who will gain access to this data through Sentinel.

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