Microsoft 365 Community Platform, 4 Oct 2022

Previous Meeting Next Meeting

⏯

youtube image

►

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

Description

Microsoft 365 platform community call delivered on September 27th. Two demos - Introduction to Privacy APIs on Microsoft Graph, Build your first Notification bot for Microsoft Teams with Teams Toolkit for Visual Studio Code, and Account Linking for Teams apps. Registration is now open for Microsoft Ignite – October 12-14, 2022. Register for App Camp online training event on October 20th. 4 Microsoft 365 platform related articles, 4 Microsoft Teams platform documents and Microsoft 365 PnP Weekly – episode 181 delivered this week. The host of this call was Vesa Juvonen (Microsoft) | @vesajuvonen. 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

We do apologize, your host forgot to click the recording button. Thank you Gary for jumping on there, so we do apologize for missing a few of the slides on the start.

B

Now something what we wanted to also promote on this course uh is the app camp for Microsoft Microsoft teams, development. This is primarily targeted for isvs, who are building experiences for Microsoft teams, but there are actually really cool Hands-On Labs, not only for isps so system integrators and consultants, and also there will be a specific event related on this app Camp material on October 20th, which is a one hour event where um the the cloud Advocates will go through the material and explaining the value and how you can reuse the material.

B

Now uh we also have the the Microsoft ignite coming up uh next week uh is on October 12th to 14th, um so registration is open. Please do sign up for the ignite.microsoft.com and we do have this as a hybrid event, so you can either be in-house in Seattle uh in the conference center or you can join and see the sessions most of the sessions also remotely. So we are broadcasting. This live uh from the uh from the site and from the Redmond. Now quick recap on the latest news. So this week we primarily have well.

B

We didn't have a significant amount of news, because the Econo is coming and ignite is the area where we are announcing it next week, a lot of cool new features and capabilities across the Microsoft 365.. But there are some news. So, first of all, we have an update on the Microsoft teams, apps coming to preview to office and Outlook apps on Android. So this is something which we announced back in build so may 2022.

B

So you can build, expose your Microsoft teams, applications in Outlook and in office, and but that was primarily for the desktop application, so right now, starting then in September and October, and you can actually have the same application exposed. Also in the Android clients of those applications and the second announcement there or a blog post is a tutorial on building a stock update notification board for Microsoft teams, using a themes toolkit for visual studio code.

B

So and that's a great summary and tutorial uh from Curry trender on the Microsoft teams and blog, we had two blocks both available. The first one was the monthly summary on the updates for Microsoft teams in the August and September. So really great summary: on okay from an interesting perspective, administrative perspective and developer perspective.

B

What are the latest and greatest on Microsoft teams and the second one is actually kind of interesting as well, more from an end user perspective, um but it's really explaining how we have our AI artificial intelligence based Innovations to help to minimize and even eliminate the negative impact of bandwidth constraints when you are having Microsoft teams calls so a really cool blog post in the Microsoft teams, blog on what the Investments, what we're doing in here now and then we'll do a quick recap on what what is the latest on the Microsoft teams, developer, documentation, site and sure p is here to cover those sorry take it away.

B

C

You Visa hello, everyone I'd, walk you through the team's documentation and platform updates. Today we have uh four updates to share on the teams platform. Let's start with the first one. The first one is manage license for third-party apps teams allows independent software, vendors, admins or users to manage SAS licenses for third-party apps purchased by theme, storefront, ISP, admins or users can easily assign unassigned use and tracks as licenses. The second one is teams. Mobile app now supports file downloads to local Loop devices.

C

You can configure an app to enable users to download files from the webview to their mobile devices. Downloading files is only supported on Android, team's mobile client, and only unauthenticated files can be downloaded. Third is the Adaptive card in search bait. Message. Extension now supports Universal actions to enable Universal actions for search based message, extensions. The app must confirm to the schema for Universal actions for adaptive cards along with the app must have conversation bot they have.

C

They must already have a conversational bot, so you must use the same bot that is used for your message. Extension. If the card is sent in a group, the app must specify team or group chat scope on their bot in the Manifest and finally, the fourth is the doc update where we've introduced a code snippet for capturing videos using camera through select media API. So these were the platform updates. If you have any feedback or suggestions, please, post on AKA dot, Ms teams, platform feedback, the link is available in the footer.

C

You could also follow us on Twitter and configure to the RSS speech to get regular platform updates. Thank you and over to you, versa.

B

Excellent, thank you, sir really. Really cool development on that side as well, and then we'll move in that we well weekly or the the really cool thing. I will have the together mode picture and together with everybody in the call, so let me put the camera on. Let me share my screen. So look at everything moving in here and as people are opening up or the video, and we will crop a gif animation from here as well, a few more seats in the room. Let's see how this goes a few more.

B

Let's wait, three more seconds before we do a hand waving we'll grab a gif animation, I can say I shot there. I can see Bob and Paul and Fabian a lot of familiar faces in the room. Let's wait three more seconds before we start recording up not yet not yet wait for it wait, wait, wait, wait, wait, I'm, gonna, start recording and let's do some handwriting everybody. Thank you. Everybody once again joining awesome to see all of the lovely faces in the house and in the room. Thank you.

B

Thank you and something strange is happening on the back seats there so exciting and thank you Gary for um doing the the safe on the back row as well, but thanks everybody really really cool. Now. Let's then actually get back on the slides.

B

So today we'll have three demos, we'll start with prime jacket and Cameron Parker on the introduction on privacy apis on Microsoft craft, then we'll go to Gary trinder on building your first notification, bot for Microsoft teams, with teams toolkit for visual studio code and then I will have the final session with Bob German and Adidas shella Bali on the account linking for Microsoft teams app but Brian, I, guess, you'll, start sharing and we'll move forward from there.

B

I've got the deck pulled up here. Excellent. Thank you. Brian hope we can see the deck. Take it away all right, excellent.

D

Good morning, good afternoon, good evening, everybody, my name, is Brandy jacket, joined by Cameron, Parker who's, my teammates, and we're going to do another um kind of Roundup introductions on some new apis that are coming out there. um If you were on a couple weeks ago, we did some things on the e-discovery premium, apis this time around we're actually going to talk about some of the Privacy apis.

D

uh This is all part of what we call the security compliance, identity and management skim apis, and these are going to be available to us actually in GA in this case uh on the V1 endpoint. So some great things we'll be able to show up for you today, all right, let's jump into things. So today, we've got a couple different things we'll be going over. I'll, give you a quick little overview of the apis themselves. Some different use cases for this camera's actually going to demo some of those different scenarios for more reviews.

D

So you can see what does this actually look like inside of Postman, but I also see that results of this inside of our environments as well talk a little bit about some of the licensing, slash monetization impacts for this um talk about how you can actually go and get a demo environment for this, so some great ways to actually be able to try this out.

D

If you don't already have licenses or you don't have an environment, you can test this with and then we'll open things up for Q a and give you some additional resources as well. Now, as I mentioned, there are actually three sets of skim apis that are out there um today record can be focusing on the far right one out there, which is our privacy apis. This actually relates to something called subject: rights, requests or srrs if you've ever dealt with things like gdpr or the California privacy laws. um This is very much in that space.

D

Things like the right to be forgotten or the you know what data do you have on me if you're looking for that type of information within your system, basically within the side of M365, there's a great way to be able to actually go and find out hey what are those things that are content related to myself to another user?

D

um Someone else that you're trying to get that subject: price request on in terms of just kind of the overall for the API with this the real goal for this is to be able to help our customers and our partners be able to automate a lot of the things that they do. Maybe today in the UI or through the compliance portal, when you have to do a lot of these kind of repetitive tasks or you've got like a bulk operation that you're trying to do for those subject, rights requests um that can be very tedious.

D

You know, would you rather have somebody you know, spending hours going and doing those you know fill in the forms and kicking off the requests for this, or would you rather be able to kind of prepare some type of CSV file or something else to be able to input and then just query it with the API lots of ways you can? Actually uh you have some efficiency and be able to be very productive.

D

Having that API Available to You versus having to actually do this directly through the UI for out there a couple different things we can share just from a sample use cases for this again, you can do things for automation, of um there's kind of two terms here, there's subject: price requests, there's also data, subject: requests or dsrs fairly similar just in terms of what the naming for these things are just some kind of a small small difference between them. But DSR is another term. We also will use for those srrs out there.

D

You might be trying to automate the creation, all those things, and this could be coming from one business. Application could be coming from an intake form. Maybe you've got something like a power app or a power automate uh to be likely, go and kick off those types of requests. We're also seeing a number of third-party vendors who are also going and doing Integrations with us. They may have their own system of record.

D

They may have their own tool, their own kind of Staff service or a website, or an app that they're using, but they can actually reach into M365 and be able to automate those types of tasks directly through the apis out there. So lots of great ways we can be able to go and work with the data. I'm also turn things over to Cameron. To talk to us a little bit about some that are unstable careers that are out there.

E

All right thanks, Brian uh yeah, so so, basically, um one of the primary use cases we have around this is the creation right and automating that srr creation and so I just have here a sample query regarding the post operation being made to to create that subject's, uh write request, and uh so you can see populated with certain information that you would pass in the body of that request in order to create uh that that srr and then link to our documentation as well. uh In case you want to learn more about that specific query.

E

Of course we have documentation for uh for for each of these apis uh and then so. Moving on to the uh the next use case, uh next big one's going to be getting that srr status right, so you create that srr. uh You know you might have done some some other things with this, uh get some additional information or perform some action right related to that subject: rights request, and so uh we have other queries as well to get details about the srr itself that that you're, looking to get say, status.

E

Information on as well is an API to get a final report once uh basically, you know once there's additional information, that's been added by that privacy administrator and that kind of thing, as well as an ability to both add and list notes right. So if someone goes in adds a note to that particular srr, you can you can get that information as well, which again we'll be demoing here shortly uh and so uh documentation for that as well, and then uh from there I believe we can go ahead and move into the demo.

E

So I will go ahead and share out my screen for this all right, so you can see here. So this is Postman and so for anyone who's not familiar with Postman Postman is a great API testing tool that you can use to basically just craft raw HTTP queries and that kind of thing to test out uh various rest apis, and so in this case we have an official Microsoft graph, essentially collection, that you can Fork that has these these queries kind of pre-crafted, so you're not having to manually, create all of these.

E

So in this particular case, under our compliance subfolder. Here you can see the subject to rights request with our two use cases that we were discussing and we will do some test queries on and so uh just a quick note about Postman. So you can see some variables in here, as noted by the kind of double curly braces, and so um where that would be populated is under your variables at the top of the collection.

E

So you can see that I've kind of got some stuff pre-populated here um and then so, let's go ahead and get started. uh We will go ahead and get a access token, and so in this case we are using delegated permissions. So we're going to go ahead and basically you know populate our application registration information so that we can get that.

E

And so you can see that these are also variables uh which I have kind of in my environment uh set up here at the top, uh and so with that we will go ahead and get our access token, and you can see that it.

E

It automatically uh went ahead and and got me my my access token that we're going to use if you were logging in for the first time being delegated permissions, you would actually get a prompt right to sign in and then, if you hadn't previously consented to the permission uh for permissions being requested right, you would see a consent prompt for that as well.

E

But of course that was done prior to this, which is why you don't see it here, all right so moving under our subjects, uh rights, requests and the uh specifically we're going to go ahead and move forward with creating uh that srr. And so uh you can see here.

E

I've got my post request, set up in the URL pattern for the creation of that srr and again populated with some information here, such as like regulation, the name that you want to use uh some information about the data subject of that request, and we will go ahead and send that query. And if everything goes well, we should get a successful response, takes just a few moments all right and we got back a successful response. Our HTTP 201 created, and we can see the information returned from the srr that we just created.

E

You can see, there's quite a bit of information there uh and then, in addition to that, if we go look at our uh at the portal here, uh we can do a quick, refresh and I would expect I believe it should show up by now yep and so here's our srr, that we just created as visible in the subjects rights request portal right.

E

So if you needed to do some manual action outside the API or just needed to go, look at it in the portal later time, you can see that that Sr is here and we can see that it's currently in the data estimate uh progress section so going back to postman.

E

Another option is to list srrs that you have available. If you notice from that uh the the UI right, we had several srrs there, and so you can see. Essentially, what this API is doing is enumerating that list of available srrs right, which you could use to grab the uh ID of one of these and feed that into a get request which we're actually about to do here in just a moment.

E

uh So you might be wondering kind of how we're getting that ID for this next request that we're making that we're seeing a variable for here and you can actually see it's populated. So how did we get that? Well in Postman? This particular query is set up essentially to read the response from that and then save that ID of that srr we just created into a variable all right and so again moving on to the uh tracking the status of that srr. uh Again, we've populated this variable with the srr that we just recently created.

E

So we want to get details about that specific srr, not list out. You know that that full list of the several srrs that we had created as as we saw in the portal- and so you can see here- we've got the uh the various stages uh that so that you can check information about.

E

Essentially, the status of this request right, and so you kind of saw a little bit about that when we saw the response of the srr that was just created, but you can also use this uh get srr request in order to see again the status of that request. uh Again, like we discussed earlier, there is an option to get a final report. Now you're not going to see anything for this one, we do get a status okay, but again it's it's just kind of like a no response right. Just because we haven't completed that srr.

E

We don't have a final report available just yet uh same. Forget final attachments: again, these are things you get added by the Privacy administrator. You will see an error in this particular one. Just because again we don't have anything associated with this, yet being a brand new request, so we get our 404 not found there, but as I was mentioning the ability to create and list notes right. So in this case we're just going to create a simple note um and send that, and we should get back a successful response for that post call.

E

We do we get our 201 created and then we can turn around and do a list of notes. So if we had several notes, you know we can go back and check and see what our notes are and then jumping back to the uh the portal.

E

Here we can take a look at that uh that srr and we can look at things such as our notes, like our note that we just created here again and just you know, through the the UI seeing things like the history status, Etc all right and Brian I will go ahead and stop presenting and turn it back to.

D

You awesome thank you so much for showing that really great to see things not only in the API with Postman, but also going back to the portal uh and seeing where that actually shows up.

D

So, let's flip back to our slides here got a couple things to wrap up with uh one thing to note, for this is subject: rights, requests and kind of the Microsoft friva space. This does require a separate set of Licensing. This is not tied to the you know: E1 E3 E5 or the A1 a385 tips excuse things like that. Every time you do a subject device request, it will require accretion of a new one. That'll require a new essentially purchase for one of those srrs.

D

The current uh pricing for this is 200 US dollars per separate price request. If you are looking for you know bulk or volume kind of Licensing. For this please do reach out to whoever your licensing expert. Is your resellers things like that? um Just note that this is not going to be one of those apis or the things that's included directly with your existing licensing. There are some additional things for that.

D

So please be aware of that, if you're looking for a way to actually go and try this out, though, we do have a slide for that here in a second, so you can see more on that also note that if there are any types of permissions or other things that might be applicable for this, these are using delegated permissions and as such, if you're, trying to view things inside of the portal for trying to get access to different areas. There are a set of Microsoft preva roles and permissions that can apply for this.

D

Please do take a look at the URL on here, we'll post this into the chat just so you can go and take a look at that if you're looking for ways to actually go and get a demo environment for this, as we mentioned previously in the community, call there is the Microsoft 365 developer program with that you can do get that sandbox tenant. uh The 25 E5 licenses again sell for news out there, the other area as we're mentioning for the licensing. For this there is a trial for Microsoft preva.

D

You can go to AKA dot, Ms, slash, try, preva and you'll get a set amount of those srrs available to you inside of your tenant or you'll, get it for a specified amount of time. For that so feel free to take a look at that again as another way to try this out before you actually go and purchase things. Would it be able to test it out there and see if it's going to meet your needs for this, and then the link also to the postman collection?

D

um Cameron did a great job of actually packaging together. The different sample queries that we have out there putting them onto the official Microsoft graph set of uh Postman collection out there. You can buy more at aka.ms, slash graph, Postman and we'll leave the slide up here. Just for a second, if you do have any questions, a couple different links to show you as well. If you want to learn more about those privacy apis, you can find them at aka.ms, preva, API and also as well for those permissions. Here's the URL for that as well.

D

So you can take a look at that and we'll post these things into the chat window.

B

But from a timing perspective I guess we can follow up on the questions in the chat. It's just easier. That way.

D

Once all right appreciate everyone's time and have a good rest of your call.

B

Excellent, thank you Frank thank you, Cameron really, really cool stuff and then, let's jump on Gary's screen uh around building your first notification bot for Microsoft teams, with Microsoft teams, toolkit for visual studio code.

F

Thank you very much. Hopefully, everyone can hear me and everyone can see the slides that are in front of you all.

B

F

Let's begin so, it was very mentioned. This session is going to cover building your first notification bot using teams toolkit for visual studio code, a little bit by myself. My name is Gary Tinder I'm, a senior Cloud developer, Advocate at Microsoft focus on Microsoft, 365., uh yeah. Basically, I'll leave this slide in there.

F

You should be able to take a look, uh and if you want to contact me, ask questions yeah, feel free to to reach out uh more than happy to answer any questions that you might have uh quickly just to cover what I'm going to go through so we'll cover. What is a notification bar quickly cover team's toolkit for visual studio code and then I'll actually go through.

F

Show you the steps of how you can create a your first bot and then run it and see how it works as well and I'll jump in and just show you how this bot Works what packages it's using, SDK, wise and then I'll leave you with some resources to find out more information. But hopefully, at the end of this, you should be able to have a good idea of what a notification bot is and go and build one in your own tenant.

F

So let's get started then. So what is a notification bar? Well, a notification. Bot really is um a great way of being able to extend Microsoft teams and with the ability to send proactive notifications into various Microsoft teams locations either that as a personal, app, that's installed in the user context or a a team Channel or a chat or a group chat as well. So a great use case for this would be you know you are wanting to react to something that's happening in an external system.

F

um When that happens, you want to send a message into a certain location, so people can see it and format that you know, maybe as an Adaptive card, with some buttons to get some immediate action on that. So that really is what a notification bot is so we're going to go through and use teams toolkit for visual studio code to build our notification box and so teams talking for visual studio code.

F

If you're not aware is a extension, um that's available in the marketplace that you can, you can install into Visual Studio code and it gives you the ability to create and debug and run and publish teams apps. So it comes with lots of project templates. Notification bar is one that we're going to look at, but it's got many others as well, and you may have may have heard teams toolkit for visual studio as well.

F

That is a enhancement for the visual studio application and that is based on net I'm, not going to go through that today. We can cover that in another call. So if you're really interested in that, please let me know in the chat today: it's Visual Studio code, so we're going to be in JavaScript and typescript um as we build our bot.

F

So with that, let's get rid of the slides and let's build so I will share my screen. Okay, so I've opened Visual Studio code. Already, um if I didn't have teams talk, it installed, it's very easy to install.

F

uh So I can search for teams toolkit very easy, just click install when you've installed it. You get the team's toolkit icon in the sidebar, but when you click on it, you get a few options. You can create your new themes app. So let's do that. So we want to create a new teams app. We do have samples we'll go into it now, but something that you might want to look into for for some examples of apps that have already been built.

F

So we're going to choose a notification box. You can see. There's other types in here that cover command Bots, tabs, SharePoint framework tabs as well other Bots, and so there's a lot of capabilities in in teams talk. It Visual Studio code for building other types of apps, but let's use the notification bot template for now.

F

um We've got four different options that we can choose. We have uh the the first option is a restify server implementation, um which is a HTTP trigger. So this is you sending a request, HTTP request to your Bot and that will trigger a message to go into the uh the different locations in Microsoft teams where you've, where you've installed it. The next three are all Azure function base we've got the HTTP trigger, um which again is the same as the first option. It's just got a different implementation.

F

We've got the timer trigger, which runs on a schedule, and the third option is you can have both. So when you create that project you can have, you know, messages going in there, everything 30 seconds or ad hoc when, when you need it, so let's choose that one. We've got the option for JavaScript and typescript I'm going to go for typescript, and we want to choose a location where we want to ins to create our project. So let's just call it Community call hit enter, and that starts the scaffolding.

F

So this is teams talk it now generating our project. It's fairly, quick, it's actually done and completed. So what I'm going to go do now is we'll just run through kind of the the folders that are in here. Just so, you've got an idea of what has actually been created for us. We've got the dot FX file folder, which holds various configuration files. These configuration files for Azure local um development.

F

These are placeholder values that will get injected into the app manifest. So you can come in here and you can create your own properties I'll, get to that bit a little bit later. Project settings, which is uh some internal code for teams toolkit. You shouldn't, need to go in into there, but this is kind of how everything is is controlled, vs code.

F

These are the debug profiles, so this is when we hit F5 um here's basically, where all the magic happens, a toolkit where we do a lot of activities and pre-provisioning to allow you to basically get your Bot up and running as as fast as possible and I'll go into more detail when I actually do that later we have our bot folder. So this is where our source code is, and we have a templates folder as well. So this templates folder provides us with a app manifest and also bicep templates for deploying and provisioning to azure.

F

um There is a nice little feature if we open the team's toolkit side panel. You can see that we've got lots of different options in here. We've got an edit manifest file, and so, if you don't know which file you need to look for, do the updates click that button.

F

It opens up the Manifest and we can see in here that we've got a teams app manifest with placeholder values in there that get injected uh in when we actually run our app and the toolkit basically handles all of that complexity uh for us like the valid domains which which will change as we are running the bot through development. So that's how you can get to your your manifest a couple. Other things to point out um is I've already installed.

F

Teams toolkit and I've authenticated my account against my Microsoft 365 tenant, so that's already showing as signed in and also that side loading is enabled that needs to be enabled on the tenant for us to be able to develop against it. And so, if you, uh if you've got a Sandbox, that's done for you automatically, but if you're using another type of Tenon, then you might need to go into your admin settings and just enable that that side, loading for for this to work.

F

Okay, um let's look at bot code because that's what everyone is interested in, and so here we have our bot as in Azure function. So we've got three functions: a message: Handler the HTTP trigger and the timer trigger that have already been created. So if you, if you're familiar with using Azure functions, this should be again pretty familiar. We've got the definition files in here which tells us that this is a HTTP trigger. Again this is HTTP the different endpoints and then we've got our timer trigger as well.

F

That is by default running every 30 seconds, so the code for the uh the two triggers the HTTP trigger and the timer trigger are in here.

F

So this is where our logic is going to live, and you can see it's just a standard, Azure function that is being invoked here and we've got some helpers from the team's toolkit that basically simplifies working with the the bot framework it so that you, you know you that there is a layer of abstraction um that um you don't have to basically handle all sorts of uh different events uh that you, you would have to have done using uh the uh the the bot framework SDK, and so this just to quickly cap.

F

What this actually does uh this code when it is run, it will go and get all the locations of uh where the bot has been installed um and it will Loop through all of those targets and it will send in an Adaptive card. So if we just quickly take a look at that, we've got an Adaptive card already created for us, and so we can see that we have a model for card data which describes the uh the the shape of our data.

F

We have a template, which is this notification default Json file, and then we have the data that we can inject into that um at uh at runtime to render Dynamic values.

F

If I quickly look at the Adaptive card, you can see that we're using the templating placeholders in there and we have a an action as well to open a URL uh one folder just to call out. So we have this internal folder. You shouldn't need to come into here, but it's good to have an idea of what lives in here. At the end, the initialize file is where our bot is actually instantiated. So this is the wrapper uh that the teams FX SDK, provides us with.

F

So this provides a nice easy contract to set our config, so our bot IDs and our bot passwords, as well as various other configurations as well, and so it's a nice way of being able to see okay, where, where are the values that have been passed into, my bot so time to run uh this project?

F

I'm not going to do that on this one, because there's a number of checks that are going to happen, including an npm, install, and we don't have that long to wait so I've already gone and run um the uh this this bot and and already done that install so to run. This bot is very simple. We can go to the debug Pane and we can choose the the profile for the browser that we want. So I'm going to use Edge and I'm going to hit run, and we can see here if I just expand this.

F

You can see that there's a number of prerequisite checks that are happening a bit fast, but essentially what toolkit's doing is it's checking the node versions. It's checking that you've authenticated with the r365 account. It's checking that you've got Azure functions, core tools installed and the npm is there as as well. Additionally, what it's also doing is it's going off to the bot framework and it's provisioning, a a bot in the service for us. So that's where the the ID and the password comes from.

F

um That's that's injected into our config. When team stalker has done its job, it will open up the browser and it will open up our bot. Now. This bot has two triggers, so it has the timer trigger and it also has the HTTP trigger as well. So we've actually seen, we've already got a message sent in the the timer trigger has already kicked in. uh This is the side loading I mentioned before we've got different places that we can install this app team chat or actually a meeting.

F

If you just click, add that will install the app as a personal app into the user context. I'm just going to do that for for now, and we should see that we've got our timer triggered um event that has come through. That adaptive card has has been sent now. I mentioned that there's a HTTP trigger. If I go back to visual studio code, we can see that there's an endpoint that has been uh stood up for us, this API notification endpoint.

F

If I come over to um Powershell, you can invoke the the service so just send it a post request which I will do now and I'll get a 200 response, and if I go back to my app that is running, we can see that that message has appeared in uh teams uh in our in our chat so by basically just simply creating the project running it teams to talk.

F

It has handled everything for us that we need to get started, provided us with the two ways to send the messages into teams and I'm quickly, going to just jump back to the code, so the in in this example here we've got the HTTP triggered notification, we're actually getting some context back. That says: okay, this is a person context and I'm just going to show you the code in the trigger uh just so you can see uh how you can then further develop this. So if I go back to code.

F

Let's go to the source file and we go to the HTTP trigger minimize this foreign, so we can see here that we get a type bat from the target. So if we just take a quick look at the Target, so this is essentially our bot installation. We've got access to various methods and properties, so we have access to an adapter. So this is the underlying bot framework adapter. So, like I mentioned, the the SDK is providing that abstraction. But if you need to go to the lower level, you can access the adapter.

F

Through this way we have some helper functions to get the channels in a particular team, get team details. The members for the chat on the team help us for sending adaptive card or sending messages as well as text, and also accessing the conversation reference as well. Another way of accessing that that underlying um API, that's provided by the the bot framework as well so I'm going to leave that there because we're rushed for time.

F

But as you can see, if you're going through this, take a look at the comments that are actually in the file as well, and you can see how you can write the if statements to only run and send cards if it's, uh if you're Bots running in the context of a group uh or a group chat or even a channel as well um and yeah, hopefully you'll be able to uh to enhance this bot to to do what you want it to do.

F

um I'm quickly, now just going to jump back to the slides, okay. So, just to summarize so notification Bots great for sending proactive messages into different teams. Locations two toolkit provides the quickest way to get started. Developing teams apps I've, shown a notification bot, but there's you know plenty of different uh scenarios that you can build with teams toolkit and teams. Fx there is, is providing a layer of abstraction to simplify working with the bot framework, which is really really useful.

F

Some resources to learn a little bit more, please check out the docs for teams toolkit and also teams, FX SDK as well and yeah. Thank you very much for listening. Apologies. I've tried to get through this as quick as possible, you'll be able to watch it back on the catch up and probably slow it down a bit um but yeah. Thank you very much. If any questions put them into the chat and I will definitely do my best to answer them and later over to you.

B

Excellent, thank you, Gary, really cool stuff and and not worry about it. Unfortunately, at the time, so it's our 50 minutes but um really cool stuff, and you do have that awesome, blog post available as well. Now, let's go then Bob on you and editing TR site, and anybody who has questions uh please. Let's use the chat for those because we do have more than 200 people in the call. We cannot, unfortunately, go to audio uh related on the questions.

B

So please please, please use that read and ask, but Bob I can see the slides great.

G

There we are, how you doing a detailed um we're ready to go so um so yeah I think we're just going to be kind of informal here uh between the two of us. So I've got some stuff prepared and uh dto just jump in whenever, whenever wherever you wish uh on this, because it turns out, we both were pursuing this very similar path here and it's a really important pattern. We wanted to share with the community here. So let me start so that well, the topic is account linking between Azure ID and teams apps.

G

What this is talking about is, if you have a teams app and you don't want to use Azure ad, you can but there's a lot of reasons that you should use Azure ID and if you've already got an app, maybe it's an Enterprise app that uses some other system, or maybe you built an app with net and you've got SQL authentication, or maybe you used some other oauth provider like Ping or identity server or OCTA, or you name it right.

G

It's still usually possible to use Azure ID as well, and that's what we're going to kind of go over today. So let me show you the example, and this is borrowed from the app Camp Labs, that I'll point you to later and so I have here a very simple application, with kind of a very basic login system built into it. So I'm going to just log in as let's say, Andrew you and you can see this is so insecure.

G

I, don't even have to give a password right, but you can see that it logs me in and I can see. My data I can see my orders, so it knows who I am. These are specifically my orders and that's all well and good.

G

The problem is: if I go into teams, I can't get a single sign-on experience, so I have to click a button and the button is there because it's a pop-up window- and we all know the browser rules with pop-up windows and stuff, like that, you have to click a button to get there, and so now I can do the same login and it works. You know, and that's great and I could declare victory at that point and and be done.

G

But then our presentation would be very short and our users would probably be kind of unhappy. So here's my top reasons for supporting Azure ID, the first one yeah good old Northwind right, can't can't uh it'll never die. Northwind database will never die so first, it allows single sign-on across devices, so users aren't going to get any extra prompts and those prompts can be extra annoying on your mobile device. Where you're trying to you know log in again and again single sign-on.

G

You could, you know, never think about it again: you're logged into teams, you're done. It also includes some key security features like multi-factor auth and conditional access where the policies are controlled by the Enterprise. So that's going to make the Enterprise a whole lot more comfortable. Even if your alternative auth scheme supports those things now, you've got the user trying to come up with another MFA prompt right so against. Let's simplify it for users, no extra usernames and passwords.

G

No extra MFA prompts um it's easier for team owners who would have to then, if you're inside of a team with Azure ID, you could set it up so that membership in the team was enough, and so you had somebody the team. They immediately get access to the right parts of the application that they need.

G

In this case it would be which ones are my orders right, but the thing about that is that if it's a separate login system, somebody, probably the team owner, is going to have to keep track of everybody's alternative login and add and remove them as appropriate as people come and go from the team. So that's a big overhead and something that I think a lot of people might not really, you know, be organized and remember to do that up front sort of and then later somebody leaves and they're like.

G

Oh, what was what was that person's login in this other system, so I can take away their access and maybe maybe the admin just goes. Oh I'm, too busy and now somebody outside the company, maybe who left under unfortunate circumstances, has a login to get into that app and Company data that they shouldn't have it's easier, also for M365 admins, who ultimately get held responsible for this kind of stuff, and you know it's important for them to have a way of managing access.

G

This is also required for monetization in the team's App Store and for the M365 app compliance program and not to put you on the spot. A deta did I miss any. Can you think of any other Big Lake yeah? We should have done Azure ad kind of moments.

A

The user retention is much higher. I want to emphasize that again it's much higher when they do um SSO and support Azure ID. It's significantly higher.

G

Oh, that's a really good one. Then I should put that on the slide. You know um I actually got that feedback from Partners as well that one partner. Actually you know they pretty much the reason that they started their app and now there's more features and they're. Taking advantage of more teams features was because of the Azure ad and their users were demanding it and that's helped their adoption quite a bit.

G

So with that in mind, you know, we've got limited time, I'm not going to go too deeply into it, except to say that Azure ID is the at the core of Microsoft 365 and Microsoft teams. A tenant, an M365 tenant is matches one to one with an Azure ad instance, and then all the users and guest users and the app itself are all registered inside of azure ID. However, when you have a scenario like the one I just showed you end up with kind of two islands, so teams graph all the data behind graph.

G

Oh that's another one, I forgot. Another reason is so that you can call graph right if you want to get anything about the user. Maybe you want to, you know, check their calendar to see when they're available, or maybe you want to just get their profile. Well, obviously, if you're in the other Island, you can't do it right.

G

So that's the challenge and I'll call out some of my some folks that I've worked with in the GPS team and the partner team have also run into this issue the the solution kind of generically and it's going to be a little different for every application, honestly, depending on how it's written is to link these identities. So basically, you get the user to log in with Azure ad and the SAS applications identity, so there for some moment in time, they're logged into both, and then you link the two identities in a database of some sort.

G

So, in this case, I'll show you the database in the demo that follows, but it is just a very simple little json-based database and we're going to put the Azure ID user IDs and the SAS applications user IDs into a table so that when a user logs into teams with single sign-on, instead of making our off making the user login again we're going to do our authorization based on the linked identity.

G

So let me show you what that looks like for a user I'm just going to pop in here and stop my my server and start it again using as if I had just done, one of the app Camp Labs instantly there and now. If I come back here and I log out and I refresh I'm gonna get a different screen and it's going to say. Oh, please, log in using your Northwind employee login to link it to your team's login.

G

So this is going to accomplish the account linking so it looks kind of the same as before, I'm just going to log in as Andrew and it works like before. We should probably take this log out button away because it doesn't do anything anymore. You can't you're just automatic as fast as you would log in log out. You get logged back in again and that's it now. I could go to my phone. I could go to another computer and I'm never going to get that prompt again. Why?

G

Because it's actually stored here in the back end and if I kind of drill into here to the data you can see. There's this little identity map here and it's taken, the Azure ID user ID and the employee ID and Associated them there, so that we can just kind of automate that process the next time the user comes back.

A

Yeah actually and Bob just to jump in here. This is a plan approach and and soon we'll present another approach as well. This is an easier push to understand, but could potentially have a few issues certain issues if you want to do it, but it's really easy to understand it's a great stepping point and so we'll present again in a soon another approach and Bob and I are going to present one. That is a little bit more advanced, but it's probably a little bit more secure in other things as well and.

G

Well and I know that um yeah but yeah I think that the a number of Partners have used this effectively where I, where I've seen it fall over, is if there are dozens of microservices all doing the authentication themselves, then it you know a lot of apps are designed with one single check for for authorization sort of at the entry point to the app, and this works fairly well in that.

G

So, if you'd like to try this out, you can go to teamsapp, AKA, dot, Ms, slash, apptip and go and take what you'd want to do is is take this B path instead of this. So the a path assumes that the app already had Azure ID and the B path, you'll see that you set up the non-azure ID app and then that's the transition. I just made was to add the identity mapping.

G

So it's a pattern you're going to have to kind of figure out how to apply that in each situation that you're in so I'll just sort of wrap it up. With this slide, we've got a Hands-On lab with the bpath. We've got the account linking now. This has been a detail, just wrote an article and a sample on this, and this is great. He goes into a little bit more depth on how this all works and is there anything else you want to say about this.

A

No, so the sample illustrates the the other sort of more sort of advanced approach, and so that's the one we'll go through again later.

G

Okay sounds good.

B

G

B

On the any questions on the chat- and we are anyway hitting the hour- uh so thank you uh on that one. uh So let me go on the slides here and just a close-up for today now. Thank you, Brian. Thank you, Cameron! Thank you, Gary! Thank you, Bob and Aditya on this one really really cool stuff. uh It's it's great to have this coverage, uh and also all of the demos are recorded.

B

So I do apologize, I messed up the intro, so we did not do the recording on the intro um we'll get it fixed uh for the next one. Now this overall recording whatever we got, which is again all of the demos uh we lost some of the intros in the start, will be available in 24 hours at the Microsoft 365 Community YouTube channel at akmsm365 videos. You can subscribe there, so you'll know when the video is available. You can follow also us on the Microsoft traces to our Dev on in Microsoft 365 PMP either.

B

One of those uh you'll follow up on and get notifications on when stuff is getting released, including some temples, demos, videos and all of that. The next Microsoft 365 platform call is on October 11th at 8am Pacific time so again, one week forward from here and you can download the recurrent invites from akms m265 calls, but that's it for this one. Thank you everybody for joining and thank you for the great demos and thank you for the feedback remember to provide us the feedback.

B

We are building the Microsoft 365 services for you, so we need to know what works and what doesn't work and if you have suggestions related on how we can improve our community efforts. Please do let us know as well, but thanks everybody. Let's stay in touch have a safe rest of the week.