Microsoft 365 backup isn't optional, and KPMG proved it. One admin changed a Teams retention policy and wiped out the chat history of 145,000 employees.
This is an encore episode of The Backup Wrap-Up. We brought it back because it's one of the most popular episodes we've ever done, and not just in downloads. People watched and listened to most of it, and a lot of them came back for more. It kicks off our seven-part Cloud Disasters encore series.
I recorded a new intro for this one, because November's massive Microsoft outage took down Outlook, Teams, and Copilot in more than 70 countries. That was bad. But an outage is the good scenario. Your data comes back. At KPMG, it didn't.
Here's what happened. Back in August 2020, a Microsoft 365 admin at KPMG tried to remove one user's private Teams chats. To do that, they had to change a retention policy. Instead of moving one person to a new policy, they edited the policy everybody was in. Poof. Every private chat for 145,000 people, gone. And Microsoft couldn't do a thing about it, because what happened is a feature, not a bug.
The irony is that retention policies are the exact feature some people point to as the reason you don't need Microsoft 365 backup. Prasanna and I explain why that argument falls apart. Retention policies are built for compliance and e-discovery. They're good at keeping data you're supposed to keep, and they're good at making data disappear on schedule. What they can't do is restore your stuff to a point in time. Get them wrong and they'll delete everything.
In this episode, we cover:
- How Microsoft 365 retention policies work, and why there are 25 pages of documentation on one feature
- The retention lock checkbox that would have saved KPMG's old chats, and what it does to your storage bill
- Why this could just as easily have been every email or every SharePoint file in the company
- What KPMG should have done, from having a real backup to having a second set of eyes on big changes
- The legal mess when "our admin made a mistake" lands in the middle of pending litigation
- Why humans are still the number one reason we back up, 30 years later
- A Valentine's Day phishing test that made an entire company feel loved for about five minutes
If you're on the fence about Microsoft 365 backup, watch this one. If you're not on the fence, send it to the person who is. The cloud isn't magic. Somebody still has to back it up, and that somebody is you.
🎧 Listen to the podcast: https://www.backupwrapup.com/microsoft-365-backup-kpmg-disaster/
📕 Learning Ransomware Response & Recovery (O'Reilly): https://www.oreilly.com/library/view/learning-ransomware-response/9781098169572/
🛡️ What Mike and I are building: https://www.stopransomware.com
CHAPTERS
00:00 Encore intro: an outage vs. losing your data
01:34 Imagine every Teams chat disappearing
03:22 Welcome to the show
05:24 Why hardly anyone backs up Microsoft 365
09:01 What happened at KPMG
11:29 How Microsoft 365 retention policies work
15:19 Retention is for compliance, not recovery
18:08 How the deletion probably happened
21:51 What KPMG should have done
24:27 What Reddit and The Register had to say
26:27 It could have been email or SharePoint
28:04 Why not just delete the user?
29:07 Adverse inference and the legal fallout
31:24 The cloud isn't magic
32:49 Humans are still the #1 reason we back up
33:52 A Valentine's Day phishing test gone wrong
36:16 Advice for smaller companies