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

Message Center

Summary

Starting mid-January 2027, legacy Microsoft Teams retention policies will apply only to Teams data, excluding Microsoft 365 Copilot interactions. Organizations must create separate retention policies for Copilot to maintain compliance. Existing Teams retention behavior remains unchanged, but action is required to cover Copilot data.

Discussionpowered by zap.ms

Last Updated

Oct 28, 2026

Published Sep 28, 2026

View version history

Service

Microsoft Purview

Tag

Major change
Updated message
User impact
Admin impact

Platforms

Web

More information

Updated October 27, 2026: We have updated the timeline. Thank you for your patience. 

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 mid-January 2027 (previously late October 2026) and expected to complete by end of January 2027 (previously mid-November)

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

QuestionAnswer
Does the change alter how existing customer data is processed, stored, or accessed?Yes. 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?Yes. 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.

Version history

2 versions tracked

Updated 1 time since Sep 28, 2026. Microsoft only ever shows the current version; this archive preserves the history.

Compare any two versions

From
To
  1. Oct 28, 2026 · 04:28 PMLatest · v2

    Changed: Body, Tags, End date

  2. Sep 28, 2026 · 11:49 PMOriginal · v1

    Changed: Initial version