Roadmap Office 365 // Teams

[hschimpf]

Hi,
we are planning to use Veeam backup for O365 to backup Microsoft Teams.
I already followed up the common blogroll and could establish some successfull backups.

The most painpoint is the restore Prozess. Chat files for example are only restoreable by running some Manual Tasks. The Tasks worked for me but is not very user friendly. Especially that I can see during the restore process the Chat Content and even Change the Content of the Chat I want to restore. I cannot believe that our privacy team will allow this.

Restoring OneNote is not possible due to modern authentication restriction. That feature will be disabled by Microsoft. https://bp.veeam.com/vbo/guide/buildcon ... ation.html

I heard that the Version 5 will be more integrated. So what I Need is a valid Roadmap for Veeam O365 for the Features and the usecase Microsoft Teams.

Thank you

[Polina]

Hi hschimpf,

The documentation on features coming in VBO v5 will be available closer to the release date (which will be announced later), but to give you an idea of what to expect I'd suggest watching this sneak peek created by one of Veeam SEs (note though that it's in Spanish). It's not an official Veeam's product video, but it covers the upcoming Teams support really nicely

Thanks!

[hschimpf]

In the Video I can see, that he is useing legacy authentication for restore. The legacy authentication is a feature that will be disabled by micorosoft in in the future.
Are the Features working with modern authentication too? https://bp.veeam.com/vbo/guide/buildcon ... ation.html

[nielsengelen]

We support both already with 4c and this will also be the case with Teams.

[hschimpf]

Full support? In 4c especially OneNote Restore will not work with modern authentication. Especially this is a must have feature in our Company.

[nielsengelen]

Unfortunately, this is due to limitations within the API's by Microsoft and we can't say if this will be resolved by then.

[cfizz34]

Will backing up a team require a license?

[Polina]

Hi Chad,

It's going to be licensed similar to SharePoint sites - a team itself will not require a license.

[Grime121]

I’m curious as to why you feel the need to back up Teams. Are you not comfortable with the amount of data replication/redundancy, and backups that MS already provides?

[Mike Resseler]

Hi Grime121,

The data you have in your tenant is still your own responsibility. As with everything else, we feel the best approach is still using both as layers of defense. Yes, Microsoft has ways to recover from thrash cans, there is versioning and so on. Which is great, and you should use it for sure. However, you have to think and decide for yourself, as a company, if you need additional protection. Are there legal reasons to keep data for X years, what if the data has been deleted longer than Microsoft keeps. And so on. It's kind of the same discussion we had years ago when the Exchange team On-premises said that they had DAG and lagged database and didn't need backups anymore. In reality it was still needed for various reasons.

Hope this explains our point of view a bit.

Thanks
Mike

[YouGotServered]

@Grime121,
In addition to Mike's comment, it's also about risk. Some organizations are not willing to accept the risk that a vendor (Microsoft in his case) has full control of their data, and that they have none of the control. The same can be said for Exchange and SharePoint data - my clients would flip if I told them "Yea, Microsoft has got it, we don't have to worry about it."

It's cheap, and easy, so why not?