Hello Trevor Sullivan,
Welcome to the Microsoft Q&A and thank you for posting your questions here.
Thank you for your excellent and important question.
Let me provide you with a clear and complete explanation. Azure Database for MySQL comes in two main types: Single Server and Flexible Server. The Single Server offering, represented by the resource type Microsoft.DBforMySQL/servers
, has been deprecated, and Microsoft no longer recommends new deployments on it. In contrast, the Flexible Server, identified as Microsoft.DBforMySQL/flexibleServers
, is the active and future-ready model.
Single Server is a traditional Platform-as-a-Service (PaaS) solution but offers limited control over aspects like maintenance scheduling, compute scaling, and networking. It provides basic high availability within the same region and only a restricted set of Azure Monitor metrics. Scaling options are relatively rigid, and while storage auto-grow is available, flexibility is minimal. Additionally, network configuration mainly involved public IPs, with VNET integration introduced later. Cost optimization was limited because the server could not be easily stopped to save money.
Flexible Server, on the other hand, is designed to offer greater control and customization. It supports zone-redundant high availability, more granular scaling (including burstable compute tiers), and allows you to select your preferred maintenance window. Flexible Server was built with Virtual Network (VNET) integration from the start, and it also offers private endpoints for better security. It delivers a broader range of Azure Monitor metrics, including IO consumption, lock waits, deadlocks, and query durations, which are not available in Single Server. Storage auto-grow is still available but with improved controls, and it allows stopping and starting servers, providing better cost-saving options similar to virtual machines.
Today, when creating a MySQL resource in the Azure Portal, only the Flexible Server option is presented. It's important to recognize that Flexible Server is not merely a renamed version of Single Server — it is a completely rearchitected service that is more powerful, flexible, and suited for modern workloads. As a result, Microsoft strongly recommends using Flexible Server for all new deployments, and planning migrations away from Single Server where applicable.
If you are planning to deploy, choose Flexible Server and if you have legacy Single Servers, start planning migration to Flexible Server to avoid risks with deprecation (end of support expected eventually).
I hope this is helpful! Do not hesitate to let me know if you have any other questions or clarifications.
Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.