Streamline Your Sales Automation Services for Teams

How to create outlook signature

okay hi good morning and good afternoon everyone my name is vasu sharma and i'd like to welcome you to today's session on voices of healthcare cloud versions of healthcare cloud is a webinar series that myself and my two colleagues shelly and josh have put together with the sole purpose of finding use cases relevant to the healthcare industry that you can solve for using teams office 365 and the connected microsoft cloud um today we're going to have a very special presentation by one of our architects and i'll let him introduce himself here shortly his name is andrew and he will talk about how to do automated role based scheduling using ships now before we start a few housekeeping items we do highly encourage you all to ask questions so go ahead and use the q a panel on the right hand side and i'll show you where that lives all questions are moderated so unless we decide to publish those questions they may not show for everybody else this webinar is going to be recorded so you don't have to worry about you know um missing out on something you can get the recording on this link aka dot ms slash hls blog um essentially on the original blog post that had the invitation in the first place um very quickly i'll walk you through how to engage with the q a panel you'll see in the top right of your screen this little question mark icon so you can click on it and that will let you into this type of screen where you can ask your question either anonymously or with your name attached so feel free to leverage the space as we work through the presentation i'm going to turn it over to andrew here um andrew take it away maybe do a quick intro and then let's dive right yeah great thank you vasu um let me know when you can see my screen yep all right well good morning everybody my name is andrew roger i worked as a technical architect out of the seattle microsoft technology center where we aim to help empower our customers digital transformation through deep technical engagements i'm excited to be here uh today with you all to talk about automated role-based scheduling in teams but i know that the topic of automated role-based scheduling might be something that is unclear to everyone on the call or maybe just the definition of what automated role-based scheduling might not be super well defined in everybody's head but the goal of today's session is to discuss what this is and also how you can achieve it inside of teams with the help of a few other different technologies so we'll also take a look at shifts for teams as well as power automate so that's kind of the goal of the day with that i can get into the agenda for our session so we'll start with an overview of shifts for teams and power automate these two technologies that will help us enable this on this role based scheduling inside of teams that should take about 10 to 15 minutes i think it's really important that before we just jump into a use case or a demonstration that we discuss the kind of technologies that we're going to be showing so that everyone's has a clear understanding of kind of what they are and how they work after that overview we'll switch into a use case discussion so we'll spend about five or so minutes talking about a particular use case where we can set up this automated role based scheduling and that use case is all going to be all around a cova vaccination clinic and how we can manage the scheduling of volunteers within that covert vaccination clinic and then we'll move into a demonstration that should take about 15 to 20 minutes and we'll wrap up with a q a but i highly encourage you throughout the session as questions come up you know submit those to the q a as fastu shared and he can you know he'll share those with me as we go through so you don't have to wait until the end to ask your questions okay so let's get into the overview of shifts for teams and so shifts in teams is a first party teams application that allows you to completely digitize the shift management and time tracking processes right from within teams we can start by maybe talking about some challenges that are associated with these more traditional scheduling processes and a lot of these traditional scheduling processes can be outdated and these processes might include you know creating a physical schedule and then distribute a paper-based schedule and distributing that to different physical locations or maybe creating a schedule and distributing it via email and these outdated processes can lead to really cumbersome methods for managers and frontline workers employees to have to go in and update the schedules so if i create a schedule send it out an email and i need to go back and update it that involves a lot of emails back and forth between a manager and their team there's also some time clock and clocking in clocking out related functionality inside of shifts for teams that can help address inconsistency caused by these manual processes but we're going to be focusing more on the shift management side of shifts and less on the time clock functionality inside of shifts for teams and so shifts for teams can help address these challenges in a few different ways first it again completely digitizes the shift management process so a manager can go into teams and put together a schedule for their team from any device that has access to teams and then share this out with all members of their team and then manage it centrally in one location next it can help empower frontline workers to really own their own schedules and so there's a lot of self-service tools that have been built into shifts for teams to make the experience uh better for these frontline workers accessing their schedules and we'll talk more on those functionalities let's dive a little bit deeper into shifts for teams now each schedule that you create in shifts is always based around a specific team so for a given team in microsoft teams you can easily create a shifts schedule from scratch or if you have an existing schedule in excel you can import that into ships now you can see this kind of image of what a shift schedule looks like on the right side of your screen so you can see the shifts in the middle and then the members of the actual group or team here on the left side of the screen once you've created your schedule we can create groups within a given schedule and so you can use these groups to track shifts for a particular job function or even maybe a particular location and keep these groups organized so each group gets to have its own unique schedule within the team so you can see that this is the schedule for the contoso east team and there's a group here for cashiers and this cashier's group gets its own unique schedule and we could create different groups to track different kind of schedules for other job functions or maybe cashiers at a different location once you have your team and you have these different groups you can easily go in and create shifts and you can create shifts manually or you can copy and paste from existing ships so if you want to create a template for a specific day and then copy and paste that out over a week or even a month you can do that through the ui one other concept that i want to cover is the concept of open shifts so it might be a little bit small on the screen here but you can see at the top uh there is this uh row for open shifts and so these are the shifts that a manager can put on the calendar and any employee can come and request one of these open ships there's a certain number of slots associated with the open ship uh with the open shifts and once an employee actually requests one then the manager can go in and approve the request or reject it and if the manager approves it then it will be put onto the employee's calendar now once the manager has put together their schedule they can share it out or share out a certain range of the schedule with all members of their team all right so we mentioned that shifts for teams can help simplify the experience for the frontline worker and so on the left most image there you can see what the view is for the frontline worker who's coming in to view their schedule they can see their schedule they can see the schedule of all their other teammates and they can also see these different group schedules that have been created within this one team now from the team's app the frontline worker can also request time off they can go in and they can offer to swap ships with other members of the team and they can set um their availability also all from the teams app on the go the uh the frontline work can also grab these open shifts like i mentioned earlier on the previous slide okay so with that i want to shift gears and talk a little bit about power automate um and then we'll get into our use case but before i do that let me check in um any any questions from the the attendees faster can you go back a slide and maybe go quick comment on the workforce management systems and and what does it mean to integrate any of these with shifts yeah so um there's a few different ways that you can kind of extend and customize shifts for teams you can do so through power automate like we're going to see you can also do so with the graph api and then there's also a set of kind of workforce management systems where you can integrate these with shifts for teams as well to kind of customize shifts for teams uh for your organization any yeah any other any other questions there is a question about is shift compatible with workday for epic um and i'll just respond offline unless you wanted to add something uh no yeah i think just a response um offline um will do okay okay so let's go forward let's talk a little bit about power automate um this is the other kind of component of this automated role based scheduling that we're going to get into but it's hard to talk about power automate without talking about the power platform as a whole and for those of you that are not familiar the power platform is a single low code platform that spans office 365 azure and dynamics now on the platform there's four different kind of products that make it up one of those is power automate and i'll come back to talk about power automate but we have power bi for business analytics power apps for rapid application development in a no code load code environment and then power virtual agents for creating intelligent chatbots with little to no code now power automate is our workflow or process automation tool on the power platform and it allows you to create uh low code workflows work low code workflows to do things like approvals uh or customize any of your business processes right all in this no code below code environment so we'll take a look we'll dive deeper into power automate how power automate works but i also want to mention these data connectors you can see this component down at the bottom of the screen and within power automate you get out of the box access to over 400 different data connectors that give you seamless secure integration to these 400 plus different data services and so these data connectors give you a lot of flexibility in power automate with what different services and data sources you can automate around now every power automate that you're going to create will have three different building blocks a trigger which is how that power automate is actually kicked off a set of actions what is that power automate going to go and do and then generally some conditional logic to guide these actions along the way now when you go to create a power automate you can choose from one of three types of triggers you can have a manual trigger meaning you're configuring your flow or power automate to only run when you actually go and explicitly press a button you can have a power automate that runs on a schedule so maybe you want a workflow to run every day every week every month you can configure that with scheduled trigger or you can have an event driven trigger and these event driven triggers are probably the most flexible so and you can use them to configure your flow to only run when an event in a cloud service happens so this could be maybe a new member being added to a team in microsoft teams or a new item being added to a sharepoint list or even a new shift request coming in in shifts for teams next we have actions this can be connecting to cloud service and taking some sort of action through a connector or an action can occur locally within the actual flow so maybe it's initializing a variable or doing some sort of data manipulation uh in the power automate and then there's the conditional logic so your your typical branching or looping scenarios you would expect out of a workflow tool and you can see the condition on the screen so if that condition is met you can branch or power automate to go and do a certain set of actions if the condition is not met you can go do a different set of actions now i mentioned that in power automate you get access to these 400 plus different connectors they're both first party and third-party connectors and these connectors give you access to hundreds of triggers and thousands of actions and so each connector has a set of triggers and actions associated with them and this makes power automate super flexible in terms of what you can do with it in the systems that you can automate around the last thing i'll mention on power automate is that there are a ton of pre-built templates available to you so you can really get started quickly with some automation and you can always go in and customize these templates to further meet your business requirements as well so they can be a great starting point as you're learning power automate all right so next we'll get into the use case before we do that i'll pause again and ask if there's any questions in the chat or in the q a around power automate no new questions andrew thank you for asking um i do want to call out that there's also a connector for fire that you can bring in data from your emr into the power platform some of our customers heavily utilize that in their workflows and i'll drop a link for that in chat here shortly a great call out thank you right so let's switch gears to talking about a particular use case uh where we can kind of enable this automated roll-based scheduling and so we can imagine that we're for an organization or a healthcare provider and we're trying to manage the volunteer scheduling process within a cova vaccination clinic so we might have one clinic or maybe multiple clinics but we want to manage how volunteers can actually sign up to work in this oxidation clinic now in the clinic there's multiple roles that a volunteer can fill so they can sign up to be a vaccinator who's actually administering vaccines to those who come to the clinic the observer who watches those who perceive vaccines for a set period of time after vaccination a runner who is bringing supplies you know to different stations into different vaccinators around the clinic the documenter who tracks who is receiving what vaccines and then check and support who's there to of course check people into the clinic and make sure things are running smoothly now one thing to note here is that each different role requires a different set of qualifications so for example to you know sign up for a vaccinator shift in this cova vaccination clinic you might have to be a nurse a doctor a medical student nursing student pharmacist and so these qualifications must be met for you to sign up for a particular shift and that's really what we're talking about when we're talking about this role-based scheduling management is the fact that there could be multiple positions that require different qualifications for people to sign up for now the observer and the documenter might also have a smaller set of kind of qualifications that have to be met and then the runner and the check and support likely don't necessarily need to meet any qualifications for someone to actually sign up for one of these different types of shifts so our goal is to again automate this process of checking to make sure that whoever signs up for one of these shifts is actually qualified to sign up for the shift pay they want in the clinic and then we also are going to add another detail here and we're going to say that the ships must first be filled by employees who won't be working overtime if they sign up for a ship so two employees or volunteers sign up for one of these shifts then we have to give that shift first the employee who would not be forced to work overtime when they sign up and we can also imagine that the organization is currently managing the scheduling process all through email so uh we have a scheduling admin and he goes and he puts together a list of all the shifts that are available for a given week and he sends it out through email to the pool of people who have signed up to volunteer and then they respond to him what ships they want and then he has to manually go and check to see if they're qualified and then if the ship's going to put them into overtime and then correspond through email to kind of verify with the volunteer so you can imagine how convoluted this manual process is and really how inefficient it is so before i get into the demo um these are the two personas that i'm going to be switching back and forth between so we have jeff h and jeff h will be the scheduling admin who is in charge of putting together the schedule on a weekly basis for this clinic and then amy a who is a md she's volunteered to you know work at this oxidation clinic and sign up for shifts there as well so with that i am going to switch over into the demo and i'm logged in here as jeff h and so the first kind of step in this process is thinking about where we're going to store this volunteer data so this is data that contains information about all of those uh people within the organization who have signed up to volunteer within this clinic so i'm storing it in sharepoint so you can see i'm storing basic information about the person first name the last name and then i also have this grid here that lets me understand kind of um what their prefix or what their title is so i can see if they're qualified for a given shift now notice that amy is an md but there are others who have signed up to volunteer who might not actually have you know meet any of these qualifications they can still sign up for the check and support or the uh runner type ships now i'm using sharepoint because it's you know simple tabular data source it has a very robust connector in power automate as well so it's very easy to interact with this data so once i have my volunteer data stored somewhere i can go into teams and i can create a team because again a team is the starting point for every shift schedule so i've created this vaccine volunteer coordination team that you see here and if i go into manage this team you'll notice that jeff is the owner of the team so he'll be the admin of that schedule that's going to get created in shifts and then everyone who is on that sharepoint list has been added as a member of the team here what i can do next is i can go into the shifts app so let me zoom in a little bit i'll go into the shifts app i can access the shift app just like i would you know find any other app in teams i can see it here in my recent so i can also just search for it and when i open up the shifts app i'm brought into the schedule that has been created for the vaccine volunteer coordination team so right now i'm looking at the schedule that's specific to that team if i had other teams that had schedules i could go in and i could switch between schedules for different teams but i've only created one schedule and it's for this vaccine volunteer coordination team so it's going to only show me the schedule now in this schedule you can see that i have one group the group is called vaccination clinic a and this is the you know clinic that we're trying to manage the scheduling process for now i can create new groups pretty easily through the ui here in ships by just coming in clicking on add group i will add the group here you can see how it gets its own unique schedule and i can add people to this schedule as well i all done right through the ui i could add someone and just like almost like adding them to the team itself now i'll delete this group because we don't need it but just wanted to show how you can create those groups and add people to them now in some instances we can imagine if we had maybe a hundred people who wanted to volunteer at this copa vaccination clinic it might not make sense to add them all through the ui that would take a long time again that's a manual process we might miss people we might have people that you know to to the wrong clinics to volunteer at and so what we can do is we can automate that process of adding people to these groups again with power automate i talked about extending teams and customizing teams with power automate or with the graph api and so i've created a power automate here called create shifts group and what this power automate does is it's manually triggered meaning that i have to come in and explicitly tell it to run and then once it's triggered it goes out to that sharepoint list so it goes out to the volunteer data sharepoint list and it gets all of the items from that sharepoint list using the sharepoint connector and then it loops through each item and adds them to array and then the last step is actually making a call to the graph api using the using the http with azure id connector we're making a call to the graph api and we're using the scheduling groups endpoint and passing in the team id where we want to create a scheduling group and you can see that this is how i created the vaccination clinic a group in my shifts calendar so that's how we created this group now i can come in here and i can run this again to maybe create a another scheduling group so if we had multiple clinics and we had to add these users to multiple clinics i could just change this and run the power automate so i'll run this real quick it should only take maybe 15 seconds or so to run so i'll run that flow and we can see it running in real time here now it's looping through the users and then it will go and actually create that group okay so i can see that that ran successfully so if i go back to my shifts calendar and refresh this we should see that new vaccination clinic b group there in the shift schedule there we go so now we have our new group so that's one easy way that you can use power automate to automate the process of creating these groups to again avoid a manual kind of air prone task now we're only focusing on one clinic here so we'll actually delete this group that we just created and now we have our group we have our team we've added our members to the group and so you can see i've already created ships now when i go to create an open shift i can come into the open shift section here i can click in here and add a new open shift so maybe i want to add a second second vaccinator shift for tomorrow september uh 16th i can come in here add shift and color code it so there's some colors and theming that you can add for these shifts which is really nice way for your employees to understand what type of shift they're actually signing up for so i'll add a dark pink shift we can specify how many open slots there's going to be for this open shift so maybe we need five vaccinator twos so i'll change this to five and then we can add a custom label for these different shifts so i'll call this the vaccinator two and we could add shift notes or even add specific activities that we want someone to kind of track while they're doing one of these shifts i'll leave those blank for now and save this and so you can see that the shift has been added to the open ships here now it hasn't been saved which is denoted by this star so as a manager i can go and share this with my team whereas jeff h the scheduling admin and when i go to share it with my team you'll see that i'm sharing a specific date range if i only want to share one day i can do that as well or if i just want to share a couple of days but i'll share the entire week it shows me how many open shifts and shifts are being shared so i'll share this and now that second vaccinator shift is available for all of these employees to sign up for i could also come in and give these team members or group member shifts directly so if i wanted to give alicia a shift i can easily come in here and add a shift fill out the information and save that to her calendar and that will go directly to alicia there okay so now we have our uh we have our team our groups our shifts everything's been configured by the scheduling admin you can notice how they're all color coded so it's really easy for an employee to understand kind of which different shifts they might be signing up for these colors can also be picked up by power automate so it's an actual property of the shift so what i'm going to do next i'm going to switch over and switch personas to amy and you can notice that amy is a member of this group and so she can come in and sign up for any of these shifts that have been shared with the group of volunteers so i'll switch over to amy um and before i get into kind of continuing with the presentation from amy's perspective i'll pause again and ask you if there's any any questions or comments that have come up in the chat there's a question andrew from sean asking whether we can use azure active directory versus a sharepoint list to pull the role information i guess the assumption here is that azure id has some custom fields that outline either the skill sets or maybe department or geography any type of a tag um is there a reason for you know wanting to use a sharepoint list versus pulling that data from a user's profile can you speak to that a little bit yeah so if you're just looking to add those users from azure active directory into the into the teams group then yes you can absolutely do that really all i was using in the actual power automate was the object id of the user if you look through what's actually being passed um when we're creating the scheduling group it is the object ids of the user so that's all stored in azure active directory so you wouldn't need to store the data in sharepoint unless you wanted a way to kind of track obviously all the people who had signed up to volunteer thanks andrew yep great question okay so going back i'll switch back and again now i'm logged in as amy and amy is uh right one of the people who assigned a volunteer now she's been added to this vaccine volunteer coordination team here so now when amy goes in and she opens up the shifts app she gets a very similar view where right she can come in i'll zoom out a little bit and she could see all the open shifts that she could request to sign up for she can see her shifts down here as well so she has a shift on friday to be a vaccinator but no other shifts so you can see that vaccinator 2 shift that was recently published by jeff h she can also switch her view and maybe look at the rest of her team's shifts so if she wants to switch over and take a look at team shifts she can see the shifts of from everybody on the rest of the team and she could easily come in here and request to swap these with others but i'll switch back to only amuse shifts and so as amy she doesn't get to see necessarily how many open slots there are for a particular open shift or how many requests have been made like jeff can but she can come in and she can request one of these shifts so maybe she also wants to be a vaccinator on saturday the 18th so she has a vaccinatorship on friday already but will go in and request a vaccinator shift for saturday the 18th now when amy goes and um requests this shift we want to automate two things first off we want to make sure that amy won't be put into overtime by taking on the shift if you remember that was one of the requirements and then secondly we need to check what shift she's signing up for so this is a vaccinator shift and we have to make sure that she meets our kind of minimum qualifications to take on this shift in the clinic so those are the two things we want to automate so i'll go ahead and i'll request this and then i'm going to switch back over to jeff h the scheduling on it so i click request switch back over to jeff now as the scheduling admin i've also created another power automate and this is the power automate for automating those two things that i just mentioned so let me switch over to that so this is the open shift approval power automate and you can see that this power automate is triggered when an open shift request is created updated or deleted and so right when uh amy went and submitted that open shift request this power automate was triggered and what it does is it goes in and gets some details about the shift the open shift the open shift request the user and then also it posts a choice of options as the flowbot to the user so what this step does is it sends an adaptive card in teams that allows that end user or the volunteer to either approve that this request will not put them into overtime or reject if the request will put them into overtime and so right when amy submitted that she should have got a notification in teams asking her to either approve or reject the fact that this shift will put her into overtime so let me go back in here uh to amy's view so i'm switching back now to amy and you can see that a chat has arrived here and if i go in i see this adaptive card has come and it says additional validations required once you do approve or reject this here and so this is um right after she has created that openshift request you can come in and approve this or reject it to keep the power automate running of course i will approve this and so once i approve this the next thing that needs to happen is before we actually approve that open shift request we need to make sure that amy is qualified for a vaccinator shift in the coma vaccine vaccination clinic so i'll click submit and i'm going to go back to the power automate so back to to jeff h here and the next thing that the power automates going to do is it's going to go and look up the sharepoint uh go grab amy's item here again this is one reason actually we might want to consider storing the details in in sharepoint is if you don't have details that are about each volunteer each user that are crucial to understanding you know if they're qualified for one of these roles that might be a reason to store it in sharepoint where you can add those details but this is where we really infuse our custom business logic into the power automate and so for this use case right obviously what we're going to do is just check to see if uh amy is a md a nurse a student a pharmacist and make sure she's qualified to administer those vaccines now your business processes might be different but it's very easy to infuse this custom business logic into these workflows and to do these approvals in validations in power automate so this is just custom business logic here it goes through finds the item checks to make sure that um amy's qualified and then the last step is approving this openshift request so if i go back to the power automate i go into the openshift request power automate that i was just showing i could see the 28 day run history i can see that this was ran three minutes ago and it succeeded and if i drill into the particular run i can get details about the run itself and i can go down to the last step and i can see that this open shift request was approved i can look at some details here so if i go back now to the shifts view i'll go into teams and here i'm logged in as jeff h and if i go into my request i can see that this request came in when amy actually requested it a few minutes ago and then it was approved automatically by the power automate and that we sent her this note along with the approval letting her know that you know this has been approved and we're looking forward to seeing her on that specific date if i go back to the schedule i should see that that uh shift has been added for saturday the 18th the vaccinator shift here for amy which i do and so if i go now to amy's view and i go back into the shifts calendar i can see that now she also has that let me actually zoom out a little bit but she also has that vaccinator shift now on the uh on the 18th and if i go to her request she also sees that her request has been approved and so that is you know how you can start thinking about automating that role-based scheduling in teams using both power automate and shifts for teams and your your business requirements and your your use case might not be identical but hopefully this gives you a good idea of how you can go about that automation for these role-based scheduling processes so let me pause again and open it up to any questions that people might have about anything that we have kind of covered here today thank you andrew um just a few sort of open-ended questions if i may walk us back to the approval workflow i'm sorry the attestation where the employee is responsible for validating if they're you know over time or not for some of us who you know aren't really on the front line can you maybe spend a few seconds talking about the importance of the step um from a tracking point of view from an auditing point of view and then maybe even from a business logic point of view to say these people need to be paid right yeah definitely and so um when it comes to this approval workflow we would if we didn't have this step in the workflow that jeff h the scheduling admin would need to go and manually you know check to see if this shift would be putting a specific employee into overtime so adding this validation here allows that process to be completely automated and it also kind of puts the responsibility on the actual volunteer who's signing up to attest to the fact that this will request will not put them into overtime now the nice thing about this adaptive card is that it's coming to that user right after after they actually sign up for one of these open shifts so they don't need to leave leave teams it all happens in one place they can come here and then with one click either approve or reject that and then our workflow can go down two different routes based on kind of what they choose and then again this is all tracked in the actual flow log so you can go back and see what the user's response was here as well anything you want to add on to that person i think you summed it up beautifully i mean it's often a requirement to track down the actual hours and the consent and hurting is report you know sort of important for those reasons and you kind of hit the nail on the head so thank you for for sharing your thoughts um another question that comes up is around what type of endpoints do we need to provide our first line worker staff to be able to use teams and shifts you only web-based are you only desktop-based or can you also load up themes on like an ipad or shared device or a mobile phone yeah so any um any device that has access to a team's client whether it's the web client or it's android or ios now the the only thing you have to ensure is that the shifts app is allowed uh in the teams admin center so you're allowing the shifts app and then you can also create a app setup policy so if you want to push this shifts app out to the side rail for your frontline workers then you can do that as well through a setup policy and you can create that in the teams admin center that's excellent info andrew thank you um can you take us back to the sharepoint list where you maintain sort of credentials alongside everybody's names one question that we are you know feeling here is this looks like a static database what's your recommendation for building a process that allows for new volunteers to sign up would you create a form or would you create some kind of a mechanism to add line items to this list and what's your easy recommendation yeah i know that's a great question so um you know there's multiple places to store this data right sharepoint is definitely not the the only place but in terms of creating a process to add new volunteers i'm always a fan of keeping it as simple as possible and so i think a simple microsoft form with maybe even a power automate behind it that's triggered when that a new form is submitted for a volunteer and then creates a new item in the sharepoint list and takes the data right off that form to create the item could be a really easy convenient way to kind of keep updating your volunteer data thank you um somewhat more generically can you speak to a few other areas in which shifts can be applicable in the healthcare clinical worker space um any examples that you can share with the group here yeah and that's maybe maybe you might want to take that one also i know you have a lot of experience working with healthcare customers using chefs totally you know i was thinking about some informal resource management in some ways so mri machines or lab equipment instead of creating um another mechanism you can sign those up as open shifts and whoever needs access to that equipment can quickly grab and go of course you know the primary use case here is is actually shift management so if you have nurses if you have social workers if you have janitorial staff who are supposed to be aligned to a particular schedule that's that's typically the primary use case but i've seen in many areas people have sort of gone creative and substituted a user within another type of an entity it could be an equipment or a facility or a location and offered that up through shifts um i remember if you want to add some more examples there yeah i think that's those are great examples and i like the kind of out-of-the-box thinking where this can also be applied to kind of equipment and equipment management as well and can you speak to the level of expertise and effort required to get started on something as simple as what you showed yeah definitely so um i'd say getting started using shifts for teams yeah right there's not really any expertise that is required um there but when it turn when it comes to kind of automating around um microsoft uh shifts or shifts for teams and using power automate you might need a little bit of you know expertise but really not a lot and the nice thing about power automate is that is it is a really a tool that is intended to be used by anyone regardless of their technical background so a lot of automation tools are kind of geared towards a more technical audience but power automate is for you know business users uh just as much as as it is for people with a more technical background so there's really easy ways to get started using power automate the power automates that i showed today um are you know somewhat complex but definitely are nothing that would be too far past beginner to learn how to do in a short manner of time thanks andrew i do also want to invite you to maybe talk a little bit about the microsoft technology center and how you guys can support some of our customers um if you wouldn't mind maybe talking about what are the mtc's how do you you know work closely with customer engagement and you know the microsoft account team that supports customers if you can maybe take a couple of minutes to talk about how best end users can engage with you yes definitely so i don't have a slide to put up here but across united states we have 15 different microsoft technology centers so like i mentioned the goal of these technology centers is to empower digital transformation through a set of deep technical engagements so we have offerings from strategy briefings to hackathons to proof of concepts and so if you're interested in engaging with a microsoft technology center you can always talk to your account team and your account team can definitely get in touch with one of us again we have 15 centers across the united states we're very geographically dispersed and we can engage uh currently right we're doing it all virtually but once we reopen you can always do engagements in person as well thank you so much andrew i'm just a personal insert there i found a very meaningful solutions come out of each mtc engagement that i've been a part of so i want to add that personal endorsement to this call we don't have any other questions um i'm guessing we can give people some time back was there any other closing remarks andrew from you uh no other closing remarks from me i just want to thank you for for having me vasu and i encourage everybody to you know take a look at shifts for teams and if you're interested in learning more about power automate it's easy to get started with there's a lot of great training out there as well you can go to ms learn to find some great free training on power automate um but that is it for me thank you very soon thanks andrew and thanks for the wonderful demo i do want to leave everybody um with the fact that you know we will be posting the recording and the supplementing links on the hls blog so just be on the lookout for that and if you have any questions don't hesitate to comment on the blog post thank you so much all for joining and hope you all have a great day ahead thank you you