Hi Windsor Vietnamese Alliance Church
Thank you for confirming that your MySQL Flexible Server is now working as expected, and we appreciate your patience throughout this process.
After investigation, the Product Group team identified that the server failed to restart due to insufficient VM capacity in the selected availability zone. This caused both the upgrade and rollback processes to fail, which in turn left the server in a non-responsive "Stopped" state.
To resolve the issue, the engineering team performed a host VM switch and repair operation, which replaced the underlying compute host and restored the MySQL container. Once this was completed, the server successfully transitioned to a Succeeded state and became available for connections.
Preventive guidance:
- Avoid scheduling frequent automatic stop/start tasks, especially in capacity-constrained regions or zones.
- If the server must be stopped and started regularly, consider using a different zone or smaller compute size, which increases allocation success.
- You can also monitor Azure regional capacity announcements or refer to Azure VM allocation guidance for best practices.
We appreciate your understanding and cooperation while our internal teams worked on this. Hope this helps. Do let us know if you any further queries.
If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.