azurerm_logic_app_workflow cost estimation

An azurerm_logic_app_workflow is a workflow on the Logic Apps Consumption plan — pay-per-execution serverless integration. Cost is per action: built-in actions run ~$0.000025 each (after a monthly free grant), connector actions cost more, and triggers count as actions. 1M built-in actions is ~$25/month. There's no standing fee — an idle workflow costs nothing.

This is the opposite cost model from the Standard plan (azurerm_logic_app_standard), which bills a flat hourly plan fee regardless of usage. Consumption is cheaper for low-to-moderate or bursty workflows where you'd rather not pay for idle capacity; Standard wins for high, steady volume or when you need VNet integration and predictable performance.

The cost driver is action count, so the levers are about doing fewer billed actions: avoid unnecessary steps, use built-in actions (cheaper) over premium connectors where possible, and don't poll on tight trigger intervals (each poll is a billed trigger evaluation). Batch processing where you can so one run handles more work.

c3x prices the workflow from monthly action volume as usage, so projected cost can be modelled.

Terraform example

A minimal but realistic configuration that C3X can estimate.

resource "azurerm_logic_app_workflow" "orders" {
  name                = "process-orders"
  location            = azurerm_resource_group.main.location
  resource_group_name = azurerm_resource_group.main.name
}

Pricing dimensions

What you actually pay for when you provision azurerm_logic_app_workflow.

Dimension	Unit	What's being charged
Actions	per action	Built-in actions ~$0.000025 each (after a free grant); connector actions cost more; triggers count as actions. No standing fee. $0.000025/built-in action → 1M actions ≈ $25/month

Sample C3X output

1M built-in actions in a month:

azurerm_logic_app_workflow.orders
└─ Actions (1M built-in)   1,000,000 actions   $25.00
                           Monthly             $25.00

Optimization tips

Common ways to reduce azurerm_logic_app_workflow cost without changing the workload.

Use Consumption for bursty/low-volume workflows

The whole plan fee vs Standard for low volume

Consumption has no standing fee and scales to zero, so it's cheaper than the flat-rate Standard plan for occasional or low-throughput workflows. Reserve Standard for high, steady volume or VNet needs.

Minimize action count

Proportional to actions removed

Cost is per action. Trim unnecessary steps, prefer built-in actions over premium connectors where possible, and batch work so one run does more — each billed action adds up at high volume.

Don't poll on tight trigger intervals

Per avoided trigger evaluation

Polling triggers count each evaluation as a billed action. Widen polling intervals or use event/webhook triggers so you're not paying for empty polls.

FAQ

How is a Consumption Logic App billed?

Per action executed — built-in actions ~$0.000025 each (after a free grant), connector actions more, triggers count as actions — with no standing fee. 1M built-in actions is ~$25/month. An idle workflow costs nothing.

Consumption or Standard Logic App?

Consumption (pay-per-action, scales to zero) for bursty or low-volume workflows; Standard (flat hourly plan fee) for high, steady volume or when you need VNet integration and predictable performance. The crossover is action volume.

How does c3x estimate the cost?

It's usage-driven, so c3x models it from monthly action volume in c3x-usage.yml. There's no standing fee to price.

Related resources

Azure

azurerm_logic_app_standard

The flat-rate Standard plan — cheaper for high steady volume

`azurerm_logic_app_workflow` cost estimation