# Azure Logic App

> Azure Logic Apps bill on two different meters: Consumption workflows charge per action execution, while Standard workflows pay for their hosting plan 24 hours a day whether any run fires. ZopNight discovers each app with its plan type via Resource Graph and attributes execution and hosting spend through Cost Management.

Source: https://zop.dev/integrations/azure/logic-app
Updated: 2026-08-19

---

Logic Apps run low-code integration workflows, billed per action execution (Consumption) or per hosting plan (Standard). Runaway trigger loops and abandoned Standard plans both leak money.

## Two billing models under one name

Consumption Logic Apps meter every action execution: each connector call, control-flow step, and trigger poll adds to the count, so cost tracks activity and a workflow that never fires costs nothing. Standard Logic Apps invert the model: workflows run on a dedicated hosting plan that bills continuously, like an App Service plan, whether the workflows on it execute constantly or were abandoned a quarter ago. The same product name therefore hides both a pure pay-per-use meter and a fixed reservation, and the waste patterns for each are opposites.

## Discovery through plan type and state

Discovered via Azure Resource Graph with plan type and state. Cost Management billing attributes execution and hosting spend, giving each workflow an actual cost trail for review of high-frequency or abandoned workflows. Logic Apps are not schedulable in ZopNight, because pausing a workflow risks dropping the events it exists to catch, so the platform's job for this type is discovery and cost visibility, making execution spend reviewable rather than switching anything off.

## Runaway triggers and abandoned Standard plans

On the Consumption side the classic leak is a runaway loop: a trigger polling every few seconds, or two workflows invoking each other, quietly multiplies action counts far beyond what the integration needs. On the Standard side the leak is inverted. A hosting plan that outlived its workflows keeps billing at its full rate with nothing meaningful deployed on it. A third pattern sits between the two: polling triggers configured at aggressive intervals for source data that changes once a day.

## Reviewing Logic Apps spend in the Azure portal

Azure portal → Logic apps lists every workflow with its plan type. For a Consumption app, the run history shows execution frequency at a glance; for a Standard app, follow the link to its hosting plan and check what else, if anything, that plan still hosts.