How to make a bot receive attachments when channeling it to MS Teams - botframework

I made a normal bot by using Microsoft Bot Framework and have deployed it to the Azure portal. I tried to channel the bot to Teams, which worked but the bot couldn’t receive attachments. How can I make it do so?
Thanks.

Microsoft Teams does not allow attachments by default. To send and receive files in the bot in teams, set the supportsFiles property in the manifest to true or else create an app for your bot in App studio. Specify your app allows upload attachments. And install it in your own Team account for testing. Please look at this sample code for reference.

Related

Azure Bot messaging endpoint does not get teamMemberRemoved event when the Bot App is removed from Teams

I created an Azure Bot and set the Messaging Endpoint to my web-app, which is not hosted on Azure.
I created a deploy package zip as a Teams App to be deployed on Teams and use my bot.
My messaging endpoint gets the ConversationUpdate events with membersAdded type when the customer adds my bot to Teams, and when users are added. The events are sent to the Messaging Endpoint configured in my bot.
When the customer deletes the App from Teams I do not get any event to the messaging endpoint.
According to https://techcommunity.microsoft.com/t5/microsoft-teams/which-event-fired-when-someone-uninstall-your-app-in-microsoft/m-p/1610299 I expected to get an event with type teamMemberRemoved to the bot messaging endpoint.
I need to know the Teams App was removed so I can clean up resources on my end, and indicate in my UI to the customer that the bot is no longer configured for his Teams team.
I tried adding and removing the App from my Teams account a few times but never got the expected event to the messaging endpoint.
How can I know that my App was uninstalled on a Teams team?
If you just want to know when the App is getting added or remove you can use OnInstallationUpdateAsync, here you will get the type installationUpdate and action as remove when it gets uninstalled.
I tried with onConversationUpdateAsync as well and got the request as . Please confirm once if you are handling it property,

Users cannot send files to Microsoft Teams chatbot

We have a Mirosoft Teams app/chatbot installed with the personal and team scopes as a tenant app in a customer's tenant.
We have received a report from a user that they cannot send files to the bot, as the paperclip icon is not available in the chat with the bot.
Note that the bot's supportsFiles is set to true in the manifest.
Could this be due to a scope mismatch, e.g. app used personally instead of as a team app? Why would the behavior change?

How to access the bot deployed from Microsoft Samples (bot-builder-samples)

I have created bots using the azure portal, which auto creates a bot app resource in azure. When I click on this resource via the portal, I can access the bot by opening the chat window and can try out the bot.
I also created bot using visual studio, published it to the azure web and then configured a 'bot channels registration' bot to use this published bot.
All good so far.
Now I am trying to go through the ready made Microsoft examples from: https://learn.microsoft.com/en-us/azure/bot-service/dotnet/bot-builder-dotnet-samples?view=azure-bot-service-3.0
I opened the "Create new conversation" link from the above website (https://github.com/Microsoft/BotBuilder-Samples/tree/master/CSharp/core-CreateNewConversation). I scroll down and click on "Deploy to Azure" button and the deploy is successful. How do I access the bot now?
I have tried creating the 'bot channels registration' bot and setting the messaging endpoint to the https://DeployedExampleAzureWebsiteLink/api/messages. Now, when I go into this azure resource, and into the test chat window, my message does not get delivered to the bot, and same issue upon retry aswell.
How do I access this bot please?
When you click deploy to Azure you get an option to fill out the Microsoft App Id and Password.
You are supposed to enter the same App Id and Password you gave while registering the Bot in the Bot channel registration

microsoft bot framework - skype for business - error

I am using Microsoft Botframework to publish a bot (Channel Registration). When I try enabling the channels , I see the bot to be working in Slack , Skype, MS Teams & Web chat . However (despite following the steps to enable bot in SFB) I could not get the bot working in Skype for Business. I keep getting the error.
"Sorry, we ran into a problem at our end."
Neither do I see any log to debug.
Waited more than 24 hrs to ensure it is not the sync issue. But issue still remains. Any help appreciated !!
I am not clear with the error as to from which end it is being thrown.
I need you to follow the below steps:
Publish Bot in azure as an app service, through VS if you are coding through c#.
Create a "Bot channel registration" in azure and connect the above app service and Bot channel registration(simple use the URL of the app service append it with /api/messages and insert the same as messaging endpoint in Bot channel registration).
use the app id and app secret in bot solution and republish the app service.
Inside Bot channel registration click on channel and enable it for Skype for business(you will find your BOT in SFB using the credentials you have used to create the bot channel registration).
Finally got it working. What i noticed is the following
I faced the issue when I used the SIP URI as somebot#mydomain.com to register the bot in my tenant.
And i got it working when I used the SIP URI as somebot#mydomain.onmicrosoft.com.
Unsure on the reasoning though :)
And btw thanks #Tanmoy for your answer aswell !!

Bot Framework - Teleram channel not published

What do I need to do to make the Telegram channel publish?
Telegram not published
Access token added.
The "publish" slider is there for listing your bot in the Bot Directory. Microsoft has not yet opened the Bot Directory to 3rd party developers, so it remains disabled. You can still create bots and share them with other people (in this case by providing them with the name of the telegram bot), you just can't list them in the directory as of yet.

Resources