 All right, I think we're ready to begin now got the we're also live streaming over on Facebook So trying to hit a few different areas for the community to see this but thanks everybody for joining and this is another Microsoft user group Utah or Muggett webinar and We're it's great to have Ashley join us. So Just some background. I'll introduce her and we'll go we'll get things started and I'll stop talking but So the Microsoft user group Utah is an umbrella organization. There's about 12 User groups that are Microsoft focused in northern Utah where most people like 90 percent of people in Utah live and the umbrella organization is just a kind of a pairing of in this case the SharePoint or office trial 365 user group and the dynamics user groups that partner together With a number of topics But we meet Every month we have had of course in person user groups that we've kind of moved everything online But we try to do more and more of these online Webinars anybody is welcome to participate You can find all of our sessions out on meetup and at the end of this also share kind of what's coming up next We've got two activities next week alone but with that It's great to have Ashley join us and speak for those that don't know Ashley So she is part of Pate Group who I you know some of you might be familiar with You've got Stephanie Donahue and Mark Rackley that are part of that team That are really well known and Mark is the lead organizer for the North American Collaboration Summit So it's great to have Ashley join and share her experience here She's been developing and consulting in SharePoint for nine years now But has started shifting the last couple years towards the the power platform So power apps power automate and kind of everything under that so she's a senior SharePoint consultant and technical project lead and I'll just turn the rest of the time over to you Ashley and well actually I should say we're recording the slides Ashley's gonna share the links to her slides The recording will be up on YouTube later this afternoon as well as the live stream available through Facebook So with that I will turn that time over to Ashley Awesome, thank you so much and thank you for having me. I am super excited. I've been looking forward to this for a couple weeks now Super excited to start doing some things, you know online especially because even though the in-person thing can't happen right now It's great to connect with everybody And I love the fact that we can kind of do this and people who wouldn't necessarily be able to come to the you know Location of the user group they can actually participate now. So that's that's really cool I think it's a it's a silver lining here. So thank you so much for having me today We are going to be talking about Azure and power automate We are going to be talking about some use cases here for both of those things to get you up to speed ways to kind of take Some burdens you might be feeling running PowerShell and having to do that. We're gonna be automating some of that there We're gonna be doing that with Azure. So let's go into that All right, so Christian already did a great introduction for me So we can fly through this a little bit. But again, my name is Ashley Rogers I focus on SharePoint and power automate I also do a lot of blogging too. So if you want to follow my blog That's at sp in between that blog spot.com and you can follow me on Twitter at Ash Rogers I'm often putting new and interesting things out there on the blog and also tweeting things that I find So if you have something have a question go and find me. I'd love to talk about it Okay, so a little bit more about what we're gonna talk about today So we'll start off with why use Azure with power automate. What are we trying to actually accomplish here? We'll go pretty quickly into the Azure step the things that you need concretely the the things you have to set up in order to Run PowerShell using Azure from power automate. Some of this can be a little bit painful. We'll go quickly through it Don't worry about taking notes or writing everything down or remembering where everything is The slides that I will share they do actually have step-by-step Inside them so you can refer to those after the presentation We'll then go into some of the more fun stuff where we'll add modules and work on runbooks And then I'm going to show you a couple of real-world use cases in power automate And so that you can kind of get those juices flowing about thinking about ideas in your own environment How you could actually use this in actually just to interrupt quickly so if people do have questions us all be monitoring and kind of We're going to interrupt Ashley and ask throughout so feel free to Post it using either the chat. I'll be monitoring the chat But it was better over in the Q&A module and anything that we don't get to We're going to provide these to Ashley so she can follow up afterwards. Maybe a blog post or something Yeah, no, I'd be super exciting. Yeah, I love that. Um, definitely interrupt me. I love having the conversation So go for it Okay, so again, why are we really doing this? What is the point of bringing power automate into Azure and then using the Azure automation accounts? well, so if you Have you know read the the blurb here for what we're talking about today It's really about automating PowerShell tasks and putting those into Azure So if you are somebody who is setting up sites configuring teams Adding users. This is really, you know, share pointy administration stuff This kind of thing can get a little bit overwhelming, especially now with the push Towards virtual and having to set up teams for folks really quickly having to add users all over the place Tons of PowerShell things that I know that I do pretty much on a weekly basis to keep things to keep maintenance going and what we're trying to do is lift those tasks off of IT and a Allow for end users to get more involved So we want to make sure that you're not spending a whole bunch of time Doing the same thing over and over again kicking that off from your local machine and instead Building in a nice business process so that you can offload some of that from yourself We're also going to be using a tool that you might be familiar with which is power automate So I think that the Azure automation really brings together two different Tools that I say are in the tool belt of a SharePoint IT admin or developer and this is power automate and PowerShell We're really just merging those together And it's a great time to get involved in both of those if you're not familiar So if you're attending today and thinking well, I've not I haven't used either one of these This is totally, you know, I'm totally out of my depth or or something like that This is actually a great way to see what that business case is see what the actual use of that is Beyond disapprovals or creating items in power automate And the roles that I think really will benefit from this These are not going to be my folks who are heavy IT admins We're not talking about spinning up servers in Azure. We're not talking about resources in that case This is really for citizen developers or SharePoint admins and developers Who need to take their skills to the next level or who need to automate things that they're gosh They're just doing all the time all day. So really more for Makers citizen developers and then also my SharePoint folks Okay, so let's talk about some real use cases This came to me as a great example something I wanted to automate for a client My client was let's see. They were a construction company and they did not want to have to learn How to create teams and how to be IT admins themselves. They came to me and they said look We have you know, our IT process is in a third party We've got them to you know to set up the majority of users etc, etc But we need a way to manage our projects and create teams and I don't want to have to You know, I want to be able to push a button. I don't want to have to go in and understand where everything lives I don't want to sift through the admin center and kind of look at what that looks like to create a SharePoint site So the use case that really brought this to light for me was going from, you know being able to push a button and Talk about the project site that needed to be created and the associated team with that and then pop out on The other side with a team, you know and big T team and then a team site Related to that they wanted to be able to do this from SharePoint So we needed to figure out a way to automate all of that and just gather information from the users and then spit out All of the artifacts that they actually needed. So thinking about that really is where Azure automation came into play So you can do cool things like again creating teams creating sites Straight away from just gathering information and automating all of that in PowerShell You can also run site designs against specific sites. Is anything that you do in PowerShell really? You can pull this out and put it into a runbook in Azure I've also seen great cases where we need to audit sites for permissions hub associations different workflows things like that So instead of, you know, setting up an audit running a script that you're used to and waiting for it to complete and then Sifting through all of the information that comes back inside your PowerShell console What we're doing here is being able to stick that inside a runbook and then pull that information Parse it out using Power Automate and then maybe send that in a formatted email to the person who actually needs to see that So we're taking away the need to babysit PowerShell on your machine and then actually doing something interesting with that information That really frees up IT to do a lot more Remember, this is really about empowering your end users lifting off the bulk of the responsibility from IT IT just manages this and then really empowering the end users to get done what they need to get done So if they need to kick off an audit because hey, I need to know some more information Well, they can do that themselves if you've set it up properly. They don't have to ask you They don't have to wait for you to be available to do it And as I said before you're really only limited by what you can think to accomplish with a PowerShell script So really the possibilities are endless All right, so let's talk about some requirements here So my first requirement Is that you should use you should set this up as an Azure admin or as a global admin I really prefer the first time that somebody sets this up that they be in that global admin role Now there are some ways that you can work around this if maybe Your company is not going to grant you the the right level of access to set this up And you do need to work with somebody else in a different department to do that That's fine that you know, that's understandable And there's ways to to kind of give people the permissions that they need on a more granular granular level But overall you're going to have a much easier time We're not going to dive into how to do that So you're going to have a much easier time if you can have access to a global admin who can work with you Or if you yourself are a global admin You're going to need an Azure subscription and we'll walk through how to set that up It's really a five minute process super super simple But you will need an azure subscription and it is going to require a credit card The power automate premium license is also required here So this is because the azure connector is a premium connector And I like to get that out in front of everybody immediately So don't be deterred because a lot of this stuff can be um, you can have a trial basis of it So that you can show your folks at at your company What's possible? So usually that's a one to three month Trial subscription that you can extend and then you can it can show people what you're actually doing here But I want to get that out in front there that you do have some requirements on the licensing side Okay, so Let's jump right into walking through the azure subscription and resource setup again painful but necessary And we'll kind of go through it. So don't worry about taking notes here Okay So where you want to start from is portal dot azure dot com This is going to bring you to azure where you have a dashboard where you can pin things to this That you consistently use so as you come in and as you get familiar with portal dot azure dot com You can actually play with this and pin Different resources that you're frequently working with so after you've created for instance your azure your automation account You can pin that here so that you can go straight straight to it Well, so the first thing that we need to do is set up our azure subscription And azure makes this really really easy for us anything that I want to find I really can just go to the search here I'm just going to type in subscription And the first thing that comes up here is my subscriptions And you can see that I already have a pay as you go subscription So when I walk you through this we're going to talk about where to set this up But really we're going to be leveraging what I already have set up So in order to add one just going to click add And then you just want to well Of course log in And so as this brings this up you're going to follow the prompts in here in order to set up your Subscription So this is going to ask you for a credit card number. It is going to ask you For information about who to call or who to bill But when you pick the pay as you go It's actually pretty simple You don't have to pay for any support off the bat and pay as you go Just means that you only pay for the resources that you actually use And I have to tell you that even having set this up and doing this demo a few times And even having this running in my tenant. I haven't paid for anything. It's it's very very very cheap And you really um, there's really nothing that you'd be on the hook for that would be incredibly expensive So as you walk through this it will ask you for payment information Ask you to verify things and it'll set you up with a pay as you go subscription So once you're all set with that You're going to see here What role you have so the fact that you're an admin on the account If you need to add additional admins, you can add them to the subscription that you set up Please know that unless you add another user Other users are not going to be able to leverage the the subscription that you create So if you want to create a subscription for just yourself or just your department That's something that you need to take into account when you add different folks with different roles But just know that you know, if you in marketing set this up Then hr is not going to be able to see this unless you add People from that department to the subscription Okay, so after we have our subscription set up, we're going to go to resource groups and we're going to create a new group This is pretty straightforward. We just go ahead and click add And this is going to ask you to put in the subscription So we add our our pay as you go subscription here And then we're just going to go ahead and name the resource group and we'll just call this test group utah Okay, and then we just um put in the region where this where you want this to run So after that we just do review and create Create again And once this goes through we're going to get a little notification here that your resource group is created Sometimes it will take a little bit longer depending on what's going on in the backend if you have a lot of other things going on But by and large it's pretty fast when you create different things inside of azure But you'll get all these nice notifications as you're going through and setting up So if you have to come back to this because you're waiting for something or you've gotten distracted by something else You can just go to the little bell here And then find all of the different things that you've been waiting on and you can go directly to them straight from the notifications I find that to be super super helpful Especially the first time you're in the portal to azure.com because it's easy to get lost with all of the things That are new to look at So after we've created our resource group. So we've got our subscription and our resource group We're going to start going into some of the more fun stuff Which is actually creating the azure automation account and then adding the modules and credentials so Just like with everything else We can go ahead and type in automation to start looking for a place to create our automation account So we just go under automation accounts here And you can see that I already have one set up. It's the arts automation account And you can see that what resource group it's using and where it's located and which subscription it's under So if you have multiple of these accounts running, it's pretty easy in the dashboard to identify which one you want to use Or which one you need to manage To create a new one we just click add And you'll go ahead and name it use the subscription. Of course use the resource group And then pick a location Now the reason I really wanted to show you guys This creation here is that you want to make sure you're selecting Yes under the create azure run as account if you click no, you really won't be able to do anything with this So make sure that that's flagged as yes before you go ahead and create it Okay, so back inside my automation accounts. We're going to use the one that I already have set up And I'm just going to open it up by clicking and you'll see that it extends out And you can see all of the different things that are available to you As I said before if you're in here for the first time it can be slightly overwhelming There's a lot in here that maybe you don't need right away if you're just trying to accomplish Working with power shell from power automate And so the search box here the secondary search box not the one up top but the secondary one This one will help you find pretty quickly the things that you need to add So with our accounts the first thing I want to do is add modules So I'm going to type in modules And you can think of this if you've worked with power shell before you can think of this as installing modules inside of power shell when you bring up that console on your On your local desktop or your laptop and you want to go ahead and do the install and maybe you're installing pnp Or something to that effect. Um, this is basically that so you have two different selections here You can look at what's already installed against your Automation account or you can look at the gallery in order to add things. So let's quickly look at the gallery And again great search box great search experience. So I'm going to type in teams click enter And here's the module for microsoft teams commandlets. So if you recall when I was talking about my um Original use case to create a team sort of automatically From information I was gathering from the users This is one of the things that's required and that's to have the teams module installed against the automation account So you want to come in here and find the things that you're trying to do, you know You want the teams module you want share point? If we can type in share point And you can see that even the pnp power shell commandlets are available to you Which is great. So all of this really puts the power into your hands inside of azure And it's very familiar to you if you've already been using power shell On the local console All right, so let's go ahead and go back. I already have the modules installed here That I want to use you can see that I've got teams installed So we'll go back And the next thing I want to do after adding my modules is adding my credentials There's a couple of gotchas here. So we'll type in credentials and we'll take a peek at it Okay So when you add a credential in here Whatever this is named. So this is arts admin That's the name of the credential that you're actually going to use inside your runbook So so think about when we go to the end here and we actually create a runbook And we're actually running power shell after all of this has gotten set up You're going to need to make a reference to the credentials So this name here that whatever it is that you that you actually name this that's what you're going to be using That is separate from the name of the azure automation account It is also separate from the user that provides the credentials themselves So if we take a peek at this I'm using my global admin account And my password in here as the arts admin Credential inside the automation account I suggest if you're doing this and setting this up in production That you go ahead and use a service account. So create a user that Is not related to a person. This is something that will never expire And that you know, basically who whomever comes along afterwards can inherit responsibility for this You don't actually want this to be so and so user because When that person leaves if that person leaves Then when that account gets turned off all of those permissions anything that was running under that person's credentials That goes away and there's going to be a problem. You'll have to fix it So I would go ahead and use a service account if this is something that you're setting up inside production So after you go ahead and add the credential you add the username and the password and save that You're basically set up at this point. So Reviewing we've got a subscription. We've got a resource group. We've got our automation account We've added the proper modules that we need to use and we've also added the proper credentials inside there So now We can actually go ahead and take a peek at runbooks So inside the automation account. It's nice that everything's sort of in here in the last few pieces It's it's nice to not have to go back and forth a bit here if we click into runbooks You can see the runbooks that I've already got set up a couple of them come As built in because these are tutorials for you So if you have something that you want to come in and learn about These are already available But I have these three that I've created and we can see that they're power shell runbooks So I'm just going to go through how to create a new one first And then we'll take a peek at something that I'm doing inside of here In order to show you what this will be when I connect it to the power automate flow that I'm actually going to be running So let's go ahead and click create a runbook We'll just call it utah runbook And then the type we're going to pick power shell. I have not played with anything else in here I've only I only stick to power shell, you know, I'm not a python person So all I do inside here is is run power shell Go ahead and click create and you get your limit notifications again up here that the new runbook was created And in here you get Basically a blank id. This is a really lightweight place to start developing your script oftentimes what I do is I take a script that I've been testing and running locally and then I plop it in here and start testing against that I don't typically develop inside here, but if you're used to visual studio code Or any other id you kind of understand that what you're doing is placing your code here And then you can go ahead and test you can publish this everything happens right inside this panel here So go ahead and close this And I'm going to use the breadcrumbs up here I want to point this out to you that if you ever get lost you can use the breadcrumbs up here to get back where you need to be So i'm going to hit the runbooks here. We're going to go in and look at get spo hub sites All right, so this is one. I've already been using there's a lot of information here. You can see activity logs You can see the jobs and anything anytime you've scheduled this So basically you can manage your power shell scripts right here And it's pretty nice if you feel like you you haven't got an error Something didn't happen you come in and you can actually look and you can start debugging straight away Inside the runbook. So let's click at it And take a peek at what's inside So this is super simple I've got this setup so that um, I can log in So I've got my login here. I'm providing a credential, which is the arts admin name. So I'm providing this command let get automation ps credential providing the actual name And then we're connecting up to power. Sorry. We're connecting up to share point. So if you're used to Running the connect spo service from the power shell console This is going to look super familiar The only difference being that you're actually providing that automation power shell credential and you need to do this in this pattern Because at the time at the actual runtime when this is actually running This is not something that you're expecting the end user to log in and to actually provide So what you want to do is is abstract The login process and actually running anything having to do with power shell away from the user Especially if what you're doing is setting up a business process for somebody to use To have that magic push a button and get information back kind of experience So after we connect up I'm just getting my spo hub site. This commandlet will go ahead and give me all of the hub sites inside my tenant And i'm throwing that into an output here, which is my variable that I want to convert to json I want to write the output as json because I want to pass this in nicely To power automate in a way that power automate will understand what i'm giving back to it So if you can picture down the line passing over some information to power automate If I if I provided as json, I'm going to be able to use the parse json action In the rest of my flow to do something cool with the information that comes back Of course at the end here. I want to make sure I disconnect from the service So this is pretty simple. All we're doing right now is getting all the hub sites and then doing something cool with that information Okay, so At this point we have set up everything we needed to do inside of azure It can feel like a bit of a fire hose. It can feel a bit painful with the setup But now that we have a run book that we can actually execute we can hop into power automate Okay, so in here inside power automate if you have not seen this before I highly recommend at least being able You know going out and playing with it Seeing what you can do creating a few small lightweight flows for yourself What we've done here is just created a couple of different flows They fall inside the my flows tab If you again are new to this and you share a flow with somebody It's going to disappear from your my flows tab and it's going to appear inside the team flows tab So don't worry if you feel like you've lost a flow that you are working on Just go ahead and check the team flows tab because that's probably where it's going to be So let's jump into our run azure job flow here And again, if you're new to this Um, this is a great dashboard to look at as far as managing the flow and seeing what um has happened with it recently How often it's run again if somebody Uh expected something to happen and it didn't this is a great place to start even before you go into Azure and you take a peek at the run book and whether or not there's been issues with that Sometimes the hang up is as simple as an issue inside of an actual flow So let's go ahead and edit this and take a peek at what's inside I always notice that this goes slower whenever I have to show anybody Uh, so all right, so we have a flow here that is manually triggered This would not necessarily be the case in production if you guys are setting this up as a business process Um, what I do is I set this up for when I do demos because then we can test it straight away from here If for instance, you want to set up a process where somebody is going to be able to hit a button on mobile Um for power automate and then have something happen That's a great use case as well. And that is a time when you would actually use the manual trigger here But for our cases, this is basically just a test. We're demonstrating the run book that we were just looking at So I don't have any inputs to this particular run book. I'm just doing a manual trigger And I'm using the create job action. This is an azure action So I've renamed this to indicate what it is that I'm doing since create job get spo hub sites to indicate exactly what's happening And when you use the create job action for azure, you're going to need to supply the different information that we just set up here So we're going to supply the name of the subscription the resource group the actual account And the run book name So you can see that every step of the way everything that we set up is important to make sure To make sure that you actually have that set up You're actually using the right one because if you don't have access to one Then you're not going to be able to run that So we want to make sure that you note everything as you go and you can see that it's still pulsed through It's all necessary information to have set up even when we're here on the power automate side So I've got this all set up And of course we want to know do we wait for the job? So I typically always wait for the job to finish because I want to do something with the information that's coming back There may be cases where you can set this to know because maybe this is a branch That you're that you're running off to the side and you don't need subsequent actions to wait for that job to complete But in situations like this where we need the output of the run book Then I always do wait for job. Yes So this create job runs the run book guess get spo hub sites And then I have another action here which gets the output of that job now what that is here Is it's pulling this output here the convert to json? So I'm coming in and I'm saying please give me back the information that actually comes from this job So again supplying subscription resource group and account and then all it takes is the job id So if we come in here, I'm just going to click out of this and show you that You just pull the job id from the previous action So we go ahead and grab this and it's from the get spo hub sites And that's all you have to provide power automate basically does it for you And then after we get the output, we're going to parse that this content is coming from this action here And we have a schema inside here So if you have used this before parse json is probably in your tool belt It's probably something you're very familiar with if you have not Just know that when you're running this you're going to need to generate a schema from the output of that job And you can do that by testing this just with these three First steps here So you can get the output you can pull out the body and generate from that sample a schema that you can use in your parse json action All right. So after we've done that I'm just doing something super simple to hold Each URL of the hub sites that I know are going to come back So I initialize a variable and then inside this apply to each loop. I'm just setting this Variable here as the site URL that's coming back from parse json So let's go ahead and run this and then see what happens And we're going to hope that the demo gods are with us today All right. So you can see that it's waiting for this job here So get spo hub sites is running And it can take some time especially if there's something else running inside of azure if you have a very active Portal where there's other jobs that are waiting that are getting queued up They're going to get queued and then this is going to run The next the next time it has available resources to do that. So we're going to cross our fingers. That doesn't take too too long Otherwise we can otherwise we're going to be looking at a previous run Hey, actually got one question here jr asked Do you have any naming convention guidance for the azure resources to keep them organized and unique? objects like resource group counts and runbooks Yeah, so for sure if you have different regions, I would include the regions inside those names If you have different offices, so maybe if your it is spread across different offices. I also do it that way But by and large as long as the naming convention that you pick makes sense to you and you stick with it That's probably the biggest piece of advice I have All right, so we can see that Now this was successful. So thumbs up. This is really great. So let's take a peek at what comes back from these So we see that the job here ran and that we can see here that we've got the job ID That's what we're referencing below And then we also have a lot more information about when it Ran and when you know, so start and end time and things like that great for debugging if you're trying to figure out when something is happening We also have in the job output. This is what I was referring to as far as the content that you would pull to Generate that schema for your parse json. This is what's being provided back to us from PowerShell So from that runbook and we're formatting it as json so that we can easily pull out this information It makes it much cleaner and neater to look at other than just the regular output that comes back from PowerShell scripts So then we're just parsing out the information here And then initializing our variable And then in our apply to each i'm going to expect two because I know I have two hub sites in this And so we've got one so this is the arts team site that I know is a hub and then also My root site, which is the hub so we've gotten back information here And you can see that the next steps that you could take with this is Maybe I want to email this to somebody. Maybe I want to put it inside a SharePoint list Any number of things that you could do with this information same as if you were pulling it from SharePoint Okay, so I've got one more Use case to show you guys moving over into SharePoint Reminder that if you guys have any questions at any point, please go ahead and ask them. Definitely happy to answer And otherwise we're going to pop over into SharePoint and talk about A much larger kind of business use case for this and kind of get those Juices flowing as far as what you think you could do with it Okay So What I've got here is my Northwind Traders SharePoint site. This is actually my root site It is a hub and I have a team approvals list inside here So I'm just pulling some very simple information. You could think that If you had more of a process around approving That a new team, you know being built out So maybe what you want to do is make sure that people follow a process to To request a new team inside of teams Especially with everybody moving to virtual that this might be a great way to gather some of that information So you could provide a rationale as to why it needs to be stood up, you know, what is the related project? What's the related department? You could collect all of that information in order to submit it for an approval But in this case, I just have super simple information I've got a team name and then I've got an owner And that's a great those are two things that you absolutely need to Ask for so if we're going to go ahead and approve this and create a team off of that We need to know what the team name should be and then we also need to know who the default owner Needs to be if you want to get really fancy you can also ask for default members And then you can add those as well using the teams power shell modules So let's pop over into power automate and take a look at create team from share point Okay So you could set this up in a couple of different ways the trigger here is for a selected item So what this is requiring someone to do is to select the item here and then use the automate drop down to then send this into flow But what we are doing so that's what we're doing here. What you could do is with You know immediately as soon as it is Added as soon as the item is added you could do that and then you could also do a manually triggered flow if you wanted to You could also do a schedule if you wanted to look for new requests on a schedule Whatever it is that works for you So we're just doing the standard select item and then get item and this is getting the information Specifically that is being passed in for that particular item. We're not pulling back everything from the list. It's just one item And then we have a start and wait for approval step here So what this is doing is allowing us to send this off to it for instance If we have users who are requesting the creation of a new team And we pass this over to whomever needs to approve it in it Maybe it then needs to get routed to a department head Whatever it is that the governance situation is for you And then we can provide details from the from the share point item inside the details field So anything that you've collected from the team name to the rationale All of that good stuff can go in here into the start and wait for approval and in here We can also provide a link to the item So we're just sticking the approval in here And then of course if approved we've got our outcome if the outcome is equal to approve Then we go ahead and follow our pattern from before to create a job and to get the job output So the only difference here when you want to create a team Is that you're actually going to have You're going to have to provide To your runbook those parameters. So you're going to be providing a team name You're going to be providing an owner things like that And in order to do that Let's pop back over to our runbooks and just take a peek at this So we'll go to the create new team runbook and edit Okay, and then I just have this setup just as you would any other power shell script So I'm defining my parameters my team name and team owner And then I can also provide an alias So if you want the alias, uh, you want the name of the team to be in the url You don't want that to be generated automatically. You can provide an alias there Um, and then we have our same pieces here to get the credentials To connect up and get that arts admin credential there to log in And then we're doing a new team We're providing that display name and the owner and then you also need to set the visibility public or private So that's something else you can also add as a parameter if you felt that was necessary By default I have mine set to public And then of course we're writing the output into json and then disconnecting from the team's module here All right, um, so I I'm not going to go ahead and show you guys how that's actually working So full disclosure. I don't have this one working in this environment Um, so there's a few more pieces. I need to straighten out in order to do that So i'm not going to show you guys this actually doing it So you've seen sort of the behind the scenes in this environment how you'd set it up But what I wanted to show you really was just the possibility here was that you can create A process such that the users can request something you can have an approval And then you can go ahead and automatically run bits that you would Have to sit and babysit or maybe that you don't want to have to do As far as waiting for all of that to be done. So in any case That is it. Let's go back over to the slides. Hey, actually one quick question that came in Is there any way we can avoid exposing username and password in azure runbook? Oh, yeah, absolutely. So here if we go back over to the runbook So the I'm glad you said that I'm glad somebody asked that because we're actually not We're actually not exposing the the actual credentials inside the runbook What we have is this name here which acts as an alias So we can go back and look at their credential in a second But this name is just the alias for the credentials And what's happening is azure is actually passing in the credentials themselves And we're not this is this is almost meaningless as far as if someone were able to look at the runbook They're not Seeing my actual username and password I hope that helps Let's go back over here. Let's go to credential Another quick question JR asked whether you know of any high quality resources that provide example run book runbooks So like names of authors specific blogs github repositories and and the like Yeah, so I actually don't know off the top of my head folks that have these as Actual examples that are available Typically when I do these it's a use case that I already have and I sort of work at creating that myself But I love to know that that's actually a need because I would love to fulfill that name. Maybe that's something that I can do for you guys I don't have anything in particular who you know people who have those repositories But if you do find them Definitely, let's let me know tweet them at me or send me a message Okay, so other questions. I saw a couple over there in the q&a Nope got those answered and there is by the way over in doc stop microsoft There is a runbook and module galleries for azure automation and they've got some samples that are down below that There's not a ton but there are some examples that are out there That's awesome. There you go. Good to know. I'll post the link here in the chat Dude, that's awesome. Great. Um, okay awesome So if you guys have any follow-up questions, um, you can find me on twitter. You can also find me on linkedin I'm always happy to engage with folks in the community I will provide the step-by-steps that are in the slides that we didn't really look at but that are in the slides I'll provide the slides after I'll make sure that christian has a copy there as well a link to the slideshare And if you guys, you know, need anything else just reach out. Thank you so much Yes, thanks so much actually and just seeing if there's a you'll get a couple more minutes in case anybody does have questions Any other questions while we have ashley's time And I am also pulling up. Uh, let me do this So we'll we've got her contact information. Please connect with her follower on twitter And let me share my last just the screen Yeah Steal this connection away from you since I there we there we go And for those that are joining just uh, that are not yet signed up and following us out on meetup So the microsoft user group utah you can search on that attractive Hashtag mugget And you'll find this out there some of the things that we have coming up If you're not aware, uh, every monday, we're doing this twice a day on mondays to try and hit The major regions we have an early morning pacific In an evening so that we're hitting both amia as well as asia pacific And so it's at um, you see my mountain time here. I'm an hour ahead of seattle But we we promoted as 8 a.m. And 6 p.m pacific These are open office hours. So a bunch of us Mostly mbps and we're just on there answering questions and when we don't have questions we sit around and chat with each other But also coming up on the 28th So i'll actually be presenting and since we're all in a virtual world i'm going to be presenting on microsoft 365 the end-to-end task management strategy and Taking a a little bit longer time and doing some demos and showing you some of the integrations that are happening around Tasks if you're interested in seeing that and then on the 29th, we have another mvp webinar Joel Lindstrom who is a 12 time business apps mvp is going to be talking about Why you should use the common data service? So you definitely want to uh, if you like this topic, this is a great Kind of follow-up but just another important topic for those that are coming up to speed on all of the power platform capabilities and with that And and uh, and somebody asked again where the video will be so this will be posted out the recording out on youtube It'll be there by end of day if you go out to youtube and search search for a collab talk You'll find it up on that page and i'll share the links out through the social And uh, as well as a link to the slides the students. Ashley sends me that url. So thanks a lot. Ashley and thanks everybody for joining