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

Introduction

Microsoft Teams now enables users to report messages they believe were incorrectly flagged as security threats in chats and channels. This capability is available to organizations with Microsoft Defender for Office 365 Plan 2 or Microsoft Defender XDR. It empowers users to provide feedback on false positives, helping improve detection accuracy and strengthen organizational security.

This feature will be available across Microsoft Teams on Android, Desktop (Windows), iOS, Mac, and Web platforms, ensuring broad accessibility for users regardless of device.

This feature is associated with Microsoft 365 Roadmap ID 501202.

When this will happen

Targeted Release (Worldwide): Begins in early September 2025; expected completion by mid-September 2025.

General Availability (Worldwide): Begins in early November 2025; expected completion by mid-November 2025.

How this affects your organization

Users will be able to report messages they believe contain URLs that were incorrectly flagged as malicious:

• During Targeted Release, the feature is off by default in Teams.
• At General Availability, the feature will be on by default in Teams. Admin settings saved during Targeted Release will remain unchanged.
• In the Microsoft Defender portal, the setting is on by default for new tenants. Existing tenants must enable it manually.

What you can do to prepare

To enable this feature and ensure reported messages appear in the User reported tab in Submissions:

• In the Teams admin center, go to Messaging settings > Messaging safety and turn on Report incorrect security detections.



• In the Microsoft Defender portal, ensure the corresponding setting is enabled.

  

Both settings must be turned on for full functionality.

Learn more: [Updated documentation to be made available on Microsoft Learn in the second week of September 2025.]

Compliance considerations

• Modern app header — This new header simplifies the layout with improved spacing and modernized icons.
• Streamlined sitemap — This new sitemap has an improved structure, which removes clutter and improves readability.
• Condensed page headers — These new headers for the form and grid pages now take up less vertical space, allowing for more data to be displayed.

1. From the app designer, select Settings from the command bar.
2. Select Features, then locate and enable the Header and navigation refresh setting.

[Introduction]

We’re excited to announce performance and usability improvements to the DLP Alerts Page in Microsoft Purview Portal to help you triage incidents faster and more efficiently.

🚀 What’s New: 

• Unified View: Events related to each alert are now available directly on the alerts page — no need to switch to new tab or drill down. 
• Faster Access: Access event details (e.g. Impacted assets) with just one click on the main alerts page itself, compared to four clicks earlier, reducing triage time significantly. 
• Enhanced Context: We’ve added four new columns – Location, DLP policy name, DLP rule name, and Rule action to display key alert and event attributes upfront — giving you more visibility at a glance. 
• Performance Boost: Cache improvements to ensure faster load times and a smoother experience. 

These updates are designed to streamline your workflow, reduce response times, and give you the context you need — all in a single, efficient view. 

This message is associated with Microsoft 365 Roadmap ID 501787.

[When this will happen:]

• Public Preview: We will begin rolling out late September 2025 and expect to complete by early October 2025.
• General Availability (Worldwide): We will begin rolling out late October 2025 and expect to complete by early November 2025.

[How this will affect your organization:]

Alerts will be loaded in collapsed state. Expand an alert to view the list of associated events (screenshots 1 and 2):

To access event details, select the event to open the right-side pane (screenshot 3):

To access the four new columns- Location, DLP policy name, DLP rule name, and Rule action, click on Customize columns and add the new columns (screenshot 4):

To update alert status, use the Update alert status button in the event details side pane (screenshot 5):

To access the alert details in a new tab, click on Open alerts page:

Note: Up to 50 events per alert will be visible/accessible in the alerts list page. To view more than 50 events, open the alert in a new tab.

[What you need to do to prepare:]

No preparation is required from the admin’s side. Change will be rolled out automatically.

[Compliance considerations:]

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

[Introduction]

We’re introducing a new admin toggle in Viva Engage that allows Engage and network admins to control who can use the Move conversation feature across communities. This update supports organizations that want to limit this capability to specific roles, helping reduce unintended content movement.

This message is associated with Roadmap ID 501458.

[When this will happen:]
General Availability (Worldwide): Rollout will begin in early October 2025 and is expected to complete by late October 2025.

[How this affects your organization:]

Who is affected:

• Viva Engage network admins and Engage admins
• Corporate communicators, community admins, and community experts
• All users with access to conversations in Viva Engage

What will happen:

• A new toggle will be available to control access to the Move conversation feature.
• By default, the toggle is ON, meaning all users with access to a conversation can move it (current behavior).
• When the toggle is OFF, only the following roles can move conversations:
  • Engage admins
  • Network admins
  • Corporate communicators
  • Community admins
  • Community experts
• No changes will occur unless the toggle is manually turned OFF.

[What you can do to prepare:]
No admin action is required unless you want to restrict the Move conversation feature. If so:

• Review the new toggle setting in the Viva Engage admin center once available.
• If desired, turn the toggle OFF to limit the move capability to permissioned roles.
• Communicate this change to your helpdesk or internal support teams.
• Update internal documentation if you reference this feature.

[Compliance considerations:]
No compliance considerations identified, review as appropriate for your organization.

[Introduction]

We’re introducing User-Based Alert Aggregation in Microsoft Purview Data Loss Prevention (DLP) to help security teams triage alerts more efficiently. This feature consolidates DLP rule match events by user identity within a defined time window, enabling faster investigation and remediation of potential insider threats.

This message is associated with Roadmap ID 501786.

[When this will happen:]

Public Preview: We will begin rolling out late September 2025 and expect to complete by early October 2025.

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

[How this affects your organization:]

Who is affected: Admins managing DLP policies in Microsoft Purview compliance portal.

What will happen:

• This feature is opt-in and can be enabled via the Microsoft Purview compliance portal.
• Navigate to Settings > Data Loss Prevention > User-Based Alert Aggregation.
• Toggle on User-Based Aggregation and select an aggregation time window (minimum 15 minutes).

• DLP rule match events for the same user and rule within the selected window will be grouped into a single alert.
• Alerts will be created per user and per rule. For example, if User A and User B violate the same rule within 15 minutes, two separate alerts will be generated.
• Alert volume may increase due to per-user aggregation.
• Events will continue to be added to an alert even if it is marked resolved or closed, as long as the aggregation window is active.

[What you can do to prepare:]

• No preparation is required unless you choose to enable the feature.
• To opt in:
  • Go to Microsoft Purview compliance portal.
  • Navigate to Settings > Data Loss Prevention > User-Based Alert Aggregation.
  • Toggle on the feature and select your preferred aggregation time window.
  • Review internal documentation and communicate the change to your security operations team.

[Compliance considerations:]

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

[Introduction]

To improve support experiences, we’re expanding the Get diagnostics feature—currently available in the new Outlook for Windows—to Outlook for Web. This allows users to securely send diagnostic data to Microsoft Support directly from the Help tab, streamlining issue resolution.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

Users of Outlook for Web and admins managing support scenarios in Microsoft 365.

What will happen:

• A new option will appear under the Help tab in Outlook for Web to send diagnostics to Microsoft Support.
• While managing a support ticket, Microsoft Support may instruct a user to submit diagnostics using this option and provide the resulting support ID.
• Diagnostic data is stored in Microsoft’s support ticketing system and accessed by support agents and engineers for troubleshooting.
• Admins can manage this feature using the cloud policy: Configure Get Diagnostics feature’s visibility in the Help Ribbon in Office applications.
• The feature is enabled by default unless disabled via policy.

[What you can do to prepare:]

No action is required unless you wish to disable or manage the feature.

To disable or configure the feature:

• Use cloud policy to disable or configure the feature’s visibility and behavior.

To prepare your organization:

• Communicate this change to helpdesk staff.
• Update internal documentation if you reference support workflows in Outlook for Web.

Learn more: Contact support and provide feedback in new Outlook for Windows (will be updated before rollout)

Compliance considerations

[Introduction:]

We’re introducing a new Library experience in the Microsoft 365 Copilot app. Library provides a central, visual-first destination in the Microsoft 365 Copilot app where users can easily access their Copilot-generated content like images and Pages and as Copilot-generated content shared with them. This experience helps users easily find and manage their Copilot-generated content in one place, streamlining productivity and reducing content fragmentation.

• Targeted Release (Worldwide): Rollout begins in late September 2025 and is expected to complete by late September 2025.
• General Availability (Worldwide): Rollout begins in late September 2025 and is expected to complete by late September 2025.

Who is affected:

• All users with Copilot chat enabled in Microsoft 365.

What will happen:

• A new Library section will appear in the Microsoft 365 Copilot app, in the left navigation menu.
• Library will consolidate Copilot-generated images (from Copilot Chat and Create experiences) and Copilot Pages into a single, unified view.
• The Pages section will be removed from the left navigation menu in the Microsoft 365 Copilot app. Users can find their existing Pages in the new Library section instead. There is no change to the experience to create a new Page via Copilot Chat.
• Library is on by default for users with Copilot chat enabled.
• If Copilot chat is disabled by the admin, the Library will not be available.
• No changes to existing admin policies or configurations.

• No admin action is required.
• There are no new controls or configuration steps associated with this change.
• Review the following documentation for more details: Copilot pages for IT Admins – Sep 2024 update 

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

Introduction

We’re introducing Microsoft Graph APIs for tenants with Standard eDiscovery licenses, enabling automation and integration of eDiscovery workflows. These APIs support case management, search, hold, and export operations, offering a secure and consistent experience aligned with the Purview portal.

This message is associated with Microsoft 365 Roadmap ID 500869.

When this will happen

• Public Preview: Rolling out early September 2025; expected completion by mid-September 2025.
• General Availability (Worldwide): Rolling out early November 2025; expected completion by mid-November 2025.

How this affects your organization

If your organization uses a Standard eDiscovery license, you can now automate eDiscovery workflows using Graph APIs. These APIs replicate the portal experience and include:

• Case management: Create, Get, List, Update, Close, Reopen, Delete
• Search management: Create, List, Get, Update, Delete, Estimate Statistics
• Hold management: List, Create, Get, Update, Delete
• Data source management: Add, List
• Export: Export results, Export report only

What you can do to prepare

Subscribe to Purview pay-as-you-go billing to enable API usage.

Learn more:

• Use the Microsoft Purview eDiscovery API in Microsoft Graph (beta)
• Billing in eDiscovery | Microsoft Learn

Compliance considerations

Compliance Area	Explanation
New customer data storage	Exported data via API may be stored in downstream systems integrated by the customer. Microsoft does not cache or store this data beyond the export operation.
Changes to existing data processing	Enables automated access and export of eDiscovery data, which may alter how customer data is accessed and transferred.
Modifies eDiscovery or Content Search	Introduces API-based access to eDiscovery case, search, and export operations, expanding automation capabilities.
Admin compliance monitoring/reporting	Admins can now monitor and report on eDiscovery activities via Graph API, enhancing audit and compliance workflows.
Integration with 3rd party software	APIs are designed for integration with downstream systems, allowing third-party tools to interact with eDiscovery data.
Admin control via Entra ID	Access to APIs can be scoped using Entra ID group membership and role-based access control.

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

In new Outlook for Windows and web, when single-clicking on an empty time slot on the calendar surface, the quick compose pop-up will no longer appear. Instead, you will be able to create an appointment by typing directly in the time slot on the calendar grid, just as you can in classic Outlook for Windows. There will be no change to double-click behavior; the full compose form will still open as it does today.

This message is associated with Microsoft 365 Roadmap ID 406948.

[When this will happen:]

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

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

[How this will affect your organization:]

This may affect how users create appointments quickly on the calendar surface. We expect this to be a better experience, especially for those familiar with classic Outlook inline appointment creation.

This update is available by default.

[What you need to do to prepare:]

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

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

Coming soon for Microsoft Purview | Data Lifecycle Management: Admins will be able to apply a retention policy or retention label in Microsoft OneDrive and Microsoft SharePoint for files that have not been accessed by anyone in your organization for a specified period of time. This message applies to retention for Microsoft 365 file types. We will support other file types (non-Microsoft 365) in a future rollout.

This message is associated with Microsoft 365 Roadmap ID 472030.

[When this will happen:]

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

General Availability (Worldwide): We will begin rolling out mid-January 2026 and expect to complete by late January 2026

[How this will affect your organization:]

This feature will help delete obsolete data, which will improve the quality and relevance of Microsoft 365 Copilot responses.

This feature will be available by default.

After the rollout, admins can use the retention control When items were last accessed when configuring labels and policies.

Retention settings page in Purview with the new “last accessed” option for retention policies:

[What you need to do to prepare:]

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

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

Introduction

We’re introducing the Content Management Assessment (CMA) in SharePoint Advanced Management to help tenant admins evaluate site health, permissions, and lifecycle readiness—all in a single, actionable dashboard. CMA consolidates multiple reports, including Site Lifecycle Management (SLM) and Data Access Governance (DAG), and provides tailored recommendations to strengthen governance and accelerate Copilot onboarding.

This message is associated with Roadmap ID 501427.

When this will happen

General Availability (Worldwide): Rollout begins early September 2025 and is expected to complete by early October 2025.

How this affects your organization

CMA is off by default and must be initiated by an admin. Once launched from the Advanced Management tab in the SharePoint Admin Center, CMA automatically generates reports such as SLM and DAG and presents results in a clean, actionable dashboard.

This update helps you:

• Save time by automating previously manual governance tasks.
• Strengthen site governance with insights into oversharing, inactive content, and permission risks.
• Prepare sites for Copilot by surfacing key lifecycle and access issues.
• Align admin teams with a standardized view of governance priorities.

Improvements include a more accessible UI, refined issue categories and tooltips, and easier navigation across reports.

What you can do to prepare

To use the Content Management Assessment (CMA), you must have either a SharePoint Advanced Management license or a Microsoft 365 Copilot license assigned to your admin account.

To get started:

• Go to the SharePoint Admin Center.
• Select the Advanced Management tab.
• Choose Start a free content assessment.
• Review the dashboard and explore tailored recommendations.
• Share feedback to help shape future improvements.

Introduction

Microsoft Teams is introducing enhanced protection against phishing attacks by detecting and warning users about malicious URLs shared in Teams chats and channels. This feature helps users make safer decisions before clicking potentially harmful links. 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 Roadmap ID 499893.

When this will happen

• Targeted Release (Worldwide): Rollout begins early September 2025 and is expected to complete by mid-September 2025.
• General Availability (Worldwide): Rollout begins early November 2025 and is expected to complete by mid-November 2025.

How this affects your organization

When a malicious link is detected, Teams will automatically display a warning to both the sender and recipient. This helps reduce the risk of phishing attacks.

• Targeted Release: Link protection is applied only when all participants in the conversation have the feature enabled.
• General Availability: Link protection is enforced if at least one participant in the conversation has the feature enabled.

Targeted release vs. General Availability behavior:

• Targeted release: Link protection is applied only when all organizations in the conversation have the feature enabled. This feature is off by default and requires admin activation.
• General Availability: Link protection is applied if at least one participant has the feature enabled. This feature is on by default. Admin settings saved during Targeted Release will remain unchanged. 

What you can do to prepare

During Public Preview, administrators must manually enable the feature:

1. Go to the Teams Admin Center
2. Navigate to Messaging Settings
3. Enable the setting: Scan messages for unsafe URLs

This setting is also available via Set-CsTeamsMessagingConfiguration PowerShell cmdlet –UrlReputationCheck parameter.

No action is required once the feature reaches General Availability, as it will be turned on by default.

Learn more: Weaponizable File Protection in Microsoft Teams

Compliance considerations

Introduction

Microsoft Teams is introducing a new protection feature that blocks messages containing weaponizable file types—such as executables—in chats and channels. This helps reduce the risk of malware and file-based attacks by preventing unsafe content from being shared. 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 Roadmap ID 499892.

When this will happen

• Targeted release (Worldwide): Starts early September 2025; expected to complete by mid-September 2025.
• General Availability (Worldwide): Starts early November 2025; expected to complete by mid-November 2025.

How this affects your organization

Once enabled, Teams will automatically block messages that include weaponizable file types. This applies to both internal and external conversations.

• Recipients will see a notification that a message was blocked but cannot access the content.
• Senders will receive a notification and can edit and resend the message without the unsafe file.

Targeted release vs. General Availability behavior:

• Targeted release: Protection is enforced only when all organizations in the conversation have the feature enabled. This feature is off by default and requires admin activation.
• General Availability: Protection is enforced if at least one participant has the feature enabled. This feature is on by default. Admin settings saved during Targeted Release will remain unchanged.

What you can do to prepare

Admins can enable this protection in the Teams Admin Center:

1. Go to the Teams Admin Center
2. Navigate to Messaging Settings
3. Turn on the setting: Scan messages for file types that are not allowed

Alternatively, use PowerShell with the -FileTypeCheck parameter.

Once enabled, all users in your tenant will begin seeing file protection applied in their messages.

Blocked file types include:

ace, ani, apk, app, appx, arj, bat, cab, cmd, com, deb, dex, dll, docm, elf, exe, hta, img, iso, jar, jnlp, kext, lha, lib, library, lnk, lzh, macho, msc, msi, msix, msp, mst, pif, ppa, ppam, reg, rev, scf, scr, sct, sys, uif, vb, vbe, vbs, vxd, wsc, wsf, wsh, xll, xz, z

Learn more: 

• Overview of security and compliance – Microsoft Teams | Microsoft Learn (will be updated before rollout)
• Malicious URL Protection in Microsoft Teams

Compliance considerations

Introduction

To enhance visibility of in-room participants during Microsoft Teams meetings, we’re updating the Gallery view experience when Teams Rooms on Android joins a meeting. Teams Rooms on Android video tiles will now dynamically resize based on the number of people detected in the room, aligning with the experience already available in Teams Rooms on Windows.

This message is associated with Roadmap ID 500635.

General Availability (Worldwide): Rollout begins early October 2025 and is expected to complete by late October 2025.

• If only one person is present in the room, the room video tile will be the same size as other remote participant tiles.
• If multiple people are present, the room video tile will remain optimized at approximately 4x the size of a remote participant tile.

Figure i. Conference Room Ruby has more than 1 person in the room, therefore, the room video tile is optimized. While, Conference Room Emerald has 1 person in the room, and the room video tile is the same size as other remote participants.

• This feature is enabled by default and requires a room camera capable of sending people count data.
• If people count is turned off in Teams Rooms on Android admin settings, the room video tile will not dynamically resize, and will not provide people count information.

• Inform users about the updated Gallery view experience.
• Update training materials and documentation as needed.
• Review and adjust Teams Rooms on Android admin settings if you wish to disable people count detection.

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

• Public Preview: Rollout begins late September 2025 and completes by early October 2025.  
• General Availability: Rollout begins late September 2025 and completes by early October 2025.

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.

Compliance considerations

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

To help you manage agent adoption for Microsoft 365 Copilot Chat, we are introducing a new usage report in the Microsoft 365 admin center. The report provides visibility into how users in your organization are actively using agents in Microsoft 365 Copilot Chat and includes metrics such as: 

• Total number of active agent users and active agents 
• Usage breakdown per user, per agent, and per user-agent pair 
• Segmentation by license state (licensed vs. unlicensed Microsoft 365 Copilot users) 
• Segmentation by agent creator type (i.e. agents built by your organization, Microsoft, or Microsoft partners) 

The new report is rolling out in preview and will be available under Reporting > Usage > Microsoft 365 Copilot > Agent. During the preview stage, the report will display a maximum of 30 days of history. In addition, usage information from prior to August 19 2025 will not be available in the report. This report only includes declarative agents. Usage data for SharePoint agents and Custom engine agents will be available in a future update.

This message is associated with Microsoft 365 Roadmap ID 497999

[When this will happen:]

Public Preview (Worldwide): Available now.

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

[How this will affect your organization:]

[What you need to do to prepare:]

With this update, Teams Rooms on Windows now support simultaneous presenter and attendee experiences for Teams Town halls and Webinars held in the same physical room. This enhancement ensures that in-room attendees see the standard attendee view on the front-of-room display, while presenters retain full control via the room console—creating a seamless and distraction-free experience. This feature is available exclusively in Teams Rooms Pro.

Microsoft 365 Roadmap ID: 496368

• General Availability (Worldwide and GCC): Rollout begins early October 2025 and completes by late October 2025.
• General Availability (GCC High): Rollout begins late October 2025 and completes by late October 2025.
• General Availability (DoD): Rollout begins late November 2025 and completes by late November 2025.

This update enables organizations to host Teams Town halls and Webinars in a Teams Room on Windows with both presenters and attendees physically present in the same room.

• Attendee Experience: The front-of-room display defaults to attendee view, hiding backstage elements such as the green room, backroom chat, and off-stage presenters.
• Presenter Experience: In-room presenters retain full access to presenter controls via the room console, allowing them to manage the event without disrupting the audience experience.

This feature is on by default for Teams Rooms Pro environments.

• Review and update any internal documentation or training materials related to hosting Teams Town halls and Webinars in Teams Rooms.
• Ensure that Teams Rooms are invited as presenters to enable the correct experience.

[Compliance considerations:]

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

• Store the files in a code repository.
• Automate generation of a canvas app.
• Improve the generative canvas app models.
• Refactor canvas apps without using the designer.
• Integrate natively with Git for Power Platform.