Microsoft Roadmap, messagecenter and blogs updates from 14-11-2025

Updated November 12, 2025: We have completed rollout of this feature. Thank you!

Coming soon: You will be able to extend Microsoft Purview to the network layer by integrating Purview with your preferred Secure Access Service Edge (SASE) / Security Service Edge (SSE) solution. Through this integration, admins can intercept and inspect traffic flowing through the network layer to identify the presence of sensitive data. This enables admins to detect sensitive data shared with untrusted cloud applications through browsers, applications, APIs, add-ins, and more, including common generative AI, cloud storage, and content sharing services. The signals from inline discovery for the network further enrich Purview solutions including Data Security Posture Management (DSPM) and Insider Risk Management (IRM), helping admins better understand how to reduce data exfiltration risks to locations outside of their organization. Learn more: Building layered protection: New Microsoft Purview data security controls for the browser & network | Microsoft Community Hub (March 24, 2025).

This message is associated with Microsoft 365 Roadmap ID 488807.

[When this will happen:]

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

General Availability (Worldwide): Now available.

[How this will affect your organization:]

After this rollout, using the new collection policies option in Purview under Classifiers, you will be able to create granular policies to detect sensitive data that’s being sent to 34,000+ unmanaged cloud applications by defining what sensitive information types you want to detect and for who. These policies are designed to discover relevant signals from data in transit without executing any enforcement actions on that data.

After integrating with one of our already-integrated Secure Access Service Edge (SASE) / Security Service Edge (SSE) partners, data security admins will be able to centrally create and manage policies for the network from the Purview portal.

[What you need to do to prepare:]

After rollout, the new policies and features will be available by default for you to enable and configure. These integrations require action by your Purview Data Security and Compliance admins to enable discovery in your organization before any signals will start to be collected, including configuring a SASE/SSE integration and creating a collection policy that targets unmanaged cloud apps.

Also, your global admin will need to activate Purview pay-as-you-go meters to enable this capability. We will update this message in May 2025 with pricing details.

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.

Updated November 12, 2025: We have updated the timeline. Thank you for your patience.

We’re improving the quarantine experience in Microsoft Defender for Office 365 to deliver greater clarity, visibility, and ease of use for administrators. These updates include backend enhancements for improved durability and consistency as well as experience updates to list messages in quarantine by individual recipients to simplify navigation and management.

• General Availability (Worldwide and GCC): We will begin rolling out in early January 2026 (previously early November 2025) and expect to complete by end of February 2026 (previously mid-December 2025).
• General Availability (GCCH and DoD): We will begin rolling out in early January 2026 (previously early December 2025) and expect to complete by end of February 2026 (previously early January 2026).

• Who is affected: Administrators managing quarantined messages in Microsoft Defender for Office 365.
• What will happen:
  • Quarantined messages will now be listed by individual recipient instead of grouped by multiple recipients.
  • Backend enhancements will improve durability and consistency.
  • Existing quarantine release cmdlets will all remain functional. Administrators should be cognizant that `ReleaseToAll` now applies to a single user as aggregation has been removed. Admins must release messages for each intended mailbox individually.
  • No changes to end-user experience.

Screenshot 1 – Updated quarantine view showing individual recipients listed separately in the Recipient column:

Screenshot 2 – Existing quarantine view showing multiple recipients in the Recipient column:

What you can do to prepare:

• Review your organization’s quarantine release practices.
• Update any internal documentation to reflect the new recipient-level view.
• Communicate this change to helpdesk or support teams as needed.
• Learn more: 
  • Microsoft Defender for Office 365 overview | Microsoft Learn
  • Manage quarantined messages and files as an admin | Microsoft Defender for Office 365 | Microsoft Learn

Compliance considerations:

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

Updated November 12, 2025: We have updated the timeline. Thank you for your patience. 

We’re updating how we bill for mid-term subscription changes to improve clarity and efficiency.

[What’s changing:]

Starting November 18, 2025 changes to existing subscriptions—such as adding or removing licenses, cancellations, and upgrades—will be billed the next day instead of at the beginning of the following month. This change ensures more timely and transparent billing, helping you better track and manage your subscription costs. 

[When this will happen:]

When you see this change will depend on the country/region your account is in. 

• Singapore and Italy: November 18 (previously November 13) 
• Asia-Pacific: November 24 (previously Nov 18) 
• Worldwide: Jan 6th

[How this will affect your organization:]

If you have an account where your invoices start with a “G” and have purchased directly from Microsoft, your organization will be impacted by this change on the date the change is launched in your region. Purchases made through a partner or a volume licensing agreement are not impacted by this change.

Example

If your account is in Singapore or Italy and you add a license to your subscription on November 18, you will receive an invoice for that additional license on November 19. Any consumption charges for Azure will continue to be billed on the monthly invoice available at the beginning of the following month. 

Additional details about this change 

During the month your region transitions: 

• If you make no changes after the transition, previous changes remain on their original invoice schedule. 
• If you make changes after the transition, any pending charges from before the transition are invoiced immediately. You’ll also receive a separate invoice for the new changes.

[What you need to do to prepare:]

No action is required. This update will be applied automatically to all eligible subscriptions. 

Updated November 12, 2025: We have added documentation links. Thank you for your patience.

Agents in OneDrive lets you group files and folders together, so you can ask questions, get summaries, and find key details across your project—without having to reselect items each time. Agents are saved in your OneDrive and can be shared with your team, making collaboration and staying up to date easier. This new capability helps users work more efficiently by turning OneDrive into a workspace for AI-powered project assistance.

This message is associated with Microsoft 365 Roadmap ID 469503.

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

Who is affected: Users with a Microsoft 365 Copilot license assigned to either work or school accounts (Microsoft 365 commercial or education tenants). 

What will happen:

Users will see a new agent option in OneDrive.

How to use Agents in OneDrive:

• Create your Agent: When users first select the Copilot button in OneDrive or the +Create or upload button, a guided experience will introduce agents and walk users through how to create and use them. From there, users can create an agent from their OneDrive using the +Create or upload option and then select the Agent option (screenshot 1):

 

• Alternatively, users can select the files to include in an agent, then choose Create an agent from the Copilot toolbar dropdown menu (screenshot 2):

 

• Access your agent as a file in OneDrive (.agent extension), filter by file type “agent” (screenshot 3):

 

• Open the agent to ask questions and get answers from your documents.
• Edit or update your agent anytime to change its sources, name, or instructions (screenshot 4):

 

• Share your agent with your team to collaborate and keep everyone informed (screenshots 5 & 6):

 

No admin action is required at this time.

You may wish to:

• Communicate this change to helpdesk staff.
• Update internal documentation to reflect the new agent capabilities in OneDrive.
• Encourage users to explore agents to improve project efficiency using AI.
• Review documentation at the following links:
  • Get started with OneDrive agents
  • Create and use an agent in OneDrive
  • Find your agent files in OneDrive
  • Share an AI agent in OneDrive

Updated November 12, 2025: We have updated the content. Thank you for your patience.

[Introduction]

To help organizations adopt Microsoft 365 Copilot securely, Microsoft Purview is introducing new capabilities in Microsoft Admin Center. These enhancements allow AI and IT admins to gain visibility into oversharing risks, remediate issues, and apply a new Data Loss Prevention (DLP) policy directly within Microsoft Admin Center. This update supports secure usage of Copilot by enabling protection of sensitive interactions.

This message is associated with Microsoft 365 Roadmap ID 523212.

[When this will happen:]

• Public Preview: We will begin rolling out mid-November 2025 and expect to complete by late November 2025.
• General Availability (Worldwide): We will begin rolling out mid-January 2026 and expect to complete by late January 2026.

[How this affects your organization:]

• Who is affected: Admins managing Microsoft 365 Copilot and data security policies via Microsoft Admin Center or Purview portal.
• What will happen:
  • A new Security pivot will be added to the Microsoft Admin Center.
  • By default, a Purview data loss prevention policy for Copilot will be available in simulation mode. Admins can configure this policy and enable it to block specific sensitive information types from being used in Copilot. You can learn more in Message Center Post 1181998.
  • Visibility into oversharing risks and sensitive Copilot interactions will be available.

[What you can do to prepare:]

• Review how Copilot is secure by default and assess if additional protections are needed.
• Once the feature is released:
  • Use an Entra AI Admin or Entra Global Admin role to create a policy to block sensitive information types in Microsoft Admin Center.
  • Collaborate with your data security admin to apply additional protections and ensure compliance with AI regulations.
  • These actions can also be performed in the Purview portal. Learn more: Use Microsoft Purview to manage data security & compliance for Microsoft 365 Copilot & Microsoft 365 Copilot Chat.

[Compliance considerations:]

Updated November 13, 2025: We have updated the timing of this change below. Thank you for your patience.

On February 13, 2026, you may encounter issues if you haven’t updated your analytic rules, automation rules/playbooks, workbooks, hunting queries, or custom integrations to be precedence-aware for account entity naming. We’ve standardized the account entity naming logic in Microsoft Sentinel incidents and alerts, where the account entity naming priority is: UPN prefix → name → display name. Please update your queries and automations to use the new precedence pattern.

You are receiving this message because our reporting indicates your organization may be using Microsoft Sentinel incidents, alerts (AlertV3), or related automation.

[When this will happen:]

February 13, 2026 (previously December 13, 2025)

[How this will affect your organization:]

If you don’t fix this problem, these queries, automations, dashboards, and reports that reference account names may be affected:

• Analytics (KQL) that filter by, join on, or normalize account names
• Automation rules & playbooks (e.g., Logic Apps) that map Account.Name or compare it to other identity fields
• Workbooks & dashboards that show account name or aggregate by that value
• Hunting queries that coalesce or parse account identity fields
• Any users or systems relying on display name as the account identifier

[What you need to do to prepare:]

To fix this problem you need to update your KQL queries and automation logic to use the new precedence-aware pattern for account entity naming. Specifically, use a coalesce pattern (e.g., coalesce(Name, DisplayName)) wherever you reference the account name, and validate your workbooks, dashboards, and playbooks against the new logic. Test changes in a nonproduction workspace before rollout.

[Introduction]

Starting December 12, 2025, Copilot in Microsoft OneNote for Windows desktop will improve the experience for on-canvas Copilot features. Instead of opening a separate window or inserting content directly on the OneNote canvas, features such as Take Notes with Copilot, Summarize Page, Create a Task List, and Rewrite Page will now open in the Copilot Chat pane. This update enables the latest Copilot Chat capabilities for these features, providing a more consistent and integrated experience.

Previous experience:

New experience:

Rollout begins December 12, 2025 and will apply to all versions of OneNote for Windows desktop.

• Who is affected:
  • All users of the Microsoft OneNote Windows desktop application.
• What will happen:
  • On-canvas Copilot features will open in the Copilot Chat pane instead of a separate window or inserting content directly on the canvas.
  • Users will no longer be able to explicitly refer to “this section” or “this notebook” in prompts.
  • Enterprise grounding remains unchanged.
  • The update will be applied automatically; no admin or user action is required.

• No action is required for this change to take effect.
• If needed, communicate this update to helpdesk staff and update internal documentation.
• For additional support, use Help > Support in OneNote for Windows or contact your Microsoft support team.

No compliance considerations identified, review as appropriate for your organization

[Introduction]

Researcher and Analyst are part of the core default experience for M365 Copilot Chat and will now continue to be available to all users with a Copilot license—even when the ability to use Copilot agents is disabled for some or all users in the organization. This change reflects customer feedback and ensures uninterrupted access to foundational productivity tools.

Screenshot 1: Agents Settings for who can access agents in the organization

[When this will happen:]

General Availability begins December 15, 2025.

[How this affects your organization:]

• Who is affected: IT Admins that manage Copilot agent access in M365 Copilot Chat and M365 Copilot licensed users.
• What will happen:
• Researcher and Analyst will remain accessible in M365 Copilot Chat via tools and @mention, even when Copilot agents are disabled in Agents Settings for some or all users.
• When No users or Specific users/groups is selected in Agents Settings, Researcher and Analyst will not appear in the left navigation of M365 Copilot Chat for those users.
• Existing admin controls to block Researcher and Analyst will continue to function as expected as set by the admin in the Agent inventory.

Screenshot 2: Agent inventory

[What you can do to prepare:]

• Review who can access Copilot agents in your organization before December 15, 2025.
• Communicate this change to helpdesk and support teams to reduce confusion.
• Update internal documentation if you reference agent visibility or access controls.
• Refer to updated admin guidance here: Manage Microsoft 365 Copilot Agents – Microsoft 365 admin | Microsoft Learn

[Compliance considerations:]

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

Introduction

We’re enhancing the macOS file management experience by integrating Microsoft 365 Copilot directly into Finder. This update allows users to interact with Copilot to ask questions about their OneDrive files, streamlining productivity and making file insights more accessible.

Note: This update applies to OneDrive on macOS. Copilot integration in Finder requires a Microsoft 365 Personal or Family subscription, or a work or school account with a Microsoft 365 Copilot license. The rollout is gradual, so availability and functionality may vary by user and region.

When this will happen

• General Availability (Worldwide, GCC, GCC High, DoD): Rollout will begin in mid-November 2025 and is expected to complete by late December 2025.

How this affects your organization

• Who is affected: All users of OneDrive on macOS with Copilot licensing.
• What will happen:
  • Users can right-click a OneDrive file in Finder, open the “OneDrive context menu”, and select Ask Copilot to query file contents:

   

  • This feature is enabled by default.
  • No admin configuration is required.
  • Available in all Microsoft 365 environments.

What you can do to prepare

• Inform users about the new Copilot capabilities in Finder.
• No admin action is required to enable the feature.
• Review Copilot licensing and availability: Which Copilot is right for me or my organization? | Microsoft 365 Copilot | Microsoft 365 | Microsoft Learn

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

Compliance considerations

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

[Introduction]

Microsoft Purview is introducing Classifier Simulation Mode, the first phase of the broader Classifier Health Monitoring Platform. This new capability allows admins to test and validate custom classifiers on production data before publishing. Simulation Mode enables admins to optimize classifier logic before deployment, helping in reducing false positives, scanning latency, and noisy matches. Admins will access simulation controls and classifier health insights directly in the Microsoft Purview compliance portal, making it easier to monitor and improve classifier performance in one centralized location.

This message is associated with Roadmap ID 523201.

[When this will happen:]

• Targeted Release (Worldwide): Rollout begins early November 2025, completes by early December 2025.
• General Availability (Worldwide): Rollout begins late February 2025, completes by late March 2026.

[How this affects your organization:]

• Who is affected: Admins managing Microsoft Purview Information Protection and custom sensitive information types (SITs).
• What will happen:
  • By default, the feature will be available to all tenants.
  • Admins will see a new option to simulate a custom classifier before publishing.
  • Simulation is optional — admins can choose to simulate or publish directly.
  • Classifiers published without simulation will still be monitored for performance and flagged if unhealthy.
  • Classifier health insights will be available in the Microsoft Purview compliance portal, helping admins identify and remediate inefficient classifiers.
  • Inefficient classifiers may be automatically disabled to maintain system performance.

[What you can do to prepare:]

• Admins can begin using Simulation Mode once available; no onboarding or training is required.
• Once the feature is available:
  • Review classifier health insights in the compliance portal.
  • Monitor any SITs flagged as unhealthy and adjust logic as needed.
  • Consider simulating classifiers before publishing to reduce risk of false positives or performance issues.

[Compliance considerations:]

• Filters and Auto Refresh:
  1. The landing page displays real-time operational metrics with intent group and user group filters.
  2. The auto-refresh feature ensures supervisors have continuous access to the most up-to-date information.
• Bot Real-Time Analytics:
  1. Real-time analytics for agent performance, highlighting crucial metrics such as containment rate and abandon rate.
  2. These metrics are viewable by intent group.
• Voice Report Enhancements:
  1. The voice report includes features such as voicemail and in-queue callback options.
  2. Additionally, it will track Average Handling Time (AHT) specific metrics like talk time, wrap time, and hold time.
• Ongoing Conversation Dashboard:
  1. This dashboard incorporates Line of Business (LOB), Intent Group, and Agent Group concepts.
  2. Provide a comprehensive view of ongoing conversations with these new categorizations.
• Backlog Conversation Dashboard:
  1. This dashboard now includes LOB, Intent groups, and Agent groups.
  2. Enable supervisors to manage and prioritize backlog conversations more effectively.

• Flow runs and performance metrics
• Failure rates with error trends
• Top errors by code

• Unlock process mining insights with a one-click experience—no manual log data wrangling or transformation needed.
• Visualize and drill down into specific process routes (variants) and bottlenecks with variant analysis.
• Trace and analyze slow or unreliable process paths directly within the process map.
• Monitor comprehensive process health, performance, and reliability metrics across end-to-end automation.
• Go deeper with advanced process analysis in the process mining product.

• Insights are accessed through the Insights (preview) toggle on the process map.
• Advanced insights are enabled with a single click—no manual exports or data prep required (subject to available capacity).
• Advanced insights use Power Automate’s Process Mining capabilities and consume from your available Process Mining capacity in the tenant.
• Metrics are computed from historical flow runs stored in Dataverse and surfaced via the DFAI service.
• In high-volume environments, preparing insights may take longer.
• Flow runs must be older than 48 hours to be included in analysis.

• Enabled by default: Basic insights.
• Enabled for: All users with access to the Automation Center and process map features.
• Disabled for: Environments where “Enable production-ready preview features” is turned off in Power Platform admin center.

• Opt-in: Advanced insights through the Insights (preview) side-panel and Enable advanced insights button.
• Access requirements: Power Automate Premium license, permission to view flow run data included in the process map, the ability to manually create Process Mining processes, and at least 50 MB of available Process Mining capacity in the environment.

Updated November 12, 2025: We have updated the timeline. Thank you for your patience. 

Coming soon: Microsoft Copilot for Microsoft 365 usage in your tenant will be added to the Microsoft Graph API to facilitate the creation of customized reporting and analytics. Metrics included in the Graph API will match those available in the Copilot for Microsoft 365 usage report in the Microsoft 365 admin center, including tenant-level count of enabled users and active users, as well as last activity date per user (totals for each Microsoft 365 app and a grand total). A Microsoft Copilot for Microsoft 365 license is required to use this feature.

This message is associated with Microsoft 365 Roadmap ID 396562 and with MC724835 Microsoft 365 admin center Usage report: Microsoft Copilot with Graph-grounded chat (Preview) (published March 2024).

[When this will happen:]

Public Preview: We will begin rolling out early September 2024 and expect to complete by mid-September 2024.

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

[How this will affect your organization:]

Before this rollout, the Graph API did not include Copilot for Microsoft 365 usage.

After this rollout, admins can use the Graph API to create customized reporting and analytics for Copilot for Microsoft 365 usage.

Sample request for one of the three APIs: getMicrosoft365CopilotUserCountSummary.

Sample response:

HTTP/1.1 200 OK

Content-Type: application/json

Content-Length: 537

{

"@odata.context": "https://graph.microsoft.com/beta/reports/getMicrosoft365CopilotUserCountSummary(period='D7')?$format=application/json",

"value": [

{

"reportRefreshDate": "2024-06-26",

"adoptionByProduct": [

{

"reportPeriod": 7,

"anyAppEnabledUsers": 354590,

"anyAppActiveUsers": 144022,

"microsoftTeamsEnabledUsers": 354449,

"microsoftTeamsActiveUsers": 88737,

"wordEnabledUsers": 354449,

"wordActiveUsers": 17493,

"powerPointEnabledUsers": 354449,

"powerPointActiveUsers": 7245,

"outlookEnabledUsers": 354449,

"outlookActiveUsers": 38140,

"excelEnabledUsers": 354449,

"excelActiveUsers": 2554,

"oneNoteEnabledUsers": 354449,

"oneNoteActiveUsers": 1382,

"loopEnabledUsers": 354449,

"loopActiveUsers": 955,

"copilotChatEnabledUsers": 354449,

"copilotChatActiveUsers": 64401

}

This feature is on by default.

[What you need to do to prepare:]

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

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

To learn more about Microsoft’s own review of this product with its works councils, please consider reading: https://aka.ms/Copilot/MSWorksCouncilsArticle