Workload profiles (v2) is now the default environment type when creating new Azure Container Apps environments!

What's Changing?

When you create a new Container Apps environment, you'll now get the Workload profiles (v2) environment type by default. The previous Consumption-only (v1) environment type is now considered legacy. At the point of this announcement the default transition has been implemented for bring-your-own-VNet environments only. V1 environments which use a managed VNet will continue to function as before for now.

Key Benefits of Workload Profiles (v2)

• Same Price: More functionality
• Flexibility: Supports both Consumption and Dedicated plans in a single environment
• Improved Networking: Access to enhanced networking features including:
  • User-defined routes (UDR)
  • Egress through NAT Gateway
  • Private endpoints
• GPU Support: Access to GPU workload profiles for AI/ML workloads
• Smaller Subnet Requirements: Requires only a /27 CIDR range (vs /23 for Consumption-only)
• Future-Proof: Easily add dedicated resources to your environment as your needs grow

What This Means for You

New Environments

• No action required – new environments will automatically use Workload profiles (v2)
• The --enable-workload-profiles flag is no longer needed when creating environments via CLI
• Simply use: az containerapp env create --name <NAME> --resource-group <RG> --location <LOCATION>

Existing Environments

• Existing Consumption-only (v1) environments continue to work without any changes
• You can continue to use your existing environments as-is

Need Consumption Pricing?

If you need consumption-based pricing, use the built-in consumption workload profile in a Workload profiles (v2) environment. This gives you:

• Pay-per-use pricing with scale-to-zero
• The flexibility to add dedicated resources later if needed
• Access to improved networking features

FAQ

Q: Will my existing Consumption-only environments stop working?
A: No, existing environments will continue to function. However, for new environments, we recommend using the default Workload profiles (v2) type.

Q: Do I need to migrate my existing Consumption-only environments?
A: Migration is not required, but recommended for new projects to take advantage of the improved features.

Q: What happened to the --enable-workload-profiles flag?
A: This flag is no longer necessary since workload profiles are now enabled by default.

Learn More

• Compute and billing structures in Azure Container Apps
• Consumption-only environment type (legacy)
• Workload profiles overview
• Billing in Azure Container Apps