Azure Container Apps: Workload Profiles v2 Is Now the Default — What You Need to Know

Azure Container Apps just made a significant change that affects every developer creating new environments. As of January 2026, Workload Profiles (v2) is now the default environment type , replacing the legacy Consumption-only (v1) model. This isn't just a version bump — it's a fundamental shift in how Container Apps environments work, and it brings substantial benefits for production workloads. In this post, I'll break down what changed, why it matters, and how to take advantage of the new capabilities. What Changed? When you create a new Azure Container Apps environment, you now get a Workload Profiles (v2) environment by default. The previous Consumption-only (v1) environment is now considered legacy . Here's the key distinction: Consumption-only (v1) : A single serverless tier where all apps run on shared, pay-per-use infrastructure Workload Profiles (v2) : A flexible architecture supporting multiple profile types — Consumption, Dedicated, and the new Flexible profile — within the