We will explore the deployment of the bot microservice in this section. This deployment installs various resources and configures them to make the Bot work. EmpowerID Bot is offered as a SaaS solution. However, customers can deploy and install the Bot in their private cloud environment. This series of docs will provide you with details of each step involved in deploying bot service and configuring the bot for different channels.
Getting Started
Prerequisite
Prerequisite: Before an organization’s Azure AD users can use Chatbot from channels like MS-Teams, administrators will have to make sure the following things have been done along with the deployment steps below.
- Users from the organization's Azure AD tenant must be inventoried into EmpowerID. Please find details about Azure AD inventory here Azure AD SCIM Connector Features.
- Inventoried Azure AD accounts must be linked to an EmpowerID person object.
- EmpowerID person object should be assigned the “EmpowerID Chat Bot Access” management role. Details about the management role required is provided in Management Roles Needed to Access the Chatbot.
Any accounts not inventoried into EmpowerID or failing any requirements mentioned above will receive an error message "Sorry, authorization failed. Please contact your system administrator regarding your Teams account.” when they try to access the Chatbot.
Set up App Service
Set up Azure Cache for Redis
Set up the Cosmos DB
Setting up the Vault
Setting up the Microsoft App ID
Setting up the Microsoft App ID
Verify Configurations & Publish the Bot Microservice to Azure
Verify Configurations & Publish Bot Microservice
Setting up the Bot Channels Registration
Setting up the Bot Channels Registration
Provisioning a Bot Tenant
Configuring the Ask to See Commands
Configuring the Ask to See Commands