| Announcement ID | MC814576 | Published Date | 07-16-2024 | |
| Service | microsoftteams | Last Updated | 08-02-2024 | |
| Category | Stay informed | Expiration Date | 09-27-2024 | |
| Roadmap ID | Action Required by Date | |||
| Tags | Admin impact, User impact | |||
| Summary |
|---|
| Microsoft Teams will integrate legal holds with Microsoft Purview directly, starting July 31, 2024, moving away from SharePoint integration. Legal holds on events before this date will continue through SharePoint, with full Purview eDiscovery support expected by early 2025. No admin action is required before the rollout. |
| More Information |
|---|
Before this rollout, compliance admins can place Microsoft Purview eDiscovery legal holds on Microsoft Teams webinar and town hall data using Team's ability to target SharePoint locations where Teams content is housed. Due to heightened security requirements and the need for specialized compliance support, we are moving legal holds in Teams from the SharePoint integration to a more direct integration with Purview. When this will happen:The more direct integration of Teams legal holds with Purview will begin July 31, 2024. Legal holds through SharePoint will not apply to any new Teams webinars or town hall meetings created after July 31, 2024, because newly created Teams town hall and webinar data will not reside in SharePoint. Legal holds on events created before July 31, 2024 will continue to work through SharePoint. Full support for Purview eDiscovery legal holds is anticipated by early 2025. Purview eDiscovery will continue to work for all events, even after July 31, 2024. Only eDiscovery legal hold will be affected by this integration. How this will affect your organization:after this rollout, legal hold through Microsoft Purview will be on by default and accessible to all admins with appropriate permissions. What you need to do to prepare:This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your admins about this change and update any relevant documentation. |