Microsoft 365 Community Community Demos, 2 Sep 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Build your first conversational chatbot for Microsoft Teams

Description

In this 11-minute developer-focused demo, Stephan Bisser steps through elements to have in place for the build. In Bot Framework Composer, he selects the CoreWithLanguage bot template with triggers calling an Azure Bot. To the bot, he adds the GetReportsDialog trigger, OAuth login service connection, discusses storage on turn.tokens, installs Microsoft.Bot.Components.Graph package for more action options and deploys the bot to Azure. Finally, he creates a new Teams app in App Studio and adds the Bot to the Channel. This PnP Community demo is taken from the General Microsoft 365 Development Special Interest Group (SIG) - Bi-weekly sync call recorded on September 2, 2021.

Demo Presenter: Stephan Bisser (Solvion) | @stephanbisser

Supporting materials:
• Documentation - Bot Framework Composer documentation | http://aka.ms/bfcomposer
• Documentation - Add authentication to your Teams bot | https://docs.microsoft.com/microsoftteams/platform/bots/how-to/authentication/add-authentication?tabs=dotnet%2Cdotnet-sample
• Documentation - Create your project | https://docs.microsoft.com/microsoftteams/platform/get-started/first-app-bot?tabs=vscode#create-your-project

Learn more:
• Learn more about the Microsoft 365 Patterns and Practices community at: http://aka.ms/m365pnp
• Visit the Microsoft 365 Patterns and Practices community YouTube channel: https://aka.ms/m365pnp-videos

A

Hi everybody and welcome to my demo on building your first conversational chatbot for microsoft teams. In case you just want to reach me after the call use my at least twitter handle. So you can reach me on twitter. If you have any questions about what I'm demoing today, um as you might know, there are few, let's say: options when building chatbots in the microsoft world. You got pva coming from the power platform, you got the microsoft bot framework and azure bot service and, of course, some other options as well.

A

uh What I'll do today is I'll go through a demo uh which I've built using button composer so but from a composer, is the more or less graphical user interface built on top of the microsoft bot framework, which you can use to build bots, not only for teams but in general, and I've prepared a little bot, which I'm gonna walk you through um in the next couple of minutes, so um I won't build anything from scratch. I've prepared the demo already and I'll walk you through that. um So first things.

A

First, if you go ahead and create a podcast composer, you got a lot of templates. You can use you can create an empty bot. You can create a more or less conversational bot. You can uh leverage the templates built by microsoft or build your own. I've gone with the core bot template, which includes at least language understanding, so it comes with some basic triggers in there. It comes with some language understanding functionality in there.

A

If you go ahead and create a bot, you need to at least assign your bot your language, understanding key. So you got to go to the azure portal, create a new lewis application or luis service, get the offering key from there and paste it into your composer bot, and the second thing I have done already is I've created a azure bot which, which was then called in the past, block channel registration service and I've pasted in the microsoft app id and my microsoft app password.

A

So um switching to the azure portal, I've created an azure bot uh with that azure bot comes a new enterprise application for app registration for you, you got to get. You got to get the microsoft app id and the app secrets based into composer and what I've done as well, because as we're speaking about building a bot for teams and building a bot targeted to the microsoft 365 ecosystem, we of course need at least some basic functionality um coming from azure id or from the graph. So what I've done for my azure bot is.

A

I have added a new oauth connection, which is uh of type service provider azure ad and in there you need to at least provide client id and client secret, and of course, you need to provide the resource, url, you're, gonna, you're, gonna use um within your bot uh use case then, which is in my case the microsoft graph, and you need to define the scopes you want to um you want to tackle, which is, in my case some basic ones. Like user read, uh profile open id and stuff.

A

So that's basically the preparation you need to fulfill before you can uh before you can, give it a go and then going back to composer. What I have done right now is within my root dialogue, which is called core with language dialogue.

A

I have added some basic triggers and some have been coming from the default template like reading can for help and stuff like that, and what I've done is I've added another trigger called get reports dialogue, because what I want to do is whenever a user interacts with the with the chatbot in microsoft, the user should be able to get basic information about his direct reports. So what I've done here is I've added the trigger and, as you can see, on the right hand, side here.

A

This trigger has some trigger phrases, so language understanding kicks in and whenever user asks the bot something about. His direct reports like show me the direct reports or stuff like that. This trigger will be triggered and then a new dialogue will begin, and this dialogue is called get reports dialog and in here um you'll, see the first connection to my azure id app with the oauth login, because somehow the chatbot needs to know who the user is and basically get the credentials of that user and get the user contact.

A

So I'm using a uh an action called oauth login and in there I just need to provide my connection. Name remember. This is the connection name. I have uh added to my azure azure bot with this ol service connection, which is called aadsbi, and then you can give it a title and stuff like that, and the most important piece of information here is that the the token property. So, where should composer? Where should the bot store the token to which is then received upon when the user um logs in which is in our case turn.token?

A

So it's valid for the current turn and the property is called token, and with that token I can then go ahead and go to the microsoft graph and, as you can see in here, I have um I've added actions for the microsoft graph, so those can be used and installed right into your composer based bot using the package management tool and in there I have just installed two basic packages which don't show up right now.

A

But if you search, for example, for graph, you can basically just install the microsoft graph package and there's another one for teams which then give you more more options in terms of actions you can use like get the user get the signed in user's profile and in there we just need to provide again the token turn.

A

The token was the property we have assigned within our oauth login action and the actual value of the token is stored into the token property, and then with that, as we have the current signed in users profile, we can then of course store that information in another property called turn.user, and then we can use that property in another action, get direct reports of a user, and this action basically just asks for a user id and as we have the user id with the signed in user's profile, we can then go ahead and say: okay, the user id is turn.user.id, and then we store that again in another property called turn reports, and with that current reports we can then go ahead and get the profile for each report.

A

For the sake of simplicity, I have just added one action: usually you would do a for each loop and loop through all uh direct reports, you'll get back and then get for each report, because you don't you just get the id of that report uh or of that user, which is a report of that uh signed in user, and then you go ahead and get the full profile. So you get display name first name last name: email, address, user, principal name and stuff like that.

A

I've just done it for one user, turn.report and the first occurrence dot id and then what we'll do is we'll just really simply send out the users display name and the user's email address, um and that's basically it so if I'm gonna run that bot right now, just right from composer click start um and we'll give it a minute or so to start I've already prepared a new microsoft teams app with the within the app studio.

A

um I have pasted in the uh microsoft f80 of the azure bot I've shown earlier and then what I can do from here is just go ahead and install and edit and I've already installed it. So the conversation won't be playing we'll see if we're gonna go back, the bob is already running, so I can go ahead now and say. Show me my direct reports and what the bot will actually do now is.

A

If uh we are lucky, we should get the the login um prompt, because I've restarted the bot right now, um but you see it's all the user account is already logged in so it reaches out to the graph gets the current user's profile gets. This gets the reports of that user and then gets the profile of the reports, and then it will basically respond back with these details.

A

What I have done as well, because one on one chat, is just one aspect of microsoft teams, but you want to include your bot uh anywhere in teams. You can also go ahead and include your bot in a channel and there's a quite a cool feature within composer, which is a trigger called on channel created. So whenever there's a channel created in a specific team where the bot is already a member of the bot can actually react to that.

A

So, in my case, what I'm going to do is I'll get the team members whenever a new channel is created, and then I can do something with it and I've just for the sake of simplicity, um send out a message to a team's channel.

A

So if I'm gonna go back to teams and open up a theme where the bot is already a member of and select add channel, give it a name, click on add, and what will now happen is that the bot will actually use that trigger on channel, created and say, okay, awesome that a new channel has been created called pnp demo, and then you can react on that and stuff like that, and, as you might imagine, um that's not not the only part where you can include your bot to, because you can also add your bot to meetings and within composer.

A

You can also uh handle those kinds of actions and triggers, so you don't need to more or less use um code to to build your first conversational plot for teams. You can do it without any any development uh efforts. Just using compose back to you, david thanks.

B

Awesome stuff, stephen, thank you that is really really cool how you can set up these various scenarios for the the uh the bots and within the teams and the triggers really cool stuff. Thank you for sharing.