Skip to content

Enterprise People Bot Azure Resource Requirement

Jump to bottom
Thomas Chung edited this page May 11, 2021 · 2 revisions

Overview

Like most bots, the Enterprise People bot has basic Azure resourcing requirement.

The following chart goes over all the different resources consumed by the bots and the functionalities they provide to the bot.

Resource Description Required (Local) Required (Production)
Bot Service Used to allow the bot to communicate with clients thru different channels. This is also required for the bot to perform OAuth calls against Microsoft Graph API by authenticating against Azure Active Directory. Yes Yes
LUIS Language Understanding service enables the bot to understand users’ utterances and translate them into intents and entities. Yes Yes
Azure Active Directory Provision the application’s ID and password for the bot. This allows the bot to be authenticated against when then allows the bot to setup authorization against the directory’s Graph APIs. Yes Yes
App Service Used to host the bot’s runtime. No Yes
Azure Cosmos DB Allows the bot to store state of a user’s conversation. No Yes
Application Insight Allows the bot to send telemetry data for bot monitoring and alerting. No No
Blob Used to store user conversation transcript for monitoring and analysis No No

Provisioning Azure Resources

In this part, we will do the following:

  1. Provision the bot’s resources using Publishing Profile.
  2. Extracting keys for bot resources
  3. Configure OAuth Success Response Return URI
  4. Configure OAuth permission scope in AAD application.
  5. Configure OAuth connection in Azure Bot Service.
  6. Configure bot settings in Composer.

Provision Bot Resources Using Publishing Profile

  1. On the left navigation pane, go to the “Publish” tab.
  2. Select “Publishing Profile” tab -> then click “Add new”.
  3. A new “Add new publishing profile” window will pop up. In “Publishing target”, select “Publish bot to Azure”.
  4. In the same window, give the bot a name (e.g., EnterprisePeopleBot)
  5. Click “Next”
  6. In the next window, select “Create new resource”.
  7. Click “Next”
  8. In the “Configure resources” window below, enter the corresponding information.

In the “Azure details” subsection

Azure Directory – select the Azure Active Directory tenant organization that owns the resources that we will provision. Subscription – select the Azure subscription within the AAD tenant organization that owns the resources that we will provision. Resource Group – select “Create new”, then enter a name for your new Azure Resource Group where the resources will be logically grouped under.

In the “Resource details” subsection

Name – enter a name for the resources that will be created for each Azure resource type. Region – select the Azure region (e.g., West US) that the resources will be provisioned to. LUIS Region – select the Azure region (e.g., West US) that the LUIS resources will be provisioned to.

  1. Click “Next”
  2. In the “Add resources” section, the three required resources (Microsoft Application Registration, Azure Hosting, Microsoft bot Channels Registration) is already selected.

However, uncheck the following:

  • Azure Cosmos DB
  • Application Insights
  • Azure Blob Storage
  • Microsoft Language Understanding Prediction Account
  • Microsoft QnA Maker
  1. Click “Next”
  2. Confirm your list of resources in the “Review & create” window
  3. Click “Create”
  4. At this stage, the Bot Composer will provision these resources above to Azure. You can see the progress in the pop-up on the top right corner.
  5. If completed successfully, you will see the message "Provision Success".
Clone this wiki locally