I'm trying to figure out if I can run botframework v4 on Azure functions. Current azure functions page shows only v3 sdk.
Anyone has any idea if we can run v4 on functions or not?
Thanks.
According to Azure portal,
Bot Framework SDK v4 is now available and comes with many updates and new functionality. Function Bots are based on SDK v3; we recommend you create a Web App Bot instead, which supports the new SDK v4.
You can set up a functions bot, but only with the v3 SDK. AFAIK, there are no plans to support functions bots in v4.
Related
I'd like to deploy one of the dotnetcore botbuilder samples as an Azure function and point the bot service registration at the Azure function.
I've found a few posts that describe this sort of thing but they seem to refer to v3 of the SDK.
Is this possible with the v4 SDK? If so, is there a sample that demonstrates this or can you provide guidance on what changes are required to the project/code to achieve this?
We are planning to add existing bot which is V4 to our Universal Bot which is in Virtual Assistant template.
For this we have come up with the Skill based approach via which we can add skills to existing VA.
The challenge which we are facing now is that we couldn't find link which was there earlier to convert existing V4 bot to skill (https://microsoft.github.io/botframework-solutions/skills/tutorials/convert-v4-bot/csharp/2-add-packages/).
and the link which there in FAQ section(https://microsoft.github.io/botframework-solutions/help/faq/ ) under "How do I convert an existing v4 Bot to a Bot Framework Skill?" redirects me to a Microsoft page implementing a skill (https://learn.microsoft.com/en-us/azure/bot-service/skill-implement-skill?view=azure-bot-service-4.0&tabs=cs)
The current document has section of migrating Virtual Assistant to Bot framework Skill(Migrate existing Virtual Assistant to Bot Framework Skills GA).
but I cannot find any page in updated document which can guide me to convert existing V4 Bot to skill.
Please help us with the same.
Looks like your problem is solved on GitHub in this issue. For others with a similar issue, here is the explanation.
The link https://learn.microsoft.com/en-us/azure/bot-service/skill-implement-skill?view=azure-bot-service-4.0&tabs=cs described how to implement a skill. If your bot is based on the BotBuilder SDK greater than or equals to 4.7.0, then your bot is automatically a skill. Virtual Assistant that's created based on the Virtual Assistant Template that's greater than or equals to the 0.7 release will be able to connect to a skill without extra work.
Hope this helps.
Recently setup a new bot in BotFrameWork.
Setup a App Registration and Function bot to work with Teams bot integration.
However after trying to migrate the bot it gives error everytime.
I have even tried recreating a bot with same info.
I have triple checked the app ID ect..
Anyone have a recommendation?
Error Message
The migration process requires an active Azure account / subscription. The email account connected to your Azure account must be an admin/owner of the bot for the migration to succeed.
From the migration documentation:
Before migrating a Functions bot created with Node.js, it is required that you use Azure Functions Pack to package the node_modules modules together. Doing so will improve performance during migration and execution of the Functions bot after it is migrated. To package your modules, see Package a Functions bot with Funcpack.
Also, note that Functions bot have not supported since Bot Framework SDK v4. It is recommended you create a Web App Bot instead, which supports the SDK v4.
Hope this helps.
Is it possible to create LUIS Dispatch for existing V3 Bot ? We have v3 bot that's in production and we have gone so far now so its difficult to switch over v4 Bot. However, there are awesome capabilities like LUIS dispatch tool that we would like to leverage.
Ref:-
https://learn.microsoft.com/en-us/azure/bot-service/bot-builder-tutorial-dispatch?view=azure-bot-service-4.0&tabs=jsaddref%2Cjsbotconfig#integrate-multiple-luis-apps-and-qna-services-with-the-dispatch-tool
Given the fact that the source code is available for the LUIS components and the provided examples, I think you can use this tool on v3 bot after some modifications.
It looks like the dispatch tool is only preparing a custom LUIS app that you will query from your bot, so nothing really linked to v4 of bot builder.
I recently built a slack bot via the BotKit toolkit and now want to be able to expand from just slack to many other services. Basically, I was reading https://venturebeat.com/2016/11/02/how-bots-will-work-on-microsoft-teams/
and it states that
"The integration means Microsoft Bot Framework users will be able to make bots for Slack, and Botkit users will be able to bring their bots to additional platforms, like Telegram, Kik, Twilio, and Skype. (Before the change, Botkit was only able to make bots for Slack and Facebook Messenger.)"
However, it is not clear to me how this can be accomplished. Do you mind explaining this to me or pointing me in the right direction? From what I understand, it should be a simple process of having my slackbot basically run within Microsoft Teams or Skype or whatever service.
Thanks!
The VentureBeat link for the Public Preview of Microsoft Teams was referring to the ability to use bots written for Slack (via BotKit or otherwise) within Microsoft Teams with little or no modification necessary. This capability is provided by Message.io. You can contact them for more information or look on their website.
Microsoft Teams also has a native bot platform - the Microsoft Bot Framework (which also supports Slack, Skype, Facebook, and several other chat platforms). BotKit does not yet support Bot Framework.
(#JasonSowers)[https://stackoverflow.com/users/3011564/jasonsowers] is correct - BotKit and Bot Framework are two different bot platforms; today Microsoft teams supports one via Message.io and one natively.
So I think your path is:
Register your bot in the Bot Framework to host the bot, referencing the Botkit. Make sure you add Microsoft Teams as a channel.
Create a package for your bot and [Sideload it][3] in Teams to test.