Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 7/9 advisories · checked 16:45 UTC Customize Public modeDiscuss ChangeIntel on Discord

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

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Roadmap
407897

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions this installation saw
  • Seen 16 Jun 2025 early June 2025, mid-June 2025 → mid-September 2025, late September 2025
  • Seen 27 Mar 2025 early March 2025, mid-March 2025, late March 2025 → early May 2025, mid-May 2025, early June 2025, mid-June 2025
  • Seen 10 Mar 2025 mid-February 2025, late February 2025 → early March 2025
  • Seen 13 Feb 2025 mid-November 2024, late November 2024 → mid-March 2025, late March 2025
  • Seen 11 Jan 2025 mid-January 2025, late January 2025 → mid-February 2025, late February 2025

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, with source markup removed
Updated June 16, 2025: We have updated the timeline below. 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 mid-September 2025 (previously early June) and expect to complete by late September 2025 (previously late June). 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.

What changed

Between archive captures, newest first
  1. Updated May 21,June 16, 2025: We have updated the content.timeline below. Thank you for your patience. Admins can follow the in-product message while … mid-May 2025 (previously mid-March). General Availability (Worldwide): We will begin rolling out early June mid-September 2025 (previously late March)early June) and expect to complete by mid-Junelate September 2025 (previously late March).June). How this will affect your organization: Admins will be able to separate …

  2. Updated March 27,May 21, 2025: We have updated the rollout timeline below. 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 … default for admins to configure from the Data Lifecycle Management Retention policies. Separate Copilot retention policies from Teams chats: What you need to do to prepare: This rollout will happen automatically …

  3. Updated March 10,27, 2025: We have updated the rollout timeline below. Thank you for your … When this will happen: Public Preview: We will begin rolling out early MarchMay 2025 (previously mid-February)early March) and expect to complete by mid-Marchmid-May 2025 (previously late February). mid-March). General Availability (Worldwide): We will begin rolling out late Marchearly June 2025 (previously mid-March)late March) and expect to complete by late March mid-June 2025 (previously ate February).late March). How this will affect your organization: Admins will be able to separate …

  4. Updated February 13,March 10, 2025: We have updated the rollout timeline below. Thank you for your … 407897. When this will happen: Public Preview: We will begin rolling out mid-Februaryearly March 2025 (previously mid-November)mid-February) and expect to complete by late February mid-March 2025 (previously late November).February). General Availability (Worldwide): We will begin rolling out mid-Marchlate March 2025 (previously mid-February)mid-March) and expect to complete by late March 2025 (previously ate February). How …

  5. Updated January 10,February 13, 2025: We have updated the rollout timeline below. Thank you for your … 407897. When this will happen: Public Preview: We will begin rolling out mid-November 2024mid-February 2025 (previously mid-November) and expect to complete by late November 2024.February 2025 (previously late November). General Availability (Worldwide): We will begin rolling out mid-Februarymid-March 2025 (previously mid-January)mid-February) and expect to complete by late FebruaryMarch 2025 (previously late January).ate February). How this will affect your organization: Admins will be able to separate …

    • Tags New feature, Admin impact → Updated message, New feature, Admin impact

    Updated January 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 … by late November 2024. General Availability (Worldwide): We will begin rolling out mid-Januarymid-February 2025 (previously mid-January) and expect to complete by late JanuaryFebruary 2025 (previously late January). How this will affect your organization: Admins will be able to separate …

  6. · first version seen

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 26 Oct 16:45 UTC · 272 of 272 readable · 271 fully read · documentation 469/469 current