/Veeam Backup for Microsoft 365 Teams API: What is coming

Veeam Backup for Microsoft 365 Teams API: What is coming

There are some months now that we know that Microsoft will change and disable basic auth on individual mailboxes on 1 of October 2022 “Today, we are announcing that, effective October 1, 2022, we will begin to permanently disable Basic Auth in all tenants, regardless of usage, with the exception of SMTP Auth.”

These changes will, of course, impact how backup tools backup Microsoft Teams, particularly Veeam Backup for Microsoft 365. But could be easy to bypass and find another way to do the backup, the problem is more complex, and it comes with an extra cost for Microsoft customers. To backup Microsoft Teams chats, Veeam Backup for Microsoft 365 is protected/back up via Exchange Online. Regardless of the backup tool, you are using.

To understand Microsoft plans and the rest of this blog post and the impact on Microsoft customers is essential to mention that Veeam is protecting Teams chats as one, not individual chat messages or groups. So for that protection, Veeam Backup for Microsoft 365 reads a hidden folder within Exchange Online called ‘TeamsMessagesData’. Regardless if the customer is using Basic or Modern Authentication.

Veeam Backup for Microsoft 365 Teams API: What is coming

What is next?

Microsoft is restricting access to the ‘TeamsMessagesData’ hidden folder in the future(October 2022?). By doing this, Veeam Backup for Microsoft 365 loses the way it works and how to access the data inside Teams. Microsoft stated that in the future(and today), the only supported method for accessing Teams data is via the Teams Graph APIs. So they are saying that accessing the hidden folder ‘TeamsMessagesData’ is not supported and is only through Teams Graph APIs.

From a security point of view, I understand that Microsoft restricts data access and needs to start using Teams Graph APIs. The problem is the after.

  • The first problem when using Teams Graph APIs

Any access to Teams Graph APIs requires additional validation by Microsoft before approval. Some information about that is HERE.

At the moment, it takes a minimum of 2 weeks for that validation and approval. So if anything was not done correctly in your form, you wasted 2 weeks(at least) and needed to do it all over again and wait again from a business perspective and data backup. This is impracticable. Companies cannot wait all this long to backup their data. Access to Protected APIs with Azure Subscription request HERE.

Note: Of course, we hope that Microsoft reduces the time for these approvals.

This means that all backup tools, vendors, and customers must adapt their tools and ways of working for this new reality.

After you receive your approval from Microsoft, these are the API permissions that your applications need to have:

    • Chat.Read.All
    • ChannelMessage.Read.All
    • User.Read.All

Note: You should always get the approval before you plan to upgrade your Veeam Backup for Microsoft 365 to the new Veeam Backup for Microsoft 365 6a version, which will now work with this new process. Check Veeam KB regarding this subject.

  • The second problem when using Teams Graph APIs, and its costs.

Using Teams Graph APIs has a cost. So if your backup tool will use(and needs to) Teams Graph APIs to backup your business data, this will come with a price, and that cost is per chat message inside your Teams. Yes, you will need to pay for each message you are backing up. The cost per message is 0,00075$

In the next board, you can see Microsoft cost models to use Microsoft Teams APIs in Microsoft Graph.

Veeam Backup for Microsoft 365 Teams API: What is coming

You can check HERE Microsoft license models.

Not much, right? Wrong!

Some examples:

If you send a message for the entire organization, let us say @all, and I will say only 10.000 messages. Is only one message, but there are 10.000 receivers. Yes is just one message and one chat, but let us say 1.000 private replies; we have 1.000 chats and a new 1.000 messages. Even is not 10.000 but only 1.000. Or even 10.000 replies. So this message to back up will cost you 7,5$. Extreme? Yes, but it could happen. Multiple that for many times a month, to during a year.

Note: Only chat private rooms messages counts.

Another example: You have 10.000 email accounts and 10.000 Teams users. A typical user sends an average of 800 messages a month. If you multiply that by 10.000, you have a monthly cost(on your backups) of 6.000$. Again, multiply that by 12 months, and the costs are significant for an organization to back up their Teams chats.

Final example: Your company has 100 Teams meeting a month, this is a minimal number for today’s reality, but during those meetings, people chat and send a message. Each of those message counts as one message to back up and costs 0,00075$.

All these costs will be charged to your Microsoft 365 accounts.

So what happens in the next Veeam Backup for Microsoft 365 6a version?

  • By default, chat backup will be off.
  • The old backup method will also be off.
  • Customer needs to decide what to protect and what is not to protect.

Example of how options should be working on the new Veeam Backup for Microsoft 365 v6a.

Note: Until is launched, options could be different.

Veeam Backup for Microsoft 365 Teams API: What is coming

Note: There are some scripts in Github from Tony Redmond that you can run to check how many messages per user you have in or organization. Check it HERE. Run that before you decide to enable or not backups on Teams. This will help you understand the costs for your organization when deciding to back up Teams chat.

In the next board, we see Microsoft 365 Shared Responsibility Model, which is shared between Microsoft and customers (together with your vendor Backup tool), but now you need to add an extra column to indicate the cost that will be on customers only.

Conclusion:

These changes on Microsoft Teams APIs in Microsoft Graph license costs will not only impact backup tools but will also impact a lot of other tools that customers use. Even internal tools.

In my examples, chat/message costs are the reality today; Microsoft could and is pretty sure it will change the way this costs because this is not practical for big organizations. This will have a significant impact on their Disaster Recover budged.

As I said above, Veeam Backup for Microsoft 365 6a will come out in August, so be very careful before upgrading. But if you upgrade your Veeam Backup for Microsoft 365, it will be disabled by default. Double-check what model you want to use and if you really want to backup Teams chats. Do not forget you have until October 2022 to decide.

Let us wait and see if Microsoft is listening to their partners and, most import, their customers, and change this way of working, and most importantly, make some changes to more moderate costs.

Share this article if you think it is worth sharing. If you have questions or comments, comment here, or contact me on Twitter.

©2022 ProVirtualzone. All Rights Reserved
By | 2022-06-23T18:56:07+02:00 June 21st, 2022|Backups Posts, Veeam|0 Comments

About the Author:

I have over 20 years of experience in the IT industry. I have been working with Virtualization for more than 15 years (mainly VMware). I recently obtained certifications, including VCP DCV 2022, VCAP DCV Design 2023, and VCP Cloud 2023. Additionally, I have VCP6.5-DCV, VMware vSAN Specialist, vExpert vSAN, vExpert NSX, vExpert Cloud Provider for the last two years, and vExpert for the last 7 years and a old MCP. My specialties are Virtualization, Storage, and Virtual Backup. I am a Solutions Architect in the area VMware, Cloud and Backup / Storage. I am employed by ITQ, a VMware partner as a Senior Consultant. I am also a blogger and owner of the blog ProVirtualzone.com and recently book author.

Leave A Comment