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

PCF vs. Web Resources: Choosing the Right Extensibility Tool for Dataverse

Image
Extensibility refers to the ability to be extended or augmented beyond the default capabilities of the platform. This involves customization but also includes more advanced techniques, such as coding, integration with external services, and the use of custom components. In the context of Power Platform and Dynamics CRM, the term "extend behavior" refers to the ability to customize and extend the functionality of the platform to meet specific business needs. Extensibility often requires technical skills, such as coding in JavaScript, C#, or using tools like Azure Logic Apps and Power Automate for complex integrations. Customization  is a subset of extensibility. Customization involves configuring and modifying existing elements within the platform to suit specific business needs. Extensibility, on the other hand, covers a wide range of functions and techniques, including customization and more advanced development and integration tasks, to extend the capabilities of the Power
Read more

Is Debt Prosperity or Trap?

 “What can be added to the happiness of a man who is in health, out of debt, and has a clear conscience?”  Adam Smith Grandfather Bhishma lay on the bed of arrows and was preaching the future king of Hastinapur about political science, economics and the duties of the king. He took a deep breath and told Yudhishthira " Fire, debt and enemies must be dealt with quickly and completely. If there is any balance left, they can continue to grow. " The future king was listening with curiosity and was eager to learn about the complete knowledge from his grandsire. Each moment was important as the sun was moving from south to north. Either we read the quote of the father of modern economics or both ancient great scholars are advising to avoid debt. But the whole of modern economics is based on the debt that advises the public to borrow money. The aggressive campaign of banks and financial institutions has been luring more and more loans. Even democratic governments and public banks con
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