Admin, security & compliance Launched #4

Microsoft Purview retention for Copilot memory

Admins can retain Copilot memory for investigations

Microsoft Purview retention for Copilot memory

Microsoft's published visual. Source: Microsoft. · Verified 2026-11-08

Screens: Microsoft 365 Copilot (source: Microsoft) ·

Admins can now configure retention for Microsoft Copilot memory in Microsoft Purview Data Lifecycle Management. Microsoft rolled out the capability in October 2026 to preserve saved memories and give security and compliance teams visibility into changes.

Key points

  • Copilot memory includes saved memories and details inferred from chat history.
  • Memory items are stored in a hidden folder in the user’s Exchange mailbox.
  • Retention and versioning support applies to inactive memory items.
  • Active memory continues to be managed by the Copilot experience.
  • The capability is available on Web in Worldwide (Standard Multi-Tenant).

What to do

Review whether Copilot memory needs retention under your organisation’s policies. Configure retention in Microsoft Purview Data Lifecycle Management where needed. Tell security and compliance teams that retained memory changes can support investigations. Explain that active memory remains managed by the Copilot experience.

Timeline

  1. 21 August 2026 Published
  2. September 2026 General availability (planned, not confirmed) Earlier schedule: Original general availability target, superseded by the October rollout.
  3. October 2026 In Microsoft’s monthly deck
  4. October 2026 General availability (confirmed) Copilot memory retention rolled out.
Speaker notes

This adds Copilot memory to the information administrators can retain through Microsoft Purview Data Lifecycle Management. Memory includes both saved memories and details inferred from chat history. The distinction to explain is that retention and versioning support covers inactive memory items, while the Copilot experience continues to manage active memory. Security and compliance teams can use visibility into saved-memory changes for investigations and lifecycle governance. Microsoft’s October deck confirms that the feature rolled out in October, replacing the roadmap’s September target. The sources do not specify licensing prerequisites.

Sources and links

Area, status, change type, licence and flags are indicative. Always open the source before you act on a card.