Teams Tidbit - Data governance and Event Based retention
I wanted to let you know about this feature that seems like an exciting change in Teams.
We now have Event based retention on Worldwide preview, with this preview, we are also adding Microsoft Teams chats and team channels in the Data Governance features of the Security & Compliance center. You can set retention policies to Teams content, similar to the way that you have the option to choose locations across Exchange, SharePoint, OneDrive and Groups today. This addition will expand your ability to meet retention and regulatory requirements with confidence across Office 365 applications.
Event Based Retention:
This feature will help organizations manage retention of content based on a certain event trigger. The event triggers the start of the retention period, and all content with a label applied for that type of event get the label’s retention actions enforced on them. Whether an employee departure, or the close of a project, you can now establish certain event triggers and create retention or deletion policies associated to those events.
For example, you can use labels with event-driven retention for:
Employees leaving the organization Suppose that employee records must be retained for 10 years from the time an employee leaves the organization. After 10 years elapse, all documents related to the hiring, performance, and termination of that employee need to be disposed. The event that triggers the 10-year retention period is the employee leaving the organization.
Intellectual property activity Suppose that all records related to intellectual property such as copyrights, trade secrets, and trademarks need to be retained for five years from the time the intellectual property expires. The event that triggers the five-year retention period is the expiration of the intellectual property.
Event-driven retention is typically used as part of a records-management process. Labels based on events also usually classify content as a record. Using labels for records management.
Before you create a policy for retention and/or deletion, if you would like to use event trigger then create the labels and publish them
Sources to review…
Blog Post: here
Techcommunity recording: here