Microsoft 365 Community Microsoft Graph, 10 Jan 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Introduction Microsoft Graph PowerShell v2 preview release

Description

In this 14-minute developer focused demo, Maisa Rissi and Peter Ombwa review features/improvements from v1 to v2 modules. Understand scripting for and how endpoints are targeted by modules, improvements to and support for more auth scenarios (managed identity support), and other improvements. In Azure Cloud Shell, appreciate the ease of installing a module, authentication, getting users, grouping users and deleting users/groups. Uses new managed identity to make calls without certificates and secrets. Supports 2 types of managed identities – system assigned and user assigned. Feedback welcome.

This PnP Community demo is taken from the weekly Microsoft 365 Platform Community call recorded on January 10, 2023.

📺 Demo Presenters
• Maisa Rissi (Microsoft) | @maisarissi_msft
• Peter Ombwa (Microsoft)

Supporting materials
• Article - Microsoft Graph PowerShell v2 is now in public preview, half the size and speeds up automation | aka.ms/graph/preview-psv2
• Documentation - Microsoft Graph PowerShell V2 Changelog and Upgrade Guide | aka.ms/graph/sdk/powershell/upgrade-to-v2
• Feedback/Issues - msgraph-sdk-powershell/issues | https://github.com/microsoftgraph/msgraph-sdk-powershell/issues/new
• Discussion - Is it a good idea to have different cmdlet names in the V2 SDK? #1705 | https://github.com/microsoftgraph/msgraph-sdk-powershell/discussions/1705

Learn more
• 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 - http://aka.ms/m365/community

👋 Join to our weekly Microsoft 365 & Power Platform Community calls to learn more. These are PUBLIC calls for you to get access on the latest details from Microsoft and to see awesome demos from community on these technologies - Download recurrent invites from https://aka.ms/community/calls

A

Foreign for those who may not know me I'm, isahisi, I'm, a product manager in the Microsoft graph, developer, experience, team and I am responsible for some of our sdks and Powershell it's one of those.

A

So we are here to talk a little bit about the new preview of Powershell V2. We have a few chains, we did so here it's pretty much what have changed it um between V1 and V2 versions. So pretty much now we have dedicated V1 and beta modules.

A

uh What that means, I will show you in the next slide, but pretty much. We have two different modules now one microsoft.graph that is targeting view, one endpoint and now microsoft.graph dot beta module, that's targeting beta uh endpoint. This is something that we thought uh as a really good Improvement, because today, like it's pretty much easy to.

A

Like use V1 and beta command, let's see in the same script and when you are like scrolling down the script today, we need to change the profile when we are targeting V1 or beta, and because of that, it's easy to miss that you are changing profiles, and maybe you are not relying as much as possible in view one as you should, because, as we know, beta endpoint sometimes can introduce Breaking Chains.

A

So we decided to split the SDK into two so to be less error prone and less ambiguous scripts, because now we have the beta prefix in all beta commandlets. The other change is that we are supporting more of scenarios, so we are now putting manage identity, client, secret ratios and environment variables, so managing identity, as some of you may know, like it's a common challenge when writing and automating uh the things you need. It's a common challenge to manage the secrets, credentials and all of that and like have everything you need secure.

A

So now we are eliminating the need to manage your credentials by yourself by using the manage identity, because now Azure resources, um we can get access tokens from Azure resources that are protected by Azure active directory, so more secure out thin areas same for client secret credentials because, like if you need um interactions in the background, you don't have an user to sign in. You can use the client secret credentials and uh for those who may need um to use environment variables or you need- or you want to.

A

You can now set your variables, pointing the client, ID the tenant ID and ask Powershell SDK to use these environment variables to authenticate against graph. Another Improvement about Alf is for the certificates because we do now support certificate authentication, but before V2, so in V1 we only were looking at the machine certificate store. But now we included the current user certificate store, so both are being looked by the V2 version, and if we have like the same certificating, both current user and the local machine, we are going to use the current user.

A

One and the other chains are HTTP 2 support when the API supports http 2., and we added also the success range code, support So. Now everything that it's 200, something we are going to be able to get this. Even though the API is saying, for example, the response will be a 202, but actually they are also respond. They are also responding with like 201 200. That's not a niche anymore, because, like now, we supported the success range code.

A

Support So 200, like 2x, um called, um are being fully supported by the SDK, and we no longer have issues with that.

A

So just you simplify what I told about different modules, so in V1 for you to use V1 and beta in the same commandlet, you would need to change your profile, so the selected profile to V1 to use what was, if you want and for beta for the things that are in beta and now in V2. We have the beta uh prefix. So, as you can see in the V2 code snippet here we have the get mg Beta Drive activity, so this beta word was included as part of the beta module.

A

So for those who are using only if you want endpoints nothing had changed, your script should be working just fine. You probably don't need to change anything for those who are relying on beta either, because the functionality you need is not exposed in view one or you need or you're trying something new some preview apis. You just need to go and just add this little word beta after mg, and you should be fine.

A

uh The New Wealth scenarios here are the Snippets just for you to have a quick review so manage identity. We have now a dash identity parameter here for environment variables. As you can see here we are using environment variables to say the client ID, the tenant, ID, the client secret and the third one is the client secret one. As you can see, Dash client secret, the initials parameter are now one of the ways you can authenticate against graph.

A

So now, I'm going to hand it over to Peter who's, going to do a quick Dem for us just to show you how it's working, the bar shell um preview, V2.

B

All right thanks, maiza um cool, so uh for this demo, I'll show you how you can use the module in uh Azure Cloud, shell using managed identity. Let me share my screen here.

B

uh So the first thing: when using manage identity, uh we support essentially two kinds of identities we have a system assigned and user sign, so system assigned will automatically use the manage identity of that service instance that you're running on in Azure, so like in this case I'm using Cloud shell Cloud, shell ships with its own identity. So in V2, all you need to do is um in your cultural environment. Just run, install module, Microsoft graph, allow pre-release, so it'll be something like this, and this will install the preview version of V1.

B

If you wanted to install beta, you could also just do here, dot beta and that should install it. The cool thing with our Azure Cloud shell is that everything is persistent. So, even if you, you know close your browser and open it again, the module will be installed so to use the system assigned identity, I'll just call connect mgraph.identity, and that will pick the access token from that environment and just like that, I've logged in and in this case, I'm using up only permissions. So there are some default permissions like the identity has.

B

So the next thing is you know: I can just use the module as usual, so like in my next sample, and essentially just you know, filter uh users in my tenant with our city specified as Redbank. So in this case, I'll get like a collection back of Redmond best users who have their City specified as red one.

B

um Then the next thing that I'll do I'll create a group M65 group for these users, um so in this case I'm just specifying the display name using the new MJ group command as a Redmond best uses uh description, mail, nickname group type and I'll say that this group is mainly enabled and they are outside security available to us, um run it, and just like that, I have a dedicated um Redmond group.

B

Here that's been created, so what I'll do next is I'll iterate through those Redmond based users and add them to this Redmond group that I created to do that. I'll just use the new group member command that ships to the SDK.

B

There we go so in this case I'll just look through the users called the new mg group member I'll, specifying the group ID as that group that I just created up there and then the directory object. Id is the ID of those users who I want to add now why it's a directory object here. It's because a member of a user is uh any type of that derives from a directory object.

B

So you know that can be a user, a group and other different types, um so I'll just look through and just like that we've added users to our groups, uh so I can confirm this by calling the um get MGA group member uh by specifying the group ideas that Redmond group that I just created and just like that I can see that all the IDS that I added uh available as members of this group, so once I'm done with my group and I, can add other.

B

You know settings for this group Etc and you can even convert the group to a team and do a lot more sophisticated work from uh using the module. But in this case I just want to keep it simple. Some double back group: what I'll do next is just go and delete it and uh one cool thing.

B

You can also call the module with the dash debug to see what's happening and just like that, we can see that we sent a request to flash URL and those were the headers, and that was the response that we got back and uh the group has been deleted yeah. So this just shows you how you can use, for instance, that new managed identity as an auth option that we just added for you to essentially make up only calls without worrying about certificate secrets, and you know, um certificate rotations and those kind of stuff.

B

um Together with this there's a whole lot more improvements that we've made you can find those in our um migration guide here. So we talk about like you know. What are the new uh features and improvements that we've added, how you can use them when providing Snippets uh as to how they can be used? Etc so I'd urge you to just go to this after guide and uh see what's new play with them and give us feedback.

A

And and just to add, on top of what Peter was saying, uh we are looking for feedback, so please feel free to raise issues or to go to the discussion topic. We have in the Powershell GitHub repo uh that we are discussing pretty much, why we separate the SDK and why we opt per per different command left names. So please go put your input there. We want to hear from you.

A

What do you think and uh we pretty much want to also tell you and let you know that we are working in a migration too, to help you migrate, your scripts from V1 to V2, so this will be available with the ga version. So it's a streaming progress, but uh this is also something that we are working on and also uh want support.

A

um So that's uh what's coming next! That's all! Thank you. Everyone, cool.

C

Excellent, thank you Micah. Thank you. Peter really awesome stuff and good to see the the Improvement as well absolutely brilliant.