MC926899 - Microsoft Purview | Data Lifecycle Management: Separate Copilot retention policies from Teams chats

Service

Microsoft Purview

Last Updated

Mar 10, 2025

Published Nov 6, 2024

Tag

Updated message
New feature
Admin impact

Platforms

Web

Summary

Admins can now create separate retention policies for Microsoft 365 Copilot interactions and Teams chats. This feature requires a Copilot license and will be available in March 2025. No admin action is needed before the rollout, but reviewing current configurations and notifying users is recommended.

More information

Updated March 10, 2025: We have updated the rollout timeline below. Thank you for your patience.

Before this rollout, Microsoft Teams chat and Microsoft 365 Copilot interactions are available together to be included or excluded in the Microsoft Purview Data Lifecycle Management policy in the Purview compliance center.

After this rollout, admins can have separate policies for Copilot interactions. Also, admins can separate Teams chat from Copilot interactions to create new retention policies for Copilot messages only.

A Microsoft 365 Copilot license is required to use this feature.

This message is associated with Microsoft 365 Roadmap ID 407897.

When this will happen:

Public Preview: We will begin rolling out early March 2025 (previously mid-February) and expect to complete by mid-March 2025 (previously late February).

General Availability (Worldwide): We will begin rolling out late March 2025 (previously mid-March) and expect to complete by late March 2025 (previously ate February).

How this will affect your organization:

Admins will be able to separate existing Teams Chat from Copilot interactions:

This feature is available by default for admins to configure from the Data Lifecycle Management Retention policies.

Separate Copilot retention policies from Teams chats:

admin controls

What you need to do to prepare:

This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation.

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