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?
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": [] }
Set work location via API (Graph?)
Hey community! The new work hours and location feature is rolling out for Outlook and Teams: https://blog.admindroid.com/work-hours-and-location-in-outlook-for-efficient-collaboration/ Does anyone know who to read and write this information (especially the location) via API / Microsoft Graph? This is a nice feature and we would like to set this programmatically. Thank you very much! Best regards, Jens
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
What if post adaptive card and wait for a response timeout
Hi Team, Scenario: Post the adaptive card to the team chat. If the user doesn't respond after 2 hours, the adaptive card should be updated as "Expired"with a new design on the same conversation. In an attempt to comply with this, I used a "Post adaptive card in char and wait for response." Challenges: What would happen if I posted an adaptable card and waited for a response timeout? I wouldn't get a response. An error is being thrown. Expectations include waiting for a response after receiving an adapted card. In any case, your card has already produced a message ID and posted. This action should to return a Message Id in the event that a timeout occurs. Would you kindly respond if you have discovered a solution?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.
Task Module shows popup but Adaptive Card does not render using M365 Agent SDK (Python)
I am using the new M365 Agent SDK for Python to return a Task Module (task/fetch). The popup opens successfully when I click the button in Teams, but the Adaptive Card inside the Task Module does not render. Instead, Teams shows the generic error: “Unable to reach app. Please try again.” My invoke handler returns the following structure: adaptive_card = { "type": "AdaptiveCard", "$schema": "http://adaptivecards.io/schemas/adaptive-card.json", "version": "1.4", "body": [ {"type": "TextBlock", "text": "Sample task module card"}, {"type": "Input.Text", "id": "notes", "isMultiline": True} ], "actions": [ { "type": "Action.Submit", "title": "Submit", "data": {"action": "sample_task_submit"} } ] } task_response = { "task": { "type": "continue", "value": { "title": "Dialog", "width": "medium", "height": "medium", "card": { "contentType": "application/vnd.microsoft.card.adaptive", "content": adaptive_card } } } } return InvokeResponse(status=200, body=task_response) Key symptoms: Task module window opens (so invoke is successful) Adaptive card does not render Shows “Unable to reach app” inside popup No errors in server logs This happens only with Task Modules; normal message replies work fine Questions: Is the above Task Module response format correct for the new M365 Agent SDK for Python? Does the SDK require a different return type or content-type for invoke responses? Are Task Modules fully supported in the M365 Agent SDK preview? Is there an example of returning a Task Module using the Python SDK? Any clarification or working sample for Python would be very helpful. Screen shot -
