HANDS ON SharePoint
HANDS ON Teams
HANDS ON Lists
HANDS ON tek
M365 Admin
Microsoft Purview Data Lifecycle Management: Support for Microsoft Teams call data records
Microsoft Teams call data records (CDR) are system-generated messages that contain metadata for meetings and calls – for example, who joined and when they joined. Previously, this type of content was not managed by retention policies for Teams (user chats, standard channels, shared channels, and private channel user messages).
We now are pleased to include support for these types of messages. CDRs will now be retained and deleted by your already-existing retention polices for Microsoft Teams. Currently, this behavior will only apply to CDRs that were generated from September 21, 2022. Call data records generated prior to this date are not yet supported by retention policies, however we are working to add this by mid-2023 and will notify you via Message Center once these are supported.
When this will happen:
This improvement to support retention policies is rolling out now and will include all Teams call data records generated from September 21, 2022, onwards.
How this will affect your organization:
Teams CDRs will now be managed per the rules specified in your Teams user chat and Teams channel messages retention policies. This inclusion happens automatically, no changes are required to your configuration.
Please note that Teams call data records generated from meetings in private channels (different from messages in private channel conversations) will be managed by the “Teams chat” messages policies. CDRs for meetings held in standard channels or shared channels will be managed by the policies configured for “Teams channel messages”.
What you need to do to prepare:
No action is needed to enable this change; however you may want to communicate this change to the team responsible for Data Lifecycle Management at your organization.
Access the Data Lifecycle Management solution in the Microsoft Purview compliance portal.
Learn more: Learn about retention for Teams
Message ID: MC455895
No comments yet