Bot publishing and provisioning failed from within Composer

Question

Hi.

There have been a few posts on this topic and I have run into the same issue. (I couldn't really find a solution to the topics).
When trying to publish to Azure from Composer having selected Create New Resources it fails during the provisioning process.
I have an Pay as you go Azure account. It uses my personal email address and Composer uses the same email address.

One thing I noticed, in Composer, when you click on View Account on Azure in the top right hand tab, the Microsoft page comes up for you to sign in with but it says you can't use a personal email address to sign in. Yet, I used my personal email address for Composer and Azure. Although I think it is unlikely this is the cause of my issue.

I haven't tried manually creating all the resources and then importing them, because even after looking at the docs I couldn't quite work out what resources need to be created.

If there is a solution to this or if anyone can help with the resources that are needed that would be great.

Thx

Answer 1

Hi. Thanks.
I think I have it worked out.

When you let Composer do the provisioning for you it gives you a list of resources you can select (see image below).
But these resources need to be registered under your subscription/Resource Provider in Azure.

The problem I had was trying to work out which resources to register - for instance for Microsoft QnA Maker to provision successfully (it is optional) you need to have Microsoft.Search registered.

The only way I knew what to register in Azure was to try publishing - it would fail - and when it failed it would tell me the reason it failed eg. I hadn't registered Microsoft.xxxxxx.

I still haven't published the bot - I finally registered all the resources and went to publish - but because I had tried and failed quite a few times, Azure throttled the ability to publish/create resources.

I got in touch with Azure and they said it is 120 hours ie 5 days, before I can try again.

5 days is a long time to wait - if anyone has any advice re: the process for trying to get back the ability to publish sooner, that would be helpful.