| ms.service | azure-logic-apps |
|---|---|
| ms.topic | include |
| author | ecfan |
| ms.author | estfan |
| ms.date | 11/18/2025 |
| Hosting option | Benefits | Resource sharing and usage | Pricing and billing model | Limits management |
|---|---|---|---|---|
| Consumption Host environment: Multitenant Azure Logic Apps |
- Easiest to get started - Pay for what you use - Fully managed |
A single logic app resource can have only one workflow. All logic apps across Microsoft Entra tenants share the same processing (compute), storage, network, and so on. Note: Regarding data residency and redundancy: - In workflows or workflow sections that don't interact with agents, the data is replicated in the paired region. For high availability, geo-redundant storage (GRS) is enabled. - Any agents in a workflow use an Azure OpenAI model that can originate from any region, so data residency isn't guaranteed for data that the model handles. |
Consumption (pay-per-execution) | Azure Logic Apps manages the default values for these limits, but you can change some of these values, if that option exists for a specific limit. |
| Standard (Workflow Service Plan) Host environment: Single-tenant Azure Logic Apps |
- More built-in connectors hosted on the single-tenant runtime for higher throughput and lower costs at scale - More control and fine-tuning capability around runtime and performance settings - Integrated support for virtual networks and private endpoints. - Create your own built-in connectors. |
A single logic app resource can have multiple stateful and stateless workflows. Workflows in a single logic app and tenant share the same processing (compute), storage, network, and so on. Data stays in the same region where you deploy your logic app. |
Standard, based on a hosting plan with a selected pricing tier. If you run stateful workflows, which use external storage, the Azure Logic Apps runtime makes storage transactions that follow Azure Storage pricing. |
You can change the default values for many limits, based on your scenario's needs. Important: Some limits have hard upper maximums. In Visual Studio Code, the changes you make to the default limit values in your logic app project configuration files won't appear in the designer experience. For more information, see Edit app and environment settings for logic apps in single-tenant Azure Logic Apps. |
| Standard (App Service Environment v3) Host environment: App Service Environment v3 (ASEv3) - Windows plans only |
Same capabilities as single-tenant plus the following benefits: - Fully isolate your logic apps. - Create and run more logic apps than in single-tenant Azure Logic Apps. - Pay only for the ASE App Service plan, no matter the number of logic apps that you create and run. - Can enable autoscaling or manually scale with more virtual machine instances or a different App Service plan. - Inherit the network setup from the selected ASEv3. For example, when you deploy to an internal ASE, workflows can access the resources in a virtual network associated with the ASE and have internal access points. Note: If accessed from outside an internal ASE, run histories for workflows in that ASE can't access action inputs and outputs. |
A single logic app can have multiple stateful and stateless workflows. Workflows in a single logic app and tenant share the same processing (compute), storage, network, and so on. Data stays in the same region where you deploy your logic apps. |
App Service plan | You can change the default values for many limits, based on your scenario's needs. Important: Some limits have hard upper maximums. In Visual Studio Code, the changes you make to the default limit values in your logic app project configuration files won't appear in the designer experience. For more information, see Edit app and environment settings for logic apps in single-tenant Azure Logic Apps. |
| Standard (Hybrid) Host environment: Your own on-premises infrastructure |
- Scenarios where you need to control, and manage your own infrastructure. - Capabilities that let you build and host integration solutions for partially connected environments that require local processing, storage, and network access. - Supports infrastructure that can include on-premises systems, private clouds, and public clouds. - Workflows are powered by the Azure Logic Apps runtime, which is hosted on premises as part of an Azure Container Apps extension. For more information, see the following articles: - Set up your own infrastructure for Standard logic apps using hybrid deployment - Create Standard logic app workflows for hybrid deployment on your own infrastructure |
A single logic app can have multiple stateful and stateless workflows. Workflows in a single logic app and tenant share the same processing (compute), storage, network, and so on. Data stays in the same region where you deploy your logic apps. |
Hybrid pricing | You can change the default values for many limits, based on your scenario's needs. Important: Some limits have hard upper maximums. In Visual Studio Code, the changes you make to the default limit values in your logic app project configuration files won't appear in the designer experience. For more information, see Edit app and environment settings for logic apps in single-tenant Azure Logic Apps. |