VM size is currently not available in your region for this subscription

Hello @Aizen Sousuke

It sounds like you’re hitting the classic “VM size not available in your region” hurdle when spinning up the CMG VM Scale Set. Here’s how you can troubleshoot and unblock yourself:

Identify the exact error type

• SkuNotAvailable: the chosen SKU isn’t offered in that region for your subscription
  • QuotaLimit: you’ve hit a vCPU/core quota for that family/region
    • AllocationFailure: regional capacity is exhausted at the moment

1. Check SKU availability in your region
   1. Run in Azure CLI:

            az vm list-skus --location <your-region> --size <Desired_VM_Size> --output table
      

   2. Make sure the SKU you want shows up and is not marked “Restricted.”
   3. Verify and raise the correct quota
   4. If your preferred size still isn’t available, pick another supported size in the same region (e.g., switch from Standard_D1_v2 to Standard_D2s_v3 or F2s_v2) Or deploy your CMG to a different Azure region that has more capacity
   5. Double-check Azure Policy or subscription restrictions.
   6. Make sure you don’t have an Azure Policy blocking certain SKUs or regions.
   7. Ensure no spending or feature restrictions remain on your subscription after upgrading from trial
   8. If you’ve only raised the generic cores quota, also check the individual family quota—sometimes you need to bump both
   9. After the request is approved, wait a few minutes for it to propagate
   10. Try an alternative size or region

Follow-Up Questions (so we can narrow it down):

1. Which Azure region are you targeting, and which VM size SKU did you try?
2. What does az vm list-skus --location <region> --size <sku> return?
3. Under “Usage + quotas,” do you see available vCPUs for that VM family?
4. Any Azure Policies applied at the subscription or management-group level?

Note : This is an AI response.

Thanks,
Manish.

Welcome to Microsoft Q&A

Hello Aizen Sousuke, I hope you are doing well,

This is a very common scenario when deploying a Cloud Management Gateway (CMG) immediately after upgrading from a Free Trial to a Pay-As-You-Go subscription.

When you deploy a CMG using a Virtual Machine Scale Set (VMSS), Configuration Manager strictly limits you to specific VM sizes: B2s (Lab), A2_v2 (Standard), or A4_v2 (Large). Even though you upgraded to Pay-As-You-Go, newly converted subscriptions often face temporary capacity restrictions for these highly demanded free-tier and low-cost VM sizes in popular regions.

You mentioned increasing your quota to 15. The AI likely instructed you to increase your Total Regional vCPUs. However, Azure enforces a two-tier quota system. You must have quota for both the regional total and the specific VM family. If you increased the total to 15, but your "Standard BS Family vCPUs" (for B2s) or "Standard Av2 Family vCPUs" (for A2_v2) is still at 0, the deployment will fail.

1. Go to Subscriptions > Usage + quotas in the Azure portal. Filter by the region you want and look for Standard BS Family vCPUs or Standard Av2 Family vCPUs. Request an increase specifically for that family to at least 10.

Try a Different Region: If Azure denies the quota due to regional capacity, restart the CMG wizard and select a neighboring, less-congested region (e.g., Central US or Canada Central instead of East US).

Clear the Wizard Cache: The Configuration Manager console caches the Azure SKU list. Once your quota is approved, you may need to re-authenticate your Azure app in the console or restart the wizard to force it to pull the fresh list of available sizes.

😊 If my answer helped you resolve your issue, please consider marking it as the correct answer. This helps others in the community find solutions more easily. Thanks!

The error is caused by the fact that Cloud Management Gateway (CMG) can only use a small, fixed set of VM SKUs, and the SKU you selected isn’t available in the Azure region for the current subscription. Increasing quota doesn’t fix this, because the problem is SKU availability in that region, not capacity limits.

For CMG, only these VM sizes are supported as of February 2026:

1. Standard_B2s
2. Standard_A2_v2
3. Standard_A4_v2

If the selected region doesn’t offer one of these SKUs for the subscription, CMG creation fails with the “VM size is currently not available in your region for this subscription” message.

To work around the issue:

1. Use a different Azure region
   • In the CMG creation wizard, select another region where one of the supported SKUs is available for the subscription.
   • To discover which regions support the required SKUs, run a SKU listing command (for example, Get-AzComputeResourceSku filtered by region) or use the Azure portal’s VM creation flow to see which sizes are offered in each region.
2. Request SKU availability via Microsoft Support
   • If the required SKU is not available in any suitable region for the subscription, open a support request with Microsoft Support and ask for an exception or enablement of the needed VM size in the target region.

Until the subscription has access to one of the supported SKUs in the chosen region, CMG deployment will remain blocked on VMSS with this error, regardless of quota changes.

References:

• Can't create a CMG in a particular region
• Resolve errors for SKU not available
• Common issues: Unavailable virtual machine SKU
• Windows virtual machine deployment FAQs