Teams chat retention and policies

Microsoft Teams chat — both 1:1 messages and channel posts — has a more complex retention story than email or files. Knowing the defaults, what Purview retention does, and where the gaps are matters for compliance and operational decisions.

Where Teams chat lives

Behind the scenes:

• Channel messages are stored as chat messages in the underlying SharePoint site / Microsoft 365 Group.
• 1:1 and group chats are stored in the participants' Exchange Online mailboxes in a hidden folder.
• Files shared in chat are stored in the sender's OneDrive (for 1:1) or the team's SharePoint site (for channel posts).
• Meeting recordings are stored in OneDrive or SharePoint depending on context.

Different storage locations have different retention models — this is a key source of confusion.

Default retention

Without explicit retention policies, Teams messages persist by default. Microsoft 365 doesn't auto-delete chat content the way some other platforms do.

However, mailbox retention defaults can affect 1:1 chat retention since the messages live in mailboxes. For most tenants, no aggressive default applies.

Purview retention policies for Teams

Purview retention policies have dedicated Teams scope options:

• Teams channel messages — applied at the channel/team level.
• Teams chats — applied at the user mailbox level for 1:1 and group chats.
• Teams meeting messages — meeting-specific in-meeting chat (technically a sub-category).
• Teams private channel messages — separately scoped because they live in different SharePoint sites.
• Teams shared channel messages — also separately scoped.

Configure each independently — a retention policy might keep channel messages 7 years for regulatory reasons while keeping 1:1 chats only 1 year.

End-user retention controls

By default, users can't delete channel messages older than X days unless the admin has enabled message deletion. Specific permissions:

• Channel posters can edit / delete their own messages.
• Team owners can delete any message in the team.
• Compliance retention overrides everything — if a policy retains for 7 years, user deletion just hides the message; it stays in preservation hold.

Common pitfalls

• Different retention per chat type — easy to set retention on 1:1 chats but forget channel posts, or vice versa.
• Files in chat — files in 1:1 chats live in OneDrive; retention on the OneDrive applies. Files in channel posts live in SharePoint; retention on SharePoint applies. They don't follow the chat retention automatically.
• Meeting chats — separate retention scope; verify it's covered.
• Private vs shared channels — separate SharePoint sites mean separate retention scope. Adaptive scopes can target all sites of a specific kind.
• Mailbox retention vs Teams retention — the Teams chats retention scope is the right control for 1:1 messages; the Exchange mailbox retention scope applies broadly to mailbox content and is less precise.

eDiscovery

Teams messages are fully searchable in eDiscovery. For investigations:

• Channel messages — searchable from the underlying SharePoint site / mailbox of the group.
• 1:1 and group chats — searchable from the participants' mailboxes.
• Conversation reconstruction in Premium eDiscovery presents chats as coherent conversations rather than isolated messages.

For tenants subject to legal discovery, Teams chat is treated like email — search, hold, export — with the same workflow.

Operational guidance

A reasonable baseline for many tenants:

• Channel messages: retain 7 years.
• 1:1 and group chats: retain 1 year (or longer for regulated industries).
• Meeting recordings: retain 60 days (or per organisational policy).
• Files in chat: retain according to file storage policy (typically same as SharePoint / OneDrive).

For regulated industries — financial services, healthcare, legal — retention may extend to 7+ years across all Teams categories.

Document the retention design, communicate it to users, audit annually. Teams chat retention is one of those topics where the defaults work for nobody specifically but accumulate problems for everyone.