Skip to main content

Azure Database for MySQL pricing

Fully managed, scalable MySQL Database

Azure Database for MySQL provides a fully managed database service for app development and deployment with built-in capabilities, such as high availability, at no extra cost.

Explore pricing options

Apply filters to customise pricing options to your needs.

Prices are estimates only and are not intended as actual price quotes. Actual pricing may vary depending on the type of agreement entered with Microsoft, date of purchase, and the currency exchange rate. Prices are calculated based on US dollars and converted using London closing spot rates that are captured in the two business days prior to the last business day of the previous month end. If the two business days prior to the end of the month autumn on a bank holiday in major markets, the rate setting day is generally the day immediately preceding the two business days. This rate applies to all transactions during the forthcoming month. Sign in to the Azure pricing calculator to see pricing based on your current programme/offer with Microsoft. Contact an Azure sales specialist for more information on pricing or to request a price quote. See frequently asked questions about Azure pricing.

Flexible Server provides maximum control for your database with a simplified developer experience and is best for workloads that require:

  • Customised maintenance windows and additional configuration parameters for database optimisation
  • Zone-redundant and same-zone high availability with up to 99.99% SLA
  • Stop/Start capabilities and burstable SKUs for cost optimisation
  • Hybrid Data Synchronisation with data-in replication
  • Offline and online migration support

Learn more about Azure Database for MySQL Flexible Server

Burstable

Workloads with flexible compute requirements.

Burstable Compute

Instance vCores Memory Pay as you go
B1ms 1 2 GiB $-
B1s 1 1 GiB $-
B2ms 2 8 GiB $-
B2s 2 4 GiB $-
B4ms 4 16 GiB $-
B8ms 8 32 GiB $-
B12ms 12 48 GiB $-
B16ms 16 64 GiB $-
B20ms 20 80 GiB $-

Storage

You are charged for the storage that you provision for your server. Storage can be provisioned up to 16 TB and includes 3 IOPS/GB of storage.

Price
GB/month $-

Additional IOPS

You can scale your IOPS to optimise the performance of an IO intensive operation. You will be provisioned 1000 free IOPS per server and charged based on the additional IOPS used rounded up to the nearest minute. See more information on additional IOPS.

Price
IOPS/month $-

Paid IO

Azure Database for MySQL will automatically scale your IOPS depending on the workload without the need for you to manually preprovision IOPS. This is a cost-effective IO model which charges only for what the workload consumes. Learn more

Price
Paid IO Locally redundant storage (LRS) $- Per 1 million requests
Paid IO Zone redundant storage (ZRS) $- Per 1 million requests

Back up Storage

Back up storage is the storage associated with automated backups of your server. Increasing your backup retention period increases the backup storage that is consumed by your server. There is no additional charge for backup storage for up to 100% of your total provisioned server storage. Additional consumption of backup storage will be charged in GB/month.

Not available Price Note
GB/month $- GRS requires twice the amount of storage capacity because it creates a replica. If you have configured the back up storage to be geo-redundant (GRS), the price will be 2x this price. Price per GB remains the same.

General Purpose

Most business workloads requiring balanced compute and memory with scalable I/O throughput.

General Purpose Compute

Instance vCores Memory Pay as you go 1 year reserved 3 year reserved
D2ds v4 2 8 GiB $- $-
$-
D4ds v4 4 16 GiB $- $-
$-
D8ds v4 8 32 GiB $- $-
$-
D16ds v4 16 64 GiB $- $-
$-
D32ds v4 32 128 GiB $- $-
$-
D48ds v4 48 192 GiB $- $-
$-
D64ds v4 64 256 GiB $- $-
$-

General Purpose AMD

Instance vCores Memory Pay as you go 1 year reserved 3 year reserved
D2as v4 2 8 GiB $- $-
$-
D4as v4 4 16 GiB $- $-
$-
D8as v4 8 32 GiB $- $-
$-
D16as v4 16 64 GiB $- $-
$-
D32as v4 32 128 GiB $- $-
$-
D48as v4 48 192 GiB $- $-
$-
D64as v4 64 256 GiB $- $-
$-

Storage

You are charged for the storage that you provision for your server. Storage can be provisioned up to 16 TB and includes 3 IOPS/GB of storage.

Price
GB/month $-

Additional IOPS

You can scale your IOPS to optimise the performance of an IO intensive operation. You will be provisioned 1000 free IOPS per server and charged based on the additional IOPS used rounded up to the nearest minute. See more information on additional IOPS.

Price
IOPS/month $-

Paid IO

Azure Database for MySQL will automatically scale your IOPS depending on the workload without the need for you to manually preprovision IOPS. This is a cost-effective IO model which charges only for what the workload consumes. Learn more

Price
Paid IO Locally redundant storage (LRS) $- Per 1 million requests
Paid IO Zone redundant storage (ZRS) $- Per 1 million requests

Back up Storage

Back up storage is the storage associated with automated backups of your server. Increasing your backup retention period increases the backup storage that is consumed by your server. There is no additional charge for backup storage for up to 100% of your total provisioned server storage. Additional consumption of backup storage will be charged in GB/month.

Not available Price Note
GB/month $- GRS requires twice the amount of storage capacity because it creates a replica. If you have configured the back up storage to be geo-redundant (GRS), the price will be 2x this price. Price per GB remains the same.

Read Replica

Read replicas allow read-heavy workloads to scale out beyond the capacity of a single Azure Database for MySQL Flexible server. Each read replica is billed for provisioned compute in vCores and storage in GB/month.

Business Critical

High performance database workloads requiring in-memory performance for faster transaction processing and higher concurrency.

Business Critical Compute

Instance vCores Memory Pay as you go 1 year reserved 3 year reserved
E2ds v4 2 16 GiB $- $-
$-
E4ds v4 4 32 GiB $- $-
$-
E8ds v4 8 64 GiB $- $-
$-
E16ds v4 16 128 GiB $- $-
$-
E32ds v4 32 256 GiB $- $-
$-
E48ds v4 48 384 GiB $- $-
$-
E64ds v4 64 504 GiB $- $-
$-
E80ds v4 80 504 GiB $- $-
$-
E96ds v4 96 672 GiB $- $-
$-

Business Critical AMD

Instance vCores Memory Pay as you go 1 year reserved 3 year reserved
E2as v4 2 16 GiB $- $-
$-
E4as v4 4 32 GiB $- $-
$-
E8as v4 8 64 GiB $- $-
$-
E16as v4 16 128 GiB $- $-
$-
E20as v4 20 160 GiB $- $-
$-
E32as v4 32 256 GiB $- $-
$-
E48as v4 48 384 GiB $- $-
$-
E64as v4 64 504 GiB $- $-
$-
E96as v4 96 672 GiB $- $-
$-

Storage

You are charged for the storage that you provision for your server. Storage can be provisioned up to 16 TB and includes 3 IOPS/GB of storage.

Price
GB/month $-

Additional IOPS

You can scale your IOPS to optimise the performance of an IO intensive operation. You will be provisioned 1000 free IOPS per server and charged based on the additional IOPS used rounded up to the nearest minute. See more information on additional IOPS.

Price
IOPS/month $-

Paid IO

Azure Database for MySQL will automatically scale your IOPS depending on the workload without the need for you to manually preprovision IOPS. This is a cost-effective IO model which charges only for what the workload consumes. Learn more

Price
Paid IO Locally redundant storage (LRS) $- Per 1 million requests
Paid IO Zone redundant storage (ZRS) $- Per 1 million requests

Back up Storage

Back up storage is the storage associated with automated backups of your server. Increasing your backup retention period increases the backup storage that is consumed by your server. There is no additional charge for backup storage for up to 100% of your total provisioned server storage. Additional consumption of backup storage will be charged in GB/month.

Not available Price Note
GB/month $- GRS requires twice the amount of storage capacity because it creates a replica. If you have configured the back up storage to be geo-redundant (GRS), the price will be 2x this price. Price per GB remains the same.

Read Replica

Read replicas allow read-heavy workloads to scale out beyond the capacity of a single Azure Database for MySQL Flexible server. Each read replica is billed for provisioned compute in vCores and storage in GB/month.

Unique capabilities to reduce total cost of ownership

Flexible and transparent pricing

Scale compute and storage independently based on your workload. Only pay for what you use.

Optimise your cost

Save up to 60% compared to pay-as-you-go options with reserved capacity. Reduce total cost of ownership with burstable instances and Stop/Start capabilities so when the database is stopped, you only pay for storage.

Choice of deployment option

Deployment options to meet your database management and customisation needs with deployment options including Single Server and Flexible Server.

Azure pricing and purchasing options

Connect with us directly

Get a walkthrough of Azure pricing. Understand pricing for your cloud solution, learn about cost optimisation and request a customised proposal.

Talk to a sales specialist

See ways to purchase

Purchase Azure services through the Azure website, a Microsoft representative or an Azure partner.

Explore your options

Additional resources

Azure Database for MySQL

Learn more about Azure Database for MySQL features and capabilities.

Pricing calculator

Estimate your expected monthly costs for using any combination of Azure products.

SLA

Review the Service Level Agreement for Azure Database for MySQL.

Documentation

Review technical tutorials, videos, and more Azure Database for MySQL resources.

  • Flexible Server is billed on a predictable, hourly rate. You are billed for the compute and storage you provision and the back up storage you consume. On your bill, you will see a separate line item for compute, storage, and back up storage. Compute is billed per vCore-hour. Storage and back up storage are billed per GB-month.
  • For each read replica you create, you are billed for the provisioned compute in vCores and provisioned storage in GB-month in the region where your replica is provisioned.
  • Servers enabled with HA have a primary and secondary replica. Secondary replica can be in same zone or zone redundant. You are billed for the provisioned compute and storage for both the primary and secondary replica. For example, if you have a primary with 4 vCores of compute and 512 GB of provisioned storage, your secondary replica will also have 4 vCores and 512 GB of provisioned storage. Your zone redundant HA server will be billed for 8 vCores and 1,024 GB of storage. An extra 36 IOPs per node in addition to the configured IOPs on your servers will be added and reserved, so additional charges for the 72 IOPs per month would apply based on your Azure region for HA enabled servers. Depending on your back up storage volume, you may also be billed for back up storage.
  • Back up storage is the storage associated with automated backups of your server, including data and log backups. Increasing your backup retention period increases the backup storage that is consumed by your server. There is no additional charge for backup storage for up to 100% of your total provisioned storage for your primary server. Additional consumption of backup storage will be charged in GB-month. For example, if your primary server has a storage size of 512 GBs, you will get 512 GBs of backup at no additional cost. However, if the backup is 612 GBs, you will pay for the incremental 100 GBs.
  • You are billed for each full hour that your server exists regardless of whether the server was active for the full hour. If you have scaled up your database, you will be billed for the higher number of vCores used within the hour. If you have switched between two compute tiers, you will be billed for the higher priced compute tier.

    For example:

    • If you create a server and delete it after five minutes, you are charged for one full hour for the provisioned compute and storage.
    • If you create a server with 8 vCores of General Purpose compute and then immediately scale up to 16 vCores of General Purpose compute, you are charged for 16 vCores of General Purpose compute for the first hour.
    • If you create a server with General Purpose compute with 8 vCores and then immediately upgrade it to Memory Optimised compute with 8 vCores, you are charged for 8 vCores Memory Optimised compute for the first hour.
  • While your server is stopped, you will only be billed for the storage you have provisioned and any back up storage you consume that exceed 100% of your primary provisioned storage volume. While your server is stopped, you will not be billed for compute.
  • Yes. Standard networking charges apply for network egress. Refer here for more details.

Talk to a sales specialist for a walk-through of Azure pricing. Understand pricing for your cloud solution.

Get free cloud services and a $200 credit to explore Azure for 30 days.

Added to estimate. Press 'v' to view on calculator
Can we help you?