Navigate to the Azure portal.
In the right pane, select Create a resource and search for Bot. Select the Azure Bot card.
Provide the necessary details to create the Bot. Choose Multi Tenant for Type of App, and Use Existing App Registration for creation type.
The Microsoft App Id and Password used here should be of the application you created while completing the step “Setting up the Microsoft App ID.”
After creating the Bot Channels Registration, you may add an icon, a display name, and a description. Select the Bot profile Tab and complete the necessary information.
Please note that end-users will see this information in the Bot.
Provide the Messaging Endpoint of the Bot. The syntax of the endpoint is HTTPS://[app service url]/api/messages. App service URL is the URL for the Linux App Service you created in step#1.
Click on the Channels tab to configure the bot for different available clients. Add Teams and Direct Line Channels to the list of default channels.
Open the Bot Service Deployment Package in the Teams App Manifest folder locate the manifest.json. Update the id and the botId to that of the Microsoft App ID (i.e., the ApplicaitonID) and save the changes. You may also update the Name and Description values as you see fit.
Now, We will deploy the bot into Microsoft Teams. After updating the manifest.json file, please zip the contents of the Teams App Manifest folder.
Upload the zip as an app into teams. You can use Upload a custom app option in Team to test the uploaded bot.
Your Bot won’t work until you have completed all the required configuration, made necessary entries in the database as below, and have provisioned a Bot Tenant for the Microsoft Teams in the next step.
In the next step, we will provision the bot tenant.