Hello Chase Kessler, Thanks for asking your query on Microsoft QnA!
Unfortunately, your Azure Database for MariaDB Single Server is currently disabled due to the service retirement, unfortunately, the data and workload associated with it are no longer recoverable. This is why you're seeing connection failures the server DNS is no longer resolvable.
I completely understand your frustration; this has been a common concern among many users affected by the Azure Database for MariaDB Single Server retirement.
To clarify, the architecture of the MariaDB Single Server platform didn’t expose the underlying virtual machines or their data disks to customers. As a managed PaaS offering, Microsoft handled the infrastructure layer entirely, which means customers didn’t have direct access to the VMs or their storage. Once the service was retired, the associated infrastructure including the data disks was decommissioned as part of the platform’s lifecycle.
I agree that having access to the underlying disks could have helped in recovery scenarios, but unfortunately, that level of access was never part of the service design. Though you can provide feedback on any product here
You can refer to the official documentation here for more context:
https://learn.microsoft.com/en-us/azure/mariadb/migrate/whats-happening-to-mariadb
At this point, I’d recommend checking any of the following for potential backups or exports:
Local or cloud storage for mysqldump or mydumper files
Azure DMS migration staging areas
ADF copy sinks
Application-side replicas or caches
If none of these options help, the best course of action is to raise a support ticket with Azure Support. You can request an escalation to the product group for post-retirement data recovery. While there’s no guarantee, this is the only viable path forward.
Here’s a related thread that might be helpful:
Please "Accept as Answer" if the information provided is useful, so that you can help others in the community looking for remediation for similar issues.
Thanks
Pratyush