Skip to content

Billing and pricing

Azure Logic Apps Automation uses consumption-based pricing, so you pay based on the resources and capabilities that your automations use. Billing meters exist in the following groups:

  • Core platform meters that apply to every workflow.
  • Optional capabilities that incur charges only when a workflow uses them.

Core platform meters cover the managed environment, workflow execution, and run history storage required to host and run your automations.

ComponentMeterPriceHow charges work
Managed environmentEnvironment hour$0.042 per environment hourThis charge applies to each hour that a managed, customer-isolated environment is provisioned.
Workflow runtimeExecution second$0.00008 per execution secondThis charge applies to the core execution time per second for an automation app.

The default profile includes 1 virtual CPU (vCPU) of core compute and 2 gibibytes (GiB) of memory.

The runtime host is active while you author workflows in the portal.
Data retentionGB per month$0.12 per GB, per monthThis charge applies to the storage used for workflow run history. The platform keeps run history up to approximately 90 days.

Optional capabilities extend a workflow’s functionality with connectors, AI, managed knowledge bases, or isolated code execution in sandboxes. You incur these charges only when your automation uses the corresponding capability.

ComponentMeterPriceHow charges work
Standard managed connectorsConnector action$0.000125 per actionThis charge applies to each time that a workflow runs an action through a Standard managed connector.
Enterprise managed connectorsConnector action$0.001 per actionThis charge applies to Enterprise connector operations, including knowledge read and write transactions.
AI usageAzure Agent Credits (AACs)Charged as AACsThe platform converts AI usage to AACs. The number of AACs depends on the selected model and the tokens processed for AI-assisted authoring, agent reasoning, inference, embeddings, and other AI operations. For more information, see Azure OpenAI Service pricing.

Note: AI tokens are consumed by agents, the chat assistant, and knowledge bases. If you bring your own model, AI token usage isn’t charged through the platform.
Knowledge storageGB per month33 Azure Agent Credits (AACs) per GB, per month,
equivalent to $0.33 per GB per month
This charge applies to storage used by the managed knowledge layer.

Note: This pricing doesn’t include AI processing or connector transactions. The platform separately bills embeddings, inference, and transactions through AI usage and connector actions.
Sandbox - isolated code executionvCPU-second and GiB-second- $0.000024 per vCPU-second

- $0.000003 per GiB-second
These charges apply to compute and memory usage when custom code runs in an isolated sandbox.

The following example shows how charges from different meters contribute to the estimated monthly cost by using East US pricing in US dollars. These usage numbers are only illustrative estimates and don’t represent any recommended configuration or a typical customer workload.

Suppose an organization has the following monthly usage:

MeterUsageCalculationEstimated cost
Managed environment730 hours provisioned730 × $0.042$30.66
Automation app execution time150,000 execution seconds consumed.

Includes time for workflow execution and time for an active runtime during workflow authoring in the portal.
150,000 × $0.00008$12.00
Standard connector actions1,000 actions1,000 × $0.000125$0.125
Enterprise connector actions for knowledge base operations100 actions100 × $0.001$0.10
Data retention for workflow run history20 GB20 × $0.12$2.40
Knowledge storage5 GB5 × $0.33$1.65
Sandbox100 executions

For 10 seconds, each execution uses 1 vCPU and 2 GiB of memory.
Executions: 100 × 10 seconds × 1 vCPU × $0.000024

Memory: 100 × 10 seconds × 2 GiB × $0.000003
Executions: $0.024

Memory: $0.006
AI usageExcludedCharged as AACs, based on selected model and token consumptionAdditional AAC charges

Estimated monthly total, excluding AI usage: $46.97

The final bill might be higher or lower, based on an automation app’s total execution time, retained data, connector activity, AI usage, and sandbox resource consumption. For AI rates, see Azure OpenAI Service pricing.