Manage retention policies for Microsoft Teams


If you are seeing a message in Teams that your chats or messages have been deleted by a retention policy, see Teams messages about retention policies.

The information on this page is for IT administrators who manage these retention policies.

Retention policies and retention labels from Microsoft 365 help you to more effectively manage the information in your organization. You can configure retention settings to keep data needed to comply with your organization's internal policies, industry regulations, or legal requirements. You can also configure retention settings to delete data that's considered a liability, that you're no longer required to keep, or that has no legal or business value.

Teams supports retention policies for chat and channel messages so that as an admin, you can decide proactively whether to retain this data, delete it, or retain it for a specific period of time and then delete it. The start of the retention period for these actions is always based on when a message is created. You can apply a Teams retention policy to your entire organization or to specific users and teams. Retention labels aren't supported for Teams.


Shared channels are supported by retention policies.

To learn more about retention solutions in Microsoft 365, see Learn about retention policies and retention labels.

Users who are subject to a retention policy for Teams must have an appropriate license, such as Office 365 E3 or Office 365 A3. For other licensing options for these retention policies, see the Microsoft Purview Data Lifecycle Management section from Microsoft 365 licensing guidance for security & compliance. To learn more about licensing for Teams, see Microsoft Teams service description.

How Teams retention policies support retain and delete actions

If you configure a Teams retention policy to retain chats or channel messages, users can still edit and delete their messages in their Teams app. Although users no longer see their pre-edited or deleted messages in Teams, data from these messages is stored in a secured location designed for eDiscovery searches by compliance administrators. Permanent deletion of this data doesn't happen before the end of the configured retention period, or if another retention policy is configured to retain this data, or it is subject to an eDiscovery hold.

When a retention policy is configured to delete chats and channel messages, these messages become eligible for automatic deletion. If the messages are still displayed in the Teams app, they disappear from there and users are informed that a retention policy has deleted these messages. If the messages were previously subject to a retain action and have been edited or deleted by users, these messages will now be deleted from the secured location and no longer returned in eDiscovery searches.

For detailed information about how these policies work depending on your policy configuration and user actions, and what message data is included and excluded for Teams retention policies, see Learn about retention for Microsoft Teams. That page also explains why you might sometimes experience delays when retention policies delete messages. For example, messages can be visible to users in the Teams app up to seven days after the expiration period you've configured in the retention policy.

If you set up multiple Teams retention policies with different retention settings, the principles of retention resolve any conflicts. For example:

  • If there's a conflict between retaining or deleting the same content, the content is always retained in the secured location so that it remains searchable with eDiscovery for compliance administrators.

    This principle also applies to messages that are under eDiscovery holds for legal or investigative reasons.

  • If there's a conflict in how long to retain the same content, it is retained in the secured location for the longest retention period.

These two principles of retention address most conflicts that might arise when you have multiple retention policies for Teams, but for more information, see The principles of retention, or what takes precedence?

When to use retention policies for Teams

In many cases, organizations consider private chat data as more of a liability than channel messages, which are typically more project-related conversations.

You can efficiently configure a single retention policy for all Teams messages. Or, for more fine-grained control, you can:

  • Have separate retention policies for private chats (1:1 or 1:many chats), messages from standard channels, or messages from private channels.

  • Apply the policies only to specific users or teams in your organization. For Teams chats and private channels, you can select which users the policy applies to. For Teams channel messages, you can select which teams the policy applies to.

For example, for standard channel messages: Create a retention policy for specific teams in your organization and configure that policy with a delete action after one year. Then create another retention policy for standard channel messages for all other teams and configure that policy with a delete action after three years.

Create and manage retention policies for Teams

To create or edit a retention policy for Teams messages, use the instructions from Create and configure a retention policy and the Retention policy for Teams tab.

That page has additional information about creating and managing retention policies for other workloads in Microsoft 365. For example, you might want to also create a retention policy for Microsoft 365 groups to retain and delete files that are accessed in Teams and stored in OneDrive or SharePoint.

Data can be stored in the form of screenshots in an end users's local drive through the Windows Recall feature and is managed separately. See the Manage Windows Recall article for more information.

End-user experience

For private chats (1:1 chats) or group chats, users will see that chats older than the retention policy configuration are deleted and an automatically generated message stating "We've deleted older messages due to your org's retention policy" is shown on top of yet undeleted messages. For example:

User informed in Teams that chat message are deleted because of a Teams retention policy.

User in Teams explaining messages are deleted as a result of a Teams retention policy.

For Channel messages, users (channel members) will see the deleted messages disappear from view after messages expire. If the deleted message was a parent message of a threaded conversation, then, in place of parent message, a message stating "This message has been deleted because of a Retention Policy" will be displayed. For example:

Screenshot of channel before retention.

Screenshot of channel after retention.


The displayed messages that users see as a result of deleted messages are not configurable at this time.

The links in these displayed messages go to Teams messages about retention policies. This documentation for end users helps to answer basic questions about why their messages have been deleted. However, as part of your retention policy deployment, make sure that you communicate to users and your help desk the impact of your configured settings.