Quota error

[ckittel]

I am getting an error when I try to run the

az deployment group create -g rg-iaas -f infra-as-code/bicep/main.bicep -p location............................................................

"message":"Operation could not be completed as it results in exceeding approved Total Regional Cores quota.
Additional details - Deployment Model: Resource Manager, Location: FranceCentral, Current Limit: 10,
Current Usage: 0, Additional Required: 18, (Minimum) New Limit Required: 18.

Whis is supporting this and who can help? Thanks in advance

Originally posted by @eliassal in mspnp/cloud-design-patterns#117 (comment)

[ckittel]

Looks like you are out of Quota, @eliassal. The deployment requires 18 cores but you only have 10 available in FranceCentral in your subscription. You'll need to 1) modify the template to use less cores or 2) increase your quota in that subscription for that region or 3) choose another region that has enough quota.

[eliassal]

Hi, I ran the
./sample-1-azure-setup.sh uniqname
(I changed the location to francecentral) It created some resources as follows

Then I get an error as follows

"details":[{"code":"QuotaExceeded",
"message":"Operation could not be completed as it results in exceeding approved Total Regional Cores quota.
Additional details - Deployment Model: Resource Manager, Location: FranceCentral, Current Limit: 10,
Current Usage: 0, Additional Required: 18, (Minimum) New Limit Required: 18.

Which does not allow to create the VMSS
I modified the template with VMs with 2 cores instead the VMs in the templates which have 4 cores but still getting the same error. I moved to use West Europe instead of FranceCentral, same thing is happening

Thanks for your help to let me know how I can make it go through with my free subscription

[ckittel]

Should be impossible to get the exact same error as the "Additional Required: 18" would have needed to change if you changed SKUs. Since there are six VMs, and a quota of 10 on your subscription, you would need to choose a single core VM, because 6 x 2 = 12 which is > 10 still. You could do a dual core SKU with one less VM in each VMSS alternatively.

[eliassal]

Hi @ckittel I did changed to 1 core, 1st run failed for an issue of outloadbalancer (a lot of items were created PIP, log space, app gateway). I deleted the RG and then rerun the deploy command but it stops after creating log-francecentral with the following error 👍

{"status":"Failed","error":
{"code":"DeploymentFailed","target":"/subscriptions/f151ee3f-4725-460d-8e3b-82512dfda843/resourceGroups/rg-iaas/providers/Microsoft.Resources/deployments/main",
"message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.",
"details":[{"code":"ResourceDeploymentFailure","target":"/subscriptions/f151ee3f-4725-460d-8e3b-82512dfda843/resourceGroups/rg-iaas/providers/Microsoft.Resources/deployments/monitoringDeploy",
"message":"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.",
"details":[{"code":"DeploymentFailed","target":"/subscriptions/f151ee3f-4725-460d-8e3b-82512dfda843/resourceGroups/rg-iaas/providers/Microsoft.Resources/deployments/monitoringDeploy",
"message":"At least one resource deployment operation failed.
Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.",
"details":[{"code":"InvalidPayload",
"message":"Data collection rule is invalid",
"details":[{"code":"InvalidOutputTable","target":"properties.dataFlows[0]","message":"Table for output stream 'Custom-WindowsLogsTable_CL' is not available for destination 'log-francecentral'."}]},
{"code":"InvalidPayload","message":"Data collection rule is invalid","details":[{"code":"InvalidOutputTable","target":"properties.dataFlows[0]",
"message":"Table for output stream 'Microsoft-ConfigurationChange' is not available for destination 'log-francecentral'."},
{"code":"InvalidOutputTable","target":"properties.dataFlows[0]","message":"Table for output stream 'Microsoft-ConfigurationChangeV2' is not available for destination 'log-francecentral'."},
{"code":"InvalidOutputTable","target":"properties.dataFlows[0]","message":"Table for output stream 'Microsoft-ConfigurationData' is not available for destination 'log-francecentral'."},
{"code":"InvalidOutputTable","target":"properties.dataFlows[1]","message":"Table for output stream 'Microsoft-InsightsMetrics' is not available for destination 'log-francecentral'."},
{"code":"InvalidOutputTable","target":"properties.dataFlows[2]","message":"Table for output stream 'Microsoft-Event' is not available for destination 'log-francecentral'."}]},
{"code":"InvalidPayload","message":"Data collection rule is invalid","details":[{"code":"InvalidOutputTable","target":"properties.dataFlows[0]",
"message":"Table for output stream 'Microsoft-ConfigurationChange' is not available for destination 'log-francecentral'."},
{"code":"InvalidOutputTable","target":"properties.dataFlows[0]","message":"Table for output stream 'Microsoft-ConfigurationChangeV2' is not available for destination 'log-francecentral'."},
{"code":"InvalidOutputTable","target":"properties.dataFlows[0]","message":"Table for output stream 'Microsoft-ConfigurationData' is not available for destination 'log-francecentral'."},
{"code":"InvalidOutputTable","target":"properties.dataFlows[1]","message":"Table for output stream 'Microsoft-InsightsMetrics' is not available for destination 'log-francecentral'."},
{"code":"InvalidOutputTable","target":"properties.dataFlows[3]","message":"Table for output stream 'Microsoft-Syslog' is not available for destination 'log-francecentral'."}]}]}]}]}}