Trying to change VM size or region

Question

First off, sorry for any snarkiness as going through this process is very frustrating.

Our VM is currently a size that will be retired at the end of Aug in Korea South. I attempted to change the size but there are no sizes available. I attemped to move using the azure mover, that failed. I don't know what to do about this problem. We don't have a support contract.

What does the community need to know to help me through this? We have 4 VMs on the same VM Size that I will probably need to change, I'll go through those once I get this one done.

Thanks!

Answer 1

Hello Josh Henry,

Thanks for your question.

The error message "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed" is usually as a result of an Azure Policy.

In the full error message you will be able to see the exact reason in the details pane of the error Json.

Please verify your policies and try again https://learn.microsoft.com/en-us/azure/azure-sql/database/policy-reference?view=azuresql

Regards,

You can mark it 'Accept Answer' if this helped.

Answer 2

Hello, @Josh Henry ! I know this has been frustrating for you but those sizes (B1ms) should be available and if you are getting an error there, that's the first place to troubleshoot. If we can't get this sorted out, I'll make sure you are able to open a support request.

I'm unable to change my VM size because of a size not available error. What should I do?

You will encounter this error in the following scenarios:

• When the resource SKU you've selected, such as VM size, isn't available for a location or zone.
• If you're deploying an Azure Spot VM or Spot scale set instance, and there isn't any capacity for Azure Spot in this location. For more information, see Spot error messages.

https://learn.microsoft.com/en-us/azure/azure-resource-manager/troubleshooting/error-sku-not-available?tabs=azure-cli#cause

You can use Azure CLI to determine if you need to submit a SKU request to address a NotAvailableForSubscription restriction:

az vm list-skus --location koreasouth --size Standard_B1ms --all --output table

Additional causes for a NotAvailableForSubscription restriction:

• You have hit your core limit for that region (and need to increase your available quota)
• You are unable to create VMs in that region due to a policy created by your admin
• The VM size you are trying to use is not available for your subscription (free/student accounts, for example)
• The specific VM SKU you are trying to create has not been enabled for your subscription (you need to open a support ticket to enable that SKU)
• You are trying to deploy an Azure Spot VM or Spot scale set instance and there isn't additional capacity at that location

If there are no restrictions, you are not using Azure Spot VMs, and you've gone through the troubleshooting list above but are still running into issues, please leave a comment and we'll look into a support request.

---

I hope this has been helpful! Your feedback is important so please take a moment to accept answers.

If you still have questions, please let us know what is needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!

Answer 3

It looks like the firewall has been blocking the Azure Agent the entire life of the VM. I've fixed that problem now and going to attempt the move again. Crossing fingers.