The shared responsibility model, the 3-2-1 rule, and the restore test nobody runs.

Takeaways first, then the detail, then the sources.
The desk answers questions about this for free, 08:00 to 18:00.
0113 216 6777Microsoft and devices · 5 min · written 30 October 2026 · by the IT-360 team · sources at the end
Microsoft's service agreement is clear: it is responsible for the availability of the service, and you are responsible for your data. Recycle bins and retention policies help for a few weeks; they are not a backup. A leaver's mailbox deleted by mistake. A SharePoint library overwritten by a sync error. A ransomware attack that encrypts every file in OneDrive. All of these are outside what Microsoft will restore for you. That is why Microsoft 365 backup is your job, not Microsoft's.
Three copies of the data, on two different kinds of storage, with one somewhere else. For Microsoft 365 that means three copies: the live tenant; a backup held by a separate provider in a separate cloud; and, for the business-critical sets, an offline or immutable copy that ransomware cannot reach. A proper Microsoft 365 backup runs several times a day and keeps versions for as long as your retention needs. For most businesses that is years, not weeks.
A Microsoft 365 backup that has never been restored is a hope. Once a quarter we restore a mailbox and a SharePoint library for each client and record how long it took. The record goes in the monthly report, and it is the first thing an insurer or an auditor asks to see. The Backup and Recovery page shows what the report looks like.
Further reading on Insights: Passkeys and MFA and Cyber Essentials in 2026.

Helpdesk 0113 216 6777, Monday to Friday 08:00 to 18:00.