MySQL Single Server auto-migration issue / status after EOL / cancelation of auto-migration
Hello,
I've tried to set up the auto-migration of two Azure Databse for MySQL instances and provided the additional info (private DNS zone, VNet access, removal of locks) - faced the same issue as this Question: https://learn.microsoft.com/en-us/answers/questions/1862296/azure-mysql-auto-migration-from-single-to-flexible
"Ready to migrate" checkmark getting reset and "save" never finalizing as the portal kept loading eternally. I assume that's why our planned migration for 12.08. got re-scheduled for September.
Issue with checkmark remains. The armConnections APIs got created, don't find any logic app though.
Now I've been informed that our application is being depreceated and will be replaced very soon, which is why we'd rather cancel the planned auto-migration of both Databases, if the existing service will remain online (just without support / updates). Is that correct? As asked here: https://learn.microsoft.com/en-us/answers/questions/1861291/end-of-life-reminder-migrate-to-azure-database-for
If the existing databases will keep running as stated there, can we have the auto-migrations canceled please?
best regards