Microsoft.Bot.Connector SendToConversationAsync Failed - 'Forbidden'
Hi. We use Microsoft.Bot.Connector (4.22.9) SendToConversationAsync for sending an activity to a conversation. Most of them are processed successfully, but some fail with 'Operation returned an invalid status code 'Forbidden'. How can I handle it? What is the reason? Also, I have a second question about "blocked conversation." If the user blocks the conversation, I think SendToConversationAsync will fail, too. How can I handle this, and what kind of error will be raised?Teams Bot vs. Azure Bot
Hi, What is the differences between the Bot what you can setup on Teams' Development Portal and Azure Bots? Azure Bot's requires response group. But Bots from development portal seems to not requiring that. Is the development portal only way to setup such a bots, or should I be able to setup those bots from some other way as well?Creating virtual Azure environment for teams toolkit VS code for teams toolkit.
Hi everyone, I am working on a project to create a teams bot app for my institute. I am using Teams Toolkit for VS code, and I have MS 365 app upload permission allocated. I was trying to create " Teams Conversation Bot SSO quick-start" using Teams Toolkit. However, after debugging the app with option of 'Debug in Edge' or 'Debug in Chrome' I faced issue with devtunnel, that the devtunnel is unable to create tunnel service use 'Test Tool' Instead. I communicated same issue with my team and came to know that firewall is blocking any tunneling service in our tenant. Then, my IT Admin suggested to create a Shared Virtualized Environment in Azure in which I should develop and deploy app for testing and production. Now I am quite confused about how to do this, because teams toolkit for VS code is installed on VS code of my local device and it's debugging will happen locally, how I should create Shared Virtualized Environment in Azure for creating, debugging and deploying Teams Bot App. Your answers are highly appreciated, this is very important project for my institute.
Issues with Bot-to-Bot Calls and Call Status Retrieval in Microsoft Teams - Issue 2
I am currently developing a bot-to-bot VOIP call feature using Microsoft Teams and have encountered critical issues that I need assistance with: Please suggest We have registered 2 bots in the same tenant with separate APP Registrations, As per the documentation sending a body to initiate VOIP calls between the bots however it is not working and getting the below error. When trying to make bot-to-bot calls, I consistently receive a "Request authorization tenant mismatch" error, despite both bots being registered under the same tenant. Steps to Reproduce: Register two bots in the same Azure tenant. Use the Microsoft Graph API to initiate a call from one bot to the other. Observe the error response. https://graph.microsoft.com/v1.0/communications/calls?Content-Type=application/json { "@odata.type": "#microsoft.graph.call", "callbackUri": "https://7084-&&&&&-234.ngrok-free.app/callback", "source": { "@odata.type": "#microsoft.graph.participantInfo", "identity": { "@odata.type": "#microsoft.graph.identitySet", "application": { "@odata.type": "#microsoft.graph.identity", "displayName": "VOIP Call Bot", "id": "BOT 1 APP ID" } }, "region": null, "languageId": null }, "targets": [ { "@odata.type": "#microsoft.graph.invitationParticipantInfo", "identity": { "@odata.type": "#microsoft.graph.identitySet", "application": { "@odata.type": "#microsoft.graph.identity", "displayName": "Calling_Teams_Bot", "id": "APP ID", "tenantId": "BOT 1 APP Tenant ID" } } } ], "requestedModalities": [ "audio" ], "tenantId": "BOT 1 APP Tenant ID", "mediaConfig": { "@odata.type": "#microsoft.graph.serviceHostedMediaConfig" } } Error Message: { "error": { "code": "7505", "message": "Request authorization tenant mismatch.", "innerError": { "date": "2024-10-23T18:28:10", "request-id": "66dd5026-763a-46bc-9a94-79cf0630ed33", "client-request-id": "66dd5026-763a-46bc-9a94-79cf0630ed33" } } }
New Microsoft Teams issue, This bot is disabled. Contact your IT admin for more information
This issue is happening only on new Microsoft Teams desktop application for some selected users. It works fine with old Teams classic and new browser application for all users. Senario: When an effected users click on adaptive card button, user is getting error "This bot is disabled. Contact your IT admin for more information". Also issue gets resolved automatic after few hours. Then some other set of users start facing the same issue.
Teams Bot App debugging locally Listener function unable to start error
Hi, I have used the following guide to set up a Teams bot with Cron trigger to test out the abilities of the Teams Development toolkit. Debug your Teams app locally using Visual Studio - Teams | Microsoft Learn I followed each step and all was well until the end when attempting to debug locally the function app could not fire its cron trigger and printed out the error "The listener for function 'NotifyTimerTrigger' was unable to start" and "No connection could be made because the target machine actively refused it. (127.0.0.1:10000)" I haven't been able to find anything I did wrong or others who have had this same issue. Any guidance would be appreciated.
Processing replies to a thread and forward them to an external application
Hi, I'd like to implement a solution in Teams and would appreciate some input on what's the best way to use. The use case looks like this: 1) A web server hosts a forum. A user of that forum starts a new thread in that forum by creating a post. 2) The web server forwards the content of the initial post that started the thread to Teams where an application (a bot or webhook etc.) uses that data to start a thread in a certain Teams channel. 3) Users in that channel can then reply to that thread and their replies are forwarded to the web server where they are posted as replies to the thread in the forum. 4) When a user replies in the forum of the web server, then that reply is send to the Teams application and posted as a reply in that Teams channel thread. So far it seems that the challenging part of that use case is that the Teams application (be it a bot or a webhook) needs to be able to parse a reply to the thread that it created. Several documentations mention this: "Bots in channel and group chat conversations require the user to @mention the bot to invoke it in a channel." Does that mean that, even when replying to a thread that the bot started, every user still has to @mention the bot so that the reply gets processed by the bot?
