Forum Discussion
Issue with Downloading Teams Sticker via Graph API - HTTP 400 Bad Request
Do anyone encounter a similar issue?
Hi Kevin,
We are experiencing a similar issue. In our environment, with two teams, we encounter the same error when backing up Teams chats using Veeam Backup for Microsoft 365, which accesses the data via the Graph API. The first occurrence was on 07.03.2025 and the second on 28.03.2025 for the other team. Following your hint about stickers in the headline, I tried to back up a test team with a sticker in a chat but couldn't replicate the issue. The backup with the sticker was successful. Thus, the issue may not be exclusively related to stickers. Veeam support advised us to file a support case with Microsoft 365 Support, but we haven't done so yet. Have you been able to resolve the issue already?
I have posted a reply earlier, but it seems the reply is missing. So I post the reply again as follows:
Unfortunately, we are still experiencing this issue in our environment as well. We previously opened a support ticket with Microsoft, but they informed us that the problem falls outside their support scope and recommended that we post about it here instead. So far, we have not received any response or resolution.
We also filed a support case but we have a contract to use the additionally paid support service. I had a session with a Microsoft supporter and collected some information etc. It looks like Graph API works as intended because there's nothing to download for something without content (response in Graph Explorer):
Meanwhile I noticed one thing in common of two teams which are affected by this error: Both have emails in channels and embedded pictures / logos. I was able to reproduce the error by forwarding an email with embedded logo to a channel and then tried to backup the team again by Veeam which leverages Graph API. Same error: 400 Bad Request. For me it seems like a bug. I provided the findings to the existing case and currently waiting for a reply.
Unfortunately, we are still experiencing this issue. We have also filed a support ticket to Microsoft, and they replied that it's out of their scope and cannot provide any help, suggesting us to post a community discussion here. Therefore we are still waiting for answers from Microsoft. :(
