365 Backup · Teams and SharePoint

The work stoppedliving in themailbox long ago.

Project files, minutes and decisions live in Teams and SharePoint. Backing up only the mailbox covers the smaller half. Conbool puts channels, files and document libraries on the same schedule.

Where collaboration quietly disappears

Four ways content vanishes from Teams and SharePoint.

A team is dissolved

Channels and the files attached to them go with the team. Whatever is still needed usually surfaces weeks later.

Tidying up a library

A document library is reorganised, folders are removed, and with them versions nobody can reconstruct.

Synced folders carry the damage

Whatever is deleted or encrypted locally propagates into the library through sync. There it looks like an intended change.

The recycle bin has two stages and an end

The site collection recycle bin expires as well. After that only your own backup helps.

How channels and libraries are captured

The same control surface as for mailboxes, not a second tool.

1. Select sources

You decide which teams and which sites belong in the backup and add more later without a new setup.

2. Capture on a schedule

Channels with their files and the document libraries of your sites run on the same plan as the mailboxes.

3. Restore precisely

One folder, one file, one state. The restore works at the level where something is missing, not across the whole site.

Project North Seacaptured
Specification v4.docx3 states
Costing.xlsx5 states
Minutes 14 July.pdfdeleted

Deleted files stay reachable in the captured states, even once the team has been dissolved.

Channels and libraries

Also what does not live in the mailbox.

A channel's files technically live in SharePoint. Capturing both together saves hunting for the right storage location when something is missing.

Channels together with their files

Document libraries including folder structure

Older states even after the recycle bin expires

Restore at file level rather than whole sites

What counts here

Six points for collaboration.

Channels together with their files

A channel's files technically live in SharePoint. Capturing both together saves hunting for the right storage location.

Document libraries of team sites

Site libraries are captured including their folder structure.

Several states

Every run is preserved. You restore from the point where the file was still intact.

Independent of the recycle bin

The backup is not bound to the site collection deadlines: whatever existed at the time of a backup stays available after the recycle bin has expired.

One schedule for everything

Mailbox and online archive, OneDrive, SharePoint with its lists, channels, chat histories, Planner and Entra ID in one control surface instead of eight separate tools.

Roles and audit trail

Who may restore is defined, and every restore stays traceable.

Built in tools and your own backup

What remains possible in each case.

 
With Conbool
Microsoft 365 alone
Restore files from a dissolved team
yes
for a limited time only
Choose an older state of a file
yes
via version history where enabled
Restore after recycle bin windows close
yes
no
Channels, chats and libraries on one schedule
yes
no
Storage outside the Microsoft environment
yes
no

Statements about Microsoft 365 follow the publicly documented behaviour of recycle bin and version history. Your tenant's settings apply.

Frequently asked questions

Is SharePoint version history not enough?
It helps with individual changes to an existing file. Once the file itself is gone or the library was removed, it no longer applies.
Are private chats captured as well?
Yes, but separately from the channels. Private and group chats belong to the participating users and are captured per user as a protection unit of their own. The Teams chat backup page covers the details.
What happens when a team is deleted?
The content remains in the captured states for the period you set, whether or not the team still exists in the tenant.
Are lists and customisations included?
Yes. Alongside the document libraries, SharePoint lists are captured as well and can be written back. Individual site customisations such as scripts and page layouts are not part of the backup.
Does this help against ransomware?
Yes, because older states sit outside the affected environment. You restore the state from before the incident instead of relying on the platform.
Does every site need its own setup?
No. Selection is central, and further sites and teams can be added later without rebuilding anything.

Related solutions

See a restore on one of your own teams

We connect a test tenant and bring a file back from a channel together with you.