Forum Widgets
Latest Discussions
Add Teams Chat Member API call inexplicably Failing
I have tried every possible permutation of this API call that I can imagine. Nothing works. I already started a thread on this, but now it appears to be glitched and I can no longer reply to message sin that thread for some reason. What can I do to contact Microsoft Support and speak directly to their API team? The responses I have gotten all appear to be AI generated and NONE ARE CORRECT. I really need help, from a human, that actually might understand what's going on here. Please help. "#microsoft.graph.aadUserConversationMember' for 'odata.type' is not valid for this operation." <- I am receiving this error despite the fact that we already have several users in this channel with that same type. This API call is intended to invite a user to an existing group chat. This should really be a very simple thing. 1. ALL users in the group chat already have type = '#microsoft.graph.aadUserConversationMember' so the error message doesn't even make sense. 2. This IS a Group chat. NOT a channel. NOT a one on one chat. 3. The Inviter has permission to invite users to this groupchat through the frontend. (and in fact can do so using the frontend.) Why is this API call failing? I have tried scrubbing the API call of special characters, I have tried using the beta endpoint, I have tried several different formats for the input. ERROR: {"error":{"code":"BadRequest","message":"The provided '#microsoft.graph.aadUserConversationMember' for 'odata.type' is not valid for this operation.","innerError":{"date":"2026-02-10T19:11:28","request-id":"XXXXX","client-request-id":"XXXXXX"}}} POST URL: https://graph.microsoft.com/v1.0/chats/IDHERE/members BODY: { "chatType": "group", "\u0040odata.type": "#microsoft.graph.aadUserConversationMember", "user\u0040odata.bind": "https://graph.microsoft.com/v1.0/users/IDHERE", "roles": [] }
All Teams Bots Not Working At All
This morning all of a sudden all our Teams bots stopped working. These are bots built using bot framework running on Azure Bot Teams Channel. Is this related to the current Teams API issue we talking about? All of a sudden all our client and test bots stopped working. But the Web Channel is working as expected. Only the teams channel. We even checked with ngrok and its not even hitting the service. We checked the app registrations and their credentials as well to ensure not issues there too. Completely lost whats happening. Help?Issue with Teams 'Add a User to Group Chat' API call?
I am getting a very strange error when trying to add a new user to an existing group chat using a GraphQL call. I have looked through the documentation, asked AI, and even contacted Microsoft support and no one can seem to explain why this API call is failing. Below is the API call that I am making. I can find no reason that I should be receiving the error message '#microsoft.graph.aadUserConversationMember' To get the basic questions out of the way.... Yes, the account making the API call DOES have permission to add users to the channel (and can do so using the frontend as normal.) Yes, the thread in question is a group chat, so adding members to that chat should be a valid command. Yes, ALL members in the group chat currently have the type '#microsoft.graph.aadUserConversationMember', so it is definitely a valid type for users in this channel. Yes, I have tried both the beta and stable channel; each gives the same error message. Yes, the invited user is internal to our organization, and is a valid target for the invite (invites work through frontend as well.) No, I cannot use the 'add member to channel' endpoint, because the chat is a group chat, not a channel. I can only assume, at this point, that the error message is a red herring and there's something else wrong with my API call?Why am I receiving this error message when trying to add a member to a pre-existing group chat? Thanks in advance for any assistance. POST to URL: https://graph.microsoft.com/beta/chats/[[THREAD_ID]]@thread.v2/members BODY: { "@odXXX.type": "#microsoft.graph.aadUserConversationMember", "roles": [], "email address removed for privacy reasons": "https://graph.microsoft.com/v1.0/users/[[USER_ID]]" } ERROR MESSAGE: {"error":{"code":"BadRequest","message":"The provided '#microsoft.graph.aadUserConversationMember' for 'odXXX.type' is not valid for this operation.","innerError":{"date":"2026-01-29T18:10:32","request-id":"<PII:moderator removed>","client-request-id":"<PII:moderator removed>"}}}
How to create an audio calling bot for the Marketplace?
What is the correct set of framework(s)/tools that allow a bot to make audio calls to teams users that can be installed to multiple customer's Teams instances, and added to the Teams Marketplace, as of January 2026? It seems that there is a lot of transition going on in the various bot frameworks that are supported by Microsoft. The new Microsoft 365 Agents https://github.com/microsoft/Agents/issues/377 , and won't do until at least March 2026. The Teams Microsoft Graph Comms libraries still work and appear to be current, however that is only half the puzzle. I need to also package up the bot that has been built, including build an app manifest, etc. The AzureBot still works, but upon packaging up, it seems that Multi-tenant support was https://github.com/microsoft/botframework-sdk/issues/6698. The permissions for the various Microsoft graph https://github.com/microsoftgraph/microsoft-graph-comms-samples do not match up with the permissions for the packaging of the new agent (e.g. Calls.AccessMedia.All, Calls.Initiate.All are required, but not present). It also isn't clear to me Microsoft Graph App Manifest can help in this matter. Any clarity on the matter would be much appreciated. This is kinda urgent, so can't wait until Agent SDK
Status during a Teams call : "in a call" only once others have joined!
Hi, I work remotely so most of my job is through Teams calls with laypeople (i.e. not necessarily Teams savvy). I like to start the calls a few minutes before to prepare my shared whiteboard, etc., make sure sound is OK... However, the status, even when I'm alone, is automatically "in a call" and so I don't have notifications anymore, which is generally OK, except that if my client tries to call me on the phone (which is on Teams), they go directly to voicemail. It is annoying to manually switch it. I think that when we are ALONE in the call, waiting for others to join, we should appear as AVAILABLE so that all notifications, etc. are still enabled until we are not alone in the meeting... and then, yes, all the do not disturb aspects must kick in! Thanks!
How to add a Teams Media Bot in an online meeting.
I am currently developing a Teams Media Bot designed to join Microsoft Teams meetings, record sessions, and perform subsequent analysis. The bot is intended to participate as a visible attendee in meetings. Below is an overview of the development environment and the key issues encountered: Current Implementation: Graph API with Application Permissions: The bot joins meetings as an application. Azure Bot Service: Facilitates communication between the bot and Microsoft Teams. Deployment: Hosted on an Azure VM. Note: No resource account is currently associated with the bot. Issue #1: Delayed Join Scenario The bot successfully joins and appears as a participant when it initiates the meeting and other participants join afterward. However, if participants are already present and the bot attempts to join later, the logs indicate successful entry, but the bot does not appear in the participant roster, nor does it begin recording. Interestingly, the bot becomes visible only after all other participants leave the meeting. The root cause of this behavior remains unclear. Issue #2: External User Access Constraints When the bot is active in a meeting and the lobby bypass setting is not configured to "Everyone," external users encounter difficulties joining. Although they receive meeting invitations and can initiate a join attempt, they are redirected to a new meeting instance instead of entering the ongoing session. This issue resolves once all participants leave the meeting, allowing external users to join successfully. Attempted Resolution: I explored creating a resource account and assigning the bot’s application ID to that account. However, I encountered authentication challenges when attempting to authorize the bot on behalf of the user account. Request for Guidance: I would appreciate any insights or recommendations to address these issues, particularly regarding the bot’s delayed visibility and the constraints affecting external user access.Approval card not working when posted in a Power Virtual Agent Bot
In My flow I am posting the approval card to a Power Virtual agent Bot, I see the approval being posted properly but, response (Approve/reject) button click is not reaching 'Waiting for an approval'. Please suggest. Same works fine when approval is posted to 'Flow bot'.
[iOS] Custom App Icon still renders as white square
I am following up on a rendering issue where my custom app icon appears as a blank white square on the iOS client. Current Status: Despite following the standard guidelines, the icon fails to render on iOS (Works perfectly on Android/Desktop). What I have tried (and failed): Changed accentColor: Updated manifest from #FFFFFF to #4B6BF5 (Brand Blue) to avoid white-on-white issues. Version Bump: Increased manifest version from 1.0.17 to 1.0.18 to force cache invalidation. Re-installation: Completely uninstalled the app on iOS, cleared app data, and re-added it. Direct Upload via Teams Admin Center: I tried uploading the app package directly through the Admin Center, but the icon still fails to render on iOS. Commercial Marketplace: I have users who installed the app via the Commercial Marketplace, and they are also seeing a blank icon. "Publish to Org" via Developer Portal: I also tried the "Publish to Org" feature within the Developer Center, and the result is the same. Icon Validation: color.png: 192x192, PNG, Transparent background. outline.png: 32x32, PNG, Pure white pixels only with transparent background. Manifest Snippet: { "version": "1.0.18", "manifestVersion": "1.22", "id": "e4fae5da-30ea-4f90-9eae-807b2a13a127", "icons": { "outline": "outline.png", "color": "color.png" }, "accentColor": "#4B6BF5" } Questions & Request for Assistance: Has anyone faced a similar "blank white square" issue on iOS recently? Any suggestions would be greatly appreciated.
Bot configuration config/fetch returns same channel ID when switching channels within same team
Summary When invoking a bot’s configuration flow (configuration.fetchTask) via an @mention-based settings entry point across different channels within the same Team, the request body consistently contains the same channelId, even after switching channels. https://learn.microsoft.com/en-us/microsoftteams/platform/bots/how-to/bot-configuration-experience?tabs=teams-bot-sdk1%2Cteams-bot-sdk2%2Cteams-bot-sdk3 This makes it impossible to reliably determine which channel initiated the configuration. Environment Microsoft Teams (desktop client) Bot installed at team scope Same Team, multiple channels Bot supports team scopes. Configuration enabled via manifest: "configuration": { "team": { "fetchTask": true } } Steps to Reproduce Install the bot into a Team with multiple channels Navigate to Channel A Invoke the bot configuration using an @Bot settings / configuration entry point Observe the incoming config/fetch request payload Note the channelId in the request body Switch to Channel B (same Team) Invoke the same configuration entry point again Observe the incoming config/fetch request payload Expected Behavior The config/fetch request body should include a channel identifier corresponding to the channel where the configuration was initiated, e.g.: channelData.channel.id or another channel-scoped identifier that uniquely identifies the initiating channel Actual Behavior The config/fetch request body always contains the same channel ID The channel ID does not change when switching channels The value appears to be: either the Team’s General channel or a cached / team-level channel context As a result, the bot cannot determine which channel the user intended to configure. Impact This behavior prevents implementing per-channel configuration using the bot configuration experience because: Configuration requests cannot be reliably scoped to the initiating channel All configuration actions appear to target the same channel Users configuring different channels in the same Team unintentionally overwrite the same settings Additional Notes This occurs within the same Team Reproduced consistently across multiple channels Observed even when the configuration is invoked after explicitly switching channels Behavior suggests the configuration context may be team-scoped rather than channel-scoped, but this is not clearly documented
