Tried to create a MySQL Flexible Server for region US-West2 and encountered an error

Question

Tried to create a MySQL Flexible Server for region US-West2 and encountered an error. However, the instance still shows up on my dashboard and keeps spinning while displaying no information. So, how can I delete this instance because I want to re-use the name and are there any limitations for creating a new MySQL Flexible Server in any of the US-West Regions? I would be okay with US-West, US-West2, US-West3, and futher, any of the US-East if needed.

Answer 1

Hello Doug_C,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you're facing a challenge with a MySQL Flexible Server instance in Azure that appears stuck in the creating state, particularly in the US-West2 region.

The approach below helps you not only address the immediate problem but also avoid future provisioning issues by verifying regional capacity and subscription health. The first step is to confirm that your Azure subscription is active and not in a restricted or disabled state:

You can verify this using the Azure CLI with the command az account show.

If your subscription is in good standing, the next step is to attempt a manual deletion of the server using the CLI:

az mysql flexible-server delete --name <server-name> --resource-group <resource-group> --yes

If deletion fails or the server remains in a non-responsive state, you should check its current provisioning status using:

az mysql flexible-server show --name <server-name> --resource-group <resource-group>

Should the server still be stuck, the most effective resolution is to open a support ticket with Microsoft. Navigate to the Azure Support Portal, select Technical > MySQL Flexible Server > Server Management > Server stuck or cannot delete, and provide details such as the region US-West2, server name, and your intent to reuse the name. Microsoft support can manually remove the resource from the backend, which is often the only way to fully resolve this issue.

Before attempting to recreate the server, it’s also wise to check the availability of MySQL Flexible Server SKUs in your preferred region using:

az mysql flexible-server list-skus --location westus2

If US-West2 continues to pose issues, consider deploying to alternative regions such as westus, westus3, eastus, or eastus2, which generally offer similar latency and availability profiles.

I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.

---

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.