Purchasing a reservation for MySQL returning non-existing options

Mike van Lienden 20 Reputation points
2025-11-20T08:50:09.3+00:00

I am encountering some confusion with the available options for reservation for MySQL Flexible Server vs the available options when selecting/ creating a MySQL Flexible Server. I have attached a screenshot that shows the issue:

reservation vs mysql

Specifically, when selecting compute inside the Reservation Purchaser, the available options are 'General Purpose,' 'Memory Optimized,' and 'Confidential Compute.' However, these options do not fully align with the available compute choices for MySQL Flexible Server, which are 'Burstable,' 'General Purpose,' and 'Business Critical.'

My question is whether the 'Memory Optimized Eadsv5 Series Compute' option is equivalent to 'Business Critical Eadsv5 Series Compute' and would therefor apply to my MySQL instance?

Also the Advisor Recommendation doesn't even return a recommendation at all.

Azure Database for MySQL
{count} votes

Answer accepted by question author
  1. Manoj Kumar Boyini 1,250 Reputation points Microsoft External Staff Moderator
    2025-11-20T10:25:39.0133333+00:00

    Hi Mike van Lienden,

    Thank you for reaching out to Microsoft QA. The Memory Optimized Eadsv5 Series Compute you see in the reservation portal is indeed the underlying hardware for the Business Critical Eadsv5 tier available for MySQL Flexible Server. Even though the names do not match exactly due to recent updates in Azure’s compute tier structure, purchasing a reservation for Memory Optimized Eadsv5 will correctly apply to your "Business Critical Eadsv5" deployment.

    If Azure Advisor does not show a recommendation, this is typically because there is not yet enough usage history or a significant projected saving to suggest a reservation. As you use your server more over time, Advisor may recommend a reservation when it identifies a cost-saving opportunity.

    1."Memory Optimized Eadsv5" reservations are valid and will apply to "Business Critical Eadsv5" flexible servers.

    2.The naming difference is due to ongoing Azure portal updates; it does not impact your billing or reservation usage.

    3.Advisor recommendations depend on sufficient and consistent server usage data.

    Helpful References:
    1.https://learn.microsoft.com/en-us/answers/questions/5619123/azure-database-for-mysql-reservation-sku-naming-in
    2.https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concepts-azure-advisor-recommendations
    3.https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concept-reserved-pricing
    4.https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concepts-service-tiers-storage

    Hope this helps. Do let us know if you have any further queries.

    1 person found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

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