Boundary that groups Azure Container Apps for security, isolation and networking; decisions about workload profiles versus Consumption only, a custom VNet, and internal or external access can't be changed after creation.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Container Apps environment 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.
- ACID
Four promises a database transaction makes: atomicity, consistency, isolation and durability. Azure Cosmos DB honours them, with snapshot isolation, only inside one logical partition, using stored procedures, triggers or transactional batch.
- 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.
- Consumption
Serverless, event-driven Azure Functions hosting plan charged per execution; runs are capped at 10 minutes and VNet integration isn't available.
- 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.
- Internal
The API Management VNet mode where the gateway can be reached solely through a private IP address.
- External
API Management virtual network mode in which the gateway stays public but can call private back ends inside the VNet.
Related terms
- Accessibility level
Whether a Container Apps environment is reachable publicly or only privately, fixed when the environment is made. With external, its virtual IP sits on a public address; with internal, an internal load balancer in your own virtual network holds it.
- Consumption-only environment
Legacy v1 type of Container Apps environment limited to the Consumption plan. If you bring your own VNet, the subnet can't be delegated and needs a size of /23 or bigger.
- Container Apps hosting
Deploying a function app as a container into a Container Apps environment, where it runs next to other microservices yet still uses the Functions programming model. Container Apps, not Functions, looks after scaling and revisions.
- Container Apps workload profiles
The default Container Apps environment type, offering Consumption and Dedicated profiles on a subnet of at least /27; unlike the legacy Consumption-only type (/23), it supports UDRs, private endpoints and NAT Gateway egress.