Since Aug 22nd we can't save any Side Panel tabs
Hello! Yesterday (Aug 22nd 2025) we got an update in our Teams Links that we normally share to start meetings. They were modified from this format: https://teams.microsoft.com/l/meetup-join/19%3ameeting_XXXXXXXXXXXXXXX%40thread.v2/0?context=%7b%22Tid%22%3a%22xxxxxxxxxxxx%22%2c%22Oid%22%3a%22xxxxxxxxxxxxxx%22%7d to https://teams.microsoft.com/meet/00000000000?p=XXXXXXXXX Sensitive values and ids have been redacted above and inside all the snippets in this post. This looks like a planned rollout, as specified here: https://mc.merill.net/message/MC772556 After this change, none of our apps are able to save a side panel into any of the meetings with the new link format. We had a couple of older, still available meetings whose link had the previous format, and we are able to save the side panel there, but no matter what we tried, nothing allowed us to solve this situation on our end. My final resort is this post in hopes of a solution to what we see. Each save operation yields a 500 on this call https://teams.microsoft.com/api/chatsvc/amer/v1/threads/19%3Ameeting_XXXXXXXXXXXXXXXXXX%40thread.v2/properties?name=tab%3A%3Axxxxxxxxxxxxxxxx { "errorCode": 500, "message": "{\"subCode\":\"TabOperationFailed\",\"details\":\"Initiator 8:orgid:xxxxxxxxxxxxxx failed perform tab operation\",\"errorCode\":1500,\"errorSubCode\":null}", "standardizedError": { "errorCode": 1500, "errorSubCode": 1, "errorDescription": "TabOperationFailed-Initiator 8:orgid:xxxxxxxxxxxxxx failed perform tab operation" } } I ended up trying to manually install it with graph api calls, which didn't work either and gave me a 502 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": "DisplayName", "email address removed for privacy reasons": "https://graph.microsoft.com/v1.0/appCatalogs/teamsApps/'"$TEAMS_APP_ID"'", "configuration": { "entityId": "entity-random", "contentUrl": "https://<domain>/?theme={theme}&locale={locale}", "websiteUrl": "https://<domain>/" } }' | jq . { "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" } } } Then, thinking there was something wrong with my app, I used a MS app, same result 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" } } } I then tested it against chats that do not belong to a meeting. Both apps succeeded curl -s -X POST "https://graph.microsoft.com/v1.0/chats/$REGULAR_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 . { "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#chats('19%3xxxxxx_xxxxxxxxxxxx%40unq.gbl.spaces')/tabs/$entity", "id": "a0cca657-12d0-4df0-84d8-cc1f8fa7d3e6", "displayName": "Website - test", "webUrl": "https://teams.microsoft.com/l/chat/19%xxxxxxxxx_XXXXXXXXX%40unq.gbl.spaces/tab%3a%3xxxxxxxxxxxxxxxxxxxxxx?webUrl=https%3a%2f%2fwww.microsoft.com&label=Website+-+test&tenantId=xxxxxxxxxxxxxxxxxxx, "configuration": { "entityId": null, "contentUrl": "https://www.microsoft.com", "removeUrl": null, "websiteUrl": "https://www.microsoft.com" } } curl -s -X POST "https://graph.microsoft.com/v1.0/chats/$REGULAR_CHAT_ID/tabs" \ -H "Authorization: Bearer $ACCESS_TOKEN" -H "Content-Type: application/json" \ -d '{ "displayName": "redacted", "email address removed for privacy reasons": "https://graph.microsoft.com/v1.0/appCatalogs/teamsApps/'"$TEAMS_APP_ID"'", "configuration": { "entityId": "redacted", "contentUrl": "https://<domain>/?theme={theme}&locale={locale}", "websiteUrl": "https://<domain>/" } }' | jq . { "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#chats('19%3xxxxxxxxxxxxx_xxxxxxxxxxxxx%40unq.gbl.spaces')/tabs/$entity", "id": "xxxxxxxxxxxxxxxxxxxxxx", "displayName": "redacted", "webUrl": "https://teams.microsoft.com/l/entity/<redacted>/_djb2_msteams_prefix_000000000?webUrl=https%3a%2f%2f<domain>%2f&label=redacted+label&context=%7b%0d%0a++%22context%22%3a+%22chat%22%2c%0d%0a++%22chatId%22%3a+%2219%3axxxxxxx_xxxxxxxxx%40unq.gbl.spaces%22%2c%0d%0a++%22subEntityId%22%3a+null%0d%0a%7d&tenantId=xxxxxxxxxxxxxxxx", "configuration": { "entityId": "redacted", "contentUrl": "https://<domain>/?theme={theme}&locale={locale}", "removeUrl": null, "websiteUrl": "https://<domain>/" } } At this point we don't know what else to do, seems like a meeting specific issue that we are unable to solve. It's affecting our tenants in all environments, since our primary business flow relies on this panel. All the snippets contain real dates and request-ids, here's hoping it helps somehow. Help, and thanks in advance. ~A. del Yerro
Meeting Bot issue: Did not receive valid response for JoinCall request from call modality controller
I'm trying to join a Teams Meeting with a bot. I used this https://microsoftgraph.github.io/microsoft-graph-comms-samples/docs/articles/index.html#making-an-outbound-call-to-join-an-existing-microsoft-teams-meeting sample. When the bot attempts to join I get the popup to admit or deny it in the meeting, but as soon as I click admit, it drops. In the logs I see this message: Call status updated to Terminated - Did not receive valid response for JoinCall request from call modality controller.. DiagCode: 580#5426.@ I am using the latest (1.2.0.10563 at time of writing) version of Microsoft.Graph.Communications libraries and the problem only started after I updated from 1.2.0.3742 that I was using previously. I could not find any info on what the call modality controller is, or how to check what it is responding if anything. Any ideas on how to troublshoot this are welcome.
Graph API: create a PSTN call and invite a PSTN participant
Hello everybody, We are using the MS Graph API within a C# project. After successful creating a PSTN call from our bot like described here https://docs.microsoft.com/en-us/graph/api/application-post-calls?view=graph-rest-1.0&tabs=http#example-7-create-peer-to-peer-pstn-call-with-service-hosted-media we run into the next problem: We want to invite another PSTN participant to this existing call like described here: https://docs.microsoft.com/en-us/graph/api/participant-invite?view=graph-rest-1.0&tabs=http#example-4-invite-one-pstn-participant-to-an-existing-group-call. But we receive following event: { "value": [ { "changeType": "Deleted", "resourceUrl": "/communications/calls/981f6100-cb65-42d9-af3c-1390c68cac8b/operations/5fedb136-cff9-446d-a8bc-4166db960e19", "resource": "/app/calls/981f6100-cb65-42d9-af3c-1390c68cac8b/operations/5fedb136-cff9-446d-a8bc-4166db960e19", "resourceData": { "@odata.type": "#microsoft.graph.inviteParticipantsOperation", "participants": [ { "@odata.type": "#microsoft.graph.invitationParticipantInfo", "identity": { "@odata.type": "#microsoft.graph.identitySet", "phone": { "@odata.type": "#microsoft.graph.identity", "id": "+49175********" } } } ], "status": "failed", "resultInfo": { "@odata.type": "#microsoft.graph.resultInfo", "code": 403, "subcode": 9999, "message": "addParticipants failed for participant 4:+49175******. Underlying reason: Call does not contain the metadata required for making this PSTN dial out.. DiagCode: 403#10151" }, "id": "5fedb136-cff9-446d-a8bc-4166db960e19" }, "@odata.type": "#microsoft.graph.commsNotification" } ], "@odata.type": "#microsoft.graph.commsNotifications" } Any idea why we can not invite another PSTN participant to an existing call from the bot to a PSTN number? Thanks. Regards Gerd
Graph api - MS Teams Meeting Recording link
Hi Team, We are setting up meetings within O365 Group and trying to get the meetings information of given Group ID using the below graph api https://graph.microsoft.com/v1.0/groups/{guid}/events?$orderby=createdDateTime What we are now interested is, Can we get the MS Teams meeting recording link along with the event details? Do we have support from Graph api to get the Teams meeting recording details. Thanks & Regards, BhanuDev environment for Teams Voice
Hi I am a Cloud specialist that looks after various Teams environments. Recently I have been migrating a lot of my clients from Skype for Business to Teams, as well as I am just about to take the MS-721 exam. I have two test environments from the M365 Developer, it is very useful and I am able to re-created a lot of my clients scenarios as well as it is extremely handy for exam study. However one limitation is Teams Voice, it would be useful to the capability to have a handful of numbers and a calling plan for a temp basis just to look at the live creation of call queues, auto attendants and the other features you would have around Teams voice capability. I have tried to get a trial license however it does not work on the Dev environments. Has anyone one found a way to make a temp test environment or is this something Microsoft can look into?Redirecting SIP calls from another SIP server to Teams user
I am trying to understand if SIP calls can be transferred/redirected from a another/thirdparty SIP server to a Microsoft Teams user. I was reading below links: https://docs.microsoft.com/en-us/microsoftteams/direct-routing-protocols-sip https://docs.microsoft.com/en-us/microsoftteams/sip-gateway-plan https://docs.microsoft.com/en-us/microsoftteams/direct-routing-plan As per my understanding we need to use Direct routing, and for direct routing Microsoft certified SBC need to be configured along with the SIP proxy. But if we have the URL for the Microsoft Teams SIP Endpoint and the credentials to access it, can we transfer calls from another SIP server by configuring the URL and credentials? Will it work or is this supported? I have below questions: 1. Can we transfer the SIP calls from another SIP server to Microsoft Teams user? 2. If it is possible what are the available ways of achieving this? 3. Do we need to have SBC configured for having this functionality, is it must? 4. Is there a document which explains this process step by step?
