Microsoft 365 Community Development, 2 Mar 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Microsoft 365 & Power Platform Development Community call – 2nd of March, 2023

Description

Microsoft 365 & Power Platform Development community call delivered on March 2nd.

Demos: Build task automation solution between Planner and GitHub using Microsoft Graph and Improve your test strategy with Microsoft Graph Developer Proxy.

Released: Microsoft Teams Toolkit – v4.2.4 (GA), Microsoft Graph Toolkit – v2.9.1 (GA), Yo teams - generator-teams – v4.1.0 (GA), 7 connectors, 6 scripts, 1 Teams sample, 2 Power Apps samples, plus 6 conversations.

Announced: Microsoft Graph & .NET Hack Together March 1st - 15th.

Please see the blog post for this call for project updates, news and events details. The host of this call was David Warner II (Microsoft) | @DavidWarnerII. Q&A takes place in chat throughout the call.

Agenda
00:00 – Intro - David Warner II (Microsoft) | @DavidWarnerII
07:06 – PnP .NET library updates - Bert Jansen (Microsoft) @O365bert
09:00 – PnP PowerShell updates - Gautam Sheth (Valo Intranet) | @gautamdsheth
10:56 – yo Teams updates - Stephan Bisser (Solvion) | @stephanbisser
12:18 – Microsoft Teams Toolkit updates - Vesa Juvonen (Microsoft) | @VesaJuvonen
12:57 – Microsoft Graph Toolkit updates - Sébastien Levert (Microsoft) | @sebastienlevert
15:18 – Independent Publisher Connectors - Jocelyn Panchal (Microsoft) | @JocelynP_PM
17:16 – Microsoft Script Samples - Paul Bullock | @pkbullock
19:23 – Microsoft Teams Samples - Bob German (Microsoft) @Bob1German
22:08 – Microsoft Power Platform Samples - Hugo Bernier (Microsoft) | @bernierh
23:02 – Together mode picture
24:02 – Demo - Build task automation solution between Planner and GitHub using Microsoft Graph – Anoop Tatti (Content+Cloud) | @anooptells
40:01 – Demo - Improve your test strategy with Microsoft Graph Developer Proxy - Adam Wójcik (Hitachi Energy) | @Adam25858782
59:40 – Closing

Learn more
• See the full blog post for this call in the Microsoft 365 platform community blog - https://aka.ms/community/blog
• Download invite for the Microsoft 365 & Power Platform Development community call: http://aka.ms/spdev-sig-call
• Microsoft 365 Unified Sample gallery - https://aka.ms/community/samples
• Microsoft 365 Platform Community in YouTube - https://aka.ms/community/videos
• Microsoft 365 Platform Community - http://aka.ms//community/home

A

B

Let's click this on and tune in.

C

B

With the community, this is the Microsoft 365 and Power Platform development. Bi-Weekly call we are all tuned in today today is March, 2nd, our first call of March. How exciting is that spring has sprung for many of us and we are excited in what the community has to offer. So, let's take a look at what we're going to talk about today we got the latest updates on the community.

B

We've got pnp.net libraries, Powershell, yo teams, Microsoft teams, toolkit Microsoft graph, toolkit, independent publisher, connector, so many amazing areas of contributions and Scripps samples, team samples, pile platform, samples, we've got all the samples and then, of course, everyone's Favorite Time picture time. Where we'll get to show our fantastic faces to the community, then we're gonna get to our two All-Stars of the day. A noob is going to cover using app only model with Microsoft graph apis for planner, and then Adam is going to get into improving your test strategy with Microsoft graph developer proxy.

B

So two very exciting demos for us to talk about today. Now, let's take an overview. Look at what resources are available to you. We've got Microsoft from 365 Microsoft and three yeah Microsoft and 365 Microsoft 365 and Power Platform Community videos uh rolled up all into one that you can subscribe to today to continue to be up to date with all the cool things that are happening.

B

If you like those picture movie things, and then we've got a LinkedIn group for discussions- and you can be part of this- so definitely go check that out and join today, a number of Open Source resources and, of course, those sample galleries. Community samples will take you to all the roll-up of them where you're gonna be able to see some very cool profiles of the actual contributors and we'll see more of that in upcoming calls and then you'll be connected to all those teams.

B

Spfx Power Platform list, formatting samples, all the samples that are available now you're, like thinking man, that's a lot of URLs for me to memorize no worries. Only one AK dot, Ms, slash, Community Home will take you to all these resources in your One-Stop shop, so definitely uh get involved there and take advantage of all those resources. Now you may be thinking I really like these Community calls.

B

We like them too, so we've got plenty to offer you the Microsoft in 365, uh there I go again: Microsoft, 365 and Power Platform Community calls uh include calls such as the Microsoft 365 and Power Platform. Microsoft speakers only call. So what this is going to provide.

B

You is all those product managers and program managers that are working hard on the products that we all love very, very much they're, going to be the only presenters on these calls, so you're going to get it directly from the mothership and you're going to be able to learn directly from those that are making the products within Microsoft. We, of course, have our other community calls Power Platform monthly, which is in a couple of weeks. That's the third Wednesday of every month.

B

We've got the identity platform office add-ins and then, of course, the Microsoft 365 and Power Platform Community bi-weekly call which you're on now and the Viva connections and SharePoint framework, which is the opposite Thursday of this week. So you can access all of these by going to AK dot, Ms, slash, Community, slash calls and of course there is also the Meetup that you can take advantage of so definitely check that out. Ak.Ms, slash, Community, slash, Meetup will also connect you and keep you informed.

B

Now you may be thinking. I would love to actually present on these calls, and we would love you to present on these calls and we made it easy for you. uh You just gotta, go to this URL AK dot, Ms, slash, Community, slash, request, slash demo and fill out the form tell us what you'd like to cover and we will get you scheduled. We've got a number of openings coming up in the next couple of months that are available to you.

B

So if you want to show a technical pattern or a sample or a demo, absolutely maybe you've blogged about it and want to show it off, don't overthink it. It doesn't have to feel like you're, inventing the flux, capacitor or making time travel possible. Remember what you have learned as valuable others will find valuable too. So definitely take advantage of this and if you've not presented and you're a little nervous about it, let us know we can buddy up with you.

B

We've got a buddy system in place and we'd love to work directly with you now. Looking ahead at the Microsoft 365 Power Platform Microsoft speakers call next week, we've got Aisha bass coming in to talk about dynamically, creating an Azure, Communication, Service, identity and token, and then our very favorite Gary trender is going to talk about the the continued path of teams. Toolkit then next week will be build. A Microsoft teams tab using a team's toolkit for a visual studio code last week or earlier this week was a bot.

B

So we look forward to that continuation and then the one and only wall that will be there to talk about Microsoft graph, hackathon recapping, that first week. So we look forward to that exciting opportunity for everyone to get involved there, and you may be thinking I want to get involved in the community, but I'm not quite sure where to start Hugo Bernier tell us a little bit about it.

C

Well, it's funny you should ask, because we have initiatives called sharing and scaring where we can actually help you get started in the patterns and practices. Community, we have first-time contributor, you have fire platform samples, contributor writing for the web, and many more we've got some new sessions scheduled for March and we strongly encourage to join us. If you want to learn how to contribute and I promise you it's not going to be recorded, it's going to be fun and everyone can be in a safe space and ask questions hey.

C

If I can ask questions and nobody makes fun of me, you know it's a safe place and then once you've joined these sessions, you can actually join our community recognition program, and so that's for anyone who has contributed to the community in many ways, so, whether you've written some samples, you've published an independent, connector, you've, uh you've, written documentation or many other things and including presenting on these calls.

C

All you need to do is you need to sign up at aka.ms, slash, Community recognition and then what we'll do is we'll associate your GitHub account to your credly account and credly is something that is used for all the official badges. So, for example, if you get certified at Microsoft, you get a badge and so we're using the same program we're using credly to create these badges they're official. So you can put them in your resume. You can put them on your LinkedIn. uh You can show it to your friends and impress people.

C

You can even get a tattoo if you want, and so again don't hesitate to sign up. This is free for you and with that I'd like to pass it back to my friend, David.

B

Awesome, thank you. Hugo yeah, uh you know getting that tattoo was painful, but uh getting the new year added on every year. Oh boy I tell you, uh but it's worth it, it's worth it. So all right. Let's talk about hack together. It is now March. So that means that hack together has started so definitely check out how you can get involved here.

B

uh Go to AK dot, Ms, slash hack, Dash, together to see the Microsoft graph and.net opportunities that are available to you in the next couple weeks and as we mentioned, waldik will be here. uh To recap the first week on that call on Tuesday, so definitely get uh invited to that and logged in there to to learn more about the hack together progress. Let's move over to some Project Specific updates and we'll start with Bert.

D

Thank you. David. um What's happened in the dotnet world, a couple of things uh for the PMP framework Library.

D

uh We had a change from Arno around the undo, checkout file, so in enabled that so it can be used in Powershell and then another one uh from Giacomo around the default column value setting- and this is one that that caused some some concerns, some issues, because in the back end, what happened is that Microsoft did uh roll out start rolling out the change that blocked, adding event receivers on uh out of the box event, receivers on lists and the default column, values values on a folder depend on that.

D

The event receiver, which caused several operation templates to start to fail. uh Suddenly the fixed former Giacomo makes the problem less prevalent. We only apply the event receiver now once really need it, but still it can fail. Now we are actually rolling back that change, so the situation should restore itself and you should get back to a working model and we will kind of review why this went through and how we can offer a solution that works for everyone all right on the course gay side. um Martin did work on enabling a permission request approval.

D

So if you deploy an application to the to your catalog and it requires like a graph permission, you have to approve it till you go to the tenant and then you approve it now you can do this problematically uh using course Decay as part of the our application support and also has support for enabling of disabling the app principle, if you would need that and finally, there is like a new Renee method on the file object, just to make your name easier and a couple of other small fixes, yeah I, think that's it for me.

D

Then, let's move to Powershell with Gotham. Thank you all.

E

Thanks thanks Bert, um what's new in the pnb? uh Well, the two point x uh nightly bills are out so do check them out. um We are. We have dropped support for Powershell five, so you should ideally update to the latest Powershell 7.3, but it will also work in 7.2 as well. uh What what is improved in the new newer lightly and nightly? Is this uh ad PNP teams tab command? So we have added better support for adding a planner tab as well as a SharePoint Pages tabs, so that has been improved.

E

uh We all um as uh I think bird mentioned in the previous uh slide, that somebody added a code for undoing the checked out file, so we also added a related commandlet to that. So, if you want to check out discard checkout to a particular file, you can do that as well.

E

um In the PNP, add PNP file a PA, sorry in the ad PNP file commandlet. We have not changed the default check into minor check to the minor chicken. It was earlier used to do major check-in, so we have changed that and if you want to still continue using the major check-in, we have specific added this additional commandlet, which is called as the chicken type parameters. You can do that and that will you add, the major major chicken and yeah one other interesting command. uh One other interesting parameter. We added to the setup list.

E

Is this default sensitivity label for the library? So if you are using the graphs Library used it used to require a premium uh graph library, but if you use this command, it uses the SharePoint DPS, and this does make things a bit more easier if you want to set that default uh sensitivity, label for a library, so yep do check them out and do reach out to us on the discussion forum, as well as on the issue list on GitHub um yep thanks ODU David awesome.

B

Thanks got him that is very cool and again 140 million commandless executed per day, fantastic, excellent. All right. Let's turn over to you, yo yo I'm, on a roll today, yo teams with Steven.

F

Thank you David, um and we have a new release. Rick released 4.1.0 four hours ago, um with support for uh generating teams, manifest versions, 1.14 and 1.15, and we fixed some bugs which we encountered and we are working on uh releasing your team's build core and deploy uh for stable versions as well later today or by tomorrow.

F

Hopefully um so definitely go check that out and give it a try, um and apart from that, we're still discussing on how to simplify the generator itself, to make it more um yeah easier to to contribute for anyone would like to contribute. So if you have an idea uh in mind- or if you have anything you'd like to see in your teams either let us know via our GitHub repo or if you uh want to do it by yourself, just file a PR. Do an uh file, an issue create an issue.

F

Let us know, and we definitely need your help to get the your teams even better over to you. David thanks.

B

All right, yo yo, thanks Steven, excellent, all right and definitely get involved folks, because uh they are a great group of guys and gals. That would love to help you get more involved. So don't don't be afraid to reach out there all right, Microsoft teams toolkit. Let's turn it over to vesa.

G

Get on here uh there's a new version available released on last day of February, so just on Tuesday this week, which is 4.2.4 and that actually includes primarily a SharePoint framework 1.16.1 support within the Microsoft teams, toolkit for teams applications and there are other updates like Note 8 18 support, 3x17 support and team JS to the latest version. Well, almost the latest version uh there's a lot of opportunities for Community to get involved and there's even a paid options related on interviews so probably want to check out the URL.

G

We'll put it in the chat for that one. But let's then move to Microsoft craft and Seb sorry, David I can't help myself God. That's.

B

Okay, no problem I appreciate the help.

A

Yeah thanks thanks Mr thanks David, um so we're excited we just shipped our v 2.9.1 um yesterday night um update your packages. It's it's all available um right now on uh npm uh we're bringing some um interesting capabilities and fixes to our MGT people, picker we're also bringing um a a subtle change to our MGT loader to invite, if you're, using MGD from a CDN, we invite you to pin your version uh from the CDN. We are so close to shipping our V3.

A

We want you to not be hit by our braking change when they're gonna hit in V3, so we're I'm, adding some console logging in the browser to let developers know that by the way, we're we're making these big changes. Please make sure that you pin your version there what's next in the next few days, we worked really hard to have it for this week.

A

um It might sleep, maybe tomorrow it might be early next week, we're going to have our first official preview of Microsoft graph toolkit V3, which is all built on fluent and with a lot of new capabilities. So we're very, very excited about about this one. It's gonna be a big release. uh Watch for the big blog post happening next week, um we're going to bring more components more generic uh templates, more theming opportunities.

A

Also uh with that version, so I think it's going to be great for anybody that is using the toolkit and wants to leverage, for example, being part of a teams app being part of a um an office.com app where we will be able to leverage over the theming capabilities right there. We need your help. We want you to help either fix some of our bikes. We need your ideas. We need to talk about your scenarios.

A

You want to hear your feedback so feel free to go on into our repo AKA dot, Ms, slash ngt, um and that's where we can uh start a discussion back to you. David.

B

Awesome thanks Deb excellent, uh excellent excellent work excited for the new stuff there, all right, independent publisher, connectors with Yas. It.

H

Is I your favorite gen zpm we're gonna switch the order today to give everybody a chance to scan that QR code. If you love connectors as much as I do, and you want to have a connector specific session hosted by myself, please scan that QR code to fill out a quick form and I will send you an invite.

H

Our next connectors Labs call will be next Wednesday morning at 7 A.M Pacific time we always have updates and educational session from another internal PM, like myself, featuring topics like Alm like the dataverse connector and as well as a demo from an independent publisher. That could be you now. If we switch gears back over to updates, we are now at 963 total connectors, which is 15 more since two weeks ago. That's more than one a day.

H

We are only a third through our six month goal between January and June, but we are two thirds to our goal in terms of want to do connectors much due to the contributions of community members. Like yourself, we are now at 246, independent publisher connectors, which has surpassed the quantity of internal-made. First party connectors 78. Amazing Publishers with seven new ones since two weeks ago, of course, we have our normals. We have Troy with one point: J service affirmations and API templates, as well as for those with air Labs.

H

Some of you might recognize amjad's name, that is our very own certification PM with yet another connector, as well as welcome to Mint management Technologies for their first connector with pastebase. If you are interested in getting involved, My Links will be in the chat. We need your help in order to help execute some of our top connector apps. We have 963, but not enough yet as well as you can receive a credly badge for your contributions as an independent publisher, connector. So please reach out and get involved thanks David.

B

Awesome thanks Josh, more independent Publishers than a first party, oh snap, but that's awesome. We love it excellent all right how about some script, samples with Paul Bullock.

I

Thank you David, uh so script samples is a place where you can share scripts with the community. um We have some awesome set of new scripts on the uh on the board there. So um so, just just to step back our script. Samples is a place where you can share scripts, such as Microsoft graph, PMP power, SPM, Management Shell and all your favorite tooling. uh The new scenarios we've got.

I

uh We've got two for the Microsoft graph, SDK Powershell, so we've got ad users to follow sites by Andrey Lange and we've got multilingual SharePoint summarization using open, Ai and API and Microsoft graph Powershell SDK by Anup. We've got some new PMP Powershell scripts, which is super super cool, so we've got remove title area from SharePoint page by ganache.

I

uh We've got uh use, uh invoke, PMP, select template with parameters by Casper, Larson export access, shared links from a SharePoint library from Andre again, and uh we've got associate multiple site collections to have site by Sadaf, which is super. Super cool I've also introduced a new Powershell script in the root of the repository. So at the moment, when you create a new sample, you need to copy the Boiler code that I've got and then fill it out.

I

So what I have done now is created a Powershell script, where you can specify things like the name of the folder, the title of the script, the descriptions and which tooling you you want to submit a sample for and that will generate out all of the boilerplate and fill out a lot of the detail for you saving. You have to do that data entry, a way to lower the barrier. If you, if you're, struggling to create new samples but by all means it is necessarily refreshing out from yesterday.

I

So if there's any issues or if you want to contribute and need some help by all means reach out to me via Twitter or LinkedIn I I'm more than happy to spend some time helping you get moving forward and again. Thank you very much for everyone. Who's contributed, you're, absolutely awesome and remember to opt in for the recognition value. You will get a badge for script samples. Thank you over to you. David awesome.

B

Well done thanks Paul a lot of great work there. Thank you. Everybody uh Microsoft team samples with Bob German.

J

Hi everybody um so I actually have a couple things today. One is a new sample. um This was actually Rabia Williams. In my hack week project we built a teams meeting app that uses the live, share, SDK and fluid framework to just organize who's going to talk next in a team meeting, it's simple enough that you can kind of get your hands around how to use fluid framework to synchronize the data behind your application and how to use teams toolkit to build an app like this.

J

That runs inside of your meeting, so I think we're scheduled in a few weeks like in April to do a deep dive on this, but you don't have to wait because we've also got a Blog article and a video that are available right now. So would love to see this is kind of low friction. If you can upload an app you can use this thing, you don't need any there's.

J

No administrative permissions required I also want to take a second and I only have one slide, so I kind of stuck this up in the corner for isv's building monetize teams apps so are the Microsoft teams. Ecosystem group, in conjunction with the global partner solutions group, is looking to accelerate getting apps into the team's App, Store and monetizing them now.

J

I know nobody likes to make money right, making making money, building something and then just having it run in the background and and generate revenue for you or your company that that's who who wants to do that, but just on the off chance, these people actually want to help.

J

You accelerate that process of getting your app into the team store integrated with the commercial Marketplace, so that people can actually pay for the app you get to keep 97 of the money because we only charge three percent, unlike certain other app stores, and so um it's a great opportunity. If you're in an isv, please go ahead to this URL teams, apps AKA, dot, Ms, slash teams, apps slash, support and uh fill in a little form there and uh they'll help it.

J

Basically, they want people who are going to sell their apps in the store, but they'll help with all the different aspects. And you know if you're, not an isv, I gotta, just say on a personal note, I've seen more and more companies that build something for their own use or for their clients use starting to break into actually becoming software Sellers as well. It's a great kind of extra income stream and an extra way to get your name out there in the world.

J

So I just wanted to mention that as well, and uh thanks very much back to you. David awesome.

B

Thanks Bob great work there, everybody and last but not least, let's kick it back to Hugo quickly for Power Platform samples. Thank.

C

You so Power Platform samples are repositories in GitHub that allows you to share your Power Platform samples, I know crazy name. We have two new samples. One is a quality assurance assessment by 90 turtle, dove it's inspired by the center of excellence, uh quality assurance, but it's always good to see how people reverse engineering, these Solutions and build new versions and Company Falls By Angelo is another one of these reverse engineered.

C

This one was rebuilt using the Creator kit and it's awesome, uh no updates or no samples from both Cameron yet but I'll keep you up to date with the situation, changes but feel free to join us on sharing and scaring on March 15th, and we always welcome your samples back to you. David awesome.

B

Thanks, you have sold me Hugo. uh Now, let's get our favorite time before we get to our All-Stars picture time. Share that camera turn on that movie picture movie thing and vessel will take on over, and we will quickly snap that we're a little behind schedule, but we will catch up yep here.

G

We go. We have only two demos today, so uh 56 56 in room who, who has time to get their few more few more States in room, few more States, one more States sold.

G

Okay, I will put the recording on and we will see the numbers in the screen uh and let's do some kind of wearing we'll do a keep animation. Out of that. Thank you. Everybody for joining Todd is.

B

G

Cool to have you on a call today.

B

G

It's doing really good on the middle actually showing how it can be done. Awesome thanks. Everybody awesome to see you in here and hopefully we'll see you in the multiple in person conferences later this spring. But let's get back to the real stars of the day right, David.

B

Absolutely awesome, thank you. Vesa. All right anoop is here to tell us about using app, only model with Microsoft graph apis for planner a noob. Take it away.

K

All right, thanks dude, let me share my screen and yes right: okay, hello, everyone, uh so, in this session, we'll be looking at using app only model uh with Microsoft graph API support planner uh with that I hope that this presentation goes according to the plan uh right. So just quickly about myself, my name is Anup uh I'm, a Microsoft MVP, and the developer at a company called content cloud here are the various links that I use for my social media platforms. You can follow me on those if Direct, okay.

K

So, uh let's start with the first slide, which is about Microsoft graph and I'm sure everyone knows about Microsoft craft, so I've just taken these two sentences from the uh docs.microsoft.com, so Microsoft craft is the gateway to data and intelligence in Microsoft 365, and it provides a programmability model that we can use to access tremendous amount of data in Microsoft, 365 windows and Enterprise mobility and Security in today's demo, we'll be focusing on getting Microsoft 365 data using Microsoft graph. So this slide is about interacting with Microsoft graph.

K

On the left side, we've got an extra external app, so this is the app that we will be building and in order to access Microsoft 365 data, which is on the right side that Microsoft 365 data can be anything, be it in SharePoint or planner, or anything else, Outlook calendar. What not so for our external app to access Microsoft 365 data, we need Microsoft graph and the process is quite straightforward. Our external app uh asks Microsoft Microsoft graph to get us. The data from Microsoft 365.

K

uh Microsoft graph verifies that everything with the external lab is correct, as in it has got the required permissions and the client ID secrets and certificates. Everything is proper uh if, if all of that is okay, Microsoft graph will get the data from Microsoft 365.

K

and then pass that back to our external app. So there are several types of apps we can develop. One of such apps is GitHub, so, as you can see, on the left side, we've got GitHub and if GitHub has to access Microsoft 365 data, then we can use Microsoft graph and then get the data. And that's what we'll be looking at today. In particular, we'll be looking at interacting with the planner from GitHub, so what we'll do is we'll use Microsoft graph to interact with planner and then pass that data back to GitHub.

K

So in order to do that, what we'll do is uh we'll look at the repository in GitHub and that repository on on GitHub will have a GitHub workflow, and this workflow uh runs on a pull request.

K

So when there is a full request say on the main branch, uh this particular GitHub workflow will run, which we'll have a look at in a minute and then that workflow calls something called as a GitHub action that gitup action has some code which passes the data to Microsoft graph and then Microsoft graph. Once it gets the data from from this GitHub action, it verifies the authentication say you know the client, ID and secret will be passed and the permissions so with that Microsoft Curve will verify that the app has got proper permissions.

K

And if that is the case, then Microsoft graph issues an instruction uh to create a planner task. And once that is done, we can see the planner task in the planner and uses scan interact with that dos. So this is just one example scenario of how we can use Microsoft graph in order to interact with planner tasks, and in this case the application we are using is GitHub, but that can be any other application as well right with that in mind, let's take a look at the demo, so let me set up the scene here.

K

uh What I have here is a user called Megan Bowen, obviously so, and I have opened a GitHub repository, which is aptly named as workflow test. So myself and Megan are the owners of this repository now. What I'll do is I have opened this repository as Megan I'll switch to the develop branch and then make a small change and create a pull request. So let's do that. What I'll do is I'll just edit the readme, and then you know this is demo. Add some nice text here and then come with that change.

K

And then, if I go back to the repository, it says that the dev branch has been changed, so I can create a pull request. So what I'll do is I'll go ahead and uh create a pull request.

K

And give it a nice title and a nice description and create that pull request right now. What this will do is this will trigger a workflow. So for that, what I'll do is I'll just switch to my GitHub account and then open the same repository and then uh I'll just go on to actions, and we can see that uh the workflow has triggered and it is running now. What this workflow will do is like I showed you in the slide earlier. It calls cir GitHub action, which then goes ahead and creates the task.

K

So, as you can see over here, um if I just zoom in a bit, the workflow calls a GitHub action called Ms graph, create task, and that task goes ahead and uh you know creates a task in in the planner.

K

Now, if we look at the planner plan itself, so here's the planar plan and, as you can see over here, there's a bucket called as pull request and in that bucket a new task has been created which says, review the pull request and if I open that it has got the title of the pull request, and it also has got the uh the link to the pull request. So, as the owner of this repository, um you know, I have a task in my planner and then I can click on that link.

K

uh And then you know, look at that pull request and go ahead and you.

D

K

uh Most people request or close or or take any other action in this case. I'll just go ahead and more stupid requests and.

A

K

Once that is done, I go back to my planner plan and.

C

K

Completed yeah, so that's the uh simple use case that we have here now just before showing you the code. I wanted to show you that we've got an app registration in.

H

K

And in that app registration, if I zoom in a bit that particular app has got tasks, dot, resite, dot, all permission and because it uh we will be using this permission in order to create tasks in the planner. With that in mind, let me go back to the slides again.

K

So, just to recap, uh what we saw was a GitHub workflow, which is triggered on pull request and that called a GitHub action which then passed the data to Microsoft Microsoft graph then went ahead and created a task in the planner. Now uh our main focus here is the GitHub action which is used to call Microsoft graph. That's the one which we saw run earlier in the workflow, so that particular GitHub action uh is nothing but a node.js project.

K

So let's have a look at the code of that and uh you know and see how the task gets created. Okay, so uh what you're seeing on the screen now is the code of that GitHub action. The link for this will be shared uh soon. uh I have a slide for that towards the end, so this particular GitHub action. uh You know if you see on the right side. uh It's you know it's a normal node.js project. We've got our source folder and dist and lib.

K

So it's just like a normal node.js project that you have I have focused here on the package.json file and we are using two particular packages here. One is azure slash, m cell node and the other one is Microsoft, slash, Microsoft graph client. These two packages are needed in order to interact with Microsoft graph okay, so this particular gate of action has three main files: the auth.ts, graph.ts and main.ts.

K

All the code that I'll be showing you here will be in these three main files right. So first, firstly, when the GitHub action triggers uh what we do is we pass certain details to this GitHub action. So I have highlighted all the details over here. uh What I'll just do is I'll quickly show you the workflow as to how we are passing this data so that uh it'll it'll it'll all make sense. So if I just go back to the workflow that we saw earlier.

K

It was this one and we saw that you know the the action was called over here and then all the details were passed. So if I quickly show you the workflow itself, sorry.

K

Which is this one? So we can see here that we call this particular action and then pass all the details like the client, ID client secret, the tenant ID, the plan, the bucket and other different, uh the title and the user ID to whom the task must be assigned so from the workflow. We are calling this particular GitHub action.

K

Now, if I go back to the slides again, so when the GitHub action is called, we get all the details from the workflow and then what we do is we parse all those details, Within These different variables, once that is done, uh we create a new object for graph when we call that code. What happens? Is it just runs the Constructor in the graph.ds file with the client, ID secret and the tent ID that goes out and creates a new object of the auth class and over here in the Constructor of auth.ts.

K

We can see that we are, you know, creating a confidential client application. Now you might have seen this particular code in in various samples that are provided by Microsoft on how to use Microsoft graph. So I have just you know, taken this code from one of those samples. All we are doing here is creating an object of confidential client application.

K

Once that is done, uh we go back to the main.ts file. Here we create an object of the type planner task in this. We have the plan ID the bucket ID, the due date, whom to whom it must be assigned and the priority now uh and then, once we have that task object, we pass it to the graph dot, create tasking method. What does this do? uh As per the name? It creates task, but before that it has to get the craft client.

K

So we have this function called as get client and the get client function. uh We uh you know it first has to get the access token in order to get the access token. What we do here is uh you know we we compose the client credential requests, first, in which we pass the scope, which is craft.com dot default, and then we let's skip cache as true. This is optional. If we set it to true, then it will skip the token cache on every request.

K

We can set it to false as well based on the requirement uh and then what we do is we call this important method, which is acquire token by client credential. uh Now that is part of the MSL library and Microsoft have done all the hard work on. uh You know writing that method. So all we have to do is just call that method, and then, with that we get the access token and then once we have the access token. What we do is now uh we we create the graph client.

K

uh So for that we, uh in order to do that, we have to firstly create the auth provider and then, uh as you can see over here, we then just call the client, dot, init method and pass in the auth provider to that now. This is part of the Microsoft graph client library that we saw earlier in the package store Json right with that we have the graph client and once we have the graph client, uh all we have to do is just call the graph API endpoint of in order to create a planar task.

K

In this case it is slash, planner, slash tasks and we post the task object that we saw earlier and once that is done, graph API goes ahead and creates the task in the planner.

K

So that was the code as you saw. It was very simple: uh we just called Microsoft graph in order to create a task all right, so in summary, uh Microsoft craft planner API now has app only permissions. This was I, think done a couple of months back. It already had delegated permissions, but there was a request for app.

K

Only permissions and Microsoft have now provided us that with that, um and in order to use this, we have to create an Azure IDI, app registration and that particular application needs to needs to have tasks, dot, uh read dot all permission.

K

If we are only, uh you know, doing read activities: uh if you want to do read and write activities, then the permission is tasks.trikitrite.hall and we saw a scenario using GitHub in which a GitHub action uh was used to create a task, and then that particular GitHub action was called by a workflow which runs on pull, request and uh I'm. Sure there will be other scenarios in which this can be used in order to create tasks in in a planner.

K

Here are some links that were used as part of this demo and I see them in the chat already and with that I pass it back to you. David awesome.

B

Yeah, this is really really cool again. I love these Better Together scenarios that show how we can use the technologies that we all use together in a variety of ways. So thank you for highlighting that those links are in the chat. uh In the interest of time. We will move on to Adam who's, going to show us how improving your test strategy with Microsoft developer proxy can be done so Adam. Take it away sure.

L

So a short Direction about me. My name is Adam I'm, a father and a pretty standard developer, I'm one of the CLI for Microsoft 365 maintainers. So if you need any guidance or help regarding CLI just pick me up, I'm a quite fresh MVP still don't know what to do with, but I guess it's really awesome I'm a freelancer, but for quite a long time I've been working for such energy I'm located in Poland, and you can catch me on LinkedIn and Twitter.

L

Okay, let's move on so today, I will be doing a showing a kind of a use case for the Microsoft developer. Proxy I hope it's a tool you already had a chance to try out, if not I hope with the Zemo I will motivate you to do so.

L

So basically, this is a console application that helps you test the untestable and improve the quality of your apps by simulating responses to to any kind of API, not also not only Microsoft graph apis, like the name could suggest, could it be configured to simulate a errors or any kind of response for any kind of API. So, with this tool, we can of course simulate errors. We can, for example, mock a specific response. We would like to have for a specific request.

L

uh This tool helps us demonstrate behaviors that are really hard to produce, especially on our test environment, where everything is always working and they also along the way they still provides. You guidance that you can, of course, turn off. I bet, it's cool to have them and, for example, to suggest you to use additional query parameters to select only the data I use post to use or, for example, to switch to using an SDK instead of just using an HTTP client which what I will be doing today.

L

Okay- and what's really awesome, it will run on nus and it's fully extendable with plugins. It's not a part of my demo today, but maybe near future. Let's see so if there is a use case that is not covered by this tool, and it's a bit out of scope for this tool.

L

It doesn't matter it cannot help you, you can still extend it with a plugin for your specific needs, and, what's really really important, is that the tool is still in the community preview as a like stage, so it's not released yet, but it means that it really needs your feedback and testing and and any kind of feedback. I guess is important, of course, reporting bugs, of course, ideas, but also positive feedback. Like you know, if I denied it's awesome, I will use it in the future thanks.

L

It will be really good for the team to have so. Please, please provide feedback for the soul, especially now before it's released, so it's really okay to introduce breaking changes from uh priorities to pre-release, as opposed to maybe when it's released. It wouldn't be so okay to introduce a breaking change like after two weeks. Even if your idea is really awesome, so I will be covering a scenario of improving the test, a Test's quality of my desktop application, and you may ask okay: that's the application boring right. Why not a web application?

L

That's because there's already a use case and a scenario how you can use an integrated tool with a web application and there's a demo provided by Seb some time ago on one of the PMP Community rules, so I'll just leave a link here, so we can just look it up and also, probably since we are on the Microsoft 365 words, you are using the sharper framework extensibility, and will this tool help us with this uh as well? Yes, and one that also presented a demo not so long ago regarding this okay?

L

So what about I'm writing scripts like I? Do a lot so can this tool help me like test improve testing of my scripts Yes? Actually, it is as long as your script in CLI or PMP, partial or whatever is actually doing some request called proxy can intercept so and regarding the desktop apps. What the? What kind of desktop application do? I mean I mean any kind of Association, so uh I mean kind if you can think of so.

L

The the main idea, I I'm, trying to the show present here- is that a gift here that actually that Microsoft graph developer proxy can help you improve the quality or test of your of of tests that the tester application of any kind of local uh up any kind of application. You are running locally, the doing that is doing any kind of request to any kind of API, not only Microsoft graph or Microsoft specific apis, and then then we can configure just Microsoft graph developer proxy to intercept this kind of call and provide a different response.

L

So you can see how your app can behave, which is quite awesome and for the sake of Simplicity I developed a really simple one view: WPS application with just three buttons: uh okay for uh to to show how we can improve the test and regarding tests, what do I actually means? What kind of test I want to improve uh um with this thought? Do I need do I like it when I'm meaning AR unit tests, integration tests?

L

Well, actually, no, because here in Newton's integration test, we are testing part of codes with code, so we can mock whatever. We are, we want not only response to any kind of request, but we can Mark any kind of response for any methods, but for sure Microsoft graph, developer proxy can help you with improving the quality of your manual or UI automated tests, which is a lot better and how well, let's think of a scenario how UI automated tests usually works. So we have like a local application like some kind of client.

L

We want to test okay, it's really cool. We, we start developing code that will run this application click it through and along the way it turns out. This application is using many kind of apis. It's good that there's.

L

Those, for example, are apis that we actually manage, so those are actually in our responsibility, so we can also set them up along the way as a part of this test or as a part of pipeline that will be running this test and any kind of a reasonable cloud or in some kind encapsulated Behavior, so we'll have also the resources that will be created directly for this client application for this UI automated test.

L

So this could be quite easy, but still in uh also, this imposes a big complexity and uh and some complexity in our UI automatic test scenario. We need to develop what about apis that are, we can consider external result sources that we don't manage. What about those? For example, yeah. We call the graph the Microsoft graph, so we cannot. We cannot like manage this because it's not our responsibility. So what what? If this fails- and it may happen from time to time?

L

Well, then we have to just uh consider that, from time to time in our pipeline, we we may see some uh fails. That will just be a successful rerun again and for sure this is some wasted time that a developer or a tester needs to check on the pipeline. Okay, why it fail? Is it actually our responsibility or was it a random error that can may happen from time to time? And what about smoking errors? Do we actually test error scenarios in UI automated tests?

L

Well, not so much because it's really hard to develop uh this kind of test. It also imposes a national complexity. Let's think of the let's wait. For example, we need to have some data and a database that is corrupt specifically for this run, and then our web API will be using this row and a specific kind of request to make it fail. So we can test a failed run, and this would we all needed to be developed as part of a setup script or a part of a pipeline that will be running before this UI.

L

Automated test will be taken care of so usually, as this imposes additional complexity or you go usually UI automated test test, the success of so when everything goes fine and with Microsoft developer proxy. We can improve each of this area. We actually would won't need any additional resources, except our client up and the developer proxy console running.

L

uh We can mock any kind of API, not only the one we manage, so we should get rid of the the errors in our pipelines and it will be just really easy to mock errors and I will show all of those in a really simple use case in a demo which is okay, which is now okay, so I have a really simple application in WPF with a couple of buttons and I will run it now um and actually my application just signing the user from uh cache start in local file, so I don't need to even if I have multi-factor authentication, Etc I don't need to do it now and I have two buttons.

L

The first one is calling the Microsoft graph to get me my information about my personal information and since it's an API that exists, it runs and successful and the other one is actually so. This is this one: it's actually running a custom API that I didn't develop, I forgot about it, so it will always fail, but still I can send the request and wait for for a response that is actually fine. Okay, that's quite cool, so I have a client application. I would like to test with the UI automated test.

L

So now, since I didn't develop this web API. For the second call, I would need to create this additional resource storage sum or keep it whatever with Microsoft developer proxy. We don't have to do it at all. Let me just start this tool.

L

For starters, it starts in a chaos mode, so it kind of listens on the URL defined and then upsetting so Json I will show you in a bit and will randomly produce a result. It can be either success or an error from one of the predefined errors. We also can Define in the up settings Json for every call we are actually listening to so now. If I would click on the call Microsoft graph API, we can see okay, it turned out it's a success.

L

Let me let me try again: okay, again I'm really lucky today, but Okay. The third time actually I got an error. uh Gateway timeout and, as you can see, it's an EOS kind of mode, so it means that it was randomly picked. An error. I I represent this error in the text box and also Microsoft graphs, as I told you gives you additional tips, how you can improve your code, but what about my second call with my custom: API. Okay, so I click this one.

L

This one still fails because the API is not still there and Microsoft graph developer proxy. That doesn't work. Yet it doesn't show me my API yeah, because it doesn't know it needs to listen for. Okay, maybe look for the request coming to this directory URL and we can configure it really easily.

L

So let me just turn this one off, and this is the upsetting station. This was part of the Microsoft graph developer proxy. You can configure the first thing. The big part are the plugins that we can just not present today, but you can get the feeling how it is developed at everything in Microsoft, developer proxy is a kind of a plug-in and extendable, and you can replace it with your own or attach a new one. But the important part I want to show us today is actually the URLs to watch I trimmed.

L

This only to look for currently for the Microsoft graph me endpoint, that's because a lot of things are not record, like also teams are using uh Microsoft graph, so I wanted to join this call without any additional problems.

L

That's why I framed this only to look at the specific URL that if you would just download the latest pre-lades 0.5 of the Microsoft developer proxy, you would have a more a bigger app settings Json with it's pre-configured, to look for any kind of call to Microsoft graph and SharePoint apis, which is quite cool because all of this work is done for you and what the only thing I need to add here is just tell Microsoft graph developer proxy to listen to my additional request, which is this one, which is the custom API endpoint get test.

L

That's all, let's save it, let's rerun and now, if I will click on my custom, a custom button to call my custom API, okay, it works, who have a success and it's prepared because the eBay is not there. But let's you click it again. Okay, it works. So you see, I got a chaos and an error. The Microsoft, craftable proxy is actually aware of my request to my custom API now and it's randomly producing errors to uh to my API that just doesn't exist. So this is quite cool.

L

It means we can test a client application without any additional resource, any additional web apis. We need to store on the cloud or in our local or run locally specifically for this test, or maybe even additional databases that are retrieving data. The wiki is retrieving data from those databases to give us the the response. Okay, but this is randomly producing error, how we can create a UI, automated test that that tests a random response- that's not not quite efficient, but it's quite easy right and Microsoft graph developer proxy. We have additional a bunch of parameters.

L

One of those is providing a mock file which I would presenting today. I have developed, uh developed, written a really short mock Json, which is producing uh the internal server error for both of those requests just for the sake of the Simplicity. But uh if you would dive deep in the documentation which I really recommend you, because the wiki is quite big and it's really awesome- you can see that the responses you can create specifically for each request. It can be either a success with a bunch of data or a specific kind of error.

L

You would like to to respond for for any kind of request, also your apis again. So, okay, let me run the Microsoft that will provocative with a small file. It already tells me that okay I have defined a mock for two URLs and now, if I will run either the Microsoft graph or call or my custom API call. I will always get the same response for in the scenario I actually written in the mog.json file, which is always the internal server error. So, okay, this is cool. I have a client up this.

L

Only the only thing I need Microsoft graph, developer proxy console application working in the background and, let's say currently, a really small one, but for a UI automated test in a big scenario, could we are quite big but a single Json file that will be producing the exact responses I want to test. For my up. That means that I can really easily test without any additional resources, except this Json file, success scenarios and error scenarios, which is great okay. So this is uh what I will actually do.

L

I developed a really simple UI, automated test it it's not the best practice. How a test should look like. Probably most of the steps here could be set up as a part of the pipeline, or it could be in a predefined setup step, but just for the sake of Simplicity I put everything in a single.

L

You know you're in a test UI automated test and as you can see, you don't need, even if even you have to be an owner of the app you want to like in you, don't need the source code of the app you are going to test. I just need the executable of the application. I want to start and then I want to start Microsoft graph developer proxy with a specific mock. Json I did I created specifically for this scenario.

L

One then I'm going to test, and this scenario is just clicking all the free buttons and it's looking if the response is actually an error. Okay, let's run it takes about like uh half an hour, so we're gonna, wait. I mean like 30 per second I hope unless crash so I'm, not touching the mouse. Now you have to just believe me, but you will see from the mouse movement that it's kind of like jumping from button to button, so I think it's impossible for me to do something like this with a touchpad.

L

uh Basically, in the background, we can see the developer proxy started and we already clicked on the first Microsoft drop button. Then now, on my second custom, API button and now the test, the UI Automotive test will close my app and that's the end. It's not it didn't close the proxy. Why? Because I didn't read it and written it in the test, only to show you what was actually done under beneath, but you can see that the test passed according to what I wanted to accept.

L

So, as you can see, the Microsoft graph developer proxy intercepted the calls and the UI automated test according to my scenario, and gave the responses I wanted it to do, and the UI automated test just passed without any additional apps resources work whatever just uh two apps and Json quite cool, then go back to the slides, yeah and I. I have a recap: slide yeah this time, I prepared. So what actually proven with this really simple test case I hope that it also motivated you to give it a try. I mean give it developer proxy.

L

A try is that, with this tool, you can improve your test, the UI automatic test quality and you can get rid of those failed running tests in the pipelines, because you can now even mock responses for the apis. You don't handle this can randomly fail. Now you can just always mock it. The way you want it to run, fail or success. Whatever so it's a really uh it's like saving you a lot of time, especially for the test team.

L

That would help to investigate each failing case and, as I said a bunch of times now it reduces the complexity for us developers When developing such a UI automatic tests.

L

We don't need to think about setting up an additional database additional web API for our only to test our small client application, and we don't need to do it in a pipeline or locally during the the test starts, which makes the, which is also saving us time and make me for sure happy as a developer and it's for sure saving a bit of money, especially if those were resources in the cloud we now don't need to keep so I guess the client will be also a bit happy, so it makes everybody happy just try it and I guess.

L

That's everything. I wanted to say I, hope, I, really motivated you to give Microsoft graph developer proxy a try and provide as much feedback as possible because it's still in the community uh preview, so feedback is really important, especially if you have some specific use space.

L

Like this one, you could you could integrate with the proxy or some other awesome ideas that could be introduced now, just from previous to pre-list and it's okay to to introduce any breaking changes, and also one thing was already mentioned on this demo call is that currently there is a huge hackathon event magnitude, but I mean it's really important and Microsoft a graph.net hackathon currently running. So if you haven't registered and you didn't participate yet, please do so because it's an awesome opportunity to learn how to use Microsoft graph and the.network.

L

Even if you are an expert, you can always earn something new and gain more experience in this area. For sure and I guess, that's pretty much I have to say I hope I was in Russian and I didn't take too much time. So I'll face my voice to you. David.

B

Awesome Adam very, very cool I, really appreciate that excellent job we'll have an opportunity to continue that conversation in a minute and we'll just close up here, but great great job. Thank you to both you and a new Adam and anoop for the uh for the double a uh demos of the day. We appreciate all that you're doing in the community. So thank you both now, you may be wondering hey I want to keep talking uh well, we have started Community calls conversations, so you can continue the conversations here with Adam and anoop.

B

We have dedicated space for you to do that. uh Don't hesitate to get involved. Here are some QR codes and some URLs. They are also in the chat for you. This is an opportunity for you to use the Power Platform power users forums to be able to continue those conversations. So we have dedicated spaces again using these QR codes or links. If you don't have an account, it is absolutely free to create one. We just want to make sure that the conversations and collaboration continues.

B

We know we don't want to use the chat after this call, uh because so many people are on it. We want to respect their area of teams, so use this space to take advantage of continuing that conversation, don't hesitate to get involved. Anup and Adam are both standing by all right. The recording will be available in 24 hours on the Microsoft 365 and Power Platform Community YouTube channel. You can access that at ak.ms. Community videos better yet subscribe today and you will be alerted exactly when those videos are dropped.

B

Don't try to download it in teams. It will just end up in sadness. Only Microsoft folks can do that, but definitely go to that link. Aka.Ms, slash, Community videos and subscribe also uh follow on Twitter at m365pnp or there's a LinkedIn group that you can join as well: AKA dot, Ms, slash, Community Li, the next M365 and Power Platform bi-weekly call two weeks from today: March 16th at 7 A.M next Viva connections and SharePoint framework next week same bat Time same bad Channel, March 9th at 7 00 a.m. You can access.

B

All of these calls at AK at Ms. Slash Community calls. Thank you, everyone for attending the wonderful collaboration conversations. You are all awesome and we are so thankful for all you're doing in the community have a great rest of the week and a wonderful weekend.

A