365Fanatic / Microsoft 365 Message Center / MC1481313
Tenant announcements

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

MC1481313

All Microsoft 365 Message Center posts · Daily summary

SummaryDetailedTimelineProduct updatesThis weekMC SummaryMC DetailedPnP Search
About this page These posts come from a tenant in West Europe and are shown as a reference. Day-by-day digest: MC Summary. Linked to the roadmap via Roadmap ID when Microsoft names one. Items are kept for 12 months. Always check Message Center in your own environment for what applies to you.
Archive This post is no longer in the Microsoft 365 Message Center (last seen on 7 okt 2026). Microsoft removes posts after a while. We keep the last version here as an archive.
MC1481313 Major change
Microsoft Purview

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

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

QuestionAnswerDoes 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.

This is in the weekly digest for week 40 · What changed this week? →