Cost calculation way for kb4322 (API for Teams Backup)

[Regnor]

MODERATOR EDIT: https://www.veeam.com/kb4322

I already wanted to give this as a feedback for the article, so perhaps we can have it updated with some details on licensing/costs. At the moment I'm rather clueless about how it works and the overview from Microsoft didn't clear up anything for me.

[Polina]

Hi,

VB365 will use Model B pricing https://docs.microsoft.com/en-us/graph/ ... quirements

[andrie]

The article mentions one important point:
• The Microsoft Graph Export API for Teams is currently not supported in Microsoft 365 US Government, Germany and China regions.

Will it still be possible to backup Teams data in Germany after the update to 6a without support for the new API?

[Regnor]

@Polina: So for now the new API is still free to use?

Note: model=B is free to use today; however, in the future, apps will pay based on the number of messages they consume.

@andrie: Germany refers to the old Microsoft Cloud Germany, which was separate from the regular Microsoft Cloud.
The first one isn't available any more and I'm also not sure if you could still have an active tenant there.
If your tenant is rather new and you didn't directly sign up for the german cloud in the past, then I would say you're not affected.

[Polina]

From what I know, the free period will be over by the time of the 6a release.

[Regnor]

Can we somehow measure how many API requests will be generated; initially and per incremental run? Perhaps there's a statistic why we could query.
At the moment it's hard to estimate the costs.

[Polina]

The cost is per message, not per request, and currently, we cannot offer any mechanism to estimate the number of messages within a team/channel to estimate costs.

[Polina]

@andrie

In the Germany region, the entire Teams backup has never been supported, so there won't be much difference with our without the new Export APIs.

[Regnor]

That will introduce some uncertainty. While I wouldn't expect the costs to be that high, not being able to calculate them before doesn't feel good.

[Mildur]

There are some teams usage report.
I not have tried it yet, but it should give you an idea on how many chat messages are send per day and currently exists in your tenant.

https://docs.microsoft.com/en-us/micros ... -reference

[Regnor]

I'll take a look at the reports. Thanks Fabian!

[cerberus]

Will this have any effect on how Exchange Online mailboxes are backed up and the changes in EWS? Will backing up EXO mailboxes go through this API that has added cost?

[Mildur]

Hi Mirza

This API is only for Teams Messages.
Backup for Exchange Online Mailboxes won't use this API.

Thanks
Fabian

[FrancWest]

The KB (https://www.veeam.com/kb4322) states:

Starting with Veeam Backup for Microsoft 365 6a, the protection of Teams data will no longer be enabled by default.

However, during the meeting it was mentioned and shown that only groupchats wouldn’t be backed up by default.

[Mike Resseler]

@FrancWest

Correct. We won't protect the other chatmessages yet through this export API. This is in the works but will take some additional time

[FrancWest]

Ok, but is the statement in the KB article correct? It states that it doesn’t backup teams by default, but shouldn’t this be only chat messages?

[Robvil]

Would it be possible already now when running version 5 to provide Microsoft with the information to get access?

[mamosorre84]

Hi, what if the organization doesn't have a subscription? How can Microsoft charge the cost?

[Regnor]

Ok, but is the statement in the KB article correct? It states that it doesn’t backup teams by default, but shouldn’t this be only chat messages?

I also think the statement could be a bit more specific.

Would it be possible already now when running version 5 to provide Microsoft with the information to get access?

Yes, you can already fill out the form now and request access.

[Polina]

Hi All,

@FrancWest Only Teams message data won't be protected by default; the KB text will be updated today. And thank you for noticing it.

@Robvil Yes, you can apply for the access in advance.

@mamosorre84 I'm not sure I understand the question correctly... Do you mean Teams subscription, or something else?

[mamosorre84]

Hi Polina, I mean if a client buy only Office 365 subscription, he will pay Teams backup within the same subscription or he must have another subscription where charge the new cost?

[ericksonj]

The article mentions one important point:
• The Microsoft Graph Export API for Teams is currently not supported in Microsoft 365 US Government, Germany and China regions.

Will it still be possible to backup Teams data in Germany after the update to 6a without support for the new API?

Will those of us on GCC be able to backup Teams chat after the 6a update?

[Polina]

Teams Export APIs are not (yet?) available in the GCC and GCC High regions. Organizations from these regions will be able to continue backing up chats with the old method (there will be a special communication on how to arrange it).

[johan.h]

The way I understand it is that the cost will show up in the Azure bill associated with the M365 subscription for which the Teams Export APIs are used.

[Regnor]

@FrancWest

Correct. We won't protect the other chatmessages yet through this export API. This is in the works but will take some additional time

The more I read it the more it confuses me, so sorry for asking again.
Does your statement mean:
a) with v6a we can "only" backup public chat messages via the Graph API but no longer user chats
b) with v6a we can "only" backup public chat messages via the Graph API, and user chats will still be backed up via EWS
and if b) will user chats not get backed up after 1.10. if the EWS way gets deprecated?

[Mike Resseler]

@Regnor

It's a) which is the correct answer. Today we do protect those user messages but you can only restore them as separate MSG messages. In the future, we want to restore them:
a) Like a html page as we do today for the public chats
b) through the future import-API (which isn't ready yet) to the original location.

I hope it is clear now.

[Regnor]

Yes it is, thanks for the clarification Mike!

[RalfH]

A question from my side about the costs (respectively on how backing up chat data with the Teams Export APIs works):
The Teams chat backup job will be running once a day. If, for instance, on day one 10.000 messages were present & backed-up and on the next day 500 additional messages were present & backed-up - will Microsoft then charge a customer with $0.00075 for 10.500 or 20.500 messages?
(I guess I already know the answer)

[Mildur]

Hi

10500, because the data is only downloaded once and not twice.

Thanks
Fabian