Power Automate (Flow) vs Azure Logic Apps EXPLAINED! (6 Key Differences)

so one of your team members says we need to use power automate flow another member says no we need to use azure logic apps what's the difference that's what i'm going to explain in this video let's dive straight in both power automate or flow as it used to be known and azure logic apps are workflow services what does that mean well it means it can automate your business process and integrate with other applications well why have two different workflow services well one is designed to be quite user friendly that's power automate and one is a bit lower level more for developers so they can build on it and build richer services so for example power automate is very integrated into office 365 whereas azure logic apps is more within the azure portal ecosystem so let's have a look at some differences well both have a really friendly interface web-based interface and they can get you up and running very quickly both options reduce the effort involved in connecting all these systems together and both systems allow you to focus on higher level tasks rather than trying to get your business processes working in fact the way to think of power automate flow is it's built on top of azure logic apps so it takes away a lot of the complexity which is available to you through azure logic apps but it kind of hides it away to make it a lot easier for the end business user so if you think power automate business user and developer and you think logic apps developer so let's have a look at six key differences between the two starting with who is the key user base so point number one is who is it aimed at what's the focus for each application well power automate is really designed for end users and business users who would construct the flows logic apps is more aimed at it professionals such as developers administrators devops and the like the second difference is the licensing model power automate is licensed per user through office 365. logic apps is more based on how much you use it or maybe for a fixed cost decided up front so the third point is when we create these processes these flows well for power automate it's all done in a web-based tool and that's actually the same in logic apps only it extends it in that you can define it as json schemas or you can use visual studio to build your logic apps the fourth point is around security now with powerapps it uses data loss prevention dlp in order to decide what policies affect each flow who can access it how long does it last etc whereas in azure apps you use azure policies to define such things for more information around dlp and azure policies see the link below the fifth difference is around handling errors flow has a built-in checker so as you go to save your flow it will tell you if you've got any errors and anything that you need to address in logic apps in a similar way it will fail when you try to save it but it's a bit more verbose in its errors helping you to target where the problem is the final difference is around trigger types how you trigger your processes with power automate it can be triggered manually it can be automated when an event happens it can be scheduled scheduled scheduled depending where you are in the world and it also has kind of crm based business processes as well whereas in logic apps it uses http requests in order to trigger its processes it can use web hooks as well and they can also be scheduled but you can see it's a far more low-level way of accessing this information so there are six main differences but it begs the question when would you use each one well it depends on what you're trying to achieve if it is a simple business process email comes in from here right to a sharepoint list maybe we connect to a third-party application flow may be sufficient to do what you want however if you need to hide a lot of that logic away if it needs to be very rich in its logic then logic apps by its very name is the one for you for example recently in flow somebody had a timetable application where they had some very complex logic by the time we built it out in flow it was actioned upon action upon action in a logic app we did all that logic within the main body of that app in code so in that case it made far more sense to use a logic app but when people are reviewing documents and they need to send off alerts or approvals then power automate is the easy choice the other thing to consider is a cost as well so is it enough just to license it on a user by user basis or do you need to pay more based on what you consume and what you used or a fixed company cost they're the two things that you need to weigh up one thing i would say is if you're new to it all start with power automate flow don't dive straight into logic apps unless you really want to get your hands dirty as it were in code start with power automate flow get to know how everything works and then move on very soon i'm going to be developing an introduction to power automate if it's already been released you'll see the link up above i hope you will join me for that if you like what you've seen please click subscribe and follow us we're going to be doing lots more power automate and logic apps in the future my name's rob happy coding if you've enjoyed this video then please do give us a like and if you like this kind of content then do make sure you subscribe and ring that bell icon so you never miss out on a video and if you want to join us on our developer journey see the link below and if you're feeling generous buy us a coffee thank you so much for watching thanks for your time happy coding we'll see you next time [Music] you

Channel: Roberts Dev Talk

Views: 13,284

Keywords: logic apps vs power automate, logic apps, power automate, microsoft flow, azure logic apps, logic apps azure, azure, tutorial, logic app, enterprise, integration, enterprise integration, workflows, workflow, Flow, Process, Sharepoint, Sharepoint workflow, Office 365, O365, Automation

Id: JMYxGrvY5w0

Length: 6min 43sec (403 seconds)

Published: Mon Nov 01 2021