Azure Logic Apps cost: Consumption per action vs Standard hosting

Quick answer

Logic Apps has two models. Consumption bills per action execution and per connector call, scaling to zero with no fixed cost, ideal for low-volume or spiky workflows. Standard runs on a dedicated hosting plan billed for allocated compute (like an App Service plan), which is cheaper at steady high volume and gives predictable performance. Match the model to how often and how much your workflows run.

Azure Logic Apps orchestrates workflows across services with connectors. It comes in two hosting models with very different pricing, and choosing the wrong one for your workflow volume is the common overspend, the same consumption-versus-provisioned decision as elsewhere.

Consumption: per action and connector call

The Consumption model bills per action executed in a workflow and per connector call (with standard and enterprise connectors priced differently), scaling to zero when idle with no fixed cost. A workflow that runs occasionally costs almost nothing; a high-frequency workflow with many actions per run accumulates per-action charges. It suits low-volume, spiky, or event-driven workflows.

Standard: dedicated hosting

Model	Bills for	Best when
Consumption	Per action + connector call, scales to zero	Low-volume, spiky workflows
Standard	Allocated hosting-plan compute	Steady, high-volume workflows

The Standard model runs on a dedicated hosting plan (similar to an App Service plan), billed for the allocated compute whether or not workflows run, and includes built-in connectors that avoid per-call charges. For steady, high-volume workflow processing, the fixed hosting cost is cheaper per execution than accumulating Consumption per-action charges, and it gives predictable performance and VNet integration.

Choosing and controlling cost

Use Consumption for low-volume, occasional, or event-driven workflows where scaling to zero avoids paying for idle capacity. Use Standard for steady, high-volume processing where the fixed hosting cost beats per-action charges. Within Consumption, reduce actions per workflow and prefer built-in over premium enterprise connectors where possible; within Standard, right-size the hosting plan. The crossover is the familiar spiky-versus-steady tradeoff, as in Azure Functions plans.

FAQ

How is Azure Logic Apps priced?

Two models: Consumption bills per action execution and per connector call, scaling to zero with no fixed cost, and Standard runs on a dedicated hosting plan billed for allocated compute (like an App Service plan) with built-in connectors that avoid per-call charges. Match the model to your workflow volume.

Consumption or Standard for Logic Apps?

Use Consumption for low-volume, occasional, or event-driven workflows, since it scales to zero and avoids paying for idle capacity. Use Standard for steady, high-volume processing, where the fixed hosting cost is cheaper per execution than accumulating per-action charges and gives predictable performance and VNet integration.

How do I reduce Logic Apps cost?

On Consumption, reduce the number of actions per workflow and prefer built-in over premium enterprise connectors where possible, since both actions and connector calls bill. On Standard, right-size the hosting plan to real workflow load. Choosing the model that matches your volume is the biggest lever.

Do connectors cost extra in Logic Apps?

On the Consumption model, yes, connector calls are billed, with standard and enterprise connectors priced differently (enterprise connectors cost more). The Standard model includes built-in connectors that avoid per-call charges, which is part of why it can be cheaper at high volume.

Does Consumption Logic Apps charge when idle?

No. The Consumption model bills per action execution and connector call and scales to zero, so an idle workflow costs nothing. This makes it ideal for occasional or event-driven workflows, unlike the Standard model, which bills for allocated hosting compute whether or not workflows run.

Does C3X estimate Logic Apps cost?

For the Standard model, C3X prices the hosting plan from your Terraform. For Consumption, cost depends on action and connector-call volume, which are usage inputs you model. Either way, you can compare the two models against your expected workflow volume.

What to do next

Compare Logic Apps models before you build. C3X reads your Terraform and prices your resources against a live catalog. Start with the quickstart.