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

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

Introduction

The Outlook Mobile team is updating the release for Data Loss Prevention (DLP) Policy Tips & Override for Outlook Mobile. A number of improvements have been made to the initial scope of this rollout, along with some unforeseen challenges that will be listed in detail.

This message is associated with Microsoft 365 Roadmap ID 496146.

When this will happen

Production Build App Store Release for Android and iOS: We are targeting May 4th to submit to the app store, and on average it can take up to a week for Apple and Google to then distribute that build via the App Stores.

How this affects your organization

The following updates have been made to this DLP rollout for Outlook Mobile:

1. [added] Custom oversharing dialog support
2. [added] Custom policy information
3. [added] Policy tip evaluation performance improvements
4. [added] Attachment scanning
5. [added] Intune control for Android and iOS to turn Data Leak Prevention on or off (default is set to OFF)
6. [temporarily removed] External recipient rule validation

Due to unique challenges with external recipient rule validation we are removing External Recipient rule validation from this release pending changes to the implementation.

After feedback we have added an Intune control that is defaulted to OFF to give your organization the opportunity for validation and user training prior to enabling DLP on Android and iOS. Documentation links for “DLP on Android and iOS” and “Intune controls for DLP in Mobile” will be provided in an update soon.

What you can do to prepare

Please prepare to validate your organization’s rules in a test environment prior to enabling Data Leak Prevention on Mobile, and where possible provide training for users which can greatly improve their success and overall experience with policy tips and rules.

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

[Introduction]

To help provide additional transparency about what content has been generated or altered by using AI in Microsoft 365, Microsoft is providing you with a policy setting that visually designates when content, such as video or audio content, is generated or altered by using AI. This policy setting controls your organization’s option to add a visual or audio watermark to video and audio content that your users generate or alter by using AI in Microsoft 365.

To turn on watermarks for video and audio content that your users generate or alter by using AI in Microsoft 365, you need to use the “Include a watermark when content from Microsoft 365 is generated or altered by AI” policy. This policy is available only in Cloud Policy service for Microsoft 365. 

Note: Watermarks are not turned on unless you set the policy to Enabled. Your organization is always responsible for following the Microsoft Enterprise AI Services Code of Conduct, including not generating or sharing deceptive AI content. 

This change is associated with Microsoft 365 Roadmap ID: 547831.

[When this will happen]

General Availability (Worldwide): We anticipate that this policy will be available in Cloud Policy by mid-April 2026 (previously late March).

[How this will affect your organization]

Users that generate or alter video and audio content by using AI in Microsoft 365

What will happen

If you set the “Include a watermark when content from Microsoft 365 is generated or altered by AI” policy to Enabled in Cloud Policy, a visual or audio watermark is added to video and audio content that is generated or altered by using AI in Microsoft 365. Here are two examples:

• A visual watermark is added to a video generated with Clipchamp.
• An audio watermark is added to an audio overview generated by Copilot from a Word document.

• This policy doesn’t affect images generated or altered by using AI in Microsoft 365.
• Instead, your users will be able to turn on watermarks for images by going to Settings & Privacy > Privacy at https://myaccount.microsoft.com. We anticipate this capability will be available in the second half of February 2026. 

[What you need to do to prepare]

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

[Introduction]

To help organizations analyze more recent Microsoft 365 Copilot usage trends, we’re adding a new export option in the Copilot dashboard. In addition to the existing user‑week export (see MC1173208), dashboard users with company‑level access will be able to export a subset of de‑identified Copilot usage metrics aggregated by user and day. This option includes 28 days of activity data and supports more granular, short‑term insights into Copilot adoption. Exported data will usually reflect copilot activity up to 3 days before the export date; actual timing may vary 

A minimum of 50 Microsoft 365 Copilot licenses is required. This feature applies to the Viva Insights web app.

This message is associated with the Microsoft 365 Roadmap ID 547749.

• Screenshot 1 – Export data button in Copilot dashboard:



• Screenshot 2 – Copilot dashboard export options:

  

[When this will happen]

• Public preview: Mid-May 2026 (previously Early April) – Late May 2026 (previously late April)
• General availability (Worldwide): Early August 2026 (previously early June) – Late August 2026 (previously late June)

[How this affects your organization]

Who is affected

This feature is available to Copilot dashboard users with full company-level data access, including:

• Senior leaders (as identified in Entra ID)
• Admin‑assigned company‑level users
• Delegates with company‑level access
• Global analysts and admins
• Group managers with access restricted to their own teams won’t have access to the user-day export.

What will happen

• A new export option will allow eligible users to download de-identified, row-level Copilot usage metrics aggregated by user and day, covering the most recent 28 days.
• Organizations can use this export to assess short-term usage patterns, support tactical adoption efforts, optimize licensing, and evaluate the impact of recent changes.
• Exported data will usually reflect copilot activity up to 3 days before the export date; actual timing may vary
• The export supports analysis across Copilot-enabled apps (for example, Word, Excel, Teams) and includes two additional attributes: Organization and Job function.
• Copilot activity metrics in exports run within 2 days of Copilot license assignments or removals may not reflect those license changes. Exports run after the 2‑day window will accurately reflect the impact of those license changes in copilot activity metrics under normal conditions.
• Data in previously exported files will not be automatically updated or modified after the export is generated.
• Access to the new user‑day export uses the same Viva Feature Access Management (VFAM) controls as the existing user‑week export (Viva Insights → Copilot Metrics Export). No new access controls are introduced. Existing VFAM settings for the Copilot dashboard export will remain in effect and apply to both day and week level export options after the day level export is released. Please read MC1173208 for more details.

[What you can do to prepare]

• Review and update VFAM settings for users with company‑wide access to the Copilot dashboard.
• Inform eligible users about this new export option.
• No additional admin configuration is required if export functionality is already enabled.
• Admins may disable the export feature for the tenant or specific groups at any time through VFAM.

Learn more:

• Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Microsoft Learn
• Microsoft Viva Feature access management | Microsoft Learn

[Compliance considerations]

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

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

[Introduction]

We’re expanding Microsoft Purview Data Loss Prevention (DLP) controls to provide broader governance for Microsoft 365 Copilot. With this update, DLP policies that prevent Copilot from processing content based on sensitivity labels will now apply to Word, Excel, and PowerPoint files regardless of where they are stored. This enhancement responds to customer feedback requesting more consistent protection coverage across local and cloud-based file locations.

This feature is associated with Microsoft 365 Roadmap ID 557255.

[When this will happen]

• General Availability (Worldwide and GCC): Rollout will begin in mid-April 2026 (previously late March) and is expected to complete by May 2026 (previously late April).

[How this affects your organization]

Who is affected

• Organizations using Microsoft Purview DLP to restrict Copilot processing of sensitivity-labeled content
• Admins who manage Purview DLP policies
• Users working with Microsoft 365 Copilot in Word, Excel, or PowerPoint

What will happen

• DLP policies that restrict Copilot from processing sensitivity‑labeled files will apply to Word, Excel, and PowerPoint files in all storage locations, including:
  • SharePoint
  • OneDrive for Business
  • Local device storage
  • Other storage locations accessible to Office apps
• When a DLP policy blocks Copilot processing, Copilot will not process the file’s content in Word, Excel, or PowerPoint.
• Existing DLP policies will continue to function normally; no policy migration or reconfiguration is required.
• The feature will be on by default for tenants with relevant DLP rules configured.
• Users will see consistent DLP enforcement when invoking Copilot in supported Microsoft 365 apps.

Implementation detail:

This update does not modify Copilot capabilities. Instead, Office clients and AugLoop have been enhanced so AugLoop can read a file’s sensitivity label directly from the client. Today, AugLoop retrieves the label by calling Microsoft Graph using the file’s SharePoint or OneDrive URL, which limits DLP enforcement to files stored in OneDrive and SharePoint. By enabling the client to provide the label, DLP enforcement now applies uniformly across all storage locations, including local files.

[What you can do to prepare]

No action is required to enable this feature.

If your organization uses DLP controls for Copilot, you may optionally:

• Review existing DLP policies that include sensitivity-label-based restrictions
• Update internal documentation or helpdesk guidance if needed
• Communicate this enhancement to relevant security or compliance teams

Learn about managing DLP policies: Learn about data loss prevention | Microsoft Purview | Microsoft Learn

[Compliance considerations]

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

[Introduction]

Copilot Cowork is now available in Frontier. Copilot Cowork enables users to orchestrate complex, multi-step work across Microsoft 365 without switching between apps. Copilot Cowork moves beyond answering questions to turning intent into execution by automatically generating plans, coordinating work across emails, meetings, messages, files, and data, and carrying tasks forward with visible progress and user control. This update reflects customer feedback to reduce manual coordination for real work while maintaining enterprise-grade security, privacy, and controls. Learn more on our blog: Powering Frontier Transformation with Copilot and agents.

Screenshot: The Copilot Cowork interface in Microsoft 365 Copilot

[When this will happen:]

• Copilot Cowork is now available in Frontier.
• General availability will be communicated at a later date.

[How this affects your organization:]

Who is affected:

• Users with a Microsoft 365 Copilot (Premium) license
• Users enabled for Frontier 
• English language only

Prerequisites and controls:

• The tenant must be enrolled in the Frontier program.
• Microsoft‑built agents must be enabled.
• Anthropic must be enabled as a subprocessor (default: on).
• For tenants based in the European Union (EU), Copilot Cowork is off by default due to EU Data Boundary requirements and must be explicitly enabled.

What will happen:

• Users can install Copilot Cowork from the Agent Store in the Microsoft 365 Copilot app and pin it to the left rail.
• Users can describe an outcome in natural language, and Copilot Cowork will:
• Automatically generate a multi-step plan grounded in the user’s Microsoft 365 context
• Coordinate tasks across Microsoft 365 apps such as Word, PowerPoint, Outlook, and others
• Continue work overtime with visible checkpoints and progress tracking
• Copilot Cowork proposes actions and requires explicit user approval before acting on tasks such as:
• Sending emails or Teams messages
• Scheduling, declining, or rescheduling meetings
• Editing or moving files
• Users can pause, adjust, or stop execution at any time and return later to review progress.
• For eligible tenants, the experience is enabled by default and respects existing Microsoft 365 permissions and policies, unless restricted by EU Data Boundary settings.

[What you can do to prepare:]

• No admin action is required.

Learn more:

• Copilot Cowork: Now Available in Frontier | Microsoft Learn
• Anthropic as a subprocessor for Microsoft Online Services | Microsoft Learn 
• Opt-in to use Anthropic’s models | Microsoft Learn
  
• Agent settings in Microsoft 365 admin center | Microsoft Learn 

[Compliance considerations:]