Insufficient quota of vCPUs available after creating a VM, imaging it, and then deleting it

Question

I am testing out Azure VMs as a disaster recovery option for my organization. I'm on an Azure AD trial. My use case is this: Ideally, I'd like to have an image standing by with all the software that my users need, pre-installed, and hooked up to our Azure AD domain. Then, if we should need our DR environment, I'd like to spin up 1..n VMs from the image, send my users the RDP connection files, have them log in with their Office 365 credentials (we also subscribe to Azure AD Premium P1), and get back to work using OneDrive.

I created a VM and populated it with the settings and software I need for my users. It has a local admin, and I confirmed I could log in using my Azure AD credentials. Then I ran sysprep /generalize and created an image of the virtual workstation. So far so good. As I could no longer access the original VM, I deleted it. The original VM was of the DS3_v2 size.

Now I'm going to create a new VM from my image to test. In the Azure portal, I go to Virtual Machines -> Add. I select my image and Resource Group. However, when I go to select a Size, I get the following error message:

"4 vCPUs are needed for this configuration, but only 0 vCPUs (of 4) remain for the Standard DSv2 Family vCPUs." I cannot select any of the available options. The "Troubleshoot" link directs me to a page instructing me to request a quota increase, but that shouldn't be necessary; I de-allocated [edit: deleted] the old VM and its 4 vCPUs so I could create a new one. Why is Azure telling me I only have 0 vCPUs left in my trial subscription?

Answer 1

This morning when I tried again, the console allowed me to select a size. It appears that there is a very substantial delay between when you delete the VM and when Azure marks the vCPUs as available to use once again.