A few months back, one of our customers lost every private channel message from a project that ran nearly two years. The team lead had been promoted, the original channel got archived (not deleted — just archived), and when the company later needed those conversations for a contract dispute, they found out the hard way: archived in Teams means read-only, not backed up. Microsoft had no copy of those messages beyond the 30-day soft-delete window, which was long gone.
This keeps happening because people assume Microsoft Teams backup works like email — that there's some invisible system capturing everything. There isn't. Not in the traditional sense, anyway.
What Microsoft Actually Preserves in Teams
Teams data sits across multiple M365 services. Channel messages are stored in Exchange Online mailboxes (hidden, system-generated ones per channel). Private chat messages live in each participant's Exchange mailbox. Files shared in Teams live in SharePoint document libraries or OneDrive, depending on context.
Microsoft keeps Teams data available while the account or team is active, and for a grace period after deletion — usually 30 days for teams, 30 days for user accounts. After that, it's gone unless you had eDiscovery holds or Compliance Center retention policies applied before the deletion happened. Most organizations don't, or they apply them inconsistently.
Here's what makes Teams particularly tricky: a user leaving the company doesn't just delete messages — it can trigger cascading deletions of private chats that only that person participated in. If their account is deleted without a hold in place, those one-on-one conversations can vanish permanently within a month.
Retention Policies vs Actual Backup
Microsoft Purview retention policies are not backup. They're compliance tools that say "keep this content for X years" — but they don't let you restore a specific message to a specific channel on a specific date. They're designed for legal holds, not operational recovery.
If a team member accidentally deletes an entire channel — something that takes exactly one click — you have 30 days to restore it from the Microsoft Teams admin center. If you miss that window, or if you need to restore it selectively (just the messages from Q3, not the whole channel), you're stuck. Retention policies can surface those messages in eDiscovery, but you can't push them back into Teams natively.
Real Teams backup means point-in-time snapshots of channel structures, message history, chat threads, reactions, and file attachments — stored outside Microsoft's infrastructure — with the ability to restore specific items without a full tenant rollback.
What a Proper Microsoft Teams Backup Covers
North Brook Vault connects to Microsoft Graph APIs and captures Teams data across several dimensions: channel messages and replies, private chat messages (with appropriate admin consent scopes), meeting transcripts, channel files, tabs, and team membership records. Each backup run uses delta sync, so we're only pulling what's changed since the last snapshot rather than re-downloading the entire Teams history on every run.
The delta change tracking in Graph is genuinely good — it captures edits and deletions, not just new messages. If someone edits a message post-backup and then deletes it, both the original and the edited version exist in your backup store. That matters a lot for dispute resolution scenarios.
The Offboarding Risk Nobody Plans For
The most common Teams data loss event we see isn't ransomware — it's employee offboarding. An IT admin deletes a user account, doesn't realize the 30-day clock is ticking, and six weeks later HR wants to pull the departing employee's project conversations. Gone.
The fix is straightforward in theory: back up all Teams data for an employee before account deletion, or keep the account in a suspended state during the transition period. In practice, most IT teams are juggling too many offboardings at once to catch every edge case. Automated backup that runs continuously — not just on-demand — is what actually closes this gap.
If your organization runs Microsoft 365, Teams backup isn't optional anymore. The conversations happening there are operational records, often legally significant, and Microsoft isn't keeping them for you.