Forum Widgets
Latest Discussions
Adaptive Card embedded audio doesn't play
Hi Everyone I have an adaptive card that was working until this week. I've got a workflow that sends an email when a voicemail is received, then saves the voicemail in SharePoint and sends the audio file embedded in an adaptive card in Teams. The code isn't complicated, I've just put the sharing link as a variable and then it's more or less like this: "type": "Media", "sources": [ { "mimeType": "audio/wav", "url": "@{variables('VoicemailLink')})" } ] It was working last week, and I didn't change anything. I've put a quick workaround in to put a hyperlink to the voicemail in the text of the adaptive card, and that seems fine so the variable link is working and the saved audio file is working, it's just not embedding the file nicely into the card. It opens up in a browser window instead. Has there been an update to adaptive cards or Teams that might break this sort of thing? Thanks for your help.MelBo1Oct 17, 2025Copper Contributor69Views0likes2CommentsBot creation failed
When i tried to create a bot in dev.teams.microsoft.com i am getting the below error { "resultType": 2, "result": null, "errorMessage": "When using this permission, the backing application of the service principal being created must in the local tenant" } can anyone help me with this Microsoft TeamsintegrationsnOct 17, 2025Copper Contributor114Views1like6CommentsHow to enable a Microsoft Teams bot to work in private channels?
We have developed a bot for Microsoft Teams that can send messages to: Team members' personal chats Public channels within the team However, when we attempt to install the bot in a private channel, we encounter the following error: "App isn't supported in the private channel. Select another channel." We would like to enable our bot to: Be installed in private channels. Send messages in the private channel where it is installed. Send messages to team members who are part of that private channel. Is there a way to configure the bot or update its app manifest to support private channels? If so, what steps are required? Are there any limitations or additional permissions needed to achieve this?1.2KViews0likes5CommentsTeams Tab Blazor App Works in Web but Not Desktop – SSO / Access Denied Issue
Hi all, I have developed a Teams tab application using Blazor with Azure AD SSO. It works perfectly in the Teams Web interface, but fails in Teams Desktop app. Troubleshooting details If you contact your administrator, send this info to them. Copy info to clipboard ✔ Copied Correlation Id: 2607e281-e81f-429f-95b6-755f4b30968d Timestamp: 2025-10-07T09:42:34.000Z DPTI: d2bf8e81894be21be1d5e1818fa47b2d8975c91c3d0eceb6622a99cc1fc8b8f1 Message: Access denied for the resource. Tag: 4usp7 Code: 3399614468 I would appreciate guidance on how to make the Blazor Teams tab work in both Web and Desktop using SSO. Thanks! TahirTahirShafiqueOct 17, 2025Copper Contributor70Views0likes3Commentshow to achieve private stage view for custom team app in meeting
I’m working on a custom Microsoft Teams app that will be added to a meeting. My goal is to have the app load in a private stage view as a popout when clicked, so that only the user who clicked it can see the content, without broadcasting it to all meeting attendees. I've created a custom Teams app for meetings, but I'm facing an issue with the viewing behavior. Currently, when a user clicks the app during a meeting, the content first loads in the side panel. The user then has to click a "Share" button to push the content to the main meeting stage, which makes it visible to all attendees. However, what I want is for the app to immediately open in a private stage view (as a popout) when clicked, without showing anything in the side panel and without requiring the user to manually share it. The content should only be visible to the individual user, not broadcast to the entire meeting.VivekPenthotaOct 16, 2025Copper Contributor69Views0likes5CommentsRSC permissions cause app to fail installation in personal scope
I am trying to update an existing up to send notifications. The plan is to use RSC permissions for it. I configured the manifest (v 1.19) with the following scopes: "authorization": { "permissions": { "resourceSpecific": [ { "name": "TeamsActivity.Send.Chat", "type": "Application" }, { "name": "TeamsActivity.Send.Group", "type": "Application" }, { "name": "TeamsActivity.Send.User", "type": "Application" } ] } }, I then sideloaded it successfully with this configuration into a team and also into a chat. However when I try to install it into the personal scope directly I get the error in a dialog box: Something went wrong In the network tab of the web inspector I see that this call fails with 403: https://teams.microsoft.com/api/mt/emea/beta/users/apps/definitions/appPackage The body of the response says: {"errorCode":"WebApplicationInfoIdConflictOnSideloadingIntoTeam"} However, when I change the included permissions in the manifest to only TeamsActivity.Send.Group the app installs successfully into personal scope "authorization": { "permissions": { "resourceSpecific": [ { "name": "TeamsActivity.Send.Group", "type": "Application" } ] } }, So I guess it has nothing to do with an id conflict. I also made sure to remove all old instances of the sideloaded app before (which was never a problem so far). How can I use all three RSC scopes in my app manifest and still install the app into the personal scope. Or what could be wrong? Anything I could check to figure out why this is not working but only the TA.Send.Group scope?jocschOct 16, 2025Brass Contributor400Views0likes11CommentsCall Event when one user calls another user so that Bot can be added to call
We have developed our Bot application and can record all media(audio, video) locally when a user directly calls the Bot User. However, we do not get a call event when one user calls another user - so that we can add the Bot to record the call. Both users have the global default compliance policy which allows recording. We have provided the necessary permissions to the Bot. What are we missing ? Thanksdebumodi1Oct 16, 2025Copper Contributor54Views0likes2CommentsDeleting AutoAttendants and CallQueue
Hello There are commands to delete AutoAttendants and CallQueue. But I get allways an error "Can't remove the Auto Attendant. Auto Attendant is still referenced by Endpoints Ids" Even if all Ressource Accounts are deleted a day before. These Auto Attendants and CallQueues are configured as Calling ID's When I manually delete them after removing there also an error that call queue time was to low. Is it possible to force the deletion. Regards JFM_12JFM_12Oct 14, 2025Iron Contributor172Views0likes7CommentsTeams channel messages delta API returns HTTP 400 BadRequest
Hello, We are encountering an unexpected error when calling the Microsoft Graph API endpoint: /teams/{team-id}/channels/{channel-id}/messages/delta This happens consistently for a specific Teams channel, which prevent us from retrieving incremental message updates using the delta query. Request URL: https://graph.microsoft.com/v1.0/teams/{team-id}/channels/{channel-id}/messages/delta?$deltatoken=<redacted-deltatoken> Error Response: HTTP 400 { "error": { "code": "BadRequest", "innerError": { "client-request-id": "<redacted>", "date": "2025-10-07T06:32:56", "request-id": "<redacted>" }, "message": "UnknownError" } } Steps already tried (unsuccessful): Start a fresh delta query without the $deltatoken to obtain a new valid token Use the beta endpoint: https://graph.microsoft.com/beta/teams/{team-id}/channels/{channel-id}/message/delta Additional observation: If we add a filter condition such as ?$filter=lastModifiedDateTime gt <some-timestamp> to skip messages before a certain time, the query works normally. This suggests that there may be one or more problematic messages within a specific time range that cause the API to fail with BadRequest. Questions: Is this a known issue with the Teams channel messages delta API? Are there any recommended workarounds to avoid this error? Thank you.Joe WuOct 14, 2025Copper Contributor70Views0likes1Comment
Resources
Tags
- microsoft teams1,759 Topics
- developer1,366 Topics
- meetings236 Topics
- Chat229 Topics
- Administrator151 Topics
- Settings114 Topics
- calling107 Topics
- files68 Topics
- teams56 Topics
- devices53 Topics