Difference between Azure MySQL Server and "Flexible" Server resources?

Trevor Sullivan 20 Reputation points
2025-04-28T15:54:20.5+00:00

What's the difference between an Azure Database for MySQL resource and Azure Database for MySQL - "Flexible" Server?

As far as I can tell, "Flexible Server" is the only option available in Azure right now. When I search for "MySQL" in the Azure Portal, there are two options (ignore the Azure Arc option in the screenshot below), but both of them take me to the creation wizard for "Flexible" server.

There's two different resource types, with different supported Azure Monitor metrics.

What's the difference here?image.png

image.png

Azure Database for MySQL
Azure Database for MySQL
An Azure managed MySQL database service for app development and deployment.
949 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Saraswathi Devadula 2,175 Reputation points Microsoft External Staff
    2025-04-28T16:21:55.5333333+00:00

    Hello Trevor Sullivan

    I understand that you want to know the difference between an Azure Database for MySQL servers and Azure database for MySQL Flexible Server.

    Azure Database for MySQL is available in two primary variants: Single Server and Flexible Server.

    Previously before the single server deprecation, we were able to select the server type based on our requirement. But after deprecation, the single server is not visible and only the flexible server is visible.
    select db

    The Single Server option, denoted by the resource type Microsoft.DBforMySQL/servers, has been deprecated, and Microsoft no longer advises new deployments using it. When setting up a MySQL resource in the Azure Portal, the only available option is Flexible Server, as the single server has been deprecated.

    The Flexible Server, recognized as Microsoft.DBforMySQL/flexibleServers, is the current and future-oriented model. Azure Database for MySQL Flexible Server is specifically designed for creating and managing flexible servers.

    I hope this has been helpful!

    Your feedback is important so please take a moment to accept answers. If you still have questions, please let us know what is needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!

    If this answers your query, do click Accept Answer and Upvote for was this answer helpful.


  2. Sina Salam 19,616 Reputation points
    2025-04-29T03:47:04.7366667+00:00

    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.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.