![]() First, let’s note down the bot app ID and secret for later. ![]() Now that our bot resource has been created, we can proceed with configurations. Configuring the bot credentials and channels After purging the vault, delete the deployed bot resource and try again. This happens by searching for Key vaults via the field at the top of Azure Portal, and selecting Manage deleted vaults. If the deployment (partially) fails, check if a key vault with the same name has recently been deleted and needs to be purged first. After the bot resource has been created, click on Go to resource.Finally, go to the Review + create tab and click on Create.Optionally, you can add tags to the Azure Bot resource as per your organization’s tagging conventions.Leave the Creation type to its default setting ( Create new Microsoft App ID).Select Multi Tenant as the Type of App.The default pricing tier is Standard but by clicking on Change plan you can downgrade it to Free if you don’t require premium channels.The correct subscription and the resource group should already be selected.You can specify the display name for your bot separately the handle is purely a unique identifier for your bot. On the Basics tab, as the first thing, give the bot a unique name as it’s “handle” (e.g., projectname-bot).Inside the newly created resource group, click on the big blue Create resources button.The Key Vault is used for storing the client secret required for authentication. The Azure Bot resource is required for handling the communication between the bot code hosted in Azure and the client application (Microsoft Teams, in this case). West Europe if your users are in Europe)Ĭreate the Azure Bot (and Key Vault) resourcesĪfter the resource group has been created, navigate to it, and create the Azure Bot and Key Vault resources according to the steps below (the vault gets created automatically when you create the bot resource). Give the resource group a name according to your organization’s naming conventions (e.g., projectname-rg).Select the subscription you wish to use.On the left, click on Resource groups and then Create. ![]() Let’s start by creating a brand new resource group in our subscription, where we will later deploy the resources required by our bot. So let’s make all of that happen! Creating a new resource group for your bot In addition, you’ll need an Azure AD application registration for authentication. You’ll need to create and configure four different resources for the bot in Azure: an Azure Bot, a Key Vault, a Web App, and an App Service Plan. Because of this, the code always needs to live somewhere else, and Azure is a natural choice for this purpose. How to create and configure the required resources for a bot via Azure PortalĮven though Teams offers the user interface for us to use the bot, it does not serve as a place for hosting the actual bot logic. If you run into any issues while following the written instructions or prefer to learn things by watching videos, below is also a demo video containing all of the same steps. How to deploy your bot to Azure (and finalize the resource configurations).How to test and debug the bot code locally, and.How to create a Teams bot code project using the Yeoman generator.How to create and configure the required resources for a bot via Azure Portal.In this guide, I’ll give you step-by-step instructions on: ![]() If this is the first time you are creating a Teams bot - or if it has been a while since you did it last time and need a reminder - this blog post is for you! Things are always easy when you know how to do them, right? Creating a Teams bot is not a complex process, but figuring out all the different things that are required for the first time can seem like a challenging feat to accomplish. If you are brand new to Teams development and would like to familiarize yourself with the general principles and what is possible, take a look at another one of my articles called How we can extend Teams with custom apps - the non-technical explanation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |