---
title: "Plug-in, Flow or Logic App?"
url: https://platformforgelabs.com/cheatsheets/logic-apps-power-automate-plugins
description: "A one-page guide to picking the right automation engine: a five-question decision path, the commit boundary that decides what can block a save, verified default limits side by side, the risks each engine brings to production, and a worked order-approval example that uses all three. Verified against Microsoft Learn on 15 November 2026."
updated: 2026-11-15
author: Sebastian Sochacki
publisher: Platform Forge Labs
---

# Plug-in, Flow or Logic App?

A one-page guide to picking the right automation engine: a five-question decision path, the commit boundary that decides what can block a save, verified default limits side by side, the risks each engine brings to production, and a worked order-approval example that uses all three. Verified against Microsoft Learn on 15 November 2026.

[Download PNG](https://platformforgelabs.com/cheatsheet-assets/logic-apps-power-automate-plugins-sheet.png)

[Open full size](https://platformforgelabs.com/cheatsheet-assets/logic-apps-power-automate-plugins-sheet.png)

![Plug-in, Flow or Logic App?](https://platformforgelabs.com/cheatsheet-assets/logic-apps-power-automate-plugins-sheet.png)

What this helps with

- Only a synchronous Dataverse plug-in can stop or change a save; flows and Logic Apps react after the row is committed.
- Power Automate suits processes people own, but a flow runs on its owner's plan, so give important flows a service principal owner.
- Logic Apps Standard fits integration that needs private networking, managed identity, high volume and Git-based releases.

Built as a visual shortcut: open it in the browser, download the PNG, or use it as a reference during architecture conversations.
