An Azure service that is used to provision Windows and Linux virtual machines.
Hello @Rathin Das
Based on the additional details, this doesn't look like a billing/free-trial or ordinary vCPU quota issue. Your subscription is Pay-As-You-Go, the spending limit is off, and several VM families show available quota.
The important error is NotAvailableForSubscription. If you're seeing this across multiple common VM sizes and regions, despite having quota, that points more to a subscription-level SKU/Compute restriction than a regional capacity shortage.
I would verify the restriction metadata for a specific SKU/region, for example:
az vm list-skus \
--location eastus \
--resource-type virtualMachines \
--all \
--query "[?name=='Standard_B2s'].{Name:name,Restrictions:restrictions}"
If restrictions reports NotAvailableForSubscription, increasing vCPU quota alone won't resolve it. Also note that Azure quota and actual SKU availability are separate concepts—a subscription can have sufficient quota while a SKU is still unavailable/restricted.
Since you're seeing the problem broadly across regions/SKUs, I recommend opening an Azure Support request and asking Microsoft to check the subscription for a backend Compute/SKU eligibility restriction. Include the subscription ID, exact NotAvailableForSubscription error, affected SKUs/regions, and correlation/request IDs from failed deployments.
Reference: Microsoft - Azure quota and compute management
Don't keep requesting additional vCPU quota until Microsoft confirms whether the subscription itself is restricted.
Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.