Microsoft Roadmap, messagecenter and blogs updates from 07-03-2026

Updated March 6, 2026: We have updated the timeline. Thank you for your patience.

Introduction

We’re updating the default behavior of Microsoft Teams Copilot in meetings. Copilot without transcription will become the default mode for newly scheduled Teams meetings where Copilot is allowed. Additionally, conversation history will now persist during meetings, improving multitasking and continuity of insights.

This update is associated with Microsoft 365 Roadmap ID 478611.

When this will happen

General Availability (Worldwide): We will begin rolling out in late April 2026 (previously late March) and expect to complete by mid-May 2026 (previously early April).

[What’s changing?]

Who is affected:

• Affected tenants: If your TeamsMeetingPolicy was created or modified before the Copilot without transcription policy option was introduced (June 2024), your tenant will be affected by this change.
• Not Affected: If your TeamsMeetingPolicy was created or modified after June 2024 when the Copilot without transcription option was introduced, your tenant will not be affected.

What will happen:

• The default Copilot policy will change from EnabledWithTranscript to Enabled for both new and existing Teams meetings where Copilot is allowed.
• Copilot and Facilitator will no longer automatically start transcription for meetings in affected tenants.
• Users must manually enable transcription to use post-meeting Copilot or Facilitator queries.
• Conversation history will persist during meetings for Copilot without transcription.
• Tenants with TeamsMeetingPolicy created or modified after June 2024 are not affected.

If adopting the new defaults:

• Review TeamsMeetingPolicy for transcription dependencies.
• Update internal documentation and training.
• Communicate to users how to enable transcription when needed.

Optional admin steps to retain current behavior:

• Update Global and Custom TeamsMeetingPolicy settings via TAC or PowerShell.
• TAC UI Portal: Navigate to Teams Admin Center and set the Copilot policy default value as required. For example, if the current default value is desired, update it to a different value, then set it back. Please ensure both TeamsMeetingPolicy and all Custom Policies are updated.
• PowerShell example to set Copilot policy to EnabledWithTranscript for all relevant meeting policies:

  get-csteamsmeetingpolicy | ? {
    $_.Identity -ne "Tag:AllOn" -and
    $_.Identity -ne "Tag:AllOff" -and
    $_.Identity -ne "Tag:Default" -and
    $_.Identity -ne "Tag:Kiosk" -and
    $_.Identity -ne "Tag:RestrictedAnonymousAccess" -and
    $_.Identity -ne "Tag:RestrictedAnonymousNoRecording"
  } | % {
    $_.Identity;
    set-csteamsmeetingpolicy -identity $_.Identity -Copilot EnabledWithTranscript
  }
      

Learn more: 

• Manage Microsoft 365 Copilot in Teams meetings and events | Microsoft Teams | Microsoft Learn
• Use Copilot without recording a Teams meeting | Copilot in Teams | Copilot | Microsoft Support

Compliance considerations

Updated March 6, 2026: We have updated the timeline. Thank you for your patience.

[Introduction]

We are introducing two new Microsoft Graph APIs that enable admins to programmatically access and manage agents and apps within their organization. These APIs provide greater flexibility for reporting and integration scenarios without relying on manual UI workflows.

This message is associated with Microsoft 365 Roadmap ID 502875.

[When this will happen:]

Frontier (Preview): Rollout will start late March 2026 and is expected to complete by end of March 2026. 

General Availability (Worldwide): Rollout will begin mid-April 2026 (previously end of March) and is expected to complete by early May 2026 (previously end of February).

[How this affects your organization:]

Who is affected: Admins managing Copilot agents and apps within Microsoft 365 environments.

What will happen:

• New Graph API endpoints will be available:
  • GET graph.microsoft.com/copilot/admin/catalog/packages – Retrieves a complete inventory of all agents and apps (Microsoft, External, Shared, and Custom).
  • GET graph.microsoft.com/copilot/admin/catalog/packages/{id} – Fetches detailed metadata for a specific agent or app, including properties and manifest details.

• These APIs allow for automated reporting and integration workflows.
• No changes to existing UI workflows or admin policies.
• These Graph API endpoints are available to users with an existing Microsoft 365 license; no additional license or add-on is required.

[What you can do to prepare:]

• Review the Microsoft Graph API documentation to familiarize yourself with usage and capabilities at this time.

[Compliance considerations:]

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

[Introduction]

We’re improving external collaboration in Microsoft Teams by enabling file attachments and Loop sharing in 1:1, group and meeting chats with external users. This update improves the collaboration experience for Files and Loop and add a new control for IT admins. Specifically, Files and Loop components will be shared automatically with external participants in the chat and won’t require any action by the sender by default. Additionally, Entra B2B Guests in your organization will be able to attach and share files from their home tenant’s OneDrive or SharePoint. 

This change applies to Teams for Windows desktop, Mac desktop, and web and is associated with Roadmap ID 492625.

Screenshot 1: Files are automatically provisioned.

Screenshot 2: Files shared have an external label and always open on Web.

[When this will happen:]

• Targeted Release: Rollout begins late October 2025; expected to complete by mid-November 2025
• General Availability (Worldwide): Rollout begins mid-January 2026

[How this affects your organization:]

Who is affected:

All Microsoft Teams users in your organization who participate in 1:1, group, or meeting chats with external users, including guest and Teams for Free users.

What will happen:

With this update:

• Unless the user chooses to share File and Loop by pasting links, external users in chat will be automatically provisioned to allow frictionless collaboration.
• You can disable automatic provisioning and have the user change permissions manually by using policy controls.
• If disabled, users will have to manually provision the file to users in the chat.
• Guest users will be able to upload files from their home tenant’s OneDrive and SharePoint.
• Files shared by external users will continue to display an External tag for clarity.
• Loop components will now be rendered inside external chats in Teams.
• Recipients will access File and Loop components as B2B guests within the resource tenant. If they are not already added as guests, they will need to give consent and might need to complete MFA, depending on your company’s B2B policy, before viewing the chat content.

• No action is required to enable the feature—it will be automatically available as the rollout progresses.
• To disable the automatic provisioning behavior for files and loops set the AutoShareFilesInExternalChats attribute of TeamsMessagingPolicy to Disabled. Learn more: Set-CsTeamsMessagingPolicy documentation.
• To provide seamless Loop access experience for external users, we recommend turning on Entra B2B Guest Access. Refer to: Microsoft Entra B2B integration for SharePoint & OneDrive – SharePoint in Microsoft 365 | Microsoft Learn.
• For configuration guidance, refer to: Set-CsTeamsFilesPolicy documentation (documentation will be updated before rollout).

Compliance considerations

Updated January 13, 2026: We have updated the timeline. Thank you for your patience. 

Microsoft is introducing a new capability in Teams that enables Channel Agent to orchestrate tasks with select third-party Model Context Protocol (MCP) servers, including GitHub, Asana, and Atlassian (JIRA). This integration supports collaborative workflows that reflect real human teamwork, allowing agents to transparently reason through tasks and gather information across tools. This change helps reduce manual switching between apps and improves task completion efficiency—all within the familiar Teams environment.

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

This message is associated with Microsoft 365 Roadmap ID 515466.

• Targeted Release (Worldwide): Begins in mid-November 2025 and is expected to complete by late January 2026 (previously mid-December 2025).

Who is affected: Microsoft 365 tenants using Teams and Channel Agent integrations.

What will happen:

• Channel Agent will be able to collaborate with Model Context Protocol (MCP) servers like GitHub, Asana, and Jira.
• Users can ask Channel Agent questions and receive coordinated responses across tools:

          Screenshot 1

Screenshot 2



• The feature will be available in preview and requires admin enablement.
• A Microsoft 365 Copilot license is required.
• There is no impact unless enabled by tenant admins.

What you can do to prepare

• Enable Channel Agent usage in Teams for your tenant.
• Allow apps that integrate with Model Context Protocol (MCP) servers such as GitHub, Asana, or Jira.
• Ensure users who need access have a Microsoft 365 Copilot license.
• Review internal documentation and update helpdesk guidance as needed.

Compliance considerations

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

Updated March 4, 2026: We have updated the timing of this change below. Thank you for your patience.

[Introduction]

Microsoft Purview Communication Compliance is undergoing a scheduled infrastructure upgrade. Although this migration is planned outside of normal business hours, some production clusters may experience higher loads, potentially causing brief delays in downstream processing. Brief delays in processing may occur during this migration, but no data will be lost.

[When this will happen:]

This migration will begin January 5, 2026, and end April 15, 2026 (Previously February 28, 2026).

[How this affects your organization:]

Who is affected:
Admins managing Microsoft Purview Communication Compliance policies and review workflows.

What will happen:

• Updates to policy insights and aggregated counts (New pending today, Total pending, Total resolved) may occur at a slower pace than usual.
• Intermittent errors may occur when reviewing flagged messages.
• Brief delays may be observed between receiving an alert notification and accessing messages for review.
• Certain report views may display outdated data until backlog processing is complete.
• Some export functions, such as exporting reports and files, might be temporarily unavailable.
• No data loss will occur—only temporary slowdowns in processing times.

This maintenance is scheduled outside of normal business hours to minimize impact. However, global organizations may experience some overlap with active hours.

[What you can do to prepare:]

• No action is required from administrators; the upgrade will be implemented automatically.
• We recommend informing your administrative and compliance teams about these possible short-term delays.
• If needed, update internal documentation to reflect potential temporary limitations.
• Learn about Communication Compliance.

[Compliance considerations:]

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

Updated March 4, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We’re updating how entities inserted from Add Work Content under the + menu behave in Microsoft 365 Copilot and Copilot Chat. With this change, entity names (such as document titles, people names, or other referenced objects) will no longer be inserted as text within the input box, making it easier for users to craft clean prompts without needing to manually delete entity labels. This feature is available to both users with a Microsoft 365 Copilot license (Microsoft 365 Copilot users) and users without a Microsoft 365 Copilot license (Copilot Chat users), but the experience varies.

This message is associated with Microsoft 365 Roadmap ID 552592.

[When this will happen]

General Availability (Worldwide): Rollout begins in mid‑February 2026 and completes in mid-March 2026 (previously late February).

[How this will affect your organization]

Who is affected: All users with access to Microsoft 365 Copilot and Copilot Chat in commercial (non-government) clouds.

What will happen:

• When users insert entities through Add Work Content (+):
  • The entity pill will appear in context, but the entity name will no longer be inserted as text in the chat input box:

     

• This change creates a cleaner prompt-building experience by removing extraneous text.
• No admin controls are changing.
• This update is enabled by default for all tenants.

[What you can do to prepare]

No action is required.

Optional steps include:

• Informing helpdesk or training teams about the change.
• Updating internal documentation that references entity insertion behavior in Copilot or Copilot Chat.

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

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

Updated March 6, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

Microsoft 365 Copilot is introducing infinite scroll for chat history, enabling users to seamlessly access older conversations by automatically loading additional chat sessions as they scroll. This update provides an improved and more fluid experience when navigating past conversations.

This feature is associated with Microsoft 365 Roadmap ID 557348. 

[When this will happen]

General Availability (Worldwide): We will begin rolling out this feature in mid-March 2026 (previously early March) and expect to complete rollout by end of March 2026 (previously mid‑March).

[How this affects your organization]

Who is affected

• All users of Microsoft 365 Copilot

What will happen

• Users will be able to view their full chat history directly in the navigation pane:

  

• Additional conversations will load automatically as users scroll.
• This feature will be enabled by default for all tenants.
• No admin controls or policy changes are introduced with this release.
• There is no impact to existing workflows or admin configurations.

[What you can do to prepare]

No action is required.

Admins may choose to inform helpdesk or support teams about the updated navigation experience.

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

Updated March 6, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

We’re introducing two new remediation actions as part of the Email table in Advanced Hunting that help security operations (SecOps) teams respond more quickly during investigations:

• Attachment block action
• Top-level URL domain block action

These actions let SecOps teams move directly from detection to mitigation within the same workflow, reducing response time and operational friction when addressing malicious campaigns.

These actions will be available through Take action if the query returns all the required columns.

[When this will happen:]

General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out early March 2026 and expect to complete by early April 2026 (previously end of March).

[How this affects your organization:]

Who is affected:

• Security operations teams and administrators using Advanced Hunting in Microsoft Defender for Office 365
• This feature is available to customers with Microsoft Defender for Office 365 Plan 2 or Microsoft 365 E5 licenses.

What will happen:

• Security teams can block malicious email attachments directly from Advanced Hunting results.
• Security teams can block top-level URL domains associated with phishing or malicious campaigns.
• Remediation actions are available in the Advanced Hunting “Take action” wizard.
• The feature is enabled by default; no configuration changes are required.
• There is no impact to user workflows unless a security action is taken.

Note:

• Attachment entries in the Tenant Allow/Block List are supported only if the query results include the Attachment column by joining with the EmailAttachmentInfo table on NetworkMessageId.
• Submit to Microsoft may be unavailable if required columns are missing. To resolve this issue, select Show empty columns before you select Take actions.

What you can do to prepare:

• No action is required.
• Review security investigation and response procedures to include the new remediation options.
• Inform SecOps teams of the updated Advanced Hunting capabilities.

Learn more: Take action on advanced hunting query results in Microsoft Defender XDR – Microsoft Defender XDR | Microsoft Learn (documentation will be updated before rollout)

Compliance considerations:

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

[Introduction]

Microsoft is introducing granular restore capabilities in Microsoft 365 Backup, allowing administrators to browse, search, and restore individual files or folders from restore points for protected SharePoint sites and OneDrive accounts. This update helps organizations reduce recovery time and operational impact by restoring only the content that is needed.

Screenshot:  Select the granular restore path when restoring content from a SharePoint site or OneDrive account

This message is associated with Roadmap ID 464991.

[When this will happen:]

• Public Preview (Worldwide): We will begin rolling out in early March 2026 and expect to complete by mid-March 2026.
• General Availability (Worldwide): We will begin rolling out in late April 2026 and expect to complete by early May 2026.

[How this affects your organization:]

Who is affected:

• Microsoft 365 tenants with Microsoft 365 Backup enabled
• Admins responsible for SharePoint Online and OneDrive for Business data protection and recovery

What will happen:

• Admins will be able to browse and search restore points for protected SharePoint sites and OneDrive accounts.
• Admins will be able to restore individual files or folders instead of restoring entire sites or drives.
• Only admins assigned the SharePoint Backup Administrator role can perform granular restore operations for SharePoint sites and OneDrive accounts.
• Existing Microsoft 365 Backup protection policies and restore points are respected.
• This feature is available only to tenants with Microsoft 365 Backup enabled.
• There is no direct impact to users; restore operations remain admin‑initiated.

[What you can do to prepare:]

• No action is required to receive this feature.
• Review your current Microsoft 365 Backup coverage for SharePoint and OneDrive to ensure critical workloads are protected.
• Familiarize backup administrators with the granular restore experience once Public Preview begins.
• Update internal recovery procedures or runbooks to include file- and folder-level restore scenarios.
• Inform helpdesk or IT operations teams when granular restores may be appropriate instead of full restores.

Learn more: Restore data in Microsoft 365 Backup | Microsoft Learn

[Compliance considerations:]

[Introduction]

To align with the iOS platform lifecycle and ensure customers remain protected with the most up‑to‑date security capabilities, Microsoft Defender for iOS will end support for devices running iOS 16. After support ends, Defender on iOS 10 devices will no longer receive feature updates, security fixes, or technical support. Devices running iOS 17 or later will continue to be fully supported.

[When this will happen]

Support for Microsoft Defender on iOS 16 devices will end on April 30, 2026.

[How this affects your organization]

Who is affected: Organizations with users or managed devices running iOS 16 and using Microsoft Defender for iOS.

What will happen:

• Existing installations of Microsoft Defender for iOS 16 devices will continue to function, but:
  • They will no longer receive new features.
  • They will no longer receive security updates.
  • They will no longer receive technical support.
• New installations on iOS 16 devices will no longer be available after support ends.
• Devices updated to iOS 17 or later will continue to receive full support.

[What you can do to prepare]

No admin action is required for this change to occur.

To prepare, you can:

• Identify iOS 16 devices using your organization’s device management tools.
• Encourage users to upgrade eligible devices to iOS 17 or later.
• Replace devices that cannot be upgraded, if necessary.
• Update internal documentation and support team guidance.
• Notify impacted users about the upcoming end of support.

Learn more: Minimum requirements for Microsoft Defender for Endpoint

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

[Introduction]

We’re adding support for sending locally stored Word, Excel, and PowerPoint files as email attachments directly through the new Outlook for Windows. This update streamlines the sharing experience and aligns with ongoing efforts to bring feature parity between classic Outlook for Windows and the new Outlook.

This message is associated with Microsoft 365 Roadmap ID 557675.

[When this will happen]

• General Availability (Worldwide): We will begin rolling out in early May 2026 and expect to complete by late May 2026.
• General Availability (GCC): We will begin rolling out in early June 2026 and expect to complete by late June 2026.

[How this affects your organization]

Who is affected

• Users working with locally stored Word, Excel, or PowerPoint files (not stored in OneDrive).
• Organizations adopting or transitioning to the new Outlook for Windows.

What will happen

• Users can now share local Office files as email attachments directly through the new Outlook for Windows.
• Users will no longer need to rely on the classic Outlook for Windows to send local file attachments.
• This feature is ON by default.
• There is no change to existing admin controls or policies, and all existing Outlook/Exchange policies continue to apply.

[What you can do to prepare]

No admin action is required.

To prepare your organization, you may:

• Inform help desk staff about this update to reduce support inquiries.
• Update your internal documentation if it references classic Outlook workflows.
• Encourage users to adopt the new Outlook for Windows if your organization is transitioning away from classic Outlook.

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

[Introduction]

The People agent in Frontier will no longer be available starting March 2026. Frontier agents help us learn what users value most and how they want to experience M365 Copilot. Through the People agent, users explored new ways to understand colleagues, prepare for meetings, and navigate organizational relationships, and this feedback has directly shaped our broader people experiences in M365 Copilot.

As part of moving these capabilities into core M365 Copilot surfaces—where more users can benefit—we are retiring the standalone People agent.

[When this will happen]

People agent retirement (Worldwide): Begins in early March 2026.

[How this affects your organization]

Who is affected

• Admins managing Microsoft 365 Copilot deployments
• Users who previously accessed the People agent through the Frontier program

What will happen:

• The People agent will no longer be available.
• Key capabilities from the People agent are being incorporated into broader Copilot people experiences.
• No admin configuration changes are required.
• No impact to existing admin policies or controls.
• There is no user action required.

[What you can do to prepare]

No preparation is required. 

Users can continue to leverage the People companion app or Copilot to find people with specific skills, and explore the greater organizational context of any colleague using the org explorer. Learn more here: 

• Org Explorer – Microsoft Support 
• Microsoft 365 companions apps overview – Microsoft 365 Apps | Microsoft Learn 

We encourage continued feedback on Copilot experiences through Frontier, which remains the primary program where we gather insights to inform early Copilot innovations.

Learn more about the Frontier program: Frontier program | Microsoft 365 Copilot

[Compliance considerations]

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

[Introduction]

We’re introducing ad-hoc room reservation directly from the Microsoft Teams Rooms on Windows console. This update enables users to reserve an available room on the spot without relying on a personal device or hallway panel, supporting quick, spontaneous meetings and helping reduce scheduling conflicts. This feature requires a Teams Rooms Pro license. 

This message is associated with Microsoft 365 Roadmap ID 548648.

[When this will happen]

• General Availability (Worldwide, GCC): We will begin rolling out in late April 2026 and expect to complete by late April 2026.
• General Availability (GCC High): We will begin rolling out late in April 2026 and expect to complete by early May 2026.
• General Availability (DoD): We will begin rolling out in late April 2026 and expect to complete by mid-May 2026.

[How this will affect your organization]

Who is affected

• Users and admins of Teams Rooms on Windows with Teams Rooms Pro licenses.

What will happen

• After this feature becomes available on room devices, users can reserve an available room directly from the Teams Rooms calendar by choosing Reserve and selecting an end time: 

  

• End times appear in 15-minute increments for up to the end of the day or until the next scheduled meeting, whichever comes sooner:

   

• The feature is enabled by default.
• Admin controls will be available on the Teams Rooms Pro Management portal: Rooms > Settings > Meetings > Allow ad-hoc room reservation.

[What you can do to prepare]

• No action is required before rollout.
• Notify users of the new reservation workflow.
• Update internal training or documentation.
• Use Teams Rooms Pro Management portal or device settings if you want to restrict ad-hoc reservations.

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

Updated March 6, 2026: We have updated the content. Thank you for your patience. 

Introduction

To reduce notification noise and improve signal quality, Microsoft will disable Teams Meeting Recording (TMR) expiration notification emails. Customer feedback indicates these emails generate high volume with minimal engagement. Only the email notifications are being removed; recording expiration and deletion behavior remains unchanged.

When this will happen

June 1, 2026

How this affects your organization

Who is affected:

• All Microsoft 365 tenants
• Users who receive Teams meeting recording expiration emails

What will happen:

• Users will no longer receive email notifications when a Teams meeting recording expires.
• Recording expiration and deletion policies remain unchanged.
• No admin action or policy updates are required.
• This change is enabled by default.

What you can do to prepare

• No action is required.
• Optionally notify users and helpdesk teams of this change.
• Update internal documentation if it references expiration emails.
• If your organization requires these notifications, submit the survey linked in the original communication.

Compliance considerations

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

[Introduction]

We are updating the AI Administrator role to support Agent 365. This update enables delegated, day-to-day agent management while preserving enterprise security and least-privilege principles.

The AI Admin role is designed for managing agent lifecycles and agentic users. By removing the dependency on Global Administrators for routine, agent-scoped actions, this change helps eliminate operational bottlenecks, supports scale, and maintains clear separation of duties. Global Admin elevation remains required only for rare, high-risk scenarios.

[When this will happen:]

General Availability: Rollout begins early March 2026; expected completion by late March 2026

[How this affects your organization:]

Who is affected

• Microsoft 365 tenants using Agent 365
• Administrators assigned the AI Administrator role
• Organizations that currently require Global Administrator involvement for routine agent management

What will happen

• AI Administrators can grant tenant-wide admin consent for apps and agents requesting permissions, except Microsoft Graph application permissions
• AI Admins can view basic subscription properties
• AI Admins can view agents flagged as risky through Microsoft Entra Identity Protection. Learn more: ID Protection for agents (Preview) (this article will be updated soon).
• To review existing capabilities of the AI Admin, visit AI Administrator.
• AI Admins can perform full CRUD (create, read, update, delete) operations on agents
• This includes adding, deleting, and managing agent credentials
• Agent management is available through the Microsoft 365 admin center, Microsoft Entra admin center, PowerShell, and APIs

What is not included

• Apps or agents requiring Microsoft Graph application permissions will continue to require Privileged Role Administrator or Global Administrator approval

[What you can do to prepare:]

• Review existing assignments for the AI Administrator role to ensure only appropriate users have access
• If you want to opt out, remove the AI Admin role from users who should not grant tenant-wide consent or manage agents

Review or update role assignments

1. Sign in to the Microsoft 365 admin center at admin.cloud.microsoft using a Global Administrator or User Administrator account.
2. Go to Roles > Role assignments.
3. Select AI Administrator.
4. Review the list of users assigned to the role.
5. If needed, remove the role from users or add users who should legitimately manage AI agents.

Learn more: About administrator roles in the Microsoft 365 admin center – Microsoft 365 admin | Microsoft Learn

[Compliance considerations]

[Introduction]

Starting in the second week of April 2026, Always-on diagnostics for Endpoint Data Loss Prevention (DLP) will be turned on by default for onboarded Windows devices in Microsoft Purview. Endpoint DLP diagnostic traces including policy evaluation logs, file classification results, enforcement actions, and error states are stored locally on the device in a secure, compressed proprietary format for up to 90 days. This collection helps eliminate the need to reproduce issues during Microsoft Support investigations. The ability to request that Microsoft collects critical diagnostic data as part of a support case will also be enabled. Endpoint diagnostic logs that you choose can then be securely shared with Microsoft for troubleshooting, reducing investigation effort and accelerating time to resolution for Endpoint DLP issues.

[When this will happen:]

General Availability (Worldwide): This change will go into effect mid-April 2026

[How this affects your organization:]

Who is affected:

• Organizations using Endpoint Data Loss Prevention (DLP) on Windows devices
• Admins managing Endpoint DLP settings in Microsoft Purview

What will happen:

• From the date of this Message Center post through the second week of April 2026, admins may choose to opt out of this setting in the Microsoft Purview portal. If an admin opts out during this period, their selection will be respected, and the setting will remain unchanged.
• If no action is taken, diagnostics will be automatically enabled in the second week of April 2026, after which admins can opt out at any time via the existing settings.

Note: Opting out of Always-on diagnostics may hinder your ability to effectively troubleshoot issues that arise in Endpoint Data Loss Prevention scenarios. Without this feature, organizations may experience prolonged investigation times, reduced visibility into policy behavior, and increased difficulty identifying and resolving Endpoint DLP issues. Keeping Always-on diagnostics enabled helps support the security, reliability, and operational stability of your environment.

[What you can do to prepare:]

• No action is required if you want to keep the default behavior.
• Review your organization’s diagnostic and data collection policies.
• If you want to opt out before the default change:
  • Go to Microsoft Purview portal
  • Navigate to Endpoint DLP settings
  • Disable Always-on diagnostics
• Communicate this change to security, compliance, and helpdesk teams

Learn more:

• Always-on diagnostics for endpoint DLP | Microsoft Learn
• Always-on diagnostics troubleshooting blog
• Always-on diagnostics blog

[Compliance considerations:]

[Introduction]

We’re introducing Phase 2 of always-on diagnostics for Endpoint Data Loss Prevention (DLP). This update enables admins to collect diagnostic traces directly from Windows endpoints and upload them to Microsoft through the Purview portal during support investigations—without involving the employee or information worker . This improves troubleshooting efficiency and helps resolve support cases faster.

This message is associated with Microsoft 365 Roadmap ID 499431.

[When this will happen]

• General Availability (Worldwide): We will begin rolling out in early March 20265 and expect to complete by mid-March 2026.

[How this affects your organization]

Who is affected

• Admins who manage Endpoint DLP in Microsoft Purview
• Organizations using Windows endpoints with Endpoint DLP enabled

What will happen

• Admins can request and retrieve always-on diagnostics directly from Windows endpoints using the Purview portal.
• Users are not interrupted, and no device-side interaction is required.
• Diagnostic traces can be uploaded directly to Microsoft Support using a request number.
• The change reduces time to reproduce issues, collect logs, and resolve support cases.
• Existing Endpoint DLP policies and enforcement remain unchanged.
• This feature requires admin enablement; it is not automatically turned on. Learn more: Always-on diagnostics for Endpoint DLP.

[What you can do to prepare]

• Review the documentation for configuring always-on diagnostics for Endpoint DLP.
• Enable the feature for your organization if you plan to use the enhanced troubleshooting capabilities.
• Update internal helpdesk documentation to ensure support staff know how to request traces from the Purview portal.
• Share the Learn documentation with admins who manage Purview or DLP policies.

Learn more: Always-on diagnostics for endpoint DLP | Microsoft Purview | Microsoft Learn

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

[Introduction]

We’re enhancing the Data Security Triage Agent in Microsoft Purview Insider Risk Management to help analysts triage alerts more efficiently and focus investigations on the activities and users that matter most. These updates respond to customer feedback for clearer risk context, streamlined alert review, and improved investigation accuracy.

This message is associated with Microsoft 365 Roadmap ID 557683.

[When this will happen]

• Public Preview: We will begin rolling out in early March 2026 and expect to complete by early April 2026.
• General Availability (Worldwide): We will begin rolling out in late June 2026 and expect to complete by late July 2026.

[How this affects your organization]

Who is affected

• Admins and security analysts who use Microsoft Purview Insider Risk Management.
• Organizations with Insider Risk Management enabled and analysts using alert triage workflows.

What will happen

The newly enhanced Data Security Triage Agent acts as the front door to investigations, helping teams immediately understand who and what matters most. Instead of manually reviewing raw alerts, the Data Security Triage Agent provides:

• Prioritized alerts based on user risk and activity patterns.
• Behavioral risk patterns summarized into investigative themes, helping analysts move more quickly from alert to insight.
• Expanded user context, including role, employment status (such as last working date), and prior alert history.
• Access to the enhanced experience in:
  • Purview portal → Insider Risk Management → Agent tab
  • Alerts tab → Triage Agent toggle
• The enhancement is not enabled by default; admins must turn on the Data Security Triage Agent.
• Organizations using Microsoft 365 E5 will also receive Security Copilot to support investigations; rollout is ongoing and customers will receive advance notice.

Screenshot 1 – View of alerts

Screenshot 2 – How to access the enhanced Triage Agent in Microsoft Purview Insider Risk Management (IRM):

[What you can do to prepare]

No immediate action is required. However, to make use of the new capabilities, consider the following steps:

• Enable the Data Security Triage Agent in the Purview portal (Agent tab).
• Train analysts to access the enhanced view using the Triage Agent toggle in the Alerts tab.
• Review your internal documentation for Insider Risk investigation processes and update it as needed.

Learn more: Agents built into your workflow: Get Security Copilot with Microsoft 365 E5

[Compliance considerations]

No compliance considerations identified. Review as appropriate for your organization.

• Pre-Paid Environments: Usage was reported only and not billed, so no adjustment is necessary.
• PAYGO Environments: Usage was reported and billed. Microsoft will automatically increase storage capacity to offset the misreported amount. The adjustment will be calculated based on each environment’s consumption during the affected period and varies by region.

[Introduction]

We are expanding Microsoft Copilot capabilities in Outlook to include shared and delegate mailboxes. This update allows users who already have access to Microsoft 365 Copilot to use Copilot features, including Copilot Chat, directly while working in shared or delegated mailboxes. This change is designed to improve productivity for teams that collaborate using shared inboxes such as executive assistants, support desks, HR, and finance teams.

This message is associated with Microsoft 365 Roadmap ID 554936.

[When this will happen:]

• Targeted Release: We will begin rolling out early April 2026 and expect to complete by early May 2026.
• General Availability: We will begin rolling out early May 2026 and expect to complete by early June 2026.

[How this affects your organization:]

Who is affected:

• Users who have access to shared or delegated mailboxes in Outlook
• Organizations where users are licensed for Microsoft 365 Copilot

What will happen:

• Users can access Copilot Chat in Outlook directly while working in a shared or delegated mailbox, rather than only from their primary mailbox.
• Copilot features such as Summarize and Draft will work in shared and delegated mailboxes.
• Support includes full-access shared mailboxes as well as shared folder permissions.
• Users no longer need to include mailbox-specific phrases (for example, “in <mailbox>@domain.com”) when prompting Copilot. Prompts can be written as if the mailbox were their own, and responses are grounded in the active shared mailbox.
• Folder-level permissions are supported for accessing Copilot Chat in shared and delegated mailboxes.
• Copilot conversation history is saved to the user’s primary account, ensuring there is no sharing of conversation history between users who access the same shared mailbox.

[What you can do to prepare:]

No action is required to enable this feature.

• Review shared and delegated mailbox permission models, including folder-level permissions, to ensure they align with your organization’s expectations.
• Inform users that Copilot conversation history remains associated with their primary account, even when Copilot is used from a shared mailbox.
• Update internal documentation or training materials to reflect that Copilot can now be used directly within shared and delegated mailboxes in Outlook for eligible users.

[Compliance considerations:]