Back to latest version
Comparing Dec 11, 2025 latest (Apr 3, 2026) Swap

MC1174856 - Microsoft 365 Copilot: Session persistence enhancement for Copilot chat

Message Center

Metadata at latest

Last Updated

Apr 3, 2026

Published Oct 18, 2025

Service

Microsoft 365 Copilot Chat

Tag

Updated message
New feature
User impact
Admin impact

Platforms

Web

Metadata changes

End date
Mar 2, 2026Jun 1, 2026

Body changes

removed textadded text

Updated December 11, 2025:April 3, 2026: We have updated the content and timelines.timeline. Thank you for your patience. 

Introduction

We’re improving the reliability of Copilot chat by ensuring that conversations are preserved even when users navigate away from a chat. With this update, a session entry is created in the navigation pane as soon as a prompt is submitted. This allows users to return to the conversation later without losing context or progress.

This capability will be available to Microsoft 365 Copilot Chat and Microsoft 365 Copilot users.

This message is associated with Microsoft 365 Roadmap ID 500638.

When this will happen:

  • Worldwide (General Availability): Rolling out from December 12, 2025 (previously December 3), to January 12,end of April 2026 (previously December 18, 2025)March)
  • GCC: Rolling out from January 19, 2026 (previously January 3), to February 2,end of April 2026 (previously January 30)March)
  • GCC High: Rolling out from January 19, 2026 (previously January 3), to February 2,end of April 2026 (previously January 30)March)
  • DoD: Rolling out from January 19, 2026 (previously January 3), to February 2,end of April 2026 (previously January 30)March)

How this affects your organization:

Who is affected: All Copilot Chat and Microsoft 365 Copilot users in commercial, GCC, GCC High, and DoD environments.

What will happen:

  • A session entry will now appear in the navigation pane immediately after a prompt is submitted.
  • Users can navigate away from a chat and return later without losing the conversation.
  • This update improves continuity and reduces the risk of session loss.
  • No changes to admin settings or policies are required.

What you can do to prepare:

No admin action is required at this time. You may wish to:

  • Inform helpdesk staff of this behavior change.
  • Update internal documentation if you describe Copilot chat behavior.

Compliance considerations:

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