Bot published to Azure: "" is not a valid LUIS application id

Describe the bug

I have a very basic bot, created in Composer with Luis as Recognizer Type:

• It works when running the bot locally in the emulator.
• After publishing the bot to Azure, I always get following in the webchat: “” is not a valid LUIS application id.

Version

Browser

• Chrome
• Safari
• Firefox
• Edge

OS

• macOS
• Windows
• Ubuntu

To Reproduce

Steps to reproduce the behavior:

1. Start by creating a new bot using the EmptyBot template.
2. Add unknown intent trigger and add a response message.
3. Switch the bot Recognizer Type to LUIS.
4. Add an intent called ‘greeting’, and a few sample utterances (‘hi’, ‘hey’, ‘hello’). Add a response message.
5. Deploy the required Azure infrastructure as such (replaced secrets by ***):

   npm install
   node provisionComposer.js --subscriptionId=*** --name=Prefix-EmptyBot2 --appPassword=*** --environment=Dev --location=westeurope --customArmTemplate=DeploymentTemplates/function- template-with-preexisting-rg.json
   

6. Copy-paste the command output json configuration into a new profile in Composer’s Publishing tab using the Azure Functions destination type.
7. In Composer, in Settings, Bot Settings, change authoringRegion to “westeurope”. (Sidenote: we do this here in settings, as the next action in step 8 does not let us modify the region, region is fixed to westus and grayed out)
8. Go back to Design Flow click on Start Bot. Copy the authoringKey from the Json received in step 5 in the LUIS Primary key field.
9. Click on Test in emulator. Test the bot, it should work well for both the ‘unknown’ and ‘greeting’ intent.
10. Note that at this point in the Settings, Bot Settings the endpointKey is still empty (might be normal)*
11. Now go to Publish and highlight the Azure Functions publishing profile we created earlier. Click Publish to selected profile.
12. Now open the resource group we published to in Azure, navigate to the Bot Channels Registration and find Test in webchat.
13. Test the bot again. Both unknown & greeting intents will fail with : “” is not a valid LUIS application id

Expected behavior

Once deployed in Azure, the bot should be able to get the Luis application ID, so it can recognize the intent.

Screenshots

Simple bot dialog:

Working in the emulator:

Luis error when running in Azure:

[luhan2017]

@bartbilliet , this is a known issue and we’ve fixed in #3128 , we will release a patch version soon, will keep you posted.

[srinivasnarula]

@cwhitten - Thanks for that. Please close this ticket. I’ll open a new one.