Blog Azure Cloud Costs Infrastructure

Azure Logic Apps Pricing 2025 Explained: Consumption vs Standard 

You've created your Logic Apps resource, your workflows, and so forth, but now you’re still left with one question: “How is Azure Logic Apps pricing composed?”. 

Yes, Azure Logic Apps pricing can be confusing. Yet, it is essential to know which logic app to create, including their associated costs. 

In this article, we’ll discuss how much it cost to run Logic Apps, when to use Consumption versus Standard, and much more.

Let’s dive in!

Niels Kroeze

Author

Niels Kroeze IT Business Copywriter

Reading time 10 minutes Published: 25 April 2025

What are Azure Logic Apps? 

Azure Logic Apps is a cloud-based platform that automates workflows that connect data, services, systems and applications.  

Azure Logic Apps provides two main hosting options:  

  1. Consumption 
  2. Standard

Diagram illustrating Logic Apps consumption, standard, and a server, with associated graphs and cloud icon.

 

Azure Logic App Consumption Explained 

Azure Logic Apps consumption incurs costs based on trigger events, the number of workflow executions and the execution duration. It is a Pay-for-what-you-use pricing model. Charges are incurred for every action, each trigger, and each connected used in your workflow. 

While running in a multi-tenant environment, this plan also uses connectors to access SaaS apps and on-prem data sources.  

Consumption Logic Apps:

  • Are fully hosted in Microsoft Azure (no need to host it yourself!) 
  • Multi-tenant Azure hosted 
  • Fully managed and supported by Microsoft (no need to scale manually) 
  • Follow a serverless, pay-per-use model 

If your Logic App runs just a few times a month, you’re only charged for those executions, sometimes just fractions of a penny. But since you're in a multi-tenant environment, your Logic App might run along with other workloads. If workloads are heavy, they could impact performance.  

 

Azure Logic App Standard Explained 

Azure Logic Apps Standard runs workflows in a single-tenant environment, which is managed by Microsoft. The Standard Logic Apps run in what’s called an App Service Plan. Think of an App Service Plan like a virtual machine – it is semi-isolated but runs on shared hardware. In other words, your App Service Plans could still be running alongside other tenants. 

Standard Logic Apps: 

  • Run on shared hardware 
  • Data stays in the same region 
  • Pricing is based on the hosting plan 
  • Support for Vnets 

Here, data must always stay in the same region. As a result, you can’t have a single App Service Plan hosting Logic Apps across multiple regions. On a brighter note, App Service Plans support Virtual Networks (VNets). This is useful if you need tighter network control or integration with on-prem systems.

 

App Service Environment (ASE)

There’s also a more advanced scenario where you can opt for a more isolated environment using the App Service Environment (ASE). To do so, you must be on ASE v3.

This truly implies a single-tenant and isolated hosting which gives you full control and enhanced network security. Note that you must use a Vnet. 

 

Run Logic Apps in AKS

Azure Logic Apps can also run in Azure Kubernetes Service (AKS) through Azure Arc-enabled Logic Apps. This allows you to deploy and run single-tenant-based logic apps anywhere that Kubernetes can run.

This means you can deploy and manage them in AKS, on-premise, or even run them on other cloud providers.

 

Azure Logic App Pricing Models 

Azure Logic App Consumption Plan Pricing 

With Consumption, you pay for execution, meaning it is serverless. Each time a Logic App runs, Azure meters usage for triggers, actions, and connector calls. 

  Price per Execution
Actions First 4000 actions free - $0.000025 

Data retention: $0.12 GB/month 

As you can see in the table above, the first 4000 actions are free, which is great. Also, the price per execution is very low. The same is not true, however, for connectors. 

Azure connector costs are based on how many calls you make, with prices different from executions – with Enterprise Connectors being the most expensive. The table below breaks it down: 

  Price per Call
Standard Connector $0.000125
Enterprise Connector $0.001

Data retention: $0.12 GB/month 

Now, let’s take this into practice with some examples. Let us say you’d run a Logic App with 10,000 executions per day, each using 20 actions

Daily usage 

  • Logic App executions: 10,000 
  • Actions per execution: 20 
  • Total actions per day: 10,000 × 20 = 200,000 

However, the first 4000 actions are free, resulting in 196000 (200000-4000) actions to be paid.

196,000 × $0.000025 = $4.90 per day 

Logic Apps settings page, showing workflow plan, region, and action execution limit of 200,000 per day at a cost of $4.90.

Now, let’s finish by adding the connector cost. Assume the following:

  • 1 Standard Connector call per run 
  • 1 Enterprise Connector call per run 
  • Standard Connector: 10,000 × $0.000125 = $1.25 per day 
  • Enterprise Connector: 10,000 × $0.001 = $10.00 per day 

Total daily cost:  

  • Actions: $4.90 
  • Standard Connector: $1.25 
  • Enterprise Connector: $10.00 
  • Total $16.15 per day  

Estimated monthly cost (30 days): $16.15 × 30 = $484.50 

Learn more about Azure Logic Apps Consumption Pricing.

 

Azure Logic App Standard Plan Pricing 

So, what’s the pricing on Standard? Azure Logic Apps (Standard) can be hosted using two different pricing models:  

  1. Workflow Standard Plan (per vCPU/memory)  
  2. App Service Premium Plan (fixed monthly rate).  

Both options support Logic Apps but differ in how you’re charged and how resources are allocated.

 

Workflow Standard Plan

The workflow Standard Plan is a usage-based model. You’re billed hourly based on the actual resources your Logic App uses: 

Workflow Service Plan
  Price
vCPU $0.1972/hour
Memory $0.0141/hour

In addition to the base price: 

  • There are additional charges for storage and storage transactions. 
  • You still need to account for costs tied to managed connectors. 

If your workflows retain data (like inputs and outputs from run history), there's a storage cost of about $0.12 per GB per month.

This approach works well for containerised Logic Apps or cases where workloads vary, and you want billing to reflect actual consumption. It's flexible and ideal if you're scaling dynamically or deploying Logic Apps in isolated environments, such as with Azure Functions Premium or Azure Arc.

 

App Service Premium Plan

The App Service Premium Plan, on the other hand, uses a fixed monthly pricing model. So, you're essentially reserving dedicated resources for your Logic Apps. You pay a set amount per instance, depending on the selected tier, which varies by the number of virtual CPUs (vCPUs) and memory allocated. 

App Service Premium plan
Premium v3 Service Plan Cores RAM Storage Price
P0v3 1 4.00 GB 250 GB $123.37/month
P1 v3 2 8.00 GB 250 GB $246.74/month
P1mv3 2 16.00 GB 250 GB $272.728/month
P2 v3 4 16.00 GB 250 GB $493.48/month
P2mv3 4 32.00 GB 250 GB $545.456/month
P3 v3 8 32.00 GB 250 GB $986.96/month

 

App Service Premium Plan – OS (Linux)
Premium v3 Service Plan Cores RAM Storage Price
P0v3 1 4.00 GB 250 GB $64.97/month
P1 v3 2 8.00 GB 250 GB $129.94/month
P1mv3 2 16.00 GB 250 GB $155.928/month
P2 v3 4 16.00 GB 250 GB $259.88/month
P2mv3 4 32.00 GB 250 GB $311.856/month
P3 v3 8 32.00 GB 250 GB $519.76/month

 

Standard edition Logic Apps can use built-in connectors, which are a subset that runs in-process. Meaning that, they execute within the Logic App runtime itself. If you're running a Logic App locally (on-prem), these built-in connectors won’t call any external services.

However, many connectors are Microsoft-managed. These always call Microsoft-hosted API connectors, regardless of whether you're running the Logic App in Azure or locally. You will still incur managed connector charges in these cases.

  Price per Call
Standard Connector $0.000125
Enterprise Connector $0.001

One significant advantage of Standard over Consumption is that you don’t need an Integration Account to use schemas, maps, or .NET assemblies. 

In Consumption, adding those capabilities requires an Integration Account, which comes at a substantial cost. In Standard, it’s included at no extra cost.

 

App Service Environment (ASE v3) Pricing 

The ASE v3 (App Service Environment version 3) is another hosting option. It's a more isolated, single-tenant environment. Pricing for ASEv3 ranges from $240 to over $11,000 per month (depending on configuration). 

For comparison, the retired Integration Services Environment (ISE) cost around $5,000 more per month than ASE v3. We can say that ASE v3 offers a more cost-effective isolated hosting option than ISE used to.

Pricing Plan Key Features Best for Cost Factors Billing or pricing details
Consumption Plan
  • Pay-as-you-go pricing
  • Charges per action executed
  • Monthly free grant of actions
  • Variable workloads
  • Unpredictable usage
  • Getting started with Logic Apps 
 
  • Number of actions
  • Connector usage
  • Data retention 
 Pay per execution (pay for what you use)
Standard Plan
  • Fixed pricing for hosting
  • Lower per-action cost at scale
  • Supports VNets
 
  • High-throughput workflows
  • Consistent usage patterns 
  • App Service Plan tier
  • Action count
  • Connector usage 
Fixed pricing model with pre-determined pricing depending on the chosen hosting plan 
App Service Environment (ASE v3)
  • Fully isolated, single-tenant
  • Runs in your VNet
  • Greater control over infrastructure
 
  • Security-sensitive workloads
  • Large-scale enterprise apps 
 
  • Base cost: $240 to $11,000+/month
  • VNet and network setup
  • Plan tier 
You pay for the App Service plan, not per execution 

 

Azure Cost Management Whitepaper

Want to save on your monthly Azure cost?

Get our Azure Cost Management Whitepaper! With the best tips, tricks, and background knowledge to optimise your cloud costs.

Download for free!

What are the cost drivers of Azure Logic Apps? 

The following factors are the main cost drivers of Azure Logic Apps: 

  • Execution count: For Logic Apps with Consumption as plan, you’re billed per action executions. That is to say, every trigger, condition, loop or call to another system adds up. The more actions your workflow runs, the higher the costs. 
  • Connector types: Standard connectors are low-cost (or free). The same is not true, however, for Enterprise connectors which cost more per action. So, if your app uses more Enterprise connectors, you can expect higher costs. 
  • Integration account: You might need an integration account which is an extra monthly charge, depending on the tier (Basic, Standard, or Enterprise). 
  • Integration with other Azure (or third-party) services: If your Logic App calls Azure Functions, Service Bus, Storage, or external APIs, the usage of those services adds to your overall cost. These are billed separately from the Logic App itself but are triggered by it. 
  • Resource consumption and scaling: In Standard tier, the more workflows you run, the more CPU and memory you consume. This can lead to needing a larger or more premium App Service Plan. In Consumption, scaling happens automatically, but a higher volume of parallel executions still means more charges. 
  • Hybrid Connections or VNET Integration: If you use VNET integration or Hybrid Connections (e.g. accessing on-prem systems), those can come with extra setup and bandwidth costs. 
Rekenmachine

Azure Cost Scan

We'd like to help you make sense of your costs. Our in-house experts provide a professional savings recommendation, based on your current Azure cloud usage. 

Yes, I want it!

Best Practices 

Combine Consumption and Standard (if possible) 

There’s no reason a solution you build for an enterprise client can’t use both types of Logic Apps. You can definitely have a mix of Consumption and Standard. But note, they operate separately, meaning you can’t cross-deploy. 

Start with consumption 

If you're new to Logic Apps, begin with the Consumption model. It's easier to get started, ideal for hands-on learning, and perfectly fine for prototyping or building smaller solutions. 

Choose Standard for long-term or complex systems 

Consumption and Standard will both continue to exist, but newer features tend to arrive in Standard first. So, opt for Standard if you're building a complete, multi-year migration or a mission-critical system. 

Use the Logic Apps Storage calculator 

Estimate how many storage operations your workflow performs with the Azure Logic Apps Storage Calculator.

Start with a sample or your own workflow definition to get an operation count. Then put that into the Azure Pricing Calculator to estimate potential costs. 

Logic Apps pricing table showing various plan options, including workflows, connectors, and integration service environments, with associated costs.

Closing thoughts 

At the end of the day, you don’t have to pick one or the other. You can use both. Your environment can include a mix of Consumption and Standard Logic Apps.

The key is to understand when to use each based on your specific business scenario.

Think about your usage patterns and connectors and whether you have integration needs.  

Your overall cost may add up if you want to combine Logic Apps with other Azure Integration services such as Azure Service Bus or other services like Azure Functions, Azure Storage, etc. 

FAQ about Azure Logic Apps

Are Azure Logic Apps free?

What is the difference between Azure Logic Apps Consumption and Standard pricing?

Is there a minimum commitment or contract duration for Logic Apps pricing plans?

Marc Bosgoed

Get in Touch!

If you would like our support in implementing any of these measures, don’t hesitate to get in touch. We are here for you.