VM not Starting

Question

VM not Starting

Julio Quinteiro 20

VM not Starting
Advisor (1 of 3): Migrate workload to D-series or better virtual machine

0 comments

Answer accepted by question author

Ankit Yadav 14,455 Microsoft External Staff Moderator

Hello @Julio Quinteiro

It seems you ran into an allocation failure and got the suggestions to migrate the workload to D-series VMs to avoid allocation failure.

For confirmation, could you please share us the complete error what you faced while starting the VM? (this can be found from the notification from Azure Portal when the Start failed or you can review your Activity Logs for the VM, more about this can be found here)

Additionally, adding some general guidance :

Check for Allocation Failures: If your VM is getting allocation failures while starting, you can look into that through the troubleshooting guide for allocation failures.
Consider VM Size and Region: If you are consistently facing issues, it may help to check if there’s a quota limit or if the requested VM size is unavailable in the region. More about this can be found in the allocation failure troubleshooting.

Let me know if this helps out or if there's any follow-up query, do let me know!

Julio Quinteiro 20

Overview: The error "ProvisioningState/failed/ZonalAllocationFailed" indicates that the deployment of your Windows-based instance failed due to an allocation failure in the desired zone. This issue typically occurs when the resources required for your instance size are insufficient or unavailable in the specified zone.

Recommendation: Here are several steps you can take to potentially resolve this issue:

Deploy to Another Region:

Allocation failures can often be circumvented by deploying your instance to a different region. This action is particularly useful if your desired instance size is unavailable due to capacity constraints in the current zone.

Visit the Azure Regions page to check available regions and their supported instance sizes.

Change Instance Size:

- You may consider changing the instance size to one that is available in your current zone. To do this:

      - In the Azure portal, navigate to your resource group and select your instance.

            - Click on "Size" under the "Settings" section.

                  - Select a different size that meets your requirements and click "Resize".

                     - Refer to [Resize a Windows VM](https://docs.microsoft.com/azure/virtual-machines/windows/resize-vm) for detailed instructions.

                     **Check Service Limits:**

                        - Ensure that you have not reached the subscription quotas or limits for the type of instance you are trying to deploy. If necessary, request an increase in your quota via the Azure portal.

                           - More information is available on [Quota Limits](https://docs.microsoft.com/azure/azure-resource-manager/templates/error-resource-quota).

                           **Troubleshoot Allocation Errors:**

                              - Further diagnostics and troubleshooting steps can be found in the documentation on [Allocation Failure](https://docs.microsoft.com/azure/virtual-machines/troubleshooting/allocation-failure). This resource provides insights into why allocation failures occur and potential resolutions.

Summary: The error "ProvisioningState/failed/ZonalAllocationFailed" typically arises due to insufficient resources in the specified zone. To address this, you can deploy your instance to another region, change the instance size, check your service limits, or troubleshoot allocation errors with the provided documentation. Adjusting your deployment based on these recommendations may help resolve the provisioning state issue for your Windows instance.

Ankit Yadav 14,455 Reputation points Microsoft External Staff Moderator

2025-10-22T14:41:35.0466667+00:00

Hello @Julio Quinteiro

We won't be able call you over your number due to limitations with the platform services, however we can offer a team's call to troubleshoot the issue with you over the call.

For that we'd need some details from you and I've asked them in the Private Message, kindly check and answer them.

3 additional answers

Your answer

Ankit Yadav 14,455 Reputation points Microsoft External Staff Moderator

2025-10-22T14:41:35.0466667+00:00

Hello @Julio Quinteiro

We won't be able call you over your number due to limitations with the platform services, however we can offer a team's call to troubleshoot the issue with you over the call.

For that we'd need some details from you and I've asked them in the Private Message, kindly check and answer them.

Answer 1

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Answer 2

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Answer 3

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Share via

VM not Starting

3 additional answers

Your answer