Microsoft Purview: Data Lifecycle Management-Legacy Teams retention policies covering Copilot will be treated as Teams-only
Some existing retention policies scoped to Microsoft Teams may currently also apply to Microsoft 365 Copilot interactions. As part of an upcoming change, these legacy Teams retention policies will be converted to—and treated as—Teams-only policies. They will no longer implicitly
DIGITAL SKILL WORKS LTD / 12 PANES
What it is
Microsoft Purview: Data Lifecycle Management-Legacy Teams retention policies covering Copilot will be treated as Teams-only is a Microsoft 365 roadmap item published via Microsoft Release Communications. Current status: In development.
What it does
Some existing retention policies scoped to Microsoft Teams may currently also apply to Microsoft 365 Copilot interactions. As part of an upcoming change, these legacy Teams retention policies will be converted to—and treated as—Teams-only policies. They will no longer implicitly govern Copilot workloads.
Why you should care
Board
Security/compliance control — fund Steady before more seats.
CISO
Prioritise as Steady control; wire into IR and GRC evidence paths.
CFO
Map licence or consumption impact to the frozen value case; avoid seat spray.
Adoption
Pilot with a named cohort and measure changed work, not vanity clicks.
Suggested action
Wave 0 first: Security → GRC → Cost & Value → Licence → Adoption. Add to Horizon watchlist with an owner. Pilot only after Steady controls for the affected surface are in place.
12 Panes: 03 Horizon · 04 Security · 05 GRC
Communication needed
- Security: Lead review; confirm control mapping before enablement.
- GRC: Update AI/agent register and evidence path; confirm DPIA triggers if personal data is in scope.
- FinOps: Forecast seat or credit impact; align to frozen value case.
- Adoption: Plan cohort messaging, clinics, and success measures.
- Comms: One story for board and staff — what changes, what does not, who owns risk.
Benefits
- May improve productivity on a specific Microsoft 365 surface when permissions and data quality allow.
- Roadmap visibility helps Horizon planning without guessing dates.
Risks
- Status and dates change; treat MRC as directional, not a contract.
- Enabling without Steady controls can amplify overshare or cost leakage.
- Preview or rolling features can change behaviour; fence exploration on Pane 12 Frontier.
Source
- MRC id: 571306
- Status: In development
- Products: Microsoft Purview
- GA / disclosure: October CY2026
- Preview: —
- Platforms: Web
- Cloud instances: Worldwide (Standard Multi-Tenant)
- moreInfoUrls: —
- Open on Microsoft 365 Roadmap
Microsoft Release Communications / Microsoft 365 Roadmap (AI at Work). Content is subject to Microsoft API Terms of Use. Dates and status change; verify in the official roadmap before acting.