Clarify ASEv3 limitations

Author: ecfan

articles/logic-apps/single-tenant-overview-compare.md

@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: conceptual
-ms.date: 04/04/2022
+ms.date: 04/26/2022
 ms.custom: ignite-fall-2021
 ---
 
@@ -34,7 +34,7 @@ The following table briefly summarizes differences between the **Logic App (Stan
 
 ## Logic App (Standard) resource
 
-The **Logic App (Standard)** resource type is powered by the redesigned single-tenant Azure Logic Apps runtime. This runtime uses the [Azure Functions extensibility model](../azure-functions/functions-bindings-register.md) and is hosted as an extension on the Azure Functions runtime. This design provides portability, flexibility, and more performance for your logic app workflows plus other capabilities and benefits inherited from the Azure Functions platform and Azure App Service ecosystem. For example, you can create, deploy, and run single-tenant based logic apps and their workflows in [Azure App Service Environment v3](../app-service/environment/overview.md).
+The **Logic App (Standard)** resource type is powered by the redesigned single-tenant Azure Logic Apps runtime. This runtime uses the [Azure Functions extensibility model](../azure-functions/functions-bindings-register.md) and is hosted as an extension on the Azure Functions runtime. This design provides portability, flexibility, and more performance for your logic app workflows plus other capabilities and benefits inherited from the Azure Functions platform and Azure App Service ecosystem. For example, you can create, deploy, and run single-tenant based logic apps and their workflows in [Azure App Service Environment v3 (Windows plans only)](../app-service/environment/overview.md).
 
 The Standard resource type introduces a resource structure that can host multiple workflows, similar to how an Azure function app can host multiple functions. With a 1-to-many mapping, workflows in the same logic app and tenant share compute and processing resources, providing better performance due to their proximity. This structure differs from the **Logic App (Consumption)** resource where you have a 1-to-1 mapping between a logic app resource and a workflow.
 
@@ -49,7 +49,7 @@ To learn more about portability, flexibility, and performance improvements, cont
 
 ### Portability and flexibility
 
-When you create logic apps using the **Logic App (Standard)** resource type, you can deploy and run your workflows in other environments, such as [Azure App Service Environment v3](../app-service/environment/overview.md). If you use Visual Studio Code with the **Azure Logic Apps (Standard)** extension, you can *locally* develop, build, and run your workflows in your development environment without having to deploy to Azure. If your scenario requires containers, [create single-tenant based logic apps using Azure Arc-enabled Logic Apps](azure-arc-enabled-logic-apps-create-deploy-workflows.md). For more information, review [What is Azure Arc enabled Logic Apps?](azure-arc-enabled-logic-apps-overview.md)
+When you create logic apps using the **Logic App (Standard)** resource type, you can deploy and run your workflows in other environments, such as [Azure App Service Environment v3 (Windows plans only)](../app-service/environment/overview.md). If you use Visual Studio Code with the **Azure Logic Apps (Standard)** extension, you can *locally* develop, build, and run your workflows in your development environment without having to deploy to Azure. If your scenario requires containers, [create single-tenant based logic apps using Azure Arc-enabled Logic Apps](azure-arc-enabled-logic-apps-create-deploy-workflows.md). For more information, review [What is Azure Arc enabled Logic Apps?](azure-arc-enabled-logic-apps-overview.md)
 
 These capabilities provide major improvements and substantial benefits compared to the multi-tenant model, which requires you to develop against an existing running resource in Azure. Also, the multi-tenant model for automating **Logic App (Consumption)** resource deployment is completely based on Azure Resource Manager templates (ARM templates), which combine and handle resource provisioning for both apps and infrastructure.
 

includes/logic-apps-resource-environment-differences-table.md

@@ -3,13 +3,13 @@ ms.service: logic-apps
 ms.topic: include
 author: ecfan
 ms.author: estfan
-ms.date: 10/05/2021
+ms.date: 04/26/2022
 ---
 
 | Resource type | Benefits | Resource sharing and usage | [Pricing and billing model](../articles/logic-apps/logic-apps-pricing.md) | [Limits management](../articles/logic-apps/logic-apps-limits-and-config.md) |
 |---------------|----------|----------------------------|---------------------------------------------------------------------------|-----------------------------------------------------------------------------|
 | **Logic App (Consumption)** <p><p>Host environment: Multi-tenant Azure Logic Apps | - Easiest to get started <p><p>- Pay-for-what-you-use <p><p>- Fully managed | A single logic app can have *only one* workflow. <p><p>Logic apps created by customers *across multiple tenants* share the same processing (compute), storage, network, and so on. | [Consumption](../articles/logic-apps/logic-apps-pricing.md#consumption-pricing) (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. |
 | **Logic App (Consumption)** <p><p>Host environment: <br>[Integration service environment (ISE)](../articles/logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md) | - Enterprise scale for large workloads <p><p>- 20+ ISE-specific connectors that connect directly to virtual networks <p><p>- Predictable pricing with included usage and customer-controlled scaling <p><p>- Data stays in the same region where you deploy the ISE. | A single logic app can have *only one* workflow. <p><p>Logic apps *in the same environment* share the same processing (compute), storage, network, and so on. | [ISE](../articles/logic-apps/logic-apps-pricing.md#ise-pricing) (fixed) | 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. |
 | **Logic App (Standard)** <p><p>Host environment: <br>Single-tenant Azure Logic Apps <p><p>**Note**: If your scenario requires containers, [create single-tenant based logic apps using Azure Arc enabled Logic Apps](../articles/logic-apps/azure-arc-enabled-logic-apps-create-deploy-workflows.md). For more information, review [What is Azure Arc enabled Logic Apps?](../articles/logic-apps/azure-arc-enabled-logic-apps-overview.md) | - Run using the single-tenant Azure Logic Apps runtime. Deployment slots are currently not supported. <p><p>- More built-in connectors for higher throughput and lower costs at scale <p>- More control and fine-tuning capability around runtime and performance settings <p>- Integrated support for virtual networks and private endpoints. <p>- Create your own built-in connectors. <p><p>- Data stays in the same region where you deploy your logic apps. | A single logic app can have multiple [*stateful* and *stateless*](../articles/logic-apps/single-tenant-overview-compare.md#stateful-stateless) workflows. <p><p>Workflows *in a single logic app and tenant* share the same processing (compute), storage, network, and so on. | [Standard](../articles/logic-apps/logic-apps-pricing.md#standard-pricing), based on a hosting plan with a selected pricing tier. <p>If you run *stateful* workflows, which use [external storage](../articles/azure-functions/storage-considerations.md#storage-account-requirements), the Azure Logic Apps runtime makes storage transactions that follow [Azure Storage pricing](https://azure.microsoft.com/pricing/details/storage/). | You can change the default values for many limits, based on your scenario's needs. <p><p>**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](../articles/logic-apps/edit-app-settings-host-settings.md). |
-| **Logic App (Standard)** <p><p>Host environment: <br>[App Service Environment v3 (ASEv3)](../articles/app-service/environment/overview.md) | Same capabilities as single-tenant *plus* the following benefits: <p>- Fully isolate your logic apps. <p>- Create and run more logic apps than in single-tenant Azure Logic Apps. <p>- Pay only for the ASE App Service plan, no matter the number of logic apps that you create and run. <p>- Can enable autoscaling or manually scale with more virtual machine instances or a different App Service plan. <p><p>- Data stays in the same region where you deploy your logic apps. <p>- Inherit the network setup from the selected ASEv3. For example, when deployed to an internal ASE, workflows can access the resources in a virtual network associated with the ASE and have internal access points. <p>**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*](../articles/logic-apps/single-tenant-overview-compare.md#stateful-stateless) workflows. <p><p>Workflows *in a single logic app and tenant* share the same processing (compute), storage, network, and so on. | [App Service plan](https://azure.microsoft.com/pricing/details/app-service/windows/) | You can change the default values for many limits, based on your scenario's needs. <p><p>**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](../articles/logic-apps/edit-app-settings-host-settings.md). |
+| **Logic App (Standard)** <p><p>Host environment: <br>[App Service Environment v3 (ASEv3) - Windows plans only](../articles/app-service/environment/overview.md) | Same capabilities as single-tenant *plus* the following benefits: <p>- Fully isolate your logic apps. <p>- Create and run more logic apps than in single-tenant Azure Logic Apps. <p>- Pay only for the ASE App Service plan, no matter the number of logic apps that you create and run. <p>- Can enable autoscaling or manually scale with more virtual machine instances or a different App Service plan. <p><p>- Data stays in the same region where you deploy your logic apps. <p>- Inherit the network setup from the selected ASEv3. For example, when deployed to an internal ASE, workflows can access the resources in a virtual network associated with the ASE and have internal access points. <p>**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*](../articles/logic-apps/single-tenant-overview-compare.md#stateful-stateless) workflows. <p><p>Workflows *in a single logic app and tenant* share the same processing (compute), storage, network, and so on. | [App Service plan](https://azure.microsoft.com/pricing/details/app-service/windows/) | You can change the default values for many limits, based on your scenario's needs. <p><p>**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](../articles/logic-apps/edit-app-settings-host-settings.md). |
 ||||||