Unable to deploy bot via ARM template

Anton Eliseev 96

I followed step-by-step this article https://video2.skills-academy.com/en-us/azure/bot-service/bot-builder-tutorial-basic-deploy?view=azure-bot-service-4.0&tabs=csharp%2Cvs

I created test Echo Bot just using C# VS template for .Net Core 3, changed nothing and decided to test deployment to Azure.
Everything worked fine until I tried to perform this step https://video2.skills-academy.com/en-us/azure/bot-service/bot-builder-tutorial-basic-deploy?view=azure-bot-service-4.0&tabs=csharp%2Cvs#deploy-via-arm-template-with-new-resource-group

It failed with error Deployment template validation failed: 'The resource 'Microsoft.Web/serverfarms/TestEchoBotPlan' is not defined in the template.

The issue seems to be known: https://stackoverflow.com/questions/63332059/deployment-template-validation-failed-the-resource-microsoft-web-serverfarms

So I decided to do as it suggested and created new resource group manually.
After that I tried to perform this step https://video2.skills-academy.com/en-us/azure/bot-service/bot-builder-tutorial-basic-deploy?view=azure-bot-service-4.0&tabs=csharp%2Cvs#deploy-via-arm-template-with-existing-resource-group

It failed with message Bot is not valid. Errors: The bot name is already registered to another bot application..

The issue also seems to be known: https://github.com/MicrosoftDocs/bot-docs/issues/1324
But in that case problem was apparently related to same names in the parameters botId, newWebAppName and display-name and fixed by changing them. In my case all these values are already different but issue is the same. Deployment fails in every combination.

Examining the deployment itself I see that fail occurs on the last step, when first ones are fine and web site is perfectly working

Wasted half a day in attempts to fix it I decided to perform last steps from the initial article and it succeeded. Deployment preparation passed and zip-file was uploaded.
Though, step 5 from here couldn't be reproduced since there is no such option https://video2.skills-academy.com/en-us/azure/bot-service/bot-builder-tutorial-basic-deploy?view=azure-bot-service-4.0&tabs=csharp%2Cvs#test-in-web-chat

So now I don't know what was wrong and how to fix it. I just can't deploy my bot normally and don't know how to test it. Azure support was also unable to help and addressed me to this forum.
Any ideas?

romungi-MSFT 45,961 Reputation points Microsoft Employee

2020-09-28T08:28:18.877+00:00

@Anton Eliseev Thanks for the detailed information of your setup and steps you followed for deploying your bot. From the above details it looks like you are stuck with testing your bot on the Azure portal or webchat.

The test in webchat feature should be available in your bot channel registration resource, you can list of all your bot resources by using this link for your subscription and check the resource type as "Bot channel registration" and use the resource that is created i.e TestEchoBot. If you have created a webapp bot you should be able to test in webchat directly from the portal.

Please do let us know if this helps.
Anton Eliseev 96 Reputation points

2020-09-28T10:34:56.06+00:00
@romungi-MSFT Thank you for response.
As I mentioned above I don't see any Bot Channel Registration resources. Deployment via ARM template fails on the last step (see the image attached). So I have only web application and service plan as resources.

So there are 2 problems:

Inability to perform deployment for new resource group

Inability to fully perform deployment for existing resource group
both by different reasons.

It's worth to mention that I use almost clear new Windows 10, untouched Echo Bot from template and brand new free Azure account.

So I can't figure out what could be wrong on my side and according to links I attached these issues are known but I don't know their current status or workaround. In fact, initial article just doesn't work when I perform all the steps on the clear system and I failed to find any other docs for creating and deploying the bot.
romungi-MSFT 45,961 Reputation points Microsoft Employee

2020-09-28T11:41:55.897+00:00

@Anton Eliseev Yes, the workarounds are for some scenarios and it would be great if you can get more details of the error when the ARM template gets failed during deployment. For example, you can use the cli command to get the request and response of the deployment to understand if there is a limitation with the subscription. The activity log(bell icon at top right corner) from azure portal should also let us know more details to debug further.
Anton Eliseev 96 Reputation points

2020-09-28T12:02:27.643+00:00

@romungi-MSFT As I mentioned above the error is the same as in that github issue.

Message: Bot is not valid. Errors: The bot name is already registered to another bot application.. See https://aka.ms/bot-requirements for detailed requirements.

ErrorCode: InvalidBotData

But in my case all the names that Yan mentioned are already different.

Do I need to provide any other info like CorrelationId or something?
romungi-MSFT 45,961 Reputation points Microsoft Employee

2020-09-28T12:36:57.15+00:00

@Anton Eliseev I think the issue might be that this name might be in use with registration created earlier. If possible I would suggest to delete this deployment or resource group from portal and then try to create a new app registration. This will ensure that the new app is not used anywhere i.e the app id.

Now, you can try the ARM template deployment with an existing or new resource group where you would want to use a new app service plan. Use the app id and secret from above and provide a unique name for the bot like "MungiBot" and try to follow the rest of the steps. Thanks for your patience.
Anton Eliseev 96 Reputation points

2020-09-28T12:42:10.487+00:00

@romungi-MSFT The thing is that I created app registration exactly by the article you suggest and performed next steps right after its creation, so it can't be used anywhere else since it is a new Azure account.
But okay, I can try to perform everything from scratch except for step with creating deployment for new resource group (since it's known not working) and create it manually.
Anton Eliseev 96 Reputation points

2020-09-28T12:56:17.3+00:00

@romungi-MSFT I tried everything as you suggested - the same issue again.
Kyle D 6 Reputation points

2020-09-30T23:03:52.893+00:00

Hello, @Anton Eliseev - I would like to help with your issue but it could use some more focus. You say the new-rg template fails, but then you say the existing-rg template also fails, and you're also having problems providing the template with a unique bot ID. Do you want help with bot ID error or just the errors with the failing templates? If you've already discovered that you need to provide an unused bot ID then why did you mention that part?

If I may ask, what ARM template are you using and where did you get it? If you got it from the samples repo and you haven't pulled the latest changes recently then you'd be using a broken template as discussed in the Stack Overflow question you linked to. There was a PR with a fix 9 days ago: https://github.com/microsoft/BotBuilder-Samples/pull/2716
Anton Eliseev 96 Reputation points

2020-10-01T11:29:32.44+00:00

Hi, anonymous userD-3625
In case with new-rg template it fails on template validation.
In case with existing-rg template validation is successful but it fails in the deployment process.
As for botID uniqueness: you mean bot ID must be unique across all azure users? If so, I didn't know that, thanks. Following article I haven't noticed this info. Maybe I was just not attentive enough, but I thought it should be unique across my apps on Azure.
As for templates I am using: yes, they are from sample. But I installed them less than 9 days ago, it was on Sunday 27th as I remember.

Anyway, I already had a call with one of MS engineer, we reproduced the problem and I was shown how to perform bot creation and deployment manually on portal + publish with VS tools as a workaround. But thank you for help!
Kyle D 6 Reputation points

2020-10-01T17:37:15.277+00:00

Are you saying you no longer need assistance? Would you like to post that as an answer?
Anton Eliseev 96 Reputation points

2020-10-01T18:20:43.217+00:00

I have tested with botId value globally unique across entire Azure scope and it works! Thank you very much for clarification. I think we can flag it as an answer
Anton Eliseev 96 Reputation points

2020-10-01T18:40:04.623+00:00

I added it in answer, thank you

Accepted answer

Anton Eliseev 96 Reputation points

2020-10-01T18:37:36.18+00:00
As a result:

First problem with new resource group template is about to be fixed (or fixed already in new sample versions)

Second problem with existing resource group deployment solves by setting globally unique botId across all Azure (Thanks anonymous userD-3625 for clarification)

There is alternative way for creating and deploying bot without ARM: Go to Azure Portal -> Add new resource -> Select "Web App Bot" -> Fill in all necessary data and create bot resources -> Click Publish on one of created resources (of type App Service if I remember correctly) -> Download .PublishSettings -> In VS bot project click Publish -> Select "Import from.. " option -> Choose you publish settings file -> Publish bot
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Unable to deploy bot via ARM template

0 additional answers

Your answer