Published Nov 6, 2024
Admins can now separate Microsoft Teams chat and Copilot interactions into distinct retention policies using PowerShell cmdlets. This feature, requiring a Microsoft 365 Copilot license, will be available in Public Preview by mid-May 2025 and generally available by mid-June 2025. No admin action is required before rollout.
Updated May 21, 2025: We have updated the content. Thank you for your patience.
Admins can follow the in-product message while editing the policy and make the required changes using PowerShell cmdlets to configure a Teams chat policy or Copilot policy. If there are existing policies covering other locations together with Teams chat and Copilot interactions in a single policy, admins can create equivalent new policies including the other locations from UI or using PowerShell cmdlets.
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 May 2025 (previously early March) and expect to complete by mid-May 2025 (previously mid-March).
General Availability (Worldwide): We will begin rolling out early June 2025 (previously late March) and expect to complete by mid-June 2025 (previously late March).
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.
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.