Forum Widgets
Latest Discussions
Bot 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 15, 2025Copper Contributor114Views1like6CommentsCall 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 14, 2025Copper Contributor56Views0likes2CommentsTeams 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 13, 2025Copper Contributor71Views0likes1CommentThe Teams Developer Portal needs administrative views
The Teams Developer portal needs some way for Teams service admins or Global admins to view everything that is being deployed to the catalog both in a published and unpublished state. Alternatively, develop some graph endpoints that could be turned into cmdlets in Microsoft Teams PowerShell module or the Graph PowerShell SDK module. As administrators we need the ability to help with keeping our tenant clean, so these kinds of views or endpoints would allow us to make sure that anything uploaded and not needed may be removed or reassigned if the underlying owner leaves and someone else needs to take over something they've been developing. I've submitted a feedback item to the portal - so please help by adding a vote to the entry to bring it up as an enhancement for the Teams Developer Portal services. The Teams Developer Portal needs administrative views or PowerShell/Graph capabilities to manage uploaded solutions and other artifacts · CommunityTimLBOct 10, 2025Iron Contributor28Views0likes0CommentsAffordable Conference Room Setups for Small Businesses Using Microsoft Teams Resource Accounts
Our small business (around 40 users) recently migrated from Google to Microsoft 365, and we’re facing several challenges in optimizing our meeting rooms for Teams without incurring large costs. Here’s our current setup and the main issues we are encountering—hoping for advice or creative solutions from the community. Current Setup All computers are domain-joined. We created resource accounts for each of our three meeting rooms; these appear correctly as Rooms in Outlook and Teams booking menus. Each meeting room contains a standard desktop PC (not MTR-certified) running Windows, logged into Teams as the room’s resource account. Employees use the meeting room computer to join calls and manage the meeting calendar. Current Issues Wireless Presenting (Casting): Teams’ wireless casting feature appears to require MTR-certified hardware, which is financially out of reach for a business our size. Unplugging and plugging HDMI cables is cumbersome and error-prone, especially since not everyone uses a laptop, and reconnecting the room PC is often forgotten. Agenda & Calendar Privacy: When meetings are booked, the full Teams agenda and chat history remain accessible on the meeting room machine. That means anyone in the room can view past meetings/agendas, which isn’t ideal from a privacy perspective. Screen Sharing and File Security: To present from the meeting room PC, any files must be accessible by the resource account, creating additional security concerns and sharing/permission headaches. What We’re Looking For Affordable wireless presenting options for meeting rooms—ideally something that integrates smoothly with Microsoft Teams, but without requiring full MTR hardware. Best practices to lock down or reset the meeting room PC so meeting agendas, chats, and files are not visible after a session. Secure ways to allow guests to present (screen share, share files, etc.) without exposing company data or making users jump through complicated permission processes. If anyone has experience setting up small, cost-effective Teams Rooms, especially with regular PCs rather than dedicated MTR devices, advice would be greatly appreciated! Specific steps, hardware/software recommendations, or management tips would all be helpful. Thanks in advance for any guidance!MegJOct 09, 2025Copper Contributor31Views0likes0Commentshow 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 08, 2025Copper Contributor69Views0likes5CommentsTeams 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 07, 2025Copper Contributor72Views0likes3CommentsMS Teams Bot Applications – Major Message Delivery Delays
Description: We are experiencing a performance issue with Microsoft Teams bot applications. Impact:Since approximately 10:00 AM CET, users have reported significant delays when sending or receiving messages via Teams bots. Messages are sent successfully but are delivered to the Microsoft Teams servers after a long delay (ranging from several minutes to no response at all). Current Status: Issue appears to affect all Teams bot applications. No changes have been made to our configuration prior to the issue. Connectivity to the Microsoft cloud is stable; the delay seems to occur on the Microsoft Teams service side. Business Impact: Users are unable to interact with Teams bots in a timely manner. Automation and workflow processes relying on Teams bot responses are disrupted. Time of Occurrence:Approximately 10:00 AM CET 07.10.2025 Severity:High widespread impact on user productivity and automated processes.Tatsiana1808Oct 07, 2025Copper Contributor40Views0likes1Comment
Resources
Tags
- microsoft teams1,759 Topics
- developer1,367 Topics
- meetings236 Topics
- Chat229 Topics
- Administrator152 Topics
- Settings115 Topics
- calling107 Topics
- files68 Topics
- teams56 Topics
- devices53 Topics