Azure MySQL flexible server stuck on actions (stop, start, change inbound ip address...)

Question

Starting this week, any action I attempt on my flexible MySQL server is met with persistent loading issues. Changes take an inordinate amount of time, often over an hour, and still fail to be implemented, such as allowing a new IP address. Additionally, if you navigate to the maintenance tab of the MySQL server, it indicates that the database is under maintenance, which seems to lock out all these actions. imagen The same maintenance on Azure_Healt appears "resolved" imagen From what I've gathered in other discussions, this appears to be a bug inherent to the tool itself, leaving little room for action on the part of the end user. Even attempting a restore proves futile, as the process stalls in the same manner. This seems to be due to the server being in an 'update' state. https://learn.microsoft.com/en-us/answers/questions/1051836/azure-mysql-flexible-server-stuck-at-updating-stat https://learn.microsoft.com/en-us/answers/questions/1344067/how-to-fix-mysql-flexible-server-the-server-is-cur Azure's recommended solution is to open a support ticket, but I don't believe this is the most suitable approach. This is especially true in environments without a support license. It seems the viable alternative would be to extract a backup of the data outside of Azure and set up the database form 0. However, this becomes significantly more complex if systems like VNET, WAF are involved, making it quite a challenging task to maintain I understand that it's likely a quite complex issue to pinpoint, but some alternative should be offered, like being able to perform a forced shutdown on the server, where the shutdown bypasses that check... so that the alternative isn't just to completely delete it and start from scratch. Is there a solution currently or on the roadmap? Thank you very much in advance