I have used the Bot Builder Teams messaging extension sample and successfully debugged the project locally on my machine using ngrok. I then proceeded to follow the Azure deployment instructions, and successfully deployed my bot project to Azure.
However, I cannot find instructions regarding what values need to change within my project to now use the assets within Azure. I have enabled the Teams channel on the Bot Channel Registration resource that was provisioned, and I tried updating the botId value within my project's manifest file to match that of the newly provisioned app registration. But I'm still receiving an 'unable to reach app' message when sideloading the app in Teams.
Are there instructions regarding how/what to change within the project so it uses the Azure assets rather than my local ones?
To narrow down what's wrong, have you tried using the Web Chat to test the bot ? If this works, then the bot is working fine in Azure and the issue is for local teams to reach Azure.
Also verify that you are using the right AppID and Password.
Once you have verified that the bot is working in Azure, at the bottom of this page, you will see steps to get a url that you can paste to get the bot added in your local MS Teams instance. (quoting below for quick access)
Copy the https part of the code that is shown in the Get bot embed code dialog. For example,
https://teams.microsoft.com/l/chat/0/0?users=28:b8a22302e-9303-4e54-b348-343232.
In the browser, paste this address and then choose the Microsoft Teams app (client or web) that you use to add the bot to Teams. You
should be able to see the bot listed as a contact that you can send
messages to and receives messages from in Microsoft Teams.
I did finally get my bot working, but found several missing steps within the deployment documentation. I have reported them in a GitHub issue, associated with the relevant documentation article.
Related
I have created a simple empty nodejs chatbot with azure compose. And then created a resource group and published it to azure.
I have followed these 2 links
Create a weather chatbot - https://learn.microsoft.com/en-us/composer/tutorial-create-weather-bot#create-a-new-dialog
Deploy the chatbot to azure - https://learn.microsoft.com/en-us/composer/how-to-publish-bot?tabs=v2x
But I was getting the error HTTP status code NOT Found error.
I tried all the StackOverflow solutions available online none of them worked.
I have deployed a Weather chat-bot to azure using below steps
I have Created a Weather chat-bot using composer using the Document that you have provide in the above DOC.
It is working in local environment as below
Now you have to deploy to azure portal from the composer for that follow the below steps.
Click on Publish and select manage profile as below.
Click on Add new as below.
Goto Crate new resource and click on Next as below.
Fill the all the required details as below and click on Next.
After creatin the manage profile and select the profile as below.
Click the check box that bot that you want to deploy to azure portal as blow and click on publish selected bots.
After deploying to azure open resource and click on bot application in azure portal navigate to test in web chat and it's working as below.
If you deploy it through the Bot composer it will automatically assign the application in sights to your Bot app below is the sample Add telemetry to your bot - Bot Service | Microsoft Learn
For More details refer this link follow the step-by-step procedure.
When I setup a Bot service on Azure, an end point was automatically setup. I then wanted to debug locally so I used ngrok and copied this URL into the messaging endpoint. Stupidly, I didn't save a copy of the auto generated end point Azure provided. Now I'd like to go back to an Azure auto generated messaging endpoint however I'm unsure how to regenerate one to use. I've been informed that this is likely a security feature and to setup a new bot service again. Do I need to setup a new bot service or is there a way of regenerating a key in azure?
This depends on which type of Bot Service you created on Azure - there are two: Web App Bot and Bot Channels Registration. The latter is basically just a "registration" of a Bot in Azure + Bot Framework Services, and it's -intended- for you to host your bot wherever you like (Azure or otherwise). If you created a "Web App Bot" then it will create an Azure Web app at the same time, and the address will be based on that resource, plus an extra bit (see in a moment). To get the first part, the base address, check for the web app resource in Azure, and find it's regular Azure-generated address (I think it's like https://[whateverBotname].azurewebsites.net/). You should be able to visit that in the browser. Next is the "extra bit", which is simply the endpoint inside the app that the bot itself runs on (basically where the bot POST messages must go). By default its "/api/messages".
So, the full address would be https://[whateverBotname].azurewebsites.net/api/messages.
As an extra tip, if you want to change it again to test with NGrok, just paste the address in the Description field - it'll get Saved when you click the Save button.
As an extra extra tip - you can create the OTHER type of Bot - a "Bot Channels Registration" in Azure, which is JUST the registration, that you can use JUST for local development (you'll basically change the address every few hours, as your NGrok endpoint resets).
Hope that helps,
I'm having really annoying problems getting my bot to work in MS Teams. I created it using Bot Framework v4 and deployed it to Azure. I deployed the bot using Direct Line from the "channels" blade and it's working ok. Then in the same blade I deployed it to MS Teams. And that caused issues.
People are telling me that the problem has to do with something about a manifest file and a "valid domains" setting I have to edit. I don't know what those are and I never had to do any of this when I told Azure to deploy it to MS Teams. It seems there's a whole different way to deploy the bot to teams, which is using App studio. I tried that way, and now I see another different issue.
So it doesn't work for me when I deploy with Azure or using App Studio. And I want to research and fix the issues, but first I need to know which method should I try to fix? Which am I supposed to use to deploy to MS Teams? Azure or App Studio?
Note: I'm not asking how to fix these issues. I want to know which method of deployment I am supposed to use. What's the difference?
Let's get the terminology straight first. You are building a bot. In Teams, a bot is just one of the possible capabilities of a Teams app. (The others are tabs, connectors, and messaging extensions.)
The definition of a Teams app is defined at a high level here.
Creating an app package (which is one of the things App Studio can do) is defined here - App Studio can also sideload/upload apps (see below).
Once you've created it, you need to make it available within Teams, first for yourself (and potentially others, if it's allowed in your tenant) via sideloading/uploading, or for your entire organization if you like. That's defined in Upload an app package, with in-depth discussion of the tenant app catalog here.
I am working on Microsoft Bot Framework, I am created the bot through Azure Bot Service in Azure Portal. When I am running my bot application in local emulator its working fine after that published into Azure Bot service.
Here my issue is whenever to test my application in in Azure Portal at Test In Web Chat option the test window will showing like this below.
Added the same bot to Skype channel there also I am not getting any response.
How can I resolve the problem?
Please check your MicrosoftAppID and MicrosoftAppPassword are correctly mentioned in both your BotApplication as well as in Azure Bot Service. Also do check if the same is deployed properly and the MessagingEndpoint is correctly mentioned.
If this was just an issue with the channel your Test in WebChat could have worked properly.
From my experience, it is happen to me with the same situation. I think you select publish as Website. You should select publish as Deployment Script.
I have a bot that I've created by merging LUIS and QnA together in a single project using Microsoft Bot Builder.
I published the bot to an EC2 instance from visual studio and I'm using the Bot Framework Emulator for testing and it works perfectly. (MUST use ngrok for tunneling).
Now I want to deploy the bot on Skype. I logged into the Bot Framework Portal and I registered my bot. Now comes the configuration part.
I'm not quite sure what to set as the HTTP endpoint here.
I found this in the Bot Framework documentation:
Complete the Configuration section of the form.
Provide your bot's HTTPS messaging endpoint. This is the endpoint
where your bot will receive HTTP POST messages from Bot Connector. If
you built your bot by using the Bot Builder SDK, the endpoint should
end with /api/messages.
If you have already deployed your bot to the cloud, specify the endpoint generated from that deployment.
If you have not yet deployed your bot to the cloud, leave the endpoint blank for now. You will return to the Bot Framework Portal
later and specify the endpoint after you've deployed your bot.
When I published from Visual Studio, from the Azure App Service Activity windows, I found this line:
Start Web Deploy Publish the Application/package to https://ec2-00-000-000-00.compute-1.amazonaws.com:PORT/msdeploy.axd?site=bots ...
I used that address for the Messaging Endpoint in the configuration and I published my app. However when I'm testing it on Skype, i'm not receiving any messages from the bot.
I don't know what the problem is exactly, does this have something to do with ngrok? Or am I missing a step here, is there something else I should be doing to deploy the bot on Skype? Maybe something to do with the appid/password that I need to use ... i really don't know
Would really appreciate an explanation of how this works exactly. I don't really understand how the whole deployment procedure works exactly, feels like i'm swimming in murky waters.
Your endpoint is going to be the root of your deployed web application instance, plus the route that your bot is listening on.
For example, one of my bots is deployed to the free version of Azure Web Sites. The URL for a site such as this is https://APPLICATION_NAME.azurewebsites.net and the route that the bot listens on is the default /api/messages. This makes the endpoint https://APPLICATION_NAME.azurewebsites.net/api/messages.
If you connect directly to your app's endpoint, you should at least get a JSON dump with an error message. To make sure your site is getting deployed, drop an HTML file into the root of EC2 and see if you can access this.