Enterprise People Bot Azure Resource Requirement

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”.