Welcome to Microsoft Q&A forum.
As I understand, you're encountering an issue with the deployment of geo-redundancy for your Azure Database for MySQL Flexible Server instance.
Moving from zone-redundant to geo-redundant backup storage - Azure Database for MySQL Flexible Server doesn't support zone-redundant storage to geo-redundant storage conversion through Compute + Storage settings change after the server is provisioned. In order to move your backup storage from zone-redundant storage to geo-redundant storage, there are two options: a) Use PITR (point-in-time restore) to restore the server with desired configuration. b) Create a new server with the desired configuration and migrate the data using dump and restore.
For more information, please refer the document: https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concepts-backup-restore#backup-redundancy-options
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.