Hi Mohamed A. Amr,
I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this!
Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll post your solution in case you'd like to "Accept" the answer.
Root Cause:
The Dedicated compute option does not appear directly in the Container Apps Job configuration or in the quota listings. This is because Dedicated compute is enabled via a Workload Profile at the Container Apps Environment level, not within the job itself.
Solution:
Enable Dedicated Compute for Container Apps Jobs:
Create or update your Container App Environment to include a Dedicated workload profile:
az containerapp env create --name my-env --resource-group my-rg --location eastus --workload-profiles workloadType=Dedicated,name=wp-dedicated,cpu=4,memory=8Gi
Or if the environment already exists:
az containerapp env update --name my-env --resource-group my-rg --add-workload-profile workloadType=Dedicated,name=wp-dedicated,cpu=4,memory=8Gi
When creating your Job, reference this workload profile:
az containerapp job create --name my-job --resource-group my-rg --environment my-env --workload-profile-name wp-dedicated --replica-timeout 1800 --trigger-type Manual --image myregistry.azurecr.io/my-image:latest --cpu 4.0 --memory 8.0Gi
Please keep it in mind:
- The Dedicated term refers to the workload type, not a visible setting in the job UI.
- Some regions may not support Dedicated workloads yet. You can verify regional support with:
az containerapp env list-usage --location <region>
For more details, please refer the following documentation: Workload Profiles in Azure Container Apps, Create and Manage Container Apps Jobs.
Please click Accept Answer and kindly upvote it so that other people who faces similar issue may get benefitted from it.