(Updated) Microsoft 365 Copilot: Session persistence enhancement for Copilot chat [MC1174856]

(Updated) Microsoft 365 Copilot: Session persistence enhancement for Copilot chat [MC1174856]

Message ID: MC1174856 (Updated)

Updated December 3, 2025: We have updated the content. 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 November 5, 2025 (previously October 27), to November 30, 2025 (previously October 31)
  • GCC: Rolling out from November 19, 2025 (previously November 3), to November 30, 2025 (previously November 28)
  • GCC High: Rolling out from November 26, 2025 (previously November 10), to November 30, 2025 (previously November 28
  • DoD: Rolling out from November 19, 2025 (previously November 10), to November 30, 2025 (previously November 28)

[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.

Source: Microsoft

<<< [MC1174856] Archive
Tooltip: View earlier revisions of this post

Latest Posts

Pass It On
Leave a Comment

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply