--- title: "Azure Logic Apps alternative: FlowRunner vs Azure Logic Apps" description: "FlowRunner bills one execution per run, however many steps, polls, loops, and retries it takes, and runs agents on your own keys. How it compares to Azure Logic Apps." url: https://flowrunner.ai/alternatives/azure-logic-apps date_published: 2026-11-02 date_modified: 2026-11-03T09:28:56-08:00 --- [Alternatives](https://flowrunner.ai/alternatives) / Azure Logic Apps ![Azure Logic Apps logo](https://flowrunner.ai/assets/alternatives/azure-logic-apps.svg) # Azure Logic Apps alternative: FlowRunner vs Azure Logic Apps FlowRunner bills one execution per run, however many steps, polls, loops, and retries it takes, and runs agents on your own keys. How it compares to Azure Logic Apps. 2026-11-02 Updated November 3, 2026 10 min ## Use FlowRunner when - You want one price per run, however many steps, trigger polls, loop iterations, and retries the workflow takes. - Operations people who don't work in the Azure portal need to build, read, and run the workflows. - Your agents should run on your own keys with Anthropic, OpenAI, Google, or another provider. - Approvals need to reach people by email, Slack, WhatsApp, phone, or a Form. - The workflow crosses SaaS apps more than it moves data between Azure services. ## Use Azure Logic Apps when - The workflow stays inside Azure and needs private networking or App Service Environment hosting. - You exchange EDI with trading partners through integration accounts. - You must run on your own Azure Arc-enabled Kubernetes cluster with your SQL Server. - You need FedRAMP High or Azure Government up to IL6. **TL;DR** - FlowRunner and Logic Apps both run integration workflows with triggers, connectors, branches, loops, retries, long-running steps, and now AI agent loops. FlowRunner bills one execution per run, however many steps, trigger polls, loop iterations, and retries it takes. - FlowRunner agents run on your own keys with any supported provider, call your other flows as tools, and can stop to ask a person by email, Slack, WhatsApp, phone, or a Form. - FlowRunner is a canvas operations teams build and run themselves, with unlimited users and no Azure subscription to set up first. You can also describe a flow in Claude, ChatGPT, Codex, or Cursor and have FlowRunner Prompt to Flow build it. - Logic Apps is stronger inside Azure: App Service Environment and hybrid hosting, B2B and EDI integration accounts, government clouds, and very low per-action prices. ## Who this comparison is for Your company runs on Azure, or Logic Apps came up because it’s already in the subscription. The work you want to automate is a business process: an order comes in, an agent checks it, a person approves the exception, three apps get updated. You want to know what that costs to run, who on your team can build and change it, and how a person gets pulled in when the agent isn’t sure. Start with what the two share. Both start workflows from schedules, webhooks, and app events, call connectors, branch, loop, retry, wait, and run AI agent loops. FlowRunner does all of that. Where they part is the meter, the builder, the models, and the way a person is brought into a run. Read them side by side and the shape is plain. ## What FlowRunner is good at FlowRunner’s tagline is “Agents That Ask.” An AI agent in FlowRunner can call your own flows as tools. When one of those flows needs a person, it sends the question by email, Slack, WhatsApp, phone, or a Form, and holds at an External Callback until the answer arrives. The agent waits without polling, then carries on with the answer and the context it had. That’s [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) the agent chooses at runtime. FlowRunner is strong on: - **One execution per run.** A run is one execution from start to finish, however many steps it has, however many times a loop goes around, and however long it waits. Retries inside the run don’t add executions. Free is 100 executions a month, Starter is $5 for 300 or $15 for 3,000, and Growth starts at $45 for 12,000, which works out to $0.00375 a run. - **A canvas the process owner can read.** Flows are built on a visual canvas, or from a chat: connect [FlowRunner Prompt to Flow](https://docs.flowrunner.ai/build/prompt-to-flow.html) to Claude, ChatGPT, Codex, or Cursor and describe what you want. Unlimited users and workflows on every plan, so the people who own the process can open it, read it, and run it. - **Agents on your keys, any provider.** With [BYOK](https://flowrunner.ai/concepts/byok) you pick a model from Anthropic, OpenAI, Google, or another supported provider, add your key, and pay the provider directly. No markup and no AI meter. - **Agents that call flows.** An AI agent can use your flows as tools, and the flow it calls can run anything a flow can, including a step that waits for a person. - **Approvals where people already are.** Email, Slack, WhatsApp, phone, or a [Form](https://docs.flowrunner.ai/platform/forms.html) with a public link that needs no sign-in. On every plan, including Free. - **The whole catalog on every plan.** 2,100+ integrations and 56,000+ callable actions (as of September 2026), all at the same price, including [Azure Service Bus](https://flowrunner.ai/integrations/azure-service-bus), [Azure Blob Storage](https://flowrunner.ai/integrations/azure-blob-storage), and [Azure OpenAI](https://flowrunner.ai/integrations/azure-openai). - **Compliance at published prices.** Audit trails and RBAC on Professional at $299 a month. A HIPAA Business Associate Agreement, SSO/SAML, and SLA tracking on Business at $999 a month. ## What Logic Apps is good at Logic Apps is Azure’s service for integration workflows. Its edges are Azure’s: - **Hosting choices inside Azure.** Multitenant Consumption, single-tenant Standard on a Workflow Service Plan or App Service Environment v3, or Hybrid on your own Azure Arc-enabled Kubernetes cluster with your SQL Server. The on-premises data gateway reaches data in your own network. - **B2B and EDI.** Integration accounts hold trading partners, agreements, schemas, and maps for EDI and XML processing, at $300 a month for Basic and $1,000 for Standard. - **Azure platform controls.** Access, sign-in, and the activity log come from Entra ID, Azure RBAC, and the Azure Activity Log, the same controls the rest of the subscription uses. - **Low per-action prices.** In East US, a built-in action is $0.000025 after the first 4,000 free, and a Standard connector action is $0.000125. - **Government clouds.** Logic Apps is in FedRAMP High and DoD IL2 scope in Azure public cloud, and up to IL6 in Azure Government Secret. ## Where FlowRunner is stronger - **A price per run, not a sum of meters.** Logic Apps Consumption bills each operation execution, “whether or not the overall workflow successfully runs, finishes, or is even instantiated.” A polling trigger is billed every time it checks, including checks that find nothing. Each action inside a loop is billed every cycle, so one action over 10 items is 11 executions. Each retry is billed too, so 5 retries count as 6. On top of that come three connector price classes (an Enterprise connector action costs eight times a Standard one), run history storage at $0.12 per GB-month, agent loop tokens, and integration accounts. Standard trades per-action billing for reserved compute that’s billed whether workflows run or not, about $175 a month for WS1 in Microsoft’s example, plus managed connector calls. Each price is small, but the bill follows the shape of the workflow: change a polling interval or a loop and the cost changes. FlowRunner gives you one number per run. - **Built by the people who own the process.** Logic Apps lives in an Azure subscription. You build in the Azure portal or in VS Code, inside a resource group, with Azure RBAC deciding who can see what. FlowRunner signup takes any real email address. The operations lead builds on the canvas or asks an AI tool to build it with FlowRunner Prompt to Flow, and every teammate can open the flow and its run history. - **Agents on any provider.** Logic Apps agent loops use models from Microsoft Foundry on Consumption, or Azure OpenAI, Foundry, or an API Management LLM API on Standard. Consumption agentic workflows are in preview and bill tokens at $1.80 per million input and $14.00 per million output. FlowRunner agents run on your own key with any supported provider, billed by that provider at your rate. - **Agents that call flows, including flows that ask a person.** In Logic Apps an agent can’t be added inline as a tool in another agent. In FlowRunner an agent calls your flows as tools. One of those flows can ask a person and wait, so the agent pauses on its own judgment and picks up with the answer. - **Approvals beyond Outlook.** The approval action Logic Apps documents is the Office 365 Outlook connector’s Send approval email. It needs a work or school account, and actionable messages work only for single-user mailboxes. Logic Apps’ conversational agent workflows talk to a person in a chat. FlowRunner asks by email, Slack, WhatsApp, phone, or a Form with a public link, on every plan, as a step the agent can call. - **One catalog, one price.** Logic Apps lists 1,400+ connectors, split into built-in, Standard, and Enterprise classes with different prices. FlowRunner’s 2,100+ integrations are all included in the run, on every plan. ## Where Logic Apps is stronger - **Azure-native hosting and networking.** App Service Environment v3, Hybrid on your own Arc-enabled Kubernetes with your SQL Server, the on-premises data gateway, and Entra ID and Azure RBAC from the platform. For integration that moves data between Azure services inside your network, that’s the natural home. For a business process that crosses SaaS apps and needs people, those same choices are infrastructure your team has to run, and FlowRunner runs it for you, with a self-hosted option on Enterprise. - **B2B and EDI.** Integration accounts give you trading partners, agreements, and EDI processing built in. If EDI is one step of a bigger process, keep that step in a logic app and call its Request trigger from a FlowRunner [HTTP Request](https://docs.flowrunner.ai/reference/http-request.html) block, while the agent, the approvals, and the other apps run in FlowRunner. - **Price per action.** $0.000025 for a built-in action and $0.000125 for a Standard connector action are low numbers. The count behind them includes every skipped poll, every loop iteration, and every retry, and Standard bills its reserved compute whether or not anything runs, so you forecast a sum of meters. FlowRunner gives you the price of a run. - **Government clouds.** FedRAMP High, DoD IL2, and up to IL6 in Azure Government Secret. If your workflows must run in a US government cloud, that decides it. If the requirement is audit trails, access control, and a HIPAA BAA, FlowRunner Business has all of it at a published $999 a month, without an Azure subscription. ## Starting free FlowRunner Free is a permanent plan at $0: 100 executions a month, every integration, AI agents on your own keys, human-in-the-loop, unlimited users and workflows, one concurrent run, and 24 hours of log history. Every new account starts with 14 days of Professional, with no card, and then moves to Free with its flows still running. Logic Apps has no free plan. On Consumption, the first 4,000 built-in actions per Azure subscription are free, and Azure’s free account credit applies. Standard connector calls, Enterprise connector calls, run history storage, and agent tokens are billed from the first one, and you need an Azure subscription to start. ## Feature comparison | Dimension | FlowRunner | Azure Logic Apps | | --- | --- | --- | | Billing unit | Execution (one complete run) | Each operation execution (Consumption); reserved vCPU and memory plus connector calls (Standard) | | Trigger polls that find nothing | Not billed; only runs count | Billed, even when skipped | | Loops | Included in the run | Each action billed every cycle | | Retries | Included in the run | Each retry billed (5 retries = 6 executions) | | Connector pricing | Every integration, same price | Built-in $0.000025, Standard $0.000125, Enterprise $0.001 per action | | Free allowance | Free plan, 100 executions a month, permanent | First 4,000 built-in actions per subscription | | Paid entry | Starter $5 a month | Pay per action; Standard WS1 about $175 a month in Microsoft’s example | | Who builds | Canvas, or a chat with FlowRunner Prompt to Flow | Azure portal or VS Code, in an Azure subscription | | Users | Unlimited, every plan | Access through Azure RBAC | | AI agents | AI Agent block on your own key, any supported provider | Agent loops on Microsoft Foundry or Azure OpenAI; Consumption in preview | | Model cost | Paid to your provider, no markup | Consumption: $1.80 per 1M input, $14.00 per 1M output tokens; Standard: model usage only | | Agent calls other flows | Yes, flows as agent tools | An agent can’t be added inline as a tool in another agent | | Human-in-the-loop | Agent calls an approval flow as a tool, every plan | Outlook Send approval email; conversational agent workflows | | Approval channels | Email, Slack, WhatsApp, phone, or a Form | Outlook (work or school account) | | Longest run | Waits up to 30 days on Free, Starter, and Growth; 1 year on Professional and up | 90 days default, configurable 7 to 365 days (Consumption) | | MCP | Agents use tools from registered MCP servers | Standard workflows exposed as MCP servers | | Integrations | 2,100+ integrations, 56,000+ actions | 1,400+ connectors in three price classes | | Where it runs | FlowRunner cloud; self-hosted option on Enterprise | Azure multitenant, single-tenant, or hybrid on Arc-enabled Kubernetes | | Audit and access | Audit trails and RBAC on Professional ($299); SSO/SAML and a HIPAA BAA on Business ($999) | Entra ID, Azure RBAC, Activity Log | | FedRAMP and government clouds | No | FedRAMP High, DoD IL2, up to IL6 in Azure Government Secret | ## Decision framework **Pick FlowRunner if:** - You want a price per run you can read off the pricing page, instead of a sum of per-action, per-poll, per-retry, storage, and token meters. - The people who own the process, not only Azure engineers, need to build, change, and run it. - Your agents should run on your own keys, with any supported provider, and call other flows as tools. - Approvals need to reach people by email, Slack, WhatsApp, phone, or a Form, including people outside your tenant. - The workflow crosses SaaS apps more than it moves data between Azure services. **Pick Logic Apps if:** - The workflow stays inside Azure and needs App Service Environment hosting or private networking. - You exchange EDI with trading partners through integration accounts. - You have to run on your own Arc-enabled Kubernetes cluster with your SQL Server. - You need FedRAMP High or Azure Government up to IL6. ## Ready to move? [How to move from Azure Logic Apps to FlowRunner](https://flowrunner.ai/alternatives/azure-logic-apps/migrate) covers exporting the workflow JSON from code view, an ARM template, or a Standard logic app, the request to paste into your AI tool with FlowRunner Prompt to Flow connected, and what to set up by hand. For a larger move, [contact us](https://flowrunner.ai/contact). ## Frequently asked questions ### How is Azure Logic Apps priced? Consumption logic apps bill each operation execution. In East US, built-in actions are $0.000025 each after the first 4,000 free per subscription, Standard connector actions are $0.000125, and Enterprise connector actions are $0.001, plus run history storage at $0.12 per GB-month and agent loop tokens. Standard logic apps bill reserved vCPU and memory whether or not workflows run, plus managed connector calls; Microsoft's example puts a WS1 plan at about $175 a month. FlowRunner bills one execution per complete run, with a Free plan at $0 and paid plans from $5 a month. ### Does Logic Apps bill trigger polls that find nothing? Yes. Microsoft's pricing page says a polling trigger's call is metered and billed whether the trigger fires or is skipped. Each action inside a loop is billed every cycle, and each retry is billed as another execution, so an action with 5 retries counts as 6. In FlowRunner, only runs count, and a run is one execution however many steps, loop iterations, and retries it takes. ### Does Azure Logic Apps have AI agents? Yes. Logic Apps agentic workflows run agent loops, autonomous or conversational, with models from Microsoft Foundry on Consumption or Azure OpenAI, Foundry, or an APIM LLM API on Standard. Consumption agentic workflows are in preview and bill tokens. FlowRunner agents run on your own key with Anthropic, OpenAI, Google, or another supported provider, with no markup, and an agent can call your other flows as tools, including one that waits for a person. ### Can Logic Apps send approvals? Yes. The Office 365 Outlook connector's Send approval email action waits for the approver's choice, and a Condition then branches on it. The connector needs a work or school account, and actionable messages work only for single-user mailboxes. FlowRunner sends approvals by email, Slack, WhatsApp, phone, or a Form with a public link, on every plan, and an AI agent can call the approval flow as a tool. ### How long can a Logic Apps run last? A Consumption run lasts 90 days by default and can be set anywhere from 7 to 365 days. Standard stateful workflows default to 90 days, and stateless workflows run up to 5 minutes. A FlowRunner run can wait up to 30 days on Free, Starter, and Growth, and up to a year on Professional and above. ### Does FlowRunner work with Azure services? Yes. FlowRunner's catalog includes [Azure Service Bus](https://flowrunner.ai/integrations/azure-service-bus), [Azure Blob Storage](https://flowrunner.ai/integrations/azure-blob-storage), Azure Cosmos DB, [Azure OpenAI](https://flowrunner.ai/integrations/azure-openai), and [Azure AI Foundry](https://flowrunner.ai/integrations/azure-ai-foundry), alongside 2,100+ integrations in total. A FlowRunner flow can also call a logic app's Request trigger with an [HTTP Request](https://docs.flowrunner.ai/reference/http-request.html) block, so a step that has to stay in Azure can stay there. ### Can I move logic apps to FlowRunner? Yes. Copy the workflow definition from code view, generate an ARM template, or download a Standard logic app's content, then let FlowRunner Prompt to Flow read the JSON and build the same workflow as a FlowRunner flow. You reconnect accounts, fill in secrets, and test. Follow [How to move from Azure Logic Apps to FlowRunner](https://flowrunner.ai/alternatives/azure-logic-apps/migrate). ## Keep reading - [How to move from Azure Logic Apps to FlowRunner](https://flowrunner.ai/alternatives/azure-logic-apps/migrate) - [FlowRunner vs Power Automate](https://flowrunner.ai/alternatives/power-automate) - [FlowRunner vs MuleSoft](https://flowrunner.ai/alternatives/mulesoft) - [FlowRunner vs Copilot Studio](https://flowrunner.ai/alternatives/copilot-studio) [All alternatives](https://flowrunner.ai/alternatives) By [Mark Piller](https://flowrunner.ai/about#mark-piller), Founder of FlowRunner [Editorial policy](https://flowrunner.ai/editorial-policy) > _I like that aspect of the human in the loop when it's needed. That's ultimately what we need to get to._ VP Operations, CPG brand --- Markdown version of https://flowrunner.ai/alternatives/azure-logic-apps. Site index: https://flowrunner.ai/llms.txt