PL 400 : determine when to use Logic Apps versus Power Automate flows

Of course, the bigger challenge is identifying the actual and optimal use of Logic Apps and Power Automate Flow. In my first exploration, I came across information about cloud status and subscription model. Whereas Logic App is PaaS and Power Automate Flow is SaaS and as per subscription model, Power Automate Flow is part of Office 365 subscription (Per-User License in Office 365) and Logic App is part of Azure subscription (Consumption-Based or Fixed Pricing Model).  These information could not help in ascertaining the actual use of both mechanism. However cost is an essential aspect. Most interestingly, the Power Automate flow is built on top of the Logic app. In other words, both are workflow as a service.


Let's talk about the difference between the both environments that can lead me to determine the use of Logic Apps vs Power Automate Flow.

Description              Power Automate                                          Logic Apps

Focus                        End users and Makers in Office 365           IT Pros, Developers, Admins using                                                                                                                 Office and Azure Service

Licensing Model      Per-User License in Office 365                     Consumption-based or Fixed Pricing                                                                                                             Model Azure Subscription

Flow Creation          Web-based Designer, Web and mobile UI      Visual Studio, JSON Definition and                                                                                                             Web Based Designer       

Restricting               Data Loss Prevention                                       Azure Policy                                           Connectors

Error Handling        Flow Checker                                                   Save Failed -highlighting errors

Trigger Types          Automated, Instant, Scheduled, UI flow,         HTTP(Automated), WebHook,                                             Business Process                                             Scheduled, HTTP Call (Manual) 

When to use Power Automate Flows :

  • Power Automate Flow provides citizen developers with a unique way of dealing with data and applications where expertise is not required, in other words, it uses in simple integration, approvals and other activities which empowers office worker.
  • Power automate flows includes several first party integrations. These integrations align with where Flow users typically like to work: SharePoint Online, OneDrive for Business, Dynamics 365, Excel ,Microsoft Teams and others.

 When to use logic Apps:

  • Logic apps is helpful as part of a Microsoft Power Platform solution when we use the Enterprise Integration Pack or we need SOAP connectors.
  • Logic Apps offers a different deployment and consumption model that can be more efficient in certain scenarios.
  • Logic Apps is typical for  business workflows to grow in complexity over time.

Conclusion:

Generally, Cloud service selection is a specialization activity and it always aligns with the business and its betterment. The cost and complexity of the business nature always plays an important role in the selection. Both services are Designer First integrations that give the upper hand to both the business as well as the technical experts.


Comments

  1. Sapphire Solutions31 December 2021 at 15:05

    PL 400 : determine when to use Logic Apps versus Power Automate flows

    Good explanation about power automate flows, students can learn from it...!

    Well, we have shared one blog here- What is Power Automate? Advantages & Disadvantages of Power Automate

    Power Automate Services

    ReplyDelete

Post a Comment

Popular posts from this blog

Powering Up Your Analytics: Exploring Power Query in Power BI

Image
Data is a valuable asset that has a profound impact on almost every aspect of modern life. Its proper collection, analysis and application can promote innovation, improve efficiency and solve complex challenges in various sectors. In data processing, ETL is a comprehensive process that includes data extraction, transformation, and loading, while Power Query is a specific tool that facilitates the "extract" and "transformation" aspects of ETL, allowing data to be collected and analyzed. Permission is granted to process. And reporting. is ready. It becomes easy to do this. Microsoft's ecosystem of products. Power Query is a data transformation and data preparation engine. Power Query is available in Microsoft Excel and Power BI. Power Query provides a user-friendly and intuitive interface for data professionals and analysts to access and manipulate data from various sources without the need for extensive coding or scripting. It allows users to connect to a wide ra
Read more

Power App Component Overview : Canvas App vs Model-Driven App

Image
The Power Platform is a suite of low-code/No-code tools and technologies developed by Microsoft and Power App is integral component of Power Platform. Power App is platform that enables users to build custom web and mobile applications with a visual interface and minimal coding. The platform support various data sources, including Microsoft 365, Azure Service, and many other, enabling users to integrate and interact with their existing data and systems. In Microsoft's Power Apps, there are two main types of apps that we can create: Canvas Apps: Canvas apps provide a blank canvas where you can design highly customizable applications with a drag-and-drop interface.  Model-Driven Apps: Model-driven apps are built on top of the Dataverse, which provides a set of pre-built data entities and business logic. There are few key technical difference between Canvas App and Model Driven App: During the usability analysis, these high-level technical differences need to be considered. The choi
Read more

Exam PL-400: Microsoft Power Platform Developer

 Create a technical design (10-15%) Validate requirements and design technical architecture design and validate the technical architecture for a solution design authentication and authorization strategy determine whether you can meet requirements with out-of-the-box functionality determine when to use Logic Apps versus Power Automate flows determine when to use serverless computing, plug-ins, or Power Automate determine when to build a virtual entity data source provider and when to use connectors Design solution components design a data model design Power Apps reusable components design custom connectors design server-side components Describe Microsoft Power Platform extensibility points describe Power Virtual Agents extensibility points including Bot Framework skills and Power Automate flows describe Power BI extensibility points including Power BI APIs, custom visuals, and embedding Power BI apps in websites and other applications describe Power Apps portal extensibility points incl
Read more