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

[Introduction]

To improve OneDrive sync performance and make file recovery more predictable, OneDrive will change how cloud-initiated file deletions are handled on local devices. When a file that is locally available on a device is deleted from the cloud, it will no longer appear in the local Recycle Bin on Windows or Trash on macOS. Recovery will instead be available from the OneDrive or SharePoint web recycle bin, depending on where the file was stored.

This change improves sync performance for users with large file libraries, making delete operations faster and ensuring restores are simpler and more predictable with a single authoritative copy in the appropriate web recycle bin (OneDrive or SharePoint).

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• All OneDrive users on Windows and macOS

What will happen:

• Files deleted from the cloud (OneDrive web or another device) that were locally available on the device:
• Will be removed directly from the local disk.
• Will not appear in the local Recycle Bin (Windows) or Trash (macOS).
• Can be recovered from the OneDrive or SharePoint web recycle bin (for up to 93 days).
• Files that are cloud-only (Files On-Demand) are unchanged.
• Files deleted locally on the device will continue to appear in the local Recycle Bin or Trash as they do today.
• There is no admin configuration or opt-out for this change.

[What you can do to prepare:]

• No admin action is required
• We recommend the following readiness steps:
  • Inform users that cloud-deleted files that were locally available must be restored from the OneDrive or SharePoint web recycle bin, not the local Recycle Bin or Trash. Learn more: Restore deleted files or folders in OneDrive | Microsoft Support.
  • Update internal help desk articles or user documentation that reference local recovery for cloud-deleted files.
  • Ensure support teams understand the difference between cloud-initiated deletes of locally available files and local deletes.

[Compliance considerations:]

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

[Introduction]

We’re adding Undo and Redo support for PDF annotations in OneDrive and SharePoint on the web. This update improves productivity by bringing the web experience in line with desktop and mobile, allowing users to easily correct or reapply annotation changes while reviewing PDFs.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• All users who annotate PDF files stored in OneDrive or SharePoint using a web browser.

What will happen:

• Users can undo and redo PDF annotation actions, including ink, highlights, and text.
• Undo and redo are available through:
  • Keyboard shortcuts:
    • Undo: Ctrl+Z (Windows), Cmd+Z (Mac)
    • Redo: Ctrl+Y (Windows), Cmd+Shift+Z (Mac)
  • New Undo and Redo buttons in the annotation toolbar.

  

• Users can undo and redo multiple actions within the same editing session.
• Undo/redo history is cleared when the file is closed or when users exit edit mode.
• The feature is enabled by default and requires no admin configuration.

[What you can do to prepare:]

• No action is required. This feature will roll out automatically.
• Consider notifying users about the new undo and redo capabilities for PDF annotations.
• Update internal help documentation or training materials if you reference PDF annotation workflows.

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

[Compliance considerations:]

Undo and redo operate on existing PDF annotation data during the active editing session but do not change where or how files are stored long term.

[Introduction]

Microsoft Teams is introducing two new system chat sections called Muted chats and Meeting chats. These sections allow users to organize their chat and channels list by grouping muted conversations and meeting chats into dedicated sections that users can turn on or off.

This message is associated with Microsoft 365 Roadmap ID 559605.

[When this will happen]

• General Availability (Worldwide, GCC, GCC High, DoD): Rollout begins in early May 2026 and is expected to complete by mid-May 2026.

[How this affects your organization]

Who is affected

• All Microsoft Teams users in Microsoft 365 tenants, including Worldwide, GCC, GCC High, and DoD

What will happen

Users may see up to two new system sections in their Teams chat and channels list:

• Muted chats section
  • Enabled by default.
  • Muted chats that are not in Favorites or user‑created sections automatically move to this section.
  • The section appears at the bottom of the chat list.
  • Unread chats continue to appear bold.
• Meeting chats section
  • Disabled by default.
  • When enabled by the user, meeting chats that are not in Favorites or user‑created sections automatically move to this section.
  • The section appears below the main chats list.
  • Unread chats continue to appear bold and contribute to badge counts.
• Chats in Favorites or user‑created sections are not moved.
• Users can drag and drop these sections to reorder them.
• There are no admin controls for these sections.

[What you can do to prepare]

No admin action is required.

You may want to:

• Inform users that new chat sections are available and that they can turn them on or off.
• Notify helpdesk staff that muted chats may appear in a separate section by default.
• Direct users to Settings > Chats and channels to manage these sections.

[Compliance considerations]

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

[Introduction]

We’re updating how chat history is displayed in the Copilot navigation pane to help users stay focused and quickly resume relevant conversations. Chat history will now be scoped to the Copilot experience a user is currently working in, while still allowing access to an All chats view.

[When this will happen:]

• General Availability (Worldwide): Rollout will begin late April 2026 and is expected to complete by late May 2026.
• General Availability (GCC, GCCH, DoD): Rollout will begin early May 2026 and is expected to complete by late May 2026.

[How this affects your organization:]

Who is affected:

• All users accessing Chat experiences across Microsoft 365 apps.

What will happen:

• The chat history list in the Copilot navigation pane will show chats relevant to the Copilot experience the user is currently in. For example, users will only see chats they started from Outlook when looking at their chat history in Outlook.
• Users can still switch to an All chats view from the navigation pane to find and continue conversations across different Copilot experiences.
• Prior to this change, the navigation pane showed all chats by default, regardless of experience.
• Existing chats are not deleted or modified; only how chats are filtered and displayed in the navigation pane is changing.
• This change is enabled by default and does not require admin configuration.
• There is no impact to data storage, retention, auditing, or compliance.

[What you can do to prepare:]

No action is required.

We recommend:

• Notifying helpdesk and support teams about the navigation pane filtering behavior to reduce potential user confusion.
• Updating internal Copilot user guidance or screenshots if they reference the chat list in the navigation pane.
• Proactively informing users that they can use All chats if they don’t immediately see a previous conversation.

[Compliance considerations:]