Summary
Microsoft Purview Data Lifecycle Management will soon support retention for Microsoft 365 Copilot memory versions. Rollout begins in late September 2026 and concludes by mid October 2026. Administrators should review compliance frameworks and retention settings to ensure proper governance of historical memory data stored in user mailboxes.
Administrator impact: No direct administrator action is required.
End user impact: Users will have their updated or deleted Copilot memory items retained for compliance purposes according to organisational policies.
Score rationale: This update introduces new compliance and retention capabilities for Copilot memory without forcing immediate administrative intervention.
Microsoft Purview Data Lifecycle Management will support retention of inactive Microsoft 365 Copilot memory versions for compliance and investigation. Historical memory items are stored in users’ Exchange mailboxes, accessible via eDiscovery. Rollout begins late September 2026. No immediate action is required; organizations should review retention policies and governance.
Message ID: MC1478965
Published: Sep 24, 2026
Expires: 14 Nov 2026
Last updated: 25 Sept 2026
Category: Plan for change
Service: Microsoft Purview
Tag: New feature, Admin impact
Roadmap ID: 569612
Platforms: Web
Microsoft Message
Microsoft Purview Data Lifecycle Management is introducing retention support for Microsoft 365 Copilot memory. Copilot memory includes saved memories, details inferred from chat history, and custom instructions that help provide personalized and context-aware Copilot experiences.
With this update, organizations will be able to retain inactive versions of Copilot memory items for compliance, governance, and investigation purposes. When memory items are updated or deleted, historical versions can be preserved according to your organization’s retention configuration, helping compliance teams understand how memory content changes over time while supporting enterprise-ready compliance requirements.
This message is associated with Microsoft 365 Roadmap ID 569612.
Rollout Schedule
Global: Rollout will begin in late September 2026 and is expected to complete by mid-October 2026.
Impact on Your Organization
Who is affected
- Organizations using Microsoft 365 Copilot.
- Compliance, legal, privacy, security, records-management, and eDiscovery teams.
- Administrators managing Microsoft Purview Data Lifecycle Management and eDiscovery.
Platforms/Services
- Microsoft Purview Data Lifecycle Management
- Microsoft Purview eDiscovery
- Microsoft 365 Copilot
- Exchange Online
What will happen
- Your organization will be able to retain inactive versions of Microsoft 365 Copilot memory items for a configured retention period.
- When a memory item is updated or deleted, an inactive version can be retained in the user’s Exchange mailbox according to applicable retention configuration.
- Compliance teams will be able to access historical versions of Copilot memory items to understand how content changed over time.
- Organizations can preserve historical versions of Copilot memory items for compliance purposes.
- The capability supports eDiscovery and internal investigations involving Copilot memory.
- Organizations can apply data lifecycle requirements to inactive memory versions.
- Relevant records can be maintained when users update or delete memory items.
- Copilot memory items are stored in a hidden folder within the user’s Exchange mailbox and inherit applicable mailbox security protections.
- Authorized administrators can use Microsoft Purview eDiscovery to search for Copilot personalization and memory items.
- Before this update, Microsoft Purview retention policies and retention labels do not apply to Copilot memory.
- Saved memories remain available until explicitly deleted by the user.
- Turning off enhanced personalization or saved memories prevents Copilot from using the applicable memory but does not automatically delete previously saved memories.
Action Required/Recommendations
No immediate action is required before rollout.
To prepare:
- Review your organization’s retention requirements for Microsoft 365 Copilot memory.
- Coordinate with legal, compliance, privacy, security, and records-management stakeholders to determine an appropriate retention period.
- Review Microsoft Purview roles and eDiscovery permissions for administrators who investigate Copilot memory.
- Update internal Microsoft 365 Copilot governance, eDiscovery, incident-response, and data-subject-request procedures as needed.
- Inform compliance and support teams that turning off enhanced personalization or saved memories does not automatically delete previously saved memories.
- After the feature becomes available, validate retention and eDiscovery behavior with a limited group of test users before broader deployment.
Compliance considerations
Does the change alter how existing customer data is processed, stored, or accessed (for example, documents, emails, chats, or Copilot memory)?
Yes. Inactive versions of Microsoft 365 Copilot memory items can be retained when memory items are updated or deleted, enabling preservation and access to historical versions for compliance and investigation purposes.
Does the change modify retention policies, holds, or deletion workflows?
Yes. Microsoft Purview Data Lifecycle Management will support retention of inactive versions of Copilot memory items for a configured retention period.
Does the change alter how admins can monitor, report on, or demonstrate compliance activities?
Yes. Authorized administrators can use Microsoft Purview eDiscovery to search and investigate Copilot personalization and memory items, including retained inactive versions.
Does the change modify how users can access, export, delete, or correct their personal data within Microsoft 365 services (GDPR Data Subject Rights)?
Yes. Historical versions of memory items may be retained after users update or delete memory items, subject to configured retention settings.
Does the change store new customer data, and if so, where?
Yes. Inactive versions of Copilot memory items can be retained in a hidden folder within the user’s Exchange mailbox according to retention configuration.