Each one gives Azure Container Apps an isolated boundary in its own VNet and can host Consumption as well as Dedicated workload profiles; its network setup can't be altered after creation.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Container Apps environments in context, with comparison tables and the common traps.
Terms in this definition
- Azure Container Apps
Container hosting built on KEDA where Azure runs the underlying cluster for you; apps scale automatically and can be zone-redundant.
- VNet
A private network belonging to a single subscription and region and covering all of that region's availability zones. A VM can only use a VNet located in the same region.
- Consumption
Serverless, event-driven Azure Functions hosting plan charged per execution; runs are capped at 10 minutes and VNet integration isn't available.
- Dedicated
Running Azure Functions on an App Service plan, which removes the execution time limit and offers VNet integration on Basic and higher tiers.
- Workload
Also called an experience: a Fabric toolset aimed at one job role, e.g. Data Factory, Data Engineering, Data Warehouse, Real-Time Intelligence or Power BI. Each keeps its data in OneLake.