Microsoft will not put your deleted Teams messages back, and most backup products cannot do it the way you expect either.
Microsoft Teams backup is sold on capture. Capture was never the difficult part. The gap shows up on the day you need a recovery, when chat history lands under an administrator’s name, stamped with today’s date, in a team nobody recognises.
Microsoft controls the route back into Teams, and that route carries conditions no datasheet mentions.
Summary:
- Microsoft 365 Backup leaves Teams messages out of scope.
- Deleting a team starts a 30-day clock you cannot extend.
- Retention policies were never designed to put messages back.
- Every vendor restores through one Microsoft API, and it is throttled.
- Restored posts often arrive under the wrong name and the wrong date.
Teams Keeps Your Data in Four Separate Places
Teams is a front end. The data sits underneath it, in stores with different owners and different clocks.
| What | Where it lives | Native recovery |
| Channel messages | Hidden folder in the group mailbox, Exchange Online | None by default |
| Chats and group chats | Mailboxes of the participants | None by default |
| Channel files | The team’s SharePoint site | Recycle bin |
| Files shared in a chat | The sharer’s OneDrive | Recycle bin, up to 93 days |
Private and shared channels complicate it further. Each one gets its own SharePoint site, separate from the team’s.
Cover three of the four, and the dashboard still reports full protection.
Microsoft 365 Backup Leaves Teams Messages Out
Microsoft’s native backup service covers three workloads: SharePoint sites, OneDrive accounts and Exchange mailboxes. Teams messages are not among them.
The trap is that channel posts do live in a mailbox, so mailbox coverage sounds like enough. It is not, and the vendors are explicit about why. Veeam names the TeamsMessagesData folder of the group mailbox as excluded content. That folder is your channel history.
Where Microsoft’s obligation ends, and yours begins, is set out in our guide to the shared responsibility model.
You Have 30 Days to Recover a Deleted Team
Deleting a team starts a countdown that cannot be extended. The team sits in a soft-delete state for 30 days. Once that window closes, a retention policy on channel messages is the only native mechanism that will have preserved anything. Deleted channels run their own 30-day clock, reachable through Manage team.
Private channels behave worse. Deleting one removes the connected SharePoint site as well, taking every document stored there.
Two cheap controls buy you time:
- Two owners on every team. A single owner leaving is one of the more common routes to an accidental deletion.
- An audit alert on team deletion. The news then reaches you on day one rather than day 31.
Neither is a backup, and both buy you the time to use one.
Retention Policies Will Not Put Messages Back
This is where the budget gets misdirected. A retention policy answers to your regulator. It does almost nothing for your recovery time.
Delete or edit a message under a retention policy, and the item moves to the SubstrateHolds folder, where it stays searchable through eDiscovery for the retention period. Searching is where the capability stops. Held messages can be exported to a file. Returning them to a live team is not something the platform offers.
There is a sharper edge. Messages removed by the retention policy itself cannot be recovered at all, which makes the control written to protect the record capable of destroying it on schedule.
Every Vendor Uses the Same Door Back In
Any product that puts messages back so they look like the original Teams history uses one route: Microsoft Graph’s import path. Microsoft publishes the conditions attached to it, and those conditions explain most of what goes wrong on restore day.
The target channel or chat enters migration mode first. While that runs, the Teams client shows users a banner saying migration is in progress and messages may appear out of order. Your recovery becomes visible to the business as it happens.
Only the application that opened the session can import into that thread, and no other tool can touch it until the session completes.
Where the import path stops:
Sovereign clouds are a harder stop. Migration mode for channels is unavailable in US Government L4, US Government L5 and the China cloud operated by 21Vianet, so check availability before shortlisting.
One Number Decides Your Teams Restore Time
Import runs at five requests per second, per channel. That is roughly 18,000 messages an hour, and it is a ceiling rather than a target.
Parallel jobs shorten a tenant-wide restore by working across channels. Inside a single channel, nothing speeds it up. Your busiest channel, therefore, sets your recovery time, and it is usually the one the business is asking about.
Tenant-wide throughput figures do not answer this. Ask for measured per-channel numbers, then apply them to your largest team and compare the result against the recovery target in your continuity plan. Where those targets should differ by scope is covered in granular restore vs full-tenant recovery.
Why Restored Messages Arrive Under the Wrong Name
Fidelity loss is the complaint that lands a week after everyone congratulated the team on a clean restore.
Published vendor documentation shows how wide the gap runs. Druva restores group mailbox posts from the administrator account that configured the application, stamped with the time the restore was triggered. The original sender and delivery time appear inside a metadata block in the message body. The words survive. The record of who said them and when becomes a footnote.
Destination matters just as much. Several products rehydrate chat into a newly created team in read-only form rather than returning history to its original home. Ask what happens before you rely on the promise.
Four things deserve a test: reply threading, reactions, mentions and edit history.
The Per-Message API Charge Disappeared in 2025
Cost has been the standard excuse for leaving Teams half-protected. It no longer stands up.
Since 25 August 2025, the Teams APIs used for export have stopped being metered. No billing configuration is required, and the model parameter is ignored when supplied. Backup applications previously fell under model=B, received no seeded capacity, and paid $0.00075 per message.
Plenty of published guidance still quotes that figure. Treat any vendor leading with export economics as working from an outdated picture.
Why Restored Messages Arrive Under the Wrong Name
Fidelity loss is the complaint that lands a week after everyone congratulated the team on a clean restore.
Vendor documentation shows how wide the gap runs. Druva restores group mailbox posts from the administrator account that configured the application, stamped with the time the restore was triggered. The original sender and delivery time are written into a metadata block inside the message body. The words survive. The evidence of who said them and when becomes a footnote.
That distinction matters beyond tidiness. A conversation restored under an administrator’s name, dated the day of the recovery, is weaker evidence in a dispute or a regulatory request than the original ever was.
Destination is the second question. Several products rehydrate chat into a newly created team in read-only form rather than returning history to where it came from. Ask which one you are buying.
Test all four before you sign: reply threading, reactions, mentions and edit history.
Read the Answers, Not the Feature Matrix
Every Teams backup vendor will say yes to coverage. The useful conversation starts when you ask what the yes is made of.
Rows two, three and four decide most shortlists. Anything a vendor cannot demonstrate in a live restore is a claim rather than a capability, which is the same test that underpins Recoverable AI’s case for an independent Microsoft 365 backup.
Test the Restore Before You Need It
Teams recovery is governed by write-side limits you cannot negotiate and a fidelity gap you can measure this week. An afternoon spent restoring your busiest channel will tell you more than a full procurement cycle.
Pick your largest channel and record four things: how long the full restore took, how long the import banner stayed visible to users, whose name appears on the restored posts, and what you had to rebuild by hand afterwards.
Those four figures are what an auditor asks for and what a board paper can use. Guesses are not.
Recoverable keeps an independent copy of your Microsoft 365 data outside your tenant, so the test also shows you what recovery looks like on the day the tenant itself is the problem. Setup takes minutes, and the first backup completes the same afternoon.
Start a 30-day trial. Then restore a real channel, time it, and write the number down.
Microsoft Teams Backup: Frequently Asked Questions
Can I recover deleted Teams messages?
No. Teams has no recycle bin for chat messages. Once a message is deleted in the client, neither the user nor an administrator can restore it through the app.
Recovery depends entirely on whether a retention policy or legal hold was already in place. Where one exists, an administrator can search eDiscovery and export the content to a file. What you get back is a file of messages. Nothing goes back into Teams. Tell staff to report accidental deletions immediately with the chat name, the participants and the approximate time, because the available options narrow quickly.
How do I back up Teams data for a deleted user?
Run the backup before you remove the licence. Backup tools read mailboxes through Microsoft’s APIs, and most cannot process a mailbox once its licence has been withdrawn. Veeam requires a valid Microsoft 365 licence on a user mailbox for backup to work. Reclaim the licence first, and the leaver’s chat history may become unreachable. Add a step to offboarding: confirm a completed backup, then release the licence. Regulated firms should also check how long leaver records must be held under their own retention obligations.
Does Teams backup slow down Microsoft 365?
It can, during large jobs. Microsoft throttles API traffic, and Veeam reports a limit of 150 MB per mailbox every five minutes even after tenant throttling is relaxed. Running OneDrive, SharePoint and Teams policies simultaneously can slow jobs or break them because those workloads share infrastructure underneath. Stagger the schedules. Initial full backups generate the heaviest load, so run the first pass outside working hours. Exchange policies usually sit alongside other workloads without trouble. Monitor job duration across the first fortnight and adjust your window accordingly.
Can Teams chat history be migrated to another tenant?
Not into Teams itself. Microsoft’s import path only accepts content originating in the tenant the application authenticated against, and federated content is excluded outright. The practical approach is to export the message data and keep it as a searchable archive, then restore files and mailbox content into the new tenant. Several backup products support cross-tenant restore for SharePoint, OneDrive and mailbox data. Confirm the specifics with your vendor well before the migration date. Timelines matter here, since the source tenant usually gets decommissioned on a fixed date and the export cannot be run afterwards.
Are Teams meeting recordings backed up?
Only if the sites and accounts holding them are included in your backup policy. A channel meeting saves its recording to the team’s SharePoint site. Every other meeting is saved to the OneDrive of whoever started the recording. Personal OneDrive accounts are often excluded from site-level policies, which is where recordings quietly fall through. Retention labels applied to recordings can also delete them on a schedule. Confirm where recordings land in your tenant before assuming they are safe.