Relationship Between Logic Apps & Power Automate

hey everyone in this video i wanted to explore the relationship between logic apps and power ultimate i've done a number of videos recently on logic apps and the questions arise well what's the difference between those logic apps and power automate as always this is useful a like and subscribe is appreciated so let's start off thinking about logic apps and i have done a number of videos about these already so i can think about logic apps are available from within an azure subscription so it's one of the pas services so it's a platform as a service i'm not worried about hosting some virtual machine or patching some operating system i focus on my application i focus on the logic and the service takes care of the hosting and the execution of it it's fought off as a serverless offering and what i mean by that is you're not really thinking about units of virtual machines underneath there's a consumption based model where i just pay for the work it does for the types of connectors it interacts with now there is also a standard plan where i can have some dedicated infrastructure if i want to maybe have more control over that pricing but it is a serverless offering i think about it's been triggered by some event that could be something's written to a queue it could be a certain scheduled time it could be some manual interaction i'm triggering by an api but say it's going to trigger it and then it's going to perform a set of actions that's really the key part around this when we talk about connectors they're ways that logic apps really wrap some very friendly ways to interact with other apis out there and it also has some built-in native capabilities as well now when i talk about it is consumption based that means that when i'm paying for it my dollars is really based on the consumption the work it does and as i mentioned it runs within an azure subscription so i have to have an azure subscription i go and create my new logic app and then i create my code that means there's a certain amount of governance associated with that azure subscription that i am going to manage if we actually stepped over for a second and looked at the pricing of logic apps we can see that consumption-based nature i can see hey the consumption plan i'm basically paying for the number of actions i do get 4000 actions free and then you pay for calls to the different types of connector both standard connector and enterprise connector or i can have a standard plan where i have that dedicated set of infrastructure on which my logic apps run this makes the billing a little bit more predictable so we have those choices and again i've done a stack of videos around logic apps already so i'm going to go into the details of that i want to focus more about what is that relationship so if that's logic apps this has solution this serverless solution what is power automate formerly known as microsoft flow so i can think here of power automate and as i'm drawing it is actually very real as to how it works because power ultimate itself sits on top of logic apps it abstracts it away so i'm not worried about hey the logic cap or an azure subscription on those governance things power ultimate is more of a sas solution it's a sas that is built on logic apps so when i think about that it's important to understand if i can do something in logic apps well i'm going to be able to do that on power automate as well but i don't have to set up subscriptions i don't have to set up an application i don't have to manage connections i don't worry about billing based on consumption it's all managed for me hence why it's really talked about more of a sas type solution although obviously i still have to create my business logic so all that azure resource management that is taken away users don't need an azure subscription at all when i think about the interaction or how do i actually create these things there are some that are specific to them but one of the main ways is there is the designer so we have a designer and that is common now there might be a little bit of extra decorative things around them powerapps has some nice templates that i can fire off from within the application so i'm in an office app for example i don't ever really see a designer it will just go and create via the power automate the logic app that does the work i want to do it is handling all of the connection management for me so when i think about the power automate side and some of the big benefits here well i'm not thinking about resource management so here there is no resource management i'm not worrying about azure subscriptions i'm not worrying about governance there's no connection management so with logic apps i set up connections i manage those that is all provided as a service layer so there is no connection management that i have to take care of for that it's just all handled for me i can go and connect to sharepoint for example it's all just handled but power ultimate is giving me all of the same connectors of logic apps because it's again it's built on top of it so i have all of the same connectors available in logic apps plus it actually has some of its own so it has some first party connectors so using the dataverse it adds things like approvals so it has a native approval capability so if we jump over for a second and just look at this so here this is a logic app so if i look at logic app i have the designer i can see the various actions there are ones that are built in there are ones where i can call rest apis there are ones where i'm calling some standard connector but we have this sort of graphical designer if i go to make.powerautomate.com which is the new url it's exactly the same i can start off with templates i hate about email files and documents notifications and reminders or i can just say hey i want to create and i could create from blank or we have all of these templates that i can leverage hey i can start from a certain connector that i want to use i want to start from blank well what's going to trigger this okay maybe it's a schedule i can put in the schedule i'm just going to do skip for now and then i'm faced with the designer so the first thing i want to do is well what is kind of that trigger so i can look at well there were standard connectors there were the built-in and these all align with what we have in logic apps as well so it's a very very familiar experience with how i would go and create these now there are different connectors if we look for a second at the license entitlements for example this i'm focusing on things around like microsoft 365. if we look at the standard connectors well this is just a list of connectors and where notice there are icons that show well does it work in logic apps is it available in power automate and as we look down these all of these connectors you'll see pretty much all of them are well yeah hey it's it's logic apps and it's power automate so this very common set across these because power automate is built on top of logic apps so it really makes sense that hey we have the same capabilities now licensing may impact exactly what you can use and we'll talk more about that in a second so if we jump back so we say okay great so power automate abstracts a lot of the resource management away the connection management way add some first party connectors like approvals to make that really really simple to do from a licensing perspective it's not based on this consumption anymore so the way this is going to work now i'm going to say per user there are other license options for example there's there's like a app for flow there are different things i can do and if we actually look at those really really quickly so these are the types of power automate plans available and if you actually go and look you can see all of the different types of hey power ultimate per user plan per user with rpa the robotic process automation per flow plans and then you have these seated plans so many of the ways people are going to get power automate is they own another license hey i own microsoft 365. so i get this hey i own dynamics 365 or maybe i do get a power app specific license and it has a nice chart here that basically explains well depending on which license you have that will say what you have access to and there are limits so we can see here there are limits around what i can actually do in terms of the amount of work it's performing how many actions a day can i do for example so if i was to jump over to this other document this goes into detail hey i own office 365 well what can i do well here you can see we're currently going for a transition period but normally it would be 2 000 power platform requests a day but it's 10 000 during this transition period and i get access to all the standard connectors i can create and execute automated scheduled button flows and things like that as well so we have those various capabilities available to us but for most of us we're going to get access to power automate because hey i have a microsoft 365 license or i have a dynamics license i'm going to have one of those so the question becomes okay why are there two solutions and which one should i be using it's actually fairly simple to think about power automate is really targeted at makers i'm trying to create some automation maybe from within an office app or dynamics or something else that's for me or it's for my team whereas logic apps is really focused at a developer i'm trying to create something maybe for my organizational level automation or it could be something that is just very high scale so it doesn't fit within those per user per flow licenses that i have with power ultimate and that's really the way to think about it i wouldn't think of a versus it's what is the persona that's leveraging and what is the target hey i want to create something for me or my team some nice automation maybe triggering it from teams or sharepoint or something like that hey power automate is a fantastic solution i don't have to worry about subscriptions or resource management or connection management or any of those things very easy to get up and running i'm trying to create something for my organization it's some very high scale job then logic apps is the right solution and that's the relationship between them the question come up so i just wanted to address it power automate sits on top of logic apps but abstracts away all of that resource management and instead of it being this consumption based model where i pay for the work it's doing or worry about some set of resources hey it's just this very simple sas solution most things are abstracted away if i go and create these flows from within an app i may not even see the fact that there is a flow being used at all it asks me a few things i put it in it creates the power ultimate flow the logic app behind the scenes i don't even see the designer it's just abstracted away i can go and look if i want to but by default i just won't even see it so that's the idea hey if i can do it in logic apps i i can do it in power automate and it adds some additional things like approvals just as a feature that's unique to that so i hope that helped i hope that uh clarified that a bit until the next video take care you

Channel: John Savill's Technical Training

Views: 9,484

Keywords: azure, azure cloud, microsoft azure, microsoft, cloud

Id: 3OixNSZkcuo

Length: 14min 37sec (877 seconds)

Published: Wed Aug 10 2022