always get the same error

[dleute]

Describe the bug
No matter my settings I get this:

"details": [
{
"code": "SubscriptionIsOverQuotaForSku",
"message": "Operation cannot be completed without additional quota. \r\nAdditional details - Location: \r\nCurrent Limit (Dynamic VMs): 0 \r\nCurrent Usage: 0\r\nAmount required for this deployment (Dynamic VMs): 1 \r\n(Minimum) New Limit that you should request to enable this deployment: 1. \r\nNote that if you experience multiple scaling operations failing (in addition to this one) and need to accommodate the aggregate quota requirements of these operations, you will need to request a higher quota limit than the one currently displayed."
}

To Reproduce
Steps to reproduce the behavior:
Launch via bicep like this:

import * as C from '../../params/constants.bicep'

var prefix = C.prefix

module acmebot 'br:cracmebotprod.azurecr.io/bicep/modules/keyvault-acmebot:v4' = {
params: {
appNamePrefix: 'perf-acme-le'
mailAddress: 'derrekl@vermontsystems.com'
keyVaultBaseUrl: 'https://${prefix}-perf-kv.${environment().suffixes.keyvaultDns}/'
createWithKeyVault: false
keyVaultSkuName: 'standard'
// location: 'East US'
acmeEndpoint: 'https://acme-v02.api.letsencrypt.org/directory'
}
}

Or by clicking the deploy links.

Environment (please complete the following information):
Irrelevant. Can't launch the bot itself. haven't gotten to getting certificates.

Additional context

I assume I don't have the quota for whatever this is using, But I have tried asking for quota increase on everything I can. Dynamic VMs don't exist, and I can't find any relevant quotas.

Even Azure support is stumped. They keep asking me for the error saying they "can't see the above error".

If this is a simple "register resource provider" or finding the right quota to increase, that would be awesome. But, I have zero left I can find that might be relevant.

Thanks!

[dleute]

For the record, I have tried in East US and East US2. same error on both.

[dleute]

I think the underlying problem is this:

resource appServicePlan 'Microsoft.Web/serverfarms@2024-11-01' = {
name: appServicePlanName
location: location
sku: {
name: 'Y1'
tier: 'Dynamic'
}
properties: {}
}

However, many of the bicep files actually in the github repository show this:

resource appServicePlan 'Microsoft.Web/serverfarms@2025-03-01' = {
name: appServicePlanName
location: location
sku: {
name: 'FC1'
tier: 'FlexConsumption'
}
properties: {
reserved: true
}
}

The FC1 version works for me. But none of the existing and published bicep registry modules actually use that one.

Obviously, I can clone the repo and use whichever bicep script works for me. But, this seems like something that is effecting everyone.

Does one of the bicep registry versions use that second version?

[shibayan]

Currently, v5 using Flex Consumption is in preview and is not published in the Bicep registry. Additionally, the Bicep definition itself has incomplete parts, so its use is not yet recommended.

The inability to deploy a Consumption Plan is due to Azure subscription limitations, so we believe this fundamentally requires resolution by Azure Support.

[dleute]

@shibayan

I agree, but azure support is being.... azure support. In several weeks they can't "find the error".

so, basically, I need to get Y1 quota, or I can't use this as is.

I did try using the v5 preview directly, and yeah, it's missing stuff. It's also throwing errors I definitely don't understand. Apperantly Contacts isn't allowed in this new version? If it's just bicep stuff, I can likely fix it myself.

I will explicitly tell azure to fix the Y1 quota issue.

Any idea when FC1 will be usable? or at least beta testable (this is not production)

[dleute]

Y1 allows the bicep to launch. But nothing works. The dashboard is a blank page. I can't find errors in any log or indication anywhere why I am getting nothing.