Azure Container Apps hardware reference
Workload profiles in Azure Container Apps run on specialized hardware with specific restrictions. Use the following information to help you select the workload profile most appropriate for your application.
Image size limit
The amount of disk space available to your application varies based on the associated workload profile. Available disk space determines the image size limit you can deploy to your container apps.
For dedicated workload profiles, the image size limit is per instance.
| Display name | Name | Image Size Limit (GB) |
|---|---|---|
| Consumption | consumption | 8* |
| Dedicated-D4 | D4 | 90 |
| Dedicated-D8 | D8 | 210 |
| Dedicated-D16 | D16 | 460 |
| Dedicated-D32 | D32 | 940 |
| Dedicated-E4 | E4 | 90 |
| Dedicated-E8 | E8 | 210 |
| Dedicated-E16 | E16 | 460 |
| Dedicated-E32 | E32 | 940 |
| Dedicated-NC24-A100 (preview) | NC24-A100 | 210 |
| Dedicated-NC48-A100 (preview) | NC48-A100 | 460 |
| Dedicated-NC96-A100 (preview) | NC96-A100 | 940 |
* The image size limit for a consumption workload profile is a shared among both image and app. For example, logs used by your app are subject to this size limit.
For more information on differences in hardware selection, see the workload profiles overview.
Next steps
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for