- [Instructor] Now we just saw my bot working in Microsoft Teams but I used the old way of registering the Microsoft Teams bot. Well, at the top here I see this big disclaimer, which says with the launch of the new Azure Bot Service, we are migrating all bots by x-x-x date, learn more about the migration or start migrating. So let's also look at the new way of registering bots. It's very simple, I will point out one thing though, that I'm logged in with a different user identity at this point.
The reason being is that this identity that I'm going to use not only it needs to be a tenant administrator, in order to administer bots, you also need to have an Azure subscription associated with this user account. So make sure that you use a tenant ID that actually has both. So I'm going to click on Create a bot or skill, and here you see that I have already a few bots registered, but let's create a new one. And I'm going to click on this create a new bot button, and it shows me this button, the URL is different, and I'm going to click on this Create button.
And now it launches me into the Azure portal. It gives me three choices here. The Bot Channels Registration is the bare bones register a bot and you host the bot service, the web service, yourself. Which is probably what I prefer to use now because I'm in dev mode and I'm already hosting the service using ngrok so that's what I'll use. The other two choices are, Web App Bot, is basically bot channels registration, plus comes with all the paraphernalia for running a Azure website which you probably need.
So chances are this will also grow over time, so that's definitely a very valid way to register a bot. And the Functions Bot is, instead of a website, you get Azure functions. So let's click on Bot Channels Registration, click on Create. And let's give it a name, I'm going to say myFancyTeamsBot. Free Trial is great, give it a resource group, I'll just put in an existing resource group.
Put it in a location, East US is great. And I'll just go with the free plan. And the Messaging endpoint as before, this is the ngrok URL. And as before, I have the flexibility of changing this URL later as well so I will simply go ahead and say https://something. Application Insites, Off, you're welcome to use it, but it's not in the purview of this course. And I'll click on this Create button. So my bot was called myFancyTeamsBot, click on the Create button, and then this takes a few seconds for it to get created so please be patient.
So it'll say Deployment in progress, as I mentioned you have to be a little patient. And let's go to the All resources area, or you can just click on this Go to resource button as well. But let's go to All resources, and you see that myFancyTeamsBot is now registered. Let's also go to my Bot Framework portal, hit refresh here, and go to My bots area. And you see that I can also view my bot registered here. Now back inside of the Azure portal, I can click on myFancyTeamsBot, and I can choose to manage it.
So if I want to test the bot in Web Chat, I use this button here, right, so this is just like how I tested it in teams, but now I can test it in Azure portal. I can choose to view analytics from here, I can choose to add Channels, so let's click on that. And the basic channel that I have is Web Chat. I can choose to configure the Teams channel by just clicking on this button. Let's go and add the Teams channel.
And now my bot is registered to use Teams. Let's go to Settings, under settings is where I can change the endpoint. But one important thing that I want to mention to you, is that this bot is also an Azure AD application. What do I mean by that, let's see that next.
- What are bots?
- Creating bots
- Testing using ngrok
- Deploying bots to Microsoft Teams
- Testing bots
- Bots as Azure AD applications
- Updating bot registration in Azure
- Building the bot package