Set up Azure Health Bot
In this exercise, you'll do the following:
Set up Health Bot from Azure portal
Configure and enable the integration between Dynamics 365 Omnichannel and Health Bot
Configure and enable Bot channel to obtain a Bot ID
Azure Health Bot empowers developers in healthcare organizations to build and deploy AI-powered, compliant, conversational healthcare experiences at scale. It combines built-in medical database with natural language capabilities to understand clinical terminology and can be easily customized to support your organization's clinical use cases. The service ensures alignment with industry compliance requirements and is privacy protected to HIPAA standards. To learn more about Azure Health Bot, reference this Azure Health Bot documentation.
Task 1: Install Azure Health Bot in Azure subscription
While logged into your Microsoft 365 tenant, open a new tab in your internet browser incognito or in-private mode and navigate to Azure portal at https://portal.azure.com
Search for Azure Health Bot in the top search bar and select it from the search results.
Select the Create button to create a new Azure Health Bot instance.
You'll be redirected to the Azure Health Bot page. Enter the following information:
Subscription: Choose your Azure Subscription
Resource Group: Use the resource group you created in environment preparation
Name: healthbot-iad (although you may choose any name)
Region: Choose the region closest to you
Plan: Free (F0)
Select Review + Create.
On the Review and create page, verify your details are correct as Azure validates your Health Bot. When the create button is enabled after validation passes, select Create.
It will take few seconds to run the backend process before the Create button is enabled.
You'll be redirected to the Deployment page for your new Azure Health Bot.
When deployment is complete, the Go to resource button will enable. Wait until deployment is complete for the Azure Health Bot, then select Go to resource when enabled.
You'll be redirected to the Resource page for your new Azure Health Bot. Select the Management portal link on the right of the Essential section to open your Azure Health Bot instance configuration page.
Please copy this Management portal link and store it to access the Health Bot later.
Your new Azure Health Bot instance homepage appears.
Congratulations! You've successfully created a new Health Bot instance in your Azure tenant.
Task 2: Update Azure Health Bot settings to enable Dynamics 365 integration
On the Azure Health Bot homepage, expand the side navigation bar to see the sitemap labels.
After expanding, you'll see the sitemap labels next to the icons.
Select Configuration > Conversation on the navigation bar.
The Interactions tab appears.
Select the Human Handoff tab in the Conversation settings.
Scroll to the bottom of the Human Handoff page. Under Dynamics 365 Omnichannel, toggle Enabled for Bridge Messages. This is required to allow communication and bridge messages between the Azure health Bot and Dynamics 365 Omnichannel for Customer Service.
Select Save in the top right.
Now let's enable the Health Bot for Microsoft Teams Channel.
Navigate to Integration > Channels.
In the Channels list, select the toggle to enable Microsoft Teams.
This will bring out a side window with your Bot ID information. Copy and store the BotId value for later to use when creating the Dynamics 365 Application User.
Select Save to enable the Teams channel and your Microsoft Teams toggle should reflect accordingly.
Congratulations! You completed the Azure Health Bot settings for integration with Microsoft Teams and Dynamics 365 Omnichannel for Customer Service.
Task 3: Obtain Azure Application ID
In this task, you'll be using the Azure Application ID you created in your Azure tenant during environment preparation. You may have called it "MCH Application ID". Registering this ID established a trusted relationship between your Dynamics 365 app and the Microsoft identity platform.
We'll now obtain the client ID and store it to later create a Dynamics 365 Application User to bridge the authentication between Azure Health Bot and Power Apps.
Navigate back to the Azure portal and search for App Registrations in the Search box.
The App registrations homepage opens to the Owned applications tab.
Select the All applications tab.
To search for our Application ID, type "MCH Application ID" in the Search box.
Select the MCH Application Id app registration resource. Copy and store the Application (client) ID for later to use when creating the Dynamics 365 Application User.
ID values have been removed in the screenshot for privacy purposes.
Congratulations! You've successfully obtained the MCH Application ID from Application Registrations in the Azure portal.