Microsoft Purview: Data Lifecycle Management-Legacy Teams retention policies covering Copilot will be treated as Teams-only

🚨 The Signal: Existing Microsoft Teams retention policies will no longer cover Copilot interactions. This change means Copilot data will not be retained by these legacy policies, potentially creating compliance gaps for AI-generated content.

The Impact

Compliance and security teams are affected by a potential gap in Copilot data retention, increasing regulatory risk.

• Compliance Officers: Risk of non-compliance with data retention obligations for AI interactions.
• Security Teams: Potential for unmanaged Copilot data, complicating eDiscovery and investigations.
• Legal Teams: Increased risk in litigation due to missing or ungoverned Copilot-generated content.
• Data Stewards: Loss of control over the lifecycle of sensitive information generated by Copilot.

The Action

1. Navigate to Microsoft Purview compliance portal: Data lifecycle management > Microsoft 365 retention policies.
2. Identify existing retention policies scoped to Microsoft Teams that were implicitly covering Copilot.
3. Create new retention policies specifically scoped to Microsoft 365 Copilot interactions.
4. Review and update existing retention labels to ensure they can be applied to Copilot content.
5. Communicate changes to legal, compliance, and security stakeholders regarding Copilot data governance.

Domain: Purview · Impact: high · Workload: Microsoft Purview