For me this has been quite surprising news. With beginning of version 6a of Veeam Backup for Microsoft 365, a different API will be used for backup of public Teams channel messages. The current way with EWS is getting deprecated by Microsoft and in the future “Microsoft Graph Export API for Teams” has to be used.
What does this mean for VB365 users?
With version 6a VB365 will no longer by default protect Teams data. In order to still being able to backup public Teams channel messages, you will have register for the “Graph Export API”. This process can take up to two weeks and in addition the usage of the Graph Export API can cause additional costs (by Microsoft).
How do you register for the Graph Export API?
The registration process is described in detail in the following KB article: https://www.veeam.com/kb4322
What costs will be expected?
Unfortunately I can’t really say what costs will be generated by Teams backup. There’s a dedicated page from Microsoft on the licensing/payment but still I’m not sure what we can expect and how the usage is actually billed.
I hope we’ll see some more detailed information on this topic in the near future, or anyone else in the community will be able to clear this topic.
What happens if I don’t switch to the new API?
We can expect that after upgrading to 6a and not registering for the new API, VB365 will no longer be able to backup Teams at all.
Failed to process team: <teamname> Invoked API requires Protected API access in application—only context when not using Resource Specific Consent. Visit https://docs.microsoft.com/en—us/graph/teams—protected—apis for more details.. The remote server returned an error: (403) Forbidden.
So if you don’t want to use the new API, you will lose the ability to protect Teams.
What do you think about this?
This topic in general will probably cause us some headache. Not only is the initial process of protecting your data getting more complicated, but also you will need to calculate some additional costs which weren’t there before (and without getting any additional value). I’m also sure more and more APIs will switch to a paid model.
For Microsoft Office 365 users > many interesting news came from Microsoft Build 2021 but this particular one has caught my eye (search the post for Microsoft Graph Data Connect). As I read it, the Graph API where Microsoft has been adding all missing Office 365 data access capabilities will now be offered as a metered service. The pros of Graph API are that it is a more secure and higher throughput connector. However, it is now turning into pay-for-access API and as I understand, there are no alternative ways to retrieve at least some of the Office 365 data [for example for backup purposes]. I think you can see where this is going: not only you're already paying to put your data into Office 365, but now Microsoft wants to charge for retrieving this data too. Oh well, let's see how this idea turns out for them. I personally think it's a mistake because even if the price is right, it adds the perfect FUD topic for competing platforms to use right at the peak of the mass exodus from on-prem Exchange.