MC1481313 Plan for changeMajor changeUser impactAdmin impact

Microsoft Purview | DLM: Legacy Teams retention policies that cover Copilot will be treated as Teams-only

Microsoft Purview Microsoft 365 admin center

Versions captured by this deployment. Earlier versions and notices may be missing; first observed is not first published.

Ends: 15 Dec 2026
Roadmap: 571306
Platforms: Web

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

Microsoft's start date: 28 Sep 2026
Last changed by Microsoft: 28 Sep 2026
First seen here: 19 Oct 2026
Versions seen: 1

What the notice says

Microsoft's text, with its sections, lists and tables; source markup removed

What and why

Microsoft Purview is updating how legacy Microsoft Teams retention policies are applied. Some existing retention policies that are scoped to Teams currently also apply to Microsoft 365 Copilot interactions. Beginning with this rollout, these legacy policies will be treated as Teams-only policies and will no longer implicitly apply to Copilot workloads.

Rollout schedule

Worldwide: Beginning in late October 2026 and expected to complete by mid-November 2026

Impact on your organization

Who is affected

Organizations using Microsoft Purview retention policies that were historically configured for Microsoft Teams and currently rely on those policies to retain or delete Microsoft 365 Copilot interactions
Compliance administrators and records management administrators responsible for retention policy configuration

Platforms and services

Microsoft Purview
Microsoft Teams
Microsoft 365 Copilot

What will happen

Legacy Teams retention policies that currently affect both Teams and Copilot data will be treated as Teams-only policies.
Copilot interactions will no longer be retained or deleted through these legacy Teams retention policies.
Retention behavior for Microsoft Teams content will remain unchanged.
Organizations that require retention coverage for Copilot interactions must configure retention settings specifically for the Copilot workload.

Action required and recommendations

Action is required if you currently rely on Teams retention policies to govern Copilot interactions.

Review existing Microsoft Purview retention policies to identify policies that may currently apply to Copilot interactions.
Determine whether your organization requires retention or deletion controls for Microsoft 365 Copilot interactions.
Configure retention policies explicitly for the Copilot workload to maintain the desired compliance coverage after this change.
Update internal compliance documentation and administrator guidance as needed.
Inform compliance and records management stakeholders of this change.

Compliance considerations

Question	Answer
Does the change alter how existing customer data is processed, stored, or accessed?	Copilot interaction data will no longer be governed by legacy Teams retention policies and must be managed through retention policies explicitly configured for the Copilot workload.
Does the change modify, interrupt, or disable retention policies, holds, or deletion workflows?	Existing Teams retention policies that currently affect Copilot interactions will no longer apply to Copilot workloads. Organizations requiring Copilot retention coverage must configure retention policies specifically for Copilot.

What changed

Between the versions this installation saw, newest first

This installation has seen one version of this notice, first on 19 Oct 2026. Later changes will show here.

Linked documentation

Microsoft pages the notice links to

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

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.
Versions before 19 Oct 2026: this installation first saw the notice after Microsoft posted it.