Because it sits on top of so many Microsoft 365 components, Teams is easily the hardest Office 365 workload to backup. You can try to backup Teams by copying its compliance records stored in Exchange Online, but that’s only a partial (and bad) solution that utterly fails to take the full spectrum of Teams data into account.
The topic of Teams tenant-to-tenant migration generated a lot of reaction after an article published last week. This lead to a chat with AvePoint, who have a product similar to BitTitan. What was interesting is that AvePoint use the same API to backup Teams. Although the backup isn’t as functional as you want and definitely not designed for backups, you do end up with data backed up that can be restored. The solution is imperfect, but it is available now.
A new report commissioned by Microsoft explains how Exchange Online and the Security and Compliance Center meet the electronic records requirements of regulatory bodies like the SEC and FINRA. Within the report, there’s some news about changes to the way that Office 365 handles Teams compliance records stored in Exchange Online. And after all that, we consider how some backup vendors treat Teams compliance records as equivalent to the data stored in the Teams Azure services.
The internet makes it easy to find material to read about technical topics. Unfortunately, a lot of content is rubbish. In this post, we compare two recent technical articles and explain why we think one marketing post is good and the other isn’t up to scratch.
Do Office 365 tenants need to take backups of Exchange Online, SharePoint Online, Teams, Planner, Yammer, and the other data that they accumulate. I don’t think they do in most cases, and the problem is exacerbated because most backup solutions sold for Office 365 can’t deal with the full suite.