Reputation: 4730
I'm trying to deploy the ms teams auth bot to azure. The bot gives a welcome message when I tested it using the bot framework emulator. Then I ran these steps to deploy my bot to azure. During the deployment steps, I used the same app id and password throughout the whole process. Then I tested it on azure and it just fails:
I look at my browser's network requests and I see this:
HTTP POST: https://webchat.botframework.com/v3/directline/conversations/JYtg14OvcjS7FiNwCMXzH1-g/activities
Response:
{
"error": {
"code": "BotError",
"message": "Failed to send activity: bot returned an error"
},
"httpStatusCode": 404
}
I streamed my application logs and it gave me a big HTML response you can see here. But it's just a 404 page response.
I tried to run this in my bot emulator, pointing to the bot in production and it gave a 404 response as well:
.deployment
file when I zipped the contents. (The file explorer was hiding the file.) So now I included it in my zipped contents and redeployed by bot again. (Unfortunately, the bot is still behaving the same.).deployment
file was zipped. My mac just didn't show it. I updated the screenshot to show my .deployment file above.Upvotes: 0
Views: 2786
Reputation: 7241
OPs issue ended up being that they need to make their App Registration available for ALL accounts, including personal. To do so, follow these steps
I'll keep the answer for posterity, but if you're running into this issue, my comments provide good troubleshooting steps.
Aha! The issue was this step. You need to zip up the contents of the project folder and not the folder itself.
This:
Instead of this:
When you deploy, your folder structure will look like this:
You aren't the first person to run into this. I've created a PR to clarify this. Let me know if you think the change I made should say something else.
Sidenote: The web.config
is created upon deployment. My mistake with that comment.
Upvotes: 1