created a backup job for this Office 365 organization.added a new Office 365 organization with AAD app and Global Admin account credentials ( docs).configured a custom AAD app (with the right permissions).added a new Backup Repository which offloads the backup data to the previously created Object Storage Repository.configured Veeam Backup for Office 365 (not so hard, if you know what you are doing and you’ve read the official docs).(it’s a “Next-Next-Finish” type of installation, hard to get it wrong) (good people at Exoscale/A1TAG/A1.digital/A1HR provided me credits, so… why not?!) created an Exoscale SOS bucket for my backups.
(good people at Veeam provided me NFR license for it, so I’ve used it instead of Community Edition) (good people at Microsoft provided me Azure credits, so… why not?!)
And even better – you can use any S3-compatible storage to do the same! How cool is that?! So, this means that you can take Amazon S3, Microsoft Azure Blob Storage or even IBM Cloud Object Storage and use it for your Veeam Backup for Office 365. This feature is “ object storage support“, as you may have guessed it already from the title of this fine post! I would like to focus on one of the features of the new Veeam Backup for Office 365 v4, which was released just the other day. I’m not going into the lengthy and exhausting discussion of why you should take care of your data, even if it’s stored in something unbreakable like “the cloud”, at least not in this post. Are you backing up your Office 365? And… why not? ?