Getting Started with Dedicated Workload profiles for Azure Container Apps

With Dedicated workload profiles, we can provision Container App environments with dedicated hardware, providing more resources to our Container Apps than Serverless workload profiles.

Will Velida
7 min readMay 1


About mid-April, the Azure Container Apps team announced a public preview of a new hosting plan and pricing structure for hosting your Container Apps. By default, there was a Serverless consumption hosting plan which you can use to host your Container Apps. This provided support for scale-to-zero scenarios and you’d only pay for resources that your application would use.

With the Dedicated hosting plan now in preview, you still have the option of having a fully managed environment for hosting your Container Apps with scale-to-zero capabilities, but in addition to this you can also run applications with customized hardware using Dedicated workload profiles.

In this blog post, I’ll dive into the details of dedicated workload profiles, what types of workload profiles that are available to us, what features come with dedicated workload profiles and how we can provision a dedicated workload profile in the Azure portal. (You can also deploy a Dedicated workload profile environment using the AZ CLI, but no support for Bicep yet!)

At the time of writing, this feature is currently in preview! That means features could change once it becomes generally available, so I’ll do my best to keep this article up-to-date (or give it a rewrite should it be required).

Let’s dive in!

Consumption vs Consumption + Dedicated plans

Before the preview hosting plan was released, you could only provision serverless Container App environments. With the ability to provision dedicated workload profiles alongside serverless workloads, we can use different workload profiles in our environments.

Depending on your application requirements, you can provision the following workload profiles:

  • Consumption — This is for apps that don’t need specific hardware to run. Since these are currently the default for…



Will Velida

Lead Software Engineer at Azenix | Ex-MSFT | International Conference Speaker. | GitHub: