Microsoft 365 Community Platform, 11 Oct 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Microsoft 365 Platform Community Call – 11th of October, 2022

Description

Microsoft 365 platform community call delivered on October 11th. Two demos - Introduction to Records Management APIs on Microsoft Graph and Build your first Command bot for Microsoft Teams with Teams Toolkit for Visual Studio Code. Microsoft Ignite starts Wednesday, October 12th, register at https://ignite.microsoft.com. Microsoft Teams App Camp online training on October 20th. Register at https://aka.ms/TeamsAppCamp. Nine Microsoft 365 platform related articles and 1 conversation - Microsoft 365 PnP Weekly – episode 182, delivered this week. The host of this call was Fabian Williams (Microsoft) | @fabianwilliams. Q&A takes place in chat throughout the call.

Learn more
• See the full blog post for this call in the Microsoft 365 platform community blog - https://aka.ms/m365pnp/blog
• Download invite for this weekly Microsoft 365 Platform community call: https://aka.ms/m365-dev-call
• Microsoft 365 Unified Sample gallery - https://aka.ms/m365/samples
• Microsoft 365 Platform Community in YouTube - https://aka.ms/m365/videos
• Microsoft 365 Platform Community - https://aka.ms/m365/community

A

B

Today is Tuesday October, the 11th 2022, uh and uh welcome to the Microsoft 365 platform. Community call I will be filling in for Visa today my name is Fabian Williams I am a senior pm on the Microsoft graph customer apartment experiences team. Today we have a fantastic lineup of speakers presenters. You know here to talk to you about a variety of things.

B

We have ham and some reading on the introduction to the records management API on Microsoft graph, and we have welcome again Gary trinder to talk to you about the command bot for Microsoft teams using the team's toolkit for vs code, but before we get to that. As you know, this is a weekly call and we have as a community call, so we have people joining all the time, we're going to start off with a few updates.

B

From the last time we met related to the Microsoft graph 365 platform, news that you can use and ways that you can work within the Microsoft 365 ecosystem and we are going to attend a group picture time in together mode for those who would like to participate. I am going to go ahead and try that again we meet weekly on Tuesdays for the platform call um you know, as new people join, we want to make sure that you have access to all of the resources and samples that are available to you.

B

There are two YouTube channels that you can subscribe, subscribe to and and consume videos which feature you know things that we're doing here today: samples, demos and so on and so forth.

B

There's the Microsoft 365 developer, videos, which is usually people from the plan, the internal Microsoft, the PM team, the dev Advocates team, the devrel team, um PM owners, PM managers that will come and talk about um the various um M365 news that they have to provide and updates that they have to provide and there's also like today, the Microsoft 365 Community videos, which is at akms and 365 videos, which are the calls that we have here today, along with others that we have in terms of monthly and bi-weekly as well.

B

Besides, the videos I mean a lot of people consume videos, it's I'm, a visual person, myself, I love videos I, like that's. Basically, the way that I learn, we have um complimentary to that a ton of Open Source resources um on Microsoft GitHub that are available to you. um You know to consume this, basically a place. You go. You pull down your on the code, clone a repo um learn um by doing and um get up and running. You know from zero to key or in relatively quickly um in a relatively a quick succession.

B

However, GitHub can be, um you know, overwhelming there's a ton of stuff there under different um Outlets. So what we have done um to make that a little bit easier for you is to create sample galleries, where you can find things relative to spfx, to teams to graph Power Platform, all of those things in bite-sized chunks and samples that you can basically search for and consume. If you can't remember- or you know, don't want to, you know, retain all of this information in terms of all of these little sublinks.

B

um If you go to akms, slash, M365 Community, you can find all of the information that I've just mentioned there in one spot for you. Besides, um you know those resources and those videos are on YouTube. We do have cost like you're attending here today. um The Microsoft 365 developer, Community call which um occurs weekly on Tuesday and the link is there for you to.

B

Basically, uh you know join and besides this call, um we have monthly calls for the Adaptive cards, the Microsoft identity platform, office address and Power Platform, and we have bi-weekly and they they alternate it's either the M365 Power, Platform Community, or the Viva connections and SharePoint framework that rotates um uh bi-weekly. Again, you can download.

B

um All of these recurring invites from akms M365 slash calls we we want to ensure that you are successful along your journey in Microsoft 365 and um there are a couple different outlets for that one, a tenant is there for you to use and it's available for you, free of and as long as you continue to use it. It'll be it'll, continue to renew you can get this um free, E5, developer, tenant and other assets. So it's full with um you know. You know either Communications in teams.

B

You know email messages, um a lot of content, so you don't have to put dummy content inside there, um which makes the developer experience um uh much better than you. Trying to you know, put dummy data. You know Lauren ipsum. um You can get that at akm, Ms, M365 Dev program and um complementary to that. um You know so that you have a tenant, that you can use and have it meaningful information for it.

B

um We have a ton of stuff for on the learn: Channel, which is n365 Dev, slash, learn where you can actually get. um You know, curated information, training, videos that are free to help you along that Journey as well. We also have two podcasts that I'd like to highlight as well: German thick and Paul Schaefer and have the M365 Dev podcast, where they usually have either people from the product team or um MVP. Well, many people from Party City, but also people from the devrel and um also the dev Advocates.

B

On that program and weekly, you have vesa and waldek that have the PNP weekly podcast and there they have a mixture of either platform folks internal to Microsoft, or also MVPs there to share um their what they're, working on and under the new stuff that is coming up in Microsoft, 365.

B

yeah, leaping back into samples. um You know definitely want to thank people for all of the contributions that they do we're now up to um 1100 samples inside the sample Gallery, um which is an akms M365 samples. We can find a ton of um information, a ton of sampler codes around Microsoft teams. You know Azure powerapps power, automates SharePoint, my own Microsoft graph, Microsoft graph toolkit as well, so I want to ensure that everyone has the resources that they have in order to be successful.

B

Based on all of the you know, the years of um you know experience that you have from the people within the community here at Large and I'm, going to turn it over to David to talk about the sharing his caring initiative.

A

Excellent, thank you Fabian. Well, friends, uh all those 1100 plus samples they didn't happen by mistake or accident or just by Microsoft. In fact, they were there because of amazing contributors. Like yourself, and you may say, how can I do that? Well, it might be a little intimidating to contribute to some of the areas of the community things like GitHub and terms like pull, requests and forking. What does all that do? Well, we are here to help you understand what it is.

A

uh The sharing is caring program is a safe space opportunity for you to get more involved in the community by alongside others uh and learning together. So in these sessions, we will show you how to do things like publish a pull request, submit a pull request, set up your developer, workstation or use those samples with NVM, and they are safe space. So that means that you do not have to worry about it being recorded.

A

You are open to ask any and all questions, you'll collaborate with members of Microsoft, you'll work with MVPs and other like-minded community, passionate contributors like yourself, and we want to enable you and Empower you as much as we possibly can.

A

These sessions are getting scheduled out for the rest of the year, they've been a little slow going with the Power Platform conference and some other changes we've been making, but we've got power Pages coming soon, we're also starting to create some videos for them, because that way you can kind of see some of it on demand and then join, maybe some office hours to ask questions that are more definitive or granular or specific. So again we app. uh We offer these up to everyone in the community you're. More than welcome.

A

We try to make times that are available to all those. We are a global community, and so it's not Redmond Standard time or anything like that. We want to make sure that it's scheduled for times that are good for all of you, so keep an eye out at ak.ms forward. Slash sharing is caring for more additional times coming soon. Fabian back to you, thank you. David in.

B

Addition to Sharon is caring initiative, um one of the things that I'm, actually you know, I I was a part of when they were actually building.

B

This out is the ad Camp, so the um the the um Dev Advocates team have um have information have solutions that are there for you to build um if you're, an isv, Building Solutions, where there's a monetary station towards Microsoft teams, there's two ways of learning um for this one there's an asynchronous learning where you can actually go to akms, slash app camp and you can get all of the content.

B

The beauty of this is that, and I've heard Bob German mentioned this so many times that I think I have it by memory right now, but oftentimes you'll see solutions that take you from zero all the way to getting to a solution, but oftentimes people are bringing their own solutions to table or they already have something built.

B

So this is quite unique in in in the way it operates in terms you can bring your own app and then get that to work within a Microsoft 365 into Microsoft teams, environment towards a um a monetization Target and on October the 20th. Just recently on between ATM to 9 A.M Pacific, um there will actually be an event. I think it is between um Rabia and Bob, where you'll be doing um a.

B

You know an online event for that one hour at AK, dot, Ms, slash teams app cap, make sure to check that out um tomorrow. Tomorrow tomorrow um begins Microsoft ignite and we're actually talking prior to this call here today, where you know there'll, be uh you know, this is an event where it's going to be both virtual and also in person. I've seen a ton of people coming in across um you know, from Air I see a budget airport shots of people saying that they're arriving in Seattle, but there are also a few Spotlight events.

B

I know, there's a um a college mentioned one in the UK. I noticed I'm in Singapore, but um you know this is a great opportunity for people to um no matter where you are and in the world to either attend virtually.

B

um You know be as inclusive as possible, but also getting back to what we were talking about before as well. In-Person events we can actually meet people have a conversation, attend a session Network.

B

All of the things that we used to do you know pre pre-pandemic, so um this starts tomorrow hope to see a lot of people inside the virtual sessions, because I myself will not be there so, but I'll be attending and hosting a couple sessions myself in terms of um the the news that you can use, there's a couple that I'd like to highlight so the besides the app Camp, which is in the middle, which I talked about before um there's a beginner um crash course um to build actually Microsoft teams in the toolkit and um there's also um link unfurling that went into public preview for Microsoft Outlook at the very top left um right here.

B

You can actually see a couple of the AK Ms links to take you to things about Aviva, Microsoft teams and also the SharePoint blog, and um we are at the time where I will actually try the optional picture time. So I am already on camera. I'm gonna, stop sharing here and I am going to present my I'm going to go to together mode first and then share my screen. So let's go to together mode.

B

Let's go I'm getting a 50 people inside here. Let me go ahead and share. This screen share this one right here, Yonder here we go and uh let me go ahead now and uh grab my trusty little Camtasia and in a few minutes in a few minutes in a few minutes, let's get 50 people inside here and, let's start the hand, wave and the hand waving. Let me get at least five or six seconds off that and then we will go ahead and stop the recording. Thank you. Everyone really appreciate it.

B

Let me go ahead and minimize this and let me go ahead and stop sharing and present back inside teams.

B

So at this point in time um we're going to jump into our demos, the real stars of the show here today the first demo is going to be um security and uh Cameron. Talking about an introduction to records management API on the Microsoft graph.

C

Yeah, if you want to stop presenting I, will go ahead and share out my screen alrighty. Thank you, Cam all right. Well, thank you everyone. uh So my name is Cameron Parker I am a product manager on the Microsoft customer and partner experience team I'm joined today by Sam, ready Seth, who is on the records management team.

C

So today we're going to be talking a little bit about automating security, compliance, identity and management with new Microsoft graph apis, and so this is specifically around the records management apis that we'll be talking about today, all right so just a little bit of the agenda uh so overview of the apis and their use cases uh we'll do a little bit of demos, uh of course, and talk about licensing and monetization uh demo environments and trials and then kind of end with uh some some links to some resources and things like that so jumping right into it um so again included API.

C

So I mentioned skim earlier right, so for skim, automation, we're really talking about three different sets of apis uh Records management. Being the one that we're talking about today, but there is also e-discovery premium, as well as privacy and so overview of the uh Records management apis and their use cases. So essentially, these these apis exist to kind of help.

C

Organizations manage that retention and deletion of data to meet their legal obligations and compliance regulations and so kind of to quote uh data lifecycle management is what helps you keep the data you need and delete what you don't a couple sample use cases for the apis that we have available again.

C

These are currently in beta uh and so right now uh what you're, looking at in terms of use cases is event space retention, uh so you know triggering based off of some sort of internal or external events, such as like an employee leaving the company, as well as label management when using a third-party tool, so automation around like creation, updates of labels and that kind of thing so moving on we're looking at a few of the sample queries via the the API, what they, what these would look like as far as like the raw HTTP request form, and so this particular one is for the events based retention example, and so looking at this use case.

C

Right got a few sample, queries so uh listing or enumerating those retention event, types that you may have retention event type being associated with a label, and then you know using a retention event uh to to again. You know trigger that event right, so that some action can be performed uh based off of labels associated with that that event type and so uh looking to the documentation down here at the bottom.

C

um Moving on to the other use case, we have label management and so again, more of like a crud operations against labels right, so you know creating enumerating labels performing updates via that patch operation. You can delete as well again a link to that documentation, all right and so enough talking.

C

Let's take a look at it and for this we're going to be using Postman, and so uh we recently, uh along with some of the other API sets, we were able to incorporate these into our official Microsoft graph collection for Postman, and so for those of you who may not be familiar with Postman. This is a great API testing tool that allows you to uh you, know craft HTTP, queries and test out the apis without having to write a whole bunch of code.

C

In order to do that, we provide a specifically for Microsoft graph, where we do provide a collection that allows you to essentially have these pre-crafted queries so that you're not having to manually craft each and every query that you want to test out against the Microsoft graph API, and so basically you you can obtain this. It's it's in our documentation, which we'll share a link to a little bit later, but essentially you can Fork. This collection, uh bring it into your local Postman instance and then set it up based off of an application registration.

C

So, of course you know using Microsoft graph you're looking at that uh that that typical setup of you know creating an application registration in Azure uh and then getting your your information, such as your tenant, ID, client, ID, client, secret and so forth, uh and that's what you're going to use in order to get that access token, and so you may have noticed that we're using the authorization code flow in this example, and so uh we are using delegated permissions here uh and so we'll go ahead and get started by grabbing an access token that we'll need all right and you can see that completed successfully, and so now you may have noticed that you know it kind of jumped straight into getting that token, even though we were using the authorization code flow, that's only because I've I've already previously consented to that permission.

C

Otherwise, you know you would you would see that typical flow of having to sign in with an account uh and then consent to that permission, had you not done so already, all right, and so uh with that, as you may have seen uh just uh just a little bit ago. We have some variables and things like that that we'll be using for the demo. So that's under the kind of root collection here and the variables that I have populated. You will find these apis.

C

The the sample queries for these apis under the compliance folder under delegated. uh Because again we are using delegated permissions here uh and so compliance folder records management, and then we have you can see. We have the two kind of use cases we talked a little bit about earlier and so moving into we'll go through this label management scenario and so uh starting out. So we've already got our token. uh You can kind of see here how like we've got.

C

You know just the basic layout of Postman and so you've got your get call and then you've got the actual HTTP query here that you would be executing to to make that call and so we'll go ahead and hit send there. Since we got our token all right, and so you can see here, we got a successful.

C

uh You know returns information about existing labels, I haven't created one yet so this is, you know, a label that I previously created, but we'll go ahead and we'll get one created. So you can see a little bit different here, we're using a post call. uh We do have the body of this request populated with some information that we need to send in order to create that event.

C

uh You may have noticed the uh this kind of weird looking text here with the um uh curly braces around it, and this is just one of those variables right, so you can actually feed the variables into the request bodies, which is, which is a really cool feature of Postman, uh so we'll go ahead and hit send there and if everything goes well uh yep, so we get our 201 created response and we can see that we've successfully created a label, and so what I'll do is I'll actually kind of jump over and show you um so if I go to, uh you can actually view this under data lifecycle management as well.

C

If we jump to records management, we should be able to take a look at this and so under our file plan, and it might have already refreshed and yep. So we can see here, I believe it's this top one right here. They look similar just from the uh the way that it's kind of uh viewed right now, let's see- and so another note about this- you can see that there's a under this test field.

C

What we're actually doing here as you'll, see here in just a moment, is we're actually capturing the ID, that's being returned in the uh body of the response. It's saving that into a variable so that we can use that in the future, which I'll show you uh here shortly and so, uh as you can see, what we did is we found the label into this. This next request- and this is just a get request to basically get that label that we just created.

C

And so again you can do things like you know, enumerating the labels creating I'm, getting details about just this one specific label that we just created. uh You could even go so far as to do an update, so we're doing a a patch for that again using that ID that we just created, you can see a 204, no content right and we effectively updated the uh description for admins there, and you can see that that actually updated and then kind of jumping back to the portal real quick. If I selected the correct one.

C

Oh, it looks like it was second one actually you'll see that if we do a refresh and then if I select that label you'll actually see that it was updated in the UI right, so that's kind of a key takeaway.

C

The reason for showing this is just that you can see that essentially we're performing actions similar what you would be doing through the UI and those actions are reflected uh when made through the API in the UI as well all right and so again you could do delete delete if you wanted to with that for that label. We're not going to do that here today, um but then again we also have this other use case.

C

uh So definitely recommend that you, you check this out if you're interested, so with that we will go ahead and jump back to our slides. A quick word about licensing and monetization, so some require some operations require an E3 license. Some require an E5, the kind of key takeaway. There is the current apis. They match the feature licensing right, so the the feature associated with you know that graph API operation that you're performing.

C

Please do note that the future records management apis uh they may be metered based on consumption, so just wanted to make sure to call that out. You can learn more about licensing at AKA dot, Ms forward, slash dlm, forward, slash licensing, okay, quick word about permissions, uh so as these apis require delegated permissions, uh I did want to make sure to call out that the uh we have this concept of effective permissions with Microsoft graph right and especially in the context of delegated permit permissions.

C

It's that intersection of not only the Microsoft graph permission that you've you've consented to, uh but also that back-end permission right associated with the essentially the the service right that you're calling right. So the essentially the the records management permissions in this case so do want to be uh cognizant of that, and so, uh if you'd like to learn more about the permissions required on the back end, you can check out this link here, all right and so for demo environments and trials.

C

uh So we do have the uh a Sandbox tenant available via the M365 developer program again comes with a 25 E5 licenses. It is 90 days. However, it does sell for new as long as you uh keep using that that tenant for developer purposes, so you can check that out at AKA dot, Ms forward, slash M365 Dev program, uh not really meant for like load testing or anything of that nature.

C

If you do want to do load, testing, I, recommend kind of checking out an actual tenant with you know additional licenses and so forth, but this is a very useful tool for that uh or I should say four. You know for just like kind of basic sandbox testing and that kind of thing. So for the postman collections, you have AKA dot, Ms forward, slash graph posts, man that was the postman collection that we were going through earlier.

C

So again, if you are interested in taking a look at that, please do check out that link all right now on the roadmap. We do have application permissions uh as well as file plan descriptors, so I just wanted to call that out all right and then so for some additional resources about this I definitely recommend checking out akaa.ms uh forward, slash dlm forward, slash, API, uh learning more about event, space retention that we talked a little bit about earlier.

C

We have a link here for that and certainly encourage you to leave feedback uh that can be done via AKA dot, Ms forward, slash, dlm, forward, slash feedback and with that uh baby and I will turn it back over to you.

B

Ken, do you have time for some questions, um or do you want to do them in the chat.

C

Yes, sir I didn't have a chance to take a look at the chat, so uh we can go ahead and it's, however, you'd like to. If we have time we could certainly take um yeah.

B

Otherwise we can yeah so that we can go. um There's a question from our event asking. Is there an API or a UI for end users to see which documents are about to expire through retention label? That's that's that kicks.

C

Us off yeah, sorry somebody would you like to.

D

Yeah I was just uh yeah, okay, first thing, uh hi everyone and great to see this platform. Thank you so much for departing these great apis with everyone, so glad to be here all right and then coming to the question and yeah thanks Cameron for this amazing presentation, love literally, of course, yeah and coming to the question right now. I, don't think we have this. But of course it's a great question. I think it's a great finding for us to uh to see.

D

If we can come right in the roadmap, uh we do need feedback, that's what we are here for. We know to see what your user experiences, what you think is the missing piece and uh we want to deliver the best right there. So yeah, we don't have this right uh at the moment. All.

B

Right is anyone. Thank you, Anthony Rita, for that um response to the question. um I think that's the only I think there were a few comments, but that was the only one question that scolder did. Anyone else have. Let me see new comment down here. Yeah.

C

And so one thing I did want to call out as well just kind of uh let me jump back to the to the slides, real, quick so going back to the uh permissions here, uh because in the demo I believe I used the the uh the default or the the demo. So I didn't want to call out the specific Microsoft graph mission that you would be using kind of in addition to those back-end permissions I was referring to, and so that would be the recordsmanagement.reader.rewrite dot.

C

All permissions so again just wanted to mention that, but uh yeah so with that uh Fabian. Thank you turn it back over to you.

B

All right thanks very much Ken. Thank you. Also Russell um I'm going to go ahead now and invite Gary um to uh to share your screen and uh take it away with your demo around the command.

E

Block Gary hi Fabian. uh Hopefully you can hear me all all good I.

B

Can hear you well.

E

Okay, so let's share my uh I'll share my slides first perfect: lots of Thumbs Up, fantastic um right: okay! uh Well, okay, thank you everyone. um So this session is going to be build your first command bot, using teams toolkit for visual studio code uh just to introduce myself. My name is Gary trinder I'm, a senior Cloud developer Advocate at Microsoft and I'm focused on Microsoft 365.. It's lots of links in in this uh slide.

E

If you want to get in touch with me with any questions after this session, or you know just check out the things that I've been doing and sharing uh loads of links on there, please do check them out, and you know, if you have any questions, please do not hesitate to uh to just get in touch with me. I'll do everything that I can to uh to help you out?

E

Okay, just a quick agenda, uh so um first I'm going to go through. What's the command bot I'm going to cover quickly teams toolkit for visual studio code? For those who don't know what it is I'm going to step through then creating this first project quick overview of of what has been created for that project?

E

Running a bot for the first time, so we're going to see it in action and then I'm going to go back through the code and explain how it works in the way that it does and also then show you how you can Implement new commands and before we wrap up with a summary and some resources for you to basically get started, building a Bots using the teams toolkit for visual studio code and I'd really love to know what you build after this.

E

um So, let's start with what is a command bot, so a command bot is something that is useful. To repeat repetitive, commands through a conversational interface. So let's say you just want to go into themes. Ask a bot to you know, send an email to your boss. You can instruct that bot through a command and run some logic that is as simple as I could probably put it. There'll, be lots of different use cases, um but that is essentially it. You have a bot with several commands that you can invoke and then get a response.

E

We're going to build this going through this session today, using teams toolkit for visual studio code. So for those who are not aware of teams, toolkit teams toolkit Visual Studio code is a an extension that you can install for the marketplace which enables you to create new projects really quickly for Microsoft teams apps, and it sets up debug and also has lots of features in there for publishing that app as well to your store and also to azure, there's also a team's toolkit for visual studio.

E

Just to make you aware, so, if you're a net developer, that's something that might interest you I'm not going to cover it today, but we'll cover it in in other sessions, and so for today, we're going to be focused on JavaScript and typescript as the technology that we're going to use you'll be glad to know that is the end of the slides really for now and we're going to jump into Visual Studio code and I'm actually going to show you things um running.

E

So, let's uh begin so like I mentioned we're going to use teams toolkit Visual Studio code, quick way of installing that we can go to the extensions pane in Visual Studio code. We can simply look for teams toolkit, not returning the results. You can click install, that's it it'll install in a matter of seconds when it has installed.

E

You'll get the team's icon in the sidebar click that you can open the team's toolkit and you're going to get the options immediately to create a new project because we're just in a in an empty Visual Studio code window here, there's some also some samples that you can take advantage of as well. So um if you're looking for ideas, check out the samples and you can install those as well and and run them, so let's create a new teams. App uh we've got very several capabilities that we can add to our app.

E

So we've got Bots, we've got tabs and we've got message extensions as well, um so we're going to concentrate on the command bot for now. So, let's select command bot um I mentioned.

E

We've got uh JavaScript and typescript support for the programming language that you want to use, I'm going to use typescript and I'm just going to select a folder on my machine for where we're going to actually create this uh this project so I'm going to give it a name call it Community call, and that has started the scaffolding of the project and in fact it's done. It's nice and quick.

E

So let's just take a quick run over as to what's actually been created here. So let's go through the folders, so we've got an fx folder in here. There's some configuration files, so these are used by teams toolkit as as part of um some of the uh the features that it it uses to launch Bots really quickly against your developer. Tenant we've got a vs code folder, so this contains debug profiles.

E

This enables us to basically use F5 in Visual Studio code to launch our bot and open a web browser and and test it out really quickly and also the debug profile. So you can actually put breakpoints in code as well and then follow that code execution, which is really really useful. We have our Bots folder, which is where our our logic is held for the bot that we're going to create I'll jump back into that for a second we'll just skip to templates folder.

E

So these templates folders uh it contains two types of of templates, so one we've got a template for our app manifest that we publish to teams and we've also got an Azure folder, which provides us with templates, uh bicep templates that we can use to deploy and provision uh all the resources that are needed uh to uh to have this running in the cloud and not running on our local machine. So toolkit provides all of that for us, which is really really great skip into the uh the bot folder.

E

So here we've got our source code in here. We've got some command handlers. We've got some adaptive cards and some internal files, where toolkit has already set up things like uh configuring out a bot um and uh and wiring up the app IDs at passwords handling all that complexity.

E

For us, um what I'm going to do is we're going to jump and I'm going to show you the bot actually running and then we'll come back and I'll jump into these individual files to just explain how the functionality that I show you uh is uh is implemented uh in this project, so I'm just going to jump to a project that I've already created just quickly jump back. So here's one that I've I've already created I've already hit F5.

E

um So when you hit F5 themes, talk it's going to do a number of um activities for you and it's going to check. Make sure that everything on your machine is good and valid. So you've got a a supplied, node version.

E

um You've got everything installed on your machine like the npm packages that are needed, um as well as connecting to your Microsoft 365 tenant, so I'm going to show you that I've already connected to my Microsoft 365 tenant.

E

uh If I look at the team's toolkit tab, so I've already signed in it's telling me that side loading is enabled, which is something that we need to be enabled on the tenant uh to uh to basically launch our app and and and and test it, and so this is enabled by default, if you're, using a Sandbox uh tenant from the developer program. If you're not. uh This might be something that you need to configure yourself. So that's a setting in the team's admin Center that you just need to go and switch.

E

um There might be a slight delay before that becomes enabled, um but once that's been done, you don't have to redo that again for that uh for that tenant, so I've already signed in. So what I'm going to do is I'm going to run uh the uh the bot and we've got some profiles there for Chrome and Edge I'm, going to run this in Edge, so I can hit the run and debug button or I can just hit F5 on my keyboard. It'll do the same thing.

E

So, let's run it so this is going to run by quite quick, but what this is doing, teams toolkit is. It's checking all those prerequisites, uh it's uh like I say it's checking for node. It's checking our 365 account it's checking. If the npm packages it's also checking and installing ngrok as well, which is uh needed for um for tunneling.

E

So um you don't have to pre-install that um you don't have to do anything with ngrok uh teams, toolkit Visual, Studio code, we'll install it for you and launch it as well. In the background so now this has launched. We've got teams uh opened in the web browser and we will get the uh the app loading pane. So we've got different places where we can install this to start a team or a chat or actually into a meeting as well.

E

So if you want to have a um a bot that is available in a meeting for people to kind of make invoke commands in then you can, you can add this, this bot to those meetings, I'm just going to add it as a personal app at the moment. So it's just installed for for my user.

E

um You can probably see there's some usage of it already, um but this is what a command bot is. uh If you go to the the text box, the the bot provides certain commands so out the box. We've got a hello world command and we get this nice suggestion um as well from from the UI. So if you've got multiple commands, you'll have a nice list here and as you're typing, um the uh the different commands that I've got available to you.

E

It will provide you with the one that matches uh your your message and what I can do is I can just invoke this I can just send the message to the bot and in this example, when we send hello world, uh it will reply with an Adaptive card and also it will uh reply with the uh I think yeah.

E

It replies with the the text as as well in there uh with using adaptive cards, you've got the ability to add actions as well, and so these are just buttons that go to URLs at the moment, but you can imagine if you want to invoke a uh a command that maybe has a form or you want to send some information somewhere. This is a a you know: a use case of using a uh a command bot you're.

E

Just invoke in some functionality uh by by sending the bot a a message so I'm going to quickly jump back to visual studio code now and let's take a look at the code. um Show you how this is all set up, so first I'm going to go to the internal folder and go to the initialize file. Now this is where our bot is defined so um convention that our bot has been set up for us by teams toolkit it's gone away to the bot framework service. It's registered a bot in that service as well.

E

It's pulled the ID and the password for us and basically inject that into this this, this new object.

E

What we've also got is further configuration, so we there's a command property uh that allows you to include different handlers, so a Handler would be a Handler for a particular message that comes in.

E

If we take a look at the hello world command Handler which has been created for us, we can see that there is a class hello world command Handler, which is uh in implementing a an interface from teams. Fx teams FX is a SDK. That's basically provided us with a layer of abstraction over the bot framework. It's making it easy for us to um to create new commands using this team's FX class.

E

So one of the things that this class allows us to do is allows us to define the trigger patterns. So if there is a message sent to this bot that matches this string, it will run the handle command received function and that will be where our logic will uh will will fire. So this trigger pattern. Actually uh it can accept a string, but it can also accept regex as well. So you can have you know a command that could be fired by different uh different words at different times, and so it can be really flexible.

E

If we just take a quick look at the handle command received function, so we can see that we're logging out that the bot received a message, so we do actually get the message back. If we take a look at that, so we can see the actual text that was sent to us and also matches as well. So, let's say, for instance, I did hello world and a name. At the end, we were able to pick out the different values that have been sent through on that command.

E

So you could, you know, easily, have a command that accepts a a parameter and then use that, within your logic, foreign.

E

So the next thing that this spot does is that it's actually going to send an Adaptive card uh back and the way that it does. That is that it can use this message Builder from teams FX again, um and we have a attach adaptive card method where we can pass in our uh hello world adaptive card and some data with it as well. So we have this variable here with title and a body and we're going to send that to our bot, along with the Adaptive card definition which is held in this Json file here.

E

So we can see that we have placeholders for title and for body and we've also got actions in there to open URLs in teams and so there's various different actions that are available in adaptive cards. You can have execute for for forms as well, um but this example it's just using open URL for the moment, so this might be great for let's say I know a q, a bot. You want to ask a question: you get a response.

E

You have some buttons provided that take you to a documentation page people can then find out their answers from.

E

So. If we look at the implementation of these, so we've we've got uh our Handler. um Our Handler knows that it is triggered by a particular pattern, in this case Hello World. One thing that we did see was we had suggestions. So when I went to the uh the text box, the compose box, it actually came up and said- oh here, are some suggested commands that you can, that you can use, so those are defined actually in the app manifest endpoint.

E

So if we go to templates uh app packages and manifest endpoint.json, we have here a command list um array and in there there is a a command array is where we can Define our commands that are available, and so this this list here. This array is the list of commands that you want to be able to show the user of your Bot um quick examples of you know what messages can you send and what functionality is going to be provided? So you can just simply add in new ones and new handlers.

E

Just add in a title and a description.

E

And then, when that next gets uploaded to um the teams, that will be available as a new suggestion. So if you're wanting to let's say Implement new command, then the way that you would do that is, you would update those uh two different locations um in um in in our source folder. So first we'll come to initialize. We would add our new Handler in here foreign like this, and we would actually create a new class that implements from the team's effects, bot command, Handler and we'd.

E

Add in the trigger patterns, add in the handle command received, and then that would be picked up and that would be a new command that users would be able to to use so the way that um Team stalker has provided us with really the the basics of. How do we register new commands? How do we invoke commands? What suggestions are available to to users and how do we, you know?

E

How do we send data back to the user is, is all handled quite nicely through this command Handler and through the handle command received function and using the attach adaptive card method? To then send you know a nice adaptive card rack. If we didn't want to send an Adaptive card, we can also just send text. So we have something called the turn context which is provided for us and we can send an activity back which can just contain plain text, so we can actually keep sending messages as well.

E

um So, as part of you know the uh the functionality of this command, uh you could just have you know single line messages and then provide an Adaptive card um as well for users to to actually follow.

E

Okay, so that really covers the basics of getting started with a command bot. So let me just quickly jump back to my slides, so I just want you to to Really summarize uh kind of what we what I'd shown, and so you know, command. Bots are a great way of being able to automate those repetitive tasks through that conversational interface. So you know, rather than having a button on a page, maybe something that's a bit more interactive, like a bot that you can use.

E

As you know, maybe like your personal assistant to just say you know, but do a particular action, and that's that's a great way of being in being able to implement that and it's the starting point as well, for you know a q, a bot, a more advanced conversational, but adding um cognitive services like Lewis as well, and to really kind of enhance that, but at its basic uh implementation level, it's a user is inputting something that the bot is then reacting to with some.

E

You know certain logic, whether that is displaying uh information through an Adaptive card or actually capturing information uh back as well. um So I've shown your team's toolkit has provided the quickest way to get started developing. Certainly these command, Bots and and just teams apps in general. You should I showed you how quickly uh and easily it was to just create that initial project and then get that running um as well, using F5 and also that teams FX is providing this layer of abstraction to simplify working with the bot framework.

E

So you were able to just create a single Handler and Define the trigger pattern, and that would invoke the logic in that command and then how that was wired up with the the bot definition as well, um and you know again, theme store, kits kind of handling a lot of the complexities there just making it really easy. So you can focus on what your command needs to do so resources.

E

So there's plenty of resources on docs, so definitely check out teams toolkit overview, and so whether you are interested in the visual studio code, extension or even the visual studio enhancement as well, and then definitely check out that page. So everything is provided on there with some quick starts about creating a new teams app and there's also more on teams FX SDK, so that is on GitHub, definitely check out the repository and the docs.

E

There's lots of information down there and samples as well um about you know how you can take this further extra things that you can do with the the command handlers and finally, just want to say. Thank you very much and I think we jump into the questions. I can see Victor's already in there. There's lots of activity in there. So I don't know if there's anything that hasn't been answered, I'm just quickly, jumping back through I.

B

Think most of it's already answered there's a couple like more governance. Questions like around you know how to manage this. These many Bots and there was one about moving from Dev to prod and I. Think Victor has actually communicating some of the you know communicating answers to some of that or at least give some suggestions.

E

Yeah I think I found one question from Scott: are there Enterprise supported options, not using anger up, so I would say that, as um you may be working for an organization that can't use ngrok. So at the moment there isn't um in the visual studio code extension, and it is very opinionated in that it uses engrock. However, it is on the roadmap to use other tunneling services, so this is something that definitely the team are aware of and are actively working to to provide an alternative.

E

But at the moment uh yeah, if you're, using the visual studio code um version, it's tied to uh ingrock.

F

Yeah I think there's two other interesting questions. The first one I partially answered, but it was about. Where do you place the logic for your command bot? If you just don't want to show that card, but you want to have some business logic or whatever? Where would you do do that and the second one is: uh do we require actual app services to run this uh how's everything being set up essentially.

E

So I can answer the second one quite quickly, um so one thing which I I didn't actually mention was the implementation of of that uh bot. So it that project template uses uh restify um as part of its implementation, which means it will need a an app service to uh to to run when you provision that and deploy it to azure.

E

So that will just need the um like, say: a normal app service. In fact, the the bicep files there's I think it uses B for the dev test, skus uh to provision that app service for you. So that is something that you need. It doesn't use it as your functions.

E

um You definitely need that that app service in terms of the the logic um in terms of uh so where will the? Where will the data save so at this? The out the box?

E

um This conversation, history, which is saved in memory? That's something that when you move to production, you're going to need to add some persistent storage easiest way to do that is using Azure, Cosmos, DB or table storage, and to save that that conversation uh data to, but at the moment that that bot is is very much just. It's running in memory, nothing saved anywhere. So that's something that you would have to look into and Implement yourself, however, saying that team's toolkit does have a feed future.

E

So there's an ad features: guest wizard in there, which gives you options to stand up a SQL database and Azure functions as well in your project. So it's a bit more advanced from what I was going through today. It was very much a. How do you get started and but if that's something that you're really interested in then that's something that we can definitely look to cover in another call, as we start to delve into you know, going past the just getting started and creating your your first project.

E

um So you know if any feedback like that, definitely want to hear it. You know we want to do kind of sessions that that are going to help you progress using teams toolkit so uh yeah just uh get in touch.

B

Absolutely that is a fantastic demo. Fantastic messaging I want to definitely thank um some really Cameron and Gary for the awesome demos that they did today really useful, really informational stuff um and for everyone who took the time to attend today, and of course, you know highlighting that tomorrow is ignite. Hope to see you on some virtual sessions as well as um you know, in person, but I won't be in person, but um you know have a good time in person. The recording will be available 24 hours after today on our YouTube channel subscribe today.

B

If you have not already subscribed, please follow us on Twitter at Microsoft, 365, Dev and M365 PNP. The next call will be on the 18th at 8am, Pacific and, of course, all of the calls that we've done are available on AKA Ms M365 calls best side only if you have anything in the last two minutes that you wanted to plug in before we sign off for today. No.

G

Nothing at this point, the last link is for the downloading of the invites of all of the course what we have. But yes thank you uh fade down for awesome hosting. Thank you for all of the presenters and thank you for all of the attendees as well, and please please, please keep the feedback coming we're building all of the services for you, so your input is more than valuable. Thanks.

B

Everybody thank you.

G

Very much take.

B