Forum Discussion
Since Aug 22nd we can't save any Side Panel tabs
Hello AdelYerro mmati ,We got the below information from Enginering team that,
This is happening because the new /meet/<guid> links no longer expose the 19:meeting…@thread.v2 id, but the tab install path they are using relies on the meeting chat thread id.
To get this working, the threadId could be resolved through Graph (/onlineMeetings → chatInfo.threadId) and then passed into POST /chats/{threadId}/tabs.
how you currently retrieving the threadId?
The threadId is known to the side panel, we don't rely in the meeting link to extract it at all.
I also added in my post a direct call I did with graph using a known threadId with both apps and both failed server side.
To be more precise when the side panel fails to install Teams is doing the following call:
https://teams.microsoft.com/api/chatsvc/amer/v1/threads/19%3Ameeting_XXXXXXXXXXXXXXXXXX%40thread.v2/properties?name=tab%3A%3Axxxxxxxxxxxxxxxx
And fails, server side.
Doing the direct approach then doing a POST to /chats/{threadId}/tabs, also fails. Above you can see a server side bad gateway response from graph when doing exactly what engineering answered:
curl -s -X POST "https://graph.microsoft.com/v1.0/chats/$CHAT_ID/tabs" \
-H "Authorization: Bearer $ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"displayName": "Website - test",
"email address removed for privacy reasons": "https://graph.microsoft.com/v1.0/appCatalogs/teamsApps/com.microsoft.teamspace.tab.web",
"configuration": {
"entityId": null,
"contentUrl": "https://www.microsoft.com",
"websiteUrl": "https://www.microsoft.com"
}
}' | jq .
{
"error": {
"code": "BadGateway",
"message": "Failed to execute backend request.",
"innerError": {
"date": "2025-08-22T04:02:36",
"request-id": "ece5590e-f23f-4780-a4a6-20c1b2f0d0f3",
"client-request-id": "ece5590e-f23f-4780-a4a6-20c1b2f0d0f3"
}
}
}
Please review the request with this information:
{
"error": {
"code": "BadGateway",
"message": "Failed to execute backend request.",
"innerError": {
"date": "2025-08-22T03:36:08",
"request-id": "b4bbade7-1ea2-46df-a1d9-92cdda9e360b",
"client-request-id": "b4bbade7-1ea2-46df-a1d9-92cdda9e360b"
}
}
}
as it is a direct (manual) graph api call with a correct meeting ThreadId from a personal meeting room (calendar->meet now->🎥 Start meeting) that returned "BadGateway". Same request succeeds if the meeting chat belongs to a scheduled meeting (calendar -> new event -> tick Teams meeting -> join).
I got the chatInfo thread Id the same way from both meetings.