VM creation failed

owen.kim 176

I'm not close to the limit of VMs I can create on my subscription.
VM creation fails with error "ProvisioningState/failed/AllocationFailed"

This issue creates major problems for operational services.
Can you check the remaining resources for VM creation in east US 2?? hourly if possible

srbhatta-MSFT 8,561 Reputation points Microsoft Employee

2022-08-12T07:41:17.947+00:00

Hello @owen.kim ,
Welcome to Microsoft QnA.
Are you trying to add your new VM to any availability set during deployment?
owen.kim 176 Reputation points

2022-08-12T07:43:25.933+00:00

No Availability configuration is not used at all.

1 answer

risolis 8,721 Reputation points

2022-08-12T07:15:26.943+00:00

Hello @owen.kim

Thank you for your heads up.

For this case scenario, I would think of 2 possible issues that can prevent you from provisioning any compute resource so please see below:

-Please review your quota usage at the Subscription level and you might check if you are reaching any VM limit or Virtual CPU limit per region. In case this is the issue you can increase your quota capacity.

-Just in case, review if there is any IAM restriction as well as any availability zone restriction if you require this during the provisioning stage.

Furthermore, I would like to provide the following article which might be very useful to overcome this problem

https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/allocation-failure

I hope this can be helpful for you.

Looking forward to hear back from you.

Cheers,

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.
Please sign in to rate this answer.
owen.kim 176 Reputation points

2022-08-12T07:32:07.953+00:00

Subscriptions are currently in use at the 10-20% level.

This issue occurs due to randomness. So, first of all, IAM doesn't seem to be a problem.

Availability Zone has not been set. Are there any restrictions on not setting Availability Zones?

risolis 8,721 Reputation points

2022-08-12T07:45:16.303+00:00

Many thanks for your response.

Let me share this image below:

See this other as well:

owen.kim 176 Reputation points

2022-08-12T07:58:34.953+00:00

It feels like a batch job that is only used when a request comes in, so availability is not required.
The VM is not persistent, it is deleted when the operation is finished.

risolis 8,721 Reputation points

2022-08-12T08:05:39.803+00:00

Ok thanks for that.

-So another possible reason could be the virtual network used... For instance if you are using an existing Vnet or subnet range so, you may try to set it up in a new Vnet or subnet range.

-Is this a customer image ? Or Was this taken from the Marketplace?

-Have you try to do it using a different size or region? To isolate the issue if it is per size or region issue.(I know that no quota limitation is seen)

Regards,

owen.kim 176 Reputation points

2022-08-12T08:17:22.58+00:00

Yep, this is an image from my computing gallery.
In a subnet that can use about 220, 30 are in use.

Now it is generating fine. This problem is still not happening. It happens intermittently.

I heard that there are cases where the creation fails due to a large number of requests in the region.
So is there a way to preview a notification or notice that a region is running out of resources?

risolis 8,721 Reputation points

2022-08-12T08:28:43.227+00:00

Many thanks for the update : )

Let me see and I am not mistaken that you may be referring to this:

https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/deployment-history-deletions?tabs=azure-powershell

Cheers,

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

owen.kim 176 Reputation points

2022-08-12T08:33:00.41+00:00

I'm sorry, but the content of the attached address has nothing to do with me.

risolis 8,721 Reputation points

2022-08-12T09:03:12.777+00:00

Thank you for your post.

For my last post what I wanted to transmit was this explanation below:

Azure Resource Manager enables you to view your deployment history. You can examine specific operations in past deployments and see which resources were deployed. This history contains information about any errors.

The deployment history for a resource group is limited to 800 deployments. As you near the limit, deployments are automatically deleted from the history. For more information, see Automatic deletions from deployment history.

Finally, here it is article to review error code meanings.

https://learn.microsoft.com/en-us/azure/azure-resource-manager/troubleshooting/common-deployment-errors

Have a good one!
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

VM creation failed

1 answer

Your answer