How Teams Content Maps to Retention Policies
Retention policies for Teams are configured in the Microsoft Purview compliance portal, not in the Teams admin center, and they target different underlying storage locations depending on content type: channel messages are captured in a hidden group mailbox associated with the Team, 1:1 and group chat messages are captured in each participant's own Exchange Online mailbox, and files shared anywhere in Teams are governed by the SharePoint or OneDrive retention settings applied to the site hosting them. This means a single retention policy scoped to 'Teams channel messages' will not automatically retain files posted in that same channel — file retention has to be configured separately against the associated SharePoint site, which is a common gap organizations miss during compliance audits.
Cricket analogy: Retention policies mapping to different storage locations is like a cricket board keeping match footage in one archive, player fitness data in another, and financial records in a third — each governed by its own retention schedule even though they all relate to the same tour.
Legal Hold and eDiscovery
When an organization anticipates litigation or a regulatory investigation, Purview eDiscovery (Standard or Premium) lets a compliance officer place a legal hold on specific custodians' Teams content, which suspends normal deletion — even if a user deletes a message or an admin's retention policy would otherwise purge it, the held copy is preserved in a hidden Substrate Preservation Hold Library invisible to end users. Because chat lives in individual mailboxes and channel messages live in the Team's group mailbox, an eDiscovery search scoped only to a custodian's personal mailbox can miss channel content unless the search also includes the Teams the custodian belongs to, which is why properly scoping an eDiscovery case (not just naming custodians) is critical to defensible collection.
Cricket analogy: A legal hold is like a match-fixing investigation freezing all communications and footage related to a specific series so nothing can be deleted or altered while the inquiry proceeds, regardless of what a normal archiving schedule would otherwise do.
Communication Compliance and Information Barriers
Beyond retention and hold, Purview Communication Compliance lets organizations configure policies that scan Teams messages for specific risk categories — offensive language, sensitive data leakage, or regulatory phrases relevant to industries like financial services — and route flagged messages to a reviewer without the sender being notified, which is commonly required for regulated firms under rules like FINRA's supervision requirements. Information Barriers, a related but distinct feature, proactively prevents certain groups from communicating or collaborating at all, such as blocking an investment bank's research analysts from chatting with the trading desk, and is enforced at the point someone tries to add a person to a chat, Team, or channel, not just monitored after the fact.
Cricket analogy: Communication compliance scanning messages is like a board's integrity unit reviewing player communications for signs of spot-fixing after the fact, while an information barrier is like a hard rule preventing players from even messaging known bookmakers in the first place.
# Microsoft Purview - create a retention policy for Teams chat and channel messages
Connect-IPPSSession
New-RetentionCompliancePolicy -Name "Teams-3yr-Retention" `
-TeamsChatLocation All `
-TeamsChannelLocation All
New-RetentionComplianceRule -Name "Teams-3yr-Retention-Rule" `
-Policy "Teams-3yr-Retention" `
-RetentionDuration 1095 `
-RetentionComplianceAction KeepRetention policies in Purview can operate in 'Keep', 'Delete', or 'Keep and Delete' modes. 'Keep and Delete' preserves content for the retention window even if a user deletes it early, then permanently deletes it once the window expires — often the correct mode for regulated industries that must retain records for a fixed period but no longer.
A retention policy scoped only to 'Teams channel messages' does NOT cover files posted in those channels — files live in SharePoint and require a separate retention policy targeting the associated SharePoint sites, or content will be deleted according to the site's default SharePoint retention settings instead, which is a frequent audit finding.
- Retention policies are configured in Microsoft Purview, not the Teams admin center, and target different storage per content type.
- Channel messages live in a hidden group mailbox; chat messages live in each participant's own Exchange mailbox; files live in SharePoint/OneDrive.
- A channel message retention policy does not automatically cover files posted in that channel — file retention must be configured separately.
- Legal hold via eDiscovery preserves content in a hidden Substrate Preservation Hold Library even if a user deletes it or a retention policy would purge it.
- eDiscovery searches must include the custodian's Teams, not just their mailbox, to capture channel content.
- Communication Compliance flags risky messages for after-the-fact review; Information Barriers proactively block communication between defined groups.
- 'Keep and Delete' retention mode preserves content for a fixed window then permanently deletes it, common for regulated industries.
Practice what you learned
1. Where are Teams channel messages actually stored for retention purposes?
2. Why might a retention policy scoped to Teams channel messages fail a compliance audit for missing files?
3. What happens to a message under legal hold if the user tries to delete it?
4. What is the key functional difference between Communication Compliance and Information Barriers?
5. What does 'Keep and Delete' retention mode do?
Was this page helpful?
You May Also Like
Teams Permissions and Roles
A practical guide to the role hierarchy in Microsoft Teams — from tenant admin down to channel member — and what each role can and cannot do.
Shared Channels
Learn how Teams shared channels let internal teams and external organizations collaborate in one space without switching tenants.
Related Reading
Related Study Notes in Microsoft Technologies
Browse all study notesWindows 10 / UWP Development Study Notes
.NET · 30 topics
Microsoft TechnologiesWindows Batch Scripting Study Notes
Batch · 30 topics
Microsoft TechnologiesMFC (Microsoft Foundation Classes) Study Notes
C++ · 30 topics
Microsoft TechnologiesSilverlight Study Notes
.NET · 30 topics
Microsoft TechnologiesXAML Study Notes
.NET · 30 topics
Microsoft TechnologiesWPF (Windows Presentation Foundation) Study Notes
.NET · 30 topics