Cannot create Azure Functions (Consumption Plan) / No Dynamic VM quota request option

Question

I am using an Azure free subscription.

When I try to create a Function App (Consumption Plan) in the Japan East region, I get an error saying "Cannot create because Dynamic VMs quota is 0".

In the quota management screen, I was able to increase "Total vCPUs in region", but there is no option to request quota for "Dynamic vCPU" or "Consumption", so I cannot apply for it.

I want to use Azure Functions within the free tier for learning purposes.

How can I create a Function App (Consumption Plan)?

Also, what should I do if there is no option to request Dynamic VM or Consumption quota?

Answer 1

Hello 純子 細野 •,

Thank you for reaching out. We understand you are encountering an error while creating an Azure Function App on the Consumption plan indicating that the Dynamic VMs quota is 0 in the Japan East region.

This behavior is expected for Azure Free / Trial subscriptions. Azure Functions running on the Consumption plan use an internal Dynamic (Y1) App Service SKU, which relies on a separate Dynamic vCPU quota. In certain regions, including Japan East, this quota is set to 0 by default for Free subscriptions. This quota is not exposed in the standard quota management blade and therefore cannot be increased directly, even if total regional vCPUs are available.

Recommended options to proceed:

• Create the Function App in a different region where Dynamic quota is available for Free subscriptions (for example, Central India, East US, or West Europe).
• Ensure the Function App is created using Windows + Consumption plan, as Linux Consumption has additional limitations.
• For learning and development, use Azure Functions Core Tools to develop and test functions locally without deploying to Azure.
• If deployment in Japan East is required, upgrading the subscription to Pay‑As‑You‑Go will allow Dynamic (Consumption) quota requests while still benefiting from the monthly free execution grants.

In summary, this is a subscription and region-level limitation, not an issue with the Function App configuration itself.

Please accept as answer and do a Thumbs-up to upvote this response if you are satisfied with the community help. Your upvote will be beneficial for the community users facing similar issues.

Answer 2

The error indicates that the subscription has a regional quota of 0 instances for the Dynamic/Consumption Functions infrastructure (“Dynamic VMs”) in Japan East. On some subscriptions (especially free or constrained offers), this quota cannot be increased for a given region, or the specific Dynamic/Consumption quota type is not exposed in the Quotas blade.

To proceed, use one of these approaches supported in the documentation and Q&A context:

1. Try a different region

• The documented guidance for similar quota issues is to switch to another region, ideally a paired region, when a region has a quota of 0 and cannot be increased.
• For example, if Japan East is blocked, try creating the Function App (Consumption plan) in another nearby or paired region that allows Consumption/Dynamic capacity.
• This matches the guidance for the error: “This region has quota of 0 instances for your subscription. Try selecting different region or SKU.”

2. Create the Function App in a new resource group

• There are known limitations when creating new Function Apps in an existing resource group, especially when mixing SKUs.
• In the Azure portal:
  1. Go to Create a resource → Function App.
  2. Under Select a hosting option, choose Consumption → Select.
  3. On Basics, choose Subscription and then create a new Resource Group (do not reuse an existing one).
  4. Choose a region that has available Dynamic/Consumption capacity.
• This can resolve “SkuNotAllowedForResourceGroup”/pricing-tier-related issues that may appear similar to quota problems.

3. Use Flex Consumption instead of classic Consumption (if available)

• If the portal offers Flex Consumption in the region, a Function App can be created in that plan instead of the classic Consumption plan.
• For example, via Azure CLI:
  • JavaScript:

        az functionapp create \
          --resource-group <RESOURCE_GROUP> \
          --name <APP_NAME> \
          --storage-account <STORAGE_NAME> \
          --flexconsumption-location <REGION> \
          --runtime node \
          --runtime-version 20
    

  • PowerShell:

        az functionapp create \
          --resource-group <RESOURCE_GROUP> \
          --name <APP_NAME> \
          --storage-account <STORAGE_NAME> \
          --flexconsumption-location <REGION> \
          --runtime powershell \
          --runtime-version 7.4
    

• In the portal: Create a resource → Function App → Flex Consumption → Select, then complete the Basics page.
• Flex Consumption is still serverless and only incurs cost when functions execute, which is suitable for learning scenarios.

4. If no Dynamic/Consumption quota option is visible

• When a specific quota type (such as Dynamic vCPU/Consumption) is not exposed in the Quotas blade, the documented guidance for similar quota issues is:
  • Try another region where the quota is available.
  • If the region must be used and the quota is not adjustable, open a support request from the quota or deployment error flow so that support can confirm whether the quota can be changed for that subscription/region. (Some offers, including certain free subscriptions, may have hard limits.)

5. Confirm Functions service limits

• Azure Functions has per-plan limits, including maximum instance counts and function apps per plan. For Consumption, there is a documented maximum instance count per region and per plan. If the subscription or region is at 0 for Dynamic/Consumption, the only supported options are to:
  • Use a different region, or
  • Use a different plan type (such as Flex Consumption or Premium) if allowed by the subscription.

For a free-tier learning scenario, the most practical options are:

• Create the Function App (Consumption) in another region that has non-zero Dynamic quota, using a new resource group; or
• Use the Flex Consumption plan in a supported region.

---

References:

• Azure Functions Consumption plan hosting
• Create a function app in the Azure portal (consumption-plan)
• Create and manage function apps in the Flex Consumption plan (programming-language-javascript)
• Create and manage function apps in the Flex Consumption plan (programming-language-powershell)
• Resolve issues when creating, deleting, or restoring Azure Function App
• Azure subscription and service limits, quotas, and constraints
• Increase regional vCPU quotas
• Increase VM-family vCPU quotas