Azure-docs: Deallocated VMs still contribute to hitting the vCPU quota limit

[AndrewJCo]

Could you update the page to show that even though deallocated VMs shouldn't have any vCPUs assigned to them, their existence still counts towards your vCPU quota limit for a region. This is unexpected and hard to work out as there's no clever way to match the Get-AzVMUsage to the actual VMs.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 7ebe6d3a-2307-1e9a-69f1-f8aeb2397266
• Version Independent ID: dac51441-6f31-0ef2-55e1-70377b7a59f0
• Content: vCPU quotas for Azure
• Content Source: articles/virtual-machines/windows/quotas.md
• Service: virtual-machines-windows
• GitHub Login: @cynthn
• Microsoft Alias: cynthn

[VikasPullagura-MSFT]

@AndrewJCo Thanks for the feedback! We are currently investigating and will get back on this.

[VikasPullagura-MSFT]

@AndrewJCo Stopping the VM from Portal which is deallocate state will release the cores to unused quota. The command you have used to check the usage may be calling API's which may be taking little time to updated, could be the reason you are seeing issue.

In case if you are stopping the VM from inside the OS then it is true as per your feedback about Quota limits.

Just want to confirm if you are still seeing the quota limit issue even after stopping the VM from portal and checking the usage limits after sometime.

Please check and let us know to further assist you on this.

[BillyA7]

Hi,
I have two VM's using 10 vCPU's that show as "Stopped (deallocated)" 16 hours ago in the portal, but they still show as being used in Usage + Quotas:

Standard DSv3 Family vCPUs - Microsoft.Compute - UK South - 100% - 10 of 10
Total Regional vCPUs - Microsoft.Compute - UK South - 100% - 10 of 10

Should they not be released.

To test, I am able to create a Standard B1s from the free services page, but unable to create the same VM from the create a resource section, everything is greyed out, accompanied by the "insufficient quota" message.

[zhanke]

I am still encountering the same issue too in Australia East region at least. Can we review this please.

[mimckitt]

It does appear the cores are still counted unless you delete the VM. I will confirm that this is by design and update everyone. If that is the case I will update the doc to make sure that is clear.

[hongooi73]

@mimckitt is there any update? I just saw this in Australiaeast as well.

[mimckitt]

UPDATE

The core count is working as expected. It DOES count both VMs that are Allocated and Deallocated. The only way to get the cores back from the deallocated VMs would be to delete them.

So if you need more cores in a region, you need to submit a request for an increase or remove old VMs.

I am going to work on updating this document to make that more clear but just wanted to share an update for now.

[BillyA7]

Thanks for the update Micah.

[mimckitt]

I added a note at the very top of the page explaining that quota counts both allocated and deallocated VMs. Once the PR merges the changes should go live after a few hours.