botframework-sdk | Bot Framework provides the most comprehensive experience | Bot library

You can use the following method to store the secret value

Much of the Bot Framework schema is channel-specific, especially when it comes to cards. If you'd like to know what card actions Teams specifically supports, you should refer to the Teams docs: https://docs.microsoft.com/microsoftteams/platform/task-modules-and-cards/cards/cards-actions

Since Teams does not support call actions, you need to use open-URL instead. Using a tel URL won't work, but you can read about that problem and a workaround here: how to make callto: works in adaptive card

That's a bunch of questions 😅, will try to synthetize.

1. Yes it's a code once, use from several channels... but not all channels have the same capabilities.

2. A bot application is "just" a state machine with a REST API endpoint to receive messages and send the replies back (seen from 30,000 ft 😉)

3. You can host your app anywhere, it just has to have a valid public https address that you can configure in the Bot Channel Registration in Azure.

4. Azure Bot Service is a channel aggregator, that handles all the connection details for the channels listed as "Azure" in the chart you mentioned. Those channels are handled "automagically" by the bot framework.

   You might want to read a blog post I wrote some time ago, it's a bit dated but still conceptually valid:
   How does a Bot Builder v4 bot work?

5. For those channels not in Azure, you have to handle each channel with a provider-supplied SDK in your web app. Of course, you could also implement authorization and all the details by yourself, after all it's just an API endpoint.

6. You don't really have to pay Azure for using the bot service channels, if you use the standard channels, and premium channels are low cost.

7. As for deploying outside Azure, supposing you'll still use the free or close-to-free Bot Service:

   • Follow section 1-3 in Deploy your bot

   • Deploy the web app wherever you want (even locally using ngrok similar to what I show in another blog post.

   • With all of the above in place, you should be able to test the bot from the channel webchat or even from Telegram, once you enable it, while your app is running in VS 😀

Please look over the 80.skills-simple-bot-to-bot sample for guidance on how to connect two bots. The sample demonstrates a "root bot" (your Bot A) calling the "skill bot" (your Bot B) and executing a dialog before returning control back to the root bot. The conversation Id is maintained across the root and skill bot by use of the SkillConversationIdFactory.

Reference the Implement a skill docs for additional information on setting up and consuming a skill.

If your card contains no inputs then I suspect you want a hero card and not an Adaptive Card. An imBack in a hero card will automatically work the way you want in both Web Chat and Teams. While Adaptive Cards are meant to adapt to the styles of their hosts, there is no builtin "imBack" feature of Adaptive Cards. String submit actions are a feature of Web Chat, and Bot Framework actions in Adaptive Cards are a feature of Teams. You're trying to get Adaptive Cards to do something that they can't do by themselves, and so you'll need to take your specific channel into consideration if you want to do that.

From this answer: How to rewrite a Adaptive Card Submit Action for MSTeams also working in Web Chat?

My blog post explains that if you want to use a string submit action you will need to do it differently in Web Chat and Teams: https://blog.botframework.com/2019/07/02/using-adaptive-cards-with-the-microsoft-bot-framework/

If you want to have the same submit action work the same way in both channels, it will need to be an object submit action. If you want a string submit action to work on both channels then your bot will need to check which channel the activity came from and react accordingly.

You should use the BeginSkill action. There is a document here that shows you how to do this in Composer.

When you get an error that says "message size too big," it means what it says. When it suggests that you use attachments, it means attachments that link to remote HTTP/HTTPS locations rather than embedding data. You should try uploading the uploading the file or using a service that's geared towards transferring audio like the Direct Line Speech channel.

"RichMoe" in the link you've provided states that Teams does not support this operation (2017) and I think the same is still true - I don't think Teams has a concept of the "end" of a conversation, in the way that, for example, a support bot on a website would - like any conversation, Teams will try to keep the entire chat history forever.

Perhaps you can explain why you need to "end" the conversation, if there's something related I can try help with.

It's completely possible to run in on Azure, and everything will work 100% fine a free trial account, or of course with a paid account. Be aware that the "web app bot" template will default to a "standard" pricing model in Azure, which will use $70 of your credit, so you should change it to a cheaper price plan immediately, especially if you're just using this for development. There's even a "Free" option (i.e. free forever, even after the Free Trial expires), but then it's limited to how many hours per day the bot will run.

Another option is to host your bot in an Azure Function ("serverless"), but it's a lot more work as the samples and wizards on the internet mostly use the Azure Web App model, so you'd need to manually convert it over to running that way. Certainly you can get started with the free trial though!

As another completely possible option, if this is just for development, then you can run the bot on your local machine, using Ngrok, which creates an real, live "https" address for you, that Teams can accept to work with your bot, even though it's running from your local machine. This is of course great for development/debugging, but not realistic for a live deployment.