Service issues › MP1471948

Some European users' Microsoft Purview retention policies for Teams and Copilot chats may have delayed message deletions

Resolved Microsoft Purview General advisory
Started
07 Sep 2026 07:00 UTC
Resolved
16 Sep 2026 19:11 UTC
Status
falsePositive
Origin
microsoft

Timeline & resolution

16 Sep 2026 19:11 UTC · regular

Title: Some European users' Microsoft Purview retention policies for Teams and Copilot chats may have delayed message deletions User impact: Users in Europe with Purview retention policies for Teams and Copilot chat deletion may take up to 14 days to process. Final status: The investigation is complete and we've determined the service is healthy. A service incident didn't actually occur. This communication will expire in 24 hours. This is the final update for the event.

14 Sep 2026 20:19 UTC · regular

Title: Some European users' Microsoft Purview retention policies for Teams and Copilot chats may have delayed message deletions User impact: Users in Europe with Purview retention policies for Teams and Copilot chat deletion may take up to 14 days to process. Current status: We’ve determined that a large increase in deletion requests generated by Purview policies created a processing backlog, resulting in delays when deleting Microsoft Teams and Copilot chat messages. We’ve added processing capacity to reduce these delays; however, users may continue to experience delayed chat message deletion while we process the remaining backlog. Scope of impact: Impact is primarily to users in Europe who have a Microsoft Purview retention policy configured for Teams and Copilot chat; however, multi-geo and organizations primarily hosted in other regions may also experience impact. Start time: Monday, September 7, 2026, at 7:00 AM UTC Root cause: A large increase in Purview deletion requests created a backlog which is increasing the processing time for deleting chat messages as per configured Purview policies. Next update by: Wednesday, September 16, 2026, at 8:00 PM UTC

© Microsoft — archived from Microsoft 365 service health. Content notice