Configuring Microsoft Teams Retention Policies in Purview

SC-401 By islever Editorial Last updated

Short answer

Create a retention policy in Microsoft Purview targeting Teams channel messages and Teams chats. Set the retention period to 5 years from the date created and configure the action to delete the content after the retention period expires. Assign the policy to the relevant user group.

Question

SIMULATION
Username and password
Use the following login credentials as needed:
To enter your username, place your cursor in the Sign in box and select the username below.
To enter your password, place your cursor in the Enter password box and select the password below.
Microsoft 365 Username:
[email protected]
Microsoft 365 Password: XXXXXXXXX
If the Microsoft Edge browser or Microsoft 365 portal does not load successfully, select the Microsoft Edge browser icon from the task bar, type the URL “https://admin microsoft.com”, and press Enter.
The following information is for technical support purposes only:
Lab Instance: XXXXXXXX.
Task 7
You need to create a retention policy that meets the following requirements:
• Applies to Microsoft Teams chats and Teams channel messages.
• Retains items for five years from the date they are created, and then deletes them.

Key Takeaways

Tests the ability to correctly map Teams content types to retention policy scopes and configure time-based deletion actions without overcomplicating with unnecessary adaptive conditions.

Learn how to create a Microsoft Purview retention policy for Teams chats and channel messages that retains data for five years before automatic deletion.

Common mistake: Learners often confuse 'static' and 'adaptive' scopes, adding complex conditions when a simple workload-based selection is sufficient. Others may forget to explicitly select both 'chats' and 'channel messages' separately, leading to incomplete coverage.

Expert Analysis

The scenario requires configuring a retention policy for Microsoft Teams data with specific duration and deletion behaviors. The core task involves navigating the Microsoft Purview compliance portal to define a policy that targets Teams content.

First, identify the correct scope settings. While some learners debate static versus adaptive scopes, the requirement is straightforward: apply to 'Microsoft Teams chats and Teams channel messages.' In the current Microsoft Purview interface, creating a retention policy allows you to select specific workloads. Under the Teams workload section, you must explicitly check the boxes for 'Teams channel messages' and 'Teams chats.' Note that private channel messages are often a separate checkbox or require specific licensing/permissions, but the prompt specifies standard chats and channels. The comment mentioning 'adaptive scope' likely refers to using conditions (like location or tags) which are not required here; a simple static scope covering the specified content types is sufficient and more direct for this simulation.

Second, configure the retention action. The policy must retain items for five years from creation and then delete them. This is achieved by setting the retention period to '5 years' and selecting the action 'Delete' after the retention period expires. It is crucial to ensure the retention starts from the 'date created,' not the date of last modification or access, unless specified otherwise. The simulation environment typically provides a clear UI where you select the retention period duration and the final disposition action.

Third, finalize and name the policy. Give the policy a descriptive name such as 'Teams Chats and Channels Retention Policy' and assign it to the appropriate users or groups (often 'All users' if not specified). Review the settings to ensure no other conflicting policies exist that might override this behavior. Submit the policy to activate it. The key is precision in selecting the exact content types ('chats' and 'channel messages') and the exact time-based deletion rule.

Official Reference

Exam Strategy

When simulating retention policies, always start by isolating the specific content type (e.g., Teams, Exchange, SharePoint) before setting durations. Verify that the retention start point (creation vs. last modified) matches the requirement exactly. Use the 'Preview' feature in the simulator to confirm selected locations before submitting.

Frequently Asked Questions

Do I need to use adaptive scope for Teams retention?

No, a static scope is sufficient for applying retention to all Teams chats and channel messages. Adaptive scope is only needed if you want to apply different rules based on conditions like sensitivity labels or user location.

Does the retention period start from creation or last modification?

The question specifies 'from the date they are created.' Ensure you select the option that triggers the retention timer at creation, not modification, to meet the requirement accurately.

More SC-401 FAQ →

Discussion 3 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 3

  1. Amias2 👍 1
    basically create retention policy with static scope not adaptive scope like the answer mentioned then select team channels messages , team chats and copilot interactions , and teams private channel messages. lastly set retention to 5 years then delete.
  2. Scrambles 👍 1
    Static scope supports team chat and channel messages just not private channel messages
  3. Amias2 👍 1
    after checking we need adaptive scope to be able to select team channel messages

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

← Back to SC-401 Study Guide