0
votes

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?

2

2 Answers

2
votes

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.

0
votes

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.