Azure managed disk types
Applies to: ✔️ Linux VMs ✔️ Windows VMs ✔️ Flexible scale sets ✔️ Uniform scale sets
Azure managed disks currently offers five disk types, each intended to address a specific customer scenario:
- Ultra disks
- Premium SSD v2
- Premium SSDs (solid-state drives)
- Standard SSDs
- Standard HDDs (hard disk drives)
Disk type comparison
The following table provides a comparison of the five disk types to help you decide which to use.
|Ultra disk||Premium SSD v2||Premium SSD||Standard SSD|
|Scenario||IO-intensive workloads such as SAP HANA, top tier databases (for example, SQL, Oracle), and other transaction-heavy workloads.||Production and performance-sensitive workloads that consistently require low latency and high IOPS and throughput||Production and performance sensitive workloads||Web servers, lightly used enterprise applications and dev/test||Backup, non-critical, infrequent access|
|Max disk size||65,536 GiB||65,536 GiB||32,767 GiB||32,767 GiB||32,767 GiB|
|Max throughput||4,000 MB/s||1,200 MB/s||900 MB/s||750 MB/s||500 MB/s|
|Max IOPS||160,000||80,000||20,000||6,000||2,000, 3,000*|
|Usable as OS Disk?||No||No||Yes||Yes||Yes|
* Only applies to disks with performance plus (preview) enabled.
For a video that covers some high level differences for the different disk types, and some ways for determining what impacts your workload requirements, see Block storage options with Azure Disk Storage and Elastic SAN.
Azure ultra disks are the highest-performing storage option for Azure virtual machines (VMs). You can change the performance parameters of an ultra disk without having to restart your VMs. Ultra disks are suited for data-intensive workloads such as SAP HANA, top-tier databases, and transaction-heavy workloads.
Ultra disks must be used as data disks and can only be created as empty disks. You should use Premium solid-state drives (SSDs) as operating system (OS) disks.
Ultra disk size
Azure ultra disks offer up to 32-TiB per region per subscription by default, but ultra disks support higher capacity by request. To request an increase in capacity, request a quota increase or contact Azure Support.
The following table provides a comparison of disk sizes and performance caps to help you decide which to use.
|Disk Size (GiB)||IOPS Cap||Throughput Cap (MB/s)|
|1,024-65,536 (sizes in this range increasing in increments of 1 TiB)||160,000||4,000|
Ultra disks are designed to provide submillisecond latencies and target IOPS and throughput described in the preceding table 99.99% of the time.
Ultra disk performance
Ultra disks feature a flexible performance configuration model that allows you to independently configure IOPS and throughput both before and after you provision the disk. Ultra disks come in several fixed sizes, ranging from 4 GiB up to 64 TiB.
Ultra disk IOPS
Ultra disks support IOPS limits of 300 IOPS/GiB, up to a maximum of 160,000 IOPS per disk. To achieve the target IOPS for the disk, ensure that the selected disk IOPS are less than the VM IOPS limit.
The current maximum limit for IOPS for a single VM in generally available sizes is 80,000. Ultra disks with greater IOPS can be used as shared disks to support multiple VMs.
The minimum guaranteed IOPS per disk are 1 IOPS/GiB, with an overall baseline minimum of 100 IOPS. For example, if you provisioned a 4-GiB ultra disk, the minimum IOPS for that disk is 100, instead of four.
For more information about IOPS, see Virtual machine and disk performance.
Ultra disk throughput
The throughput limit of a single ultra disk is 256-KiB/s for each provisioned IOPS, up to a maximum of 4000 MB/s per disk (where MB/s = 10^6 Bytes per second). The minimum guaranteed throughput per disk is 4KiB/s for each provisioned IOPS, with an overall baseline minimum of 1 MB/s.
You can adjust ultra disk IOPS and throughput performance at runtime without detaching the disk from the virtual machine. After a performance resize operation has been issued on a disk, it can take up to an hour for the change to take effect. Up to four performance resize operations are permitted during a 24-hour window.
It's possible for a performance resize operation to fail because of a lack of performance bandwidth capacity.
Ultra disk limitations
Ultra disks can't be used as OS disks, they can only be created as empty data disks. Ultra disks also can't be used with some features and functionality, including disk export, changing disk type, VM images, availability sets, or Azure disk encryption. The size of an Ultra Disk can't be expanded without either deallocating the VM or detaching the disk. Azure Backup and Azure Site Recovery do not support ultra disks. In addition, only un-cached reads and un-cached writes are supported. Snapshots for ultra disks are available but have additional limitations. See Incremental snapshots of Premium SSD v2 and Ultra Disks for details.
Ultra disks support a 4k physical sector size by default. A 512E sector size is available as a generally available offering with no sign-up required. While most applications are compatible with 4k sector sizes, some require 512 byte sector sizes. Oracle Database, for example, requires release 12.2 or later in order to support 4k native disks. For older versions of Oracle DB, 512 byte sector size is required.
The only infrastructure redundancy options currently available to ultra disks are availability zones. VMs using any other redundancy options cannot attach an ultra disk.
The following table outlines the regions ultra disks are available in, as well as their corresponding availability options.
If a region in the following list lacks availability zones that support ultra disks, then a VM in that region must be deployed without infrastructure redundancy in order to attach an ultra disk.
|Single VMs||Australia Central
Germany West Central
North Central US, South Central US, West US
US Gov Arizona, US Gov Texas, US Gov Virginia
|One availability zone||Brazil Southeast
|Two availability zones||South Africa North
China North 3
|Three availability zones||Australia East
North Europe, West Europe
Central US, East US, East US 2, West US 2, West US 3
Not every VM size is available in every supported region with ultra disks. The following table lists VM series which are compatible with ultra disks.
|General purpose||DSv3-series, Ddsv4-series, Dsv4-series, Dasv4-series, Dsv5-series, Ddsv5-series, Dasv5-series||Balanced CPU-to-memory ratio. Ideal for testing and development, small to medium databases, and low to medium traffic web servers.|
|Compute optimized||FSv2-series||High CPU-to-memory ratio. Good for medium traffic web servers, network appliances, batch processes, and application servers.|
|Memory optimized||ESv3-series, Easv4-series, Edsv4-series, Esv4-series, Esv5-series, Edsv5-series, Easv5-series, Ebsv5 series, Ebdsv5 series, M-series, Mv2-series, Msv2/Mdsv2-series||High memory-to-CPU ratio. Great for relational database servers, medium to large caches, and in-memory analytics.|
|Storage optimized||LSv2-series, Lsv3-series, Lasv3-series||High disk throughput and IO ideal for Big Data, SQL, NoSQL databases, data warehousing and large transactional databases.|
|GPU optimized||NCv2-series, NCv3-series, NCasT4_v3-series, ND-series, NDv2-series, NVv3-series, NVv4-series, NVadsA10 v5-series||Specialized virtual machines targeted for heavy graphic rendering and video editing, as well as model training and inferencing (ND) with deep learning. Available with single or multiple GPUs.|
|HB-series, HC-series, HBv2-series||The fastest and most powerful CPU virtual machines with optional high-throughput network interfaces (RDMA).|
If you would like to start using ultra disks, see the article on using Azure Ultra Disks.
Premium SSD v2
Premium SSD v2 offers higher performance than Premium SSDs while also generally being less costly. You can individually tweak the performance (capacity, throughput, and IOPS) of Premium SSD v2 disks at any time, allowing workloads to be cost efficient while meeting shifting performance needs. For example, a transaction-intensive database may need a large amount of IOPS at a small size, or a gaming application may need a large amount of IOPS but only during peak hours. Because of this, for most general purpose workloads, Premium SSD v2 can provide the best price performance.
Premium SSD v2 is suited for a broad range of workloads such as SQL server, Oracle, MariaDB, SAP, Cassandra, Mongo DB, big data/analytics, and gaming, on virtual machines or stateful containers.
Premium SSD v2 support a 4k physical sector size by default, but can be configured to use a 512E sector size as well. While most applications are compatible with 4k sector sizes, some require 512 byte sector sizes. Oracle Database, for example, requires release 12.2 or later in order to support 4k native disks. For older versions of Oracle DB, 512 byte sector size is required.
Differences between Premium SSD and Premium SSD v2
Unlike Premium SSDs, Premium SSD v2 doesn't have dedicated sizes. You can set a Premium SSD v2 to any supported size you prefer, and make granular adjustments to the performance without downtime. Premium SSD v2 doesn't support host caching but, benefits significantly from lower latency, which addresses some of the same core problems host caching addresses. The ability to adjust IOPS, throughput, and size at any time also means you can avoid the maintenance overhead of having to stripe disks to meet your needs.
Premium SSD v2 limitations
- Premium SSD v2 disks can't be used as an OS disk.
- Currently, Premium SSD v2 disks can only be attached to zonal VMs.
- Currently, encryption at host isn't supported for Premium SSD v2 disks. You can still attach Premium SSD v2 disks to VMs where you have enabled encryption at host for disk types.
- Azure Disk Encryption (guest VM encryption via Bitlocker/DM-Crypt) isn't supported for VMs with Premium SSD v2 disks. We recommend you to use encryption at rest with platform-managed or customer-managed keys, which is supported for Premium SSD v2.
- Currently, Premium SSD v2 disks can't be attached to VMs in Availability Sets.
- Azure Backup and Azure Site Recovery aren't supported for VMs with Premium SSD v2 disks.
- The size of a Premium SSD v2 can't be expanded without either deallocating the VM or detaching the disk.
Currently only available in the following regions:
- North Europe
- West Europe
- East US
- East US 2
- West US 2
Premium SSD v2 performance
With Premium SSD v2 disks, you can individually set the capacity, throughput, and IOPS of a disk based on your workload needs, providing you with more flexibility and reduced costs. Each of these values determines the cost of your disk.
Premium SSD v2 capacities
Premium SSD v2 capacities range from 1 GiB to 64 TiBs, in 1-GiB increments. You're billed on a per GiB ratio, see the pricing page for details.
Premium SSD v2 offers up to 32 TiBs per region per subscription by default, but supports higher capacity by request. To request an increase in capacity, request a quota increase or contact Azure Support.
Premium SSD v2 IOPS
All Premium SSD v2 disks have a baseline IOPS of 3000 that is free of charge. After 6 GiB, the maximum IOPS a disk can have increases at a rate of 500 per GiB, up to 80,000 IOPS. So an 8 GiB disk can have up to 4,000 IOPS, and a 10 GiB can have up to 5,000 IOPS. To be able to set 80,000 IOPS on a disk, that disk must have at least 160 GiBs. Increasing your IOPS beyond 3000 increases the price of your disk.
Premium SSD v2 throughput
All Premium SSD v2 disks have a baseline throughput of 125 MB/s that is free of charge. After 6 GiB, the maximum throughput that can be set increases by 0.25 MB/s per set IOPS. If a disk has 3,000 IOPS, the max throughput it can set is 750 MB/s. To raise the throughput for this disk beyond 750 MB/s, its IOPS must be increased. For example, if you increased the IOPS to 4,000, then the max throughput that can be set is 1,000. 1,200 MB/s is the maximum throughput supported for disks that have 5,000 IOPS or more. Increasing your throughput beyond 125 increases the price of your disk.
Premium SSD v2 Sector Sizes
Premium SSD v2 supports a 4k physical sector size by default. A 512E sector size is also supported. While most applications are compatible with 4k sector sizes, some require 512-byte sector sizes. Oracle Database, for example, requires release 12.2 or later in order to support 4k native disks. For older versions of Oracle DB, 512-byte sector size is required.
The following table provides a comparison of disk capacities and performance maximums to help you decide which to use.
|Disk Size||Maximum available IOPS||Maximum available throughput (MB/s)|
|1 GiB-64 TiBs||3,000-80,000 (Increases by 500 IOPS per GiB)||125-1,200 (increases by 0.25 MB/s per set IOPS)|
To deploy a Premium SSD v2, see Deploy a Premium SSD v2.
Azure Premium SSDs deliver high-performance and low-latency disk support for virtual machines (VMs) with input/output (IO)-intensive workloads. To take advantage of the speed and performance of Premium SSDs, you can migrate existing VM disks to Premium SSDs. Premium SSDs are suitable for mission-critical production applications, but you can use them only with compatible VM series.
To learn more about individual Azure VM types and sizes for Windows or Linux, including size compatibility for premium storage, see Sizes for virtual machines in Azure. You'll need to check each individual VM size article to determine if it's premium storage-compatible.
Premium SSD size
|Premium SSD sizes||P1||P2||P3||P4||P6||P10||P15||P20||P30||P40||P50||P60||P70||P80|
|Disk size in GiB||4||8||16||32||64||128||256||512||1,024||2,048||4,096||8,192||16,384||32,767|
|Base provisioned IOPS per disk||120||120||120||120||240||500||1,100||2,300||5,000||7,500||7,500||16,000||18,000||20,000|
|**Expanded provisioned IOPS per disk||N/A||N/A||N/A||N/A||N/A||N/A||N/A||N/A||8,000||16,000||20,000||20,000||20,000||20,000|
|Base provisioned Throughput per disk||25 MB/s||25 MB/s||25 MB/s||25 MB/s||50 MB/s||100 MB/s||125 MB/s||150 MB/s||200 MB/s||250 MB/s||250 MB/s||500 MB/s||750 MB/s||900 MB/s|
|**Expanded provisioned Throughput per disk||N/A||N/A||N/A||N/A||N/A||N/A||N/A||N/A||300 MB/s||600 MB/s||900 MB/s||900 MB/s||900 MB/s||900 MB/s|
|Max burst IOPS per disk||3,500||3,500||3,500||3,500||3,500||3,500||3,500||3,500||30,000*||30,000*||30,000*||30,000*||30,000*||30,000*|
|Max burst throughput per disk||170 MB/s||170 MB/s||170 MB/s||170 MB/s||170 MB/s||170 MB/s||170 MB/s||170 MB/s||1,000 MB/s*||1,000 MB/s*||1,000 MB/s*||1,000 MB/s*||1,000 MB/s*||1,000 MB/s*|
|Max burst duration||30 min||30 min||30 min||30 min||30 min||30 min||30 min||30 min||Unlimited*||Unlimited*||Unlimited*||Unlimited*||Unlimited*||Unlimited*|
|Eligible for reservation||No||No||No||No||No||No||No||No||Yes, up to one year||Yes, up to one year||Yes, up to one year||Yes, up to one year||Yes, up to one year||Yes, up to one year|
*Applies only to disks with on-demand bursting enabled.
** Only applies to disks with performance plus (preview) enabled.
Capacity, IOPS, and throughput are guaranteed when a premium storage disk is provisioned. For example, if you create a P50 disk, Azure provisions 4,095-GB storage capacity, 7,500 IOPS, and 250-MB/s throughput for that disk. Your application can use all or part of the capacity and performance. Premium SSDs are designed to provide the single-digit millisecond latencies, target IOPS, and throughput described in the preceding table 99.9% of the time.
Premium SSD bursting
Premium SSDs offer disk bursting, which provides better tolerance on unpredictable changes of IO patterns. Disk bursting is especially useful during OS disk boot and for applications with spiky traffic. To learn more about how bursting for Azure disks works, see Disk-level bursting.
Premium SSD transactions
For Premium SSDs, each I/O operation less than or equal to 256 KiB of throughput is considered a single I/O operation. I/O operations larger than 256 KiB of throughput are considered multiple I/Os of size 256 KiB.
Azure standard SSDs are optimized for workloads that need consistent performance at lower IOPS levels. They're an especially good choice for customers with varying workloads supported by on-premises hard disk drive (HDD) solutions. Compared to standard HDDs, standard SSDs deliver better availability, consistency, reliability, and latency. Standard SSDs are suitable for web servers, low IOPS application servers, lightly used enterprise applications, and non-production workloads. Like standard HDDs, standard SSDs are available on all Azure VMs.
Standard SSD size
|Standard SSD sizes||E1||E2||E3||E4||E6||E10||E15||E20||E30||E40||E50||E60||E70||E80|
|Disk size in GiB||4||8||16||32||64||128||256||512||1,024||2,048||4,096||8,192||16,384||32,767|
|Base IOPS per disk||Up to 500||Up to 500||Up to 500||Up to 500||Up to 500||Up to 500||Up to 500||Up to 500||Up to 500||Up to 500||Up to 500||Up to 2,000||Up to 4,000||Up to 6,000|
|*Expanded IOPS per disk||N/A||N/A||N/A||N/A||N/A||N/A||N/A||N/A||Up to 1,500||Up to 3,000||Up to 6,000||Up to 6,000||Up to 6,000||Up to 6,000|
|Base throughput per disk||Up to 60 MB/s||Up to 60 MB/s||Up to 60 MB/s||Up to 60 MB/s||Up to 60 MB/s||Up to 60 MB/s||Up to 60 MB/s||Up to 60 MB/s||Up to 60 MB/s||Up to 60 MB/s||Up to 60 MB/s||Up to 400 MB/s||Up to 600 MB/s||Up to 750 MB/s|
|*Expanded throughput per disk||N/A||N/A||N/A||N/A||N/A||N/A||N/A||N/A||Up to 150 MB/s||Up to 300 MB/s||Up to 600 MB/s||Up to 750 MB/s||Up to 750 MB/s||Up to 750 MB/s|
|Max burst IOPS per disk||600||600||600||600||600||600||600||600||1000|
|Max burst throughput per disk||150 MB/s||150 MB/s||150 MB/s||150 MB/s||150 MB/s||150 MB/s||150 MB/s||150 MB/s||250 MB/s|
|Max burst duration||30 min||30 min||30 min||30 min||30 min||30 min||30 min||30 min||30 min|
* Only applies to disks with performance plus (preview) enabled.
Standard SSDs are designed to provide single-digit millisecond latencies and the IOPS and throughput up to the limits described in the preceding table 99% of the time. Actual IOPS and throughput may vary sometimes depending on the traffic patterns. Standard SSDs provide more consistent performance than the HDD disks with the lower latency.
Standard SSD transactions
For standard SSDs, each I/O operation less than or equal to 256 KiB of throughput is considered a single I/O operation. I/O operations larger than 256 KiB of throughput are considered multiple I/Os of size 256 KiB. These transactions incur a billable cost but, there's an hourly limit on the number of transactions that can incur a billable cost. If that hourly limit is reached, additional transactions during that hour no longer incur a cost. For details, see the blog post.
Standard SSD Bursting
Standard SSDs offer disk bursting, which provides better tolerance for the unpredictable IO pattern changes. OS boot disks and applications prone to traffic spikes will both benefit from disk bursting. To learn more about how bursting for Azure disks works, see Disk-level bursting.
Azure standard HDDs deliver reliable, low-cost disk support for VMs running latency-tolerant workloads. With standard storage, your data is stored on HDDs, and performance may vary more widely than that of SSD-based disks. Standard HDDs are designed to deliver write latencies of less than 10 ms and read latencies of less than 20 ms for most IO operations. Actual performance may vary depending on IO size and workload pattern, however. When working with VMs, you can use standard HDD disks for dev/test scenarios and less critical workloads. Standard HDDs are available in all Azure regions and can be used with all Azure VMs.
Standard HDD size
|Standard Disk Type||S4||S6||S10||S15||S20||S30||S40||S50||S60||S70||S80|
|Disk size in GiB||32||64||128||256||512||1,024||2,048||4,096||8,192||16,384||32,767|
|Base IOPS per disk||Up to 500||Up to 500||Up to 500||Up to 500||Up to 500||Up to 500||Up to 500||Up to 500||Up to 1,300||Up to 2,000||Up to 2,000|
|*Expanded IOPS per disk||N/A||N/A||N/A||N/A||N/A||Up to 1,500||Up to 3,000||Up to 3,000||Up to 3,000||Up to 3,000||Up to 3,000|
|Base throughput per disk||Up to 60 MB/s||Up to 60 MB/s||Up to 60 MB/s||Up to 60 MB/s||Up to 60 MB/s||Up to 60 MB/s||Up to 60 MB/s||Up to 60 MB/s||Up to 300 MB/s||Up to 500 MB/s||Up to 500 MB/s|
|*Expanded throughput per disk||N/A||N/A||N/A||N/A||N/A||Up to 150 MB/s||Up to 300 MB/s||Up to 500 MB/s||Up to 500 MB/s||Up to 500 MB/s||Up to 500 MB/s|
* Only applies to disks with performance plus (preview) enabled.
Standard HDD Transactions
For Standard HDDs, each I/O operation is considered as a single transaction, whatever the I/O size. These transactions have a billing impact.
When using managed disks, the following billing considerations apply:
- Disk type
- Managed disk Size
- Outbound data transfers
- Number of transactions
Managed disk size: Managed disks are billed according to their provisioned size. Azure maps the provisioned size (rounded up) to the nearest offered disk size. For details of the disk sizes offered, see the previous tables. Each disk maps to a supported provisioned disk-size offering and is billed accordingly. For example, if you provisioned a 200-GiB standard SSD, it maps to the disk size offer of E15 (256 GiB). Billing for any provisioned disk is prorated hourly by using the monthly price for the storage offering. For example, you provision an E10 disk and delete it after 20 hours of use. In this case, you're billed for the E10 offering prorated to 20 hours, regardless of the amount of data written to the disk.
Snapshots: Snapshots are billed based on the size used. For example, you create a snapshot of a managed disk with provisioned capacity of 64 GiB and actual used data size of 10 GiB. In this case, the snapshot is billed only for the used data size of 10 GiB.
For more information on snapshots, see the section on snapshots in the managed disk overview.
Outbound data transfers: Outbound data transfers (data going out of Azure data centers) incur billing for bandwidth usage.
Transactions: You're billed for the number of transactions performed on a standard managed disk. For standard SSDs, each I/O operation less than or equal to 256 KiB of throughput is considered a single I/O operation. I/O operations larger than 256 KiB of throughput are considered multiple I/Os of size 256 KiB. For Standard HDDs, each IO operation is considered a single transaction, whatever the I/O size.
For detailed information on pricing for managed disks (including transaction costs), see Managed Disks Pricing.
Ultra disks VM reservation fee
Azure VMs have the capability to indicate if they're compatible with ultra disks. An ultra disk-compatible VM allocates dedicated bandwidth capacity between the compute VM instance and the block storage scale unit to optimize the performance and reduce latency. When you add this capability on the VM, it results in a reservation charge. The reservation charge is only imposed if you enabled ultra disk capability on the VM without an attached ultra disk. When an ultra disk is attached to the ultra disk compatible VM, the reservation charge wouldn't be applied. This charge is per vCPU provisioned on the VM.
For constrained core VM sizes, the reservation fee is based on the actual number of vCPUs and not the constrained cores. For Standard_E32-8s_v3, the reservation fee will be based on 32 cores.
Refer to the Azure Disks pricing page for ultra disk pricing details.
Azure disk reservation
Disk reservation provides you with a discount on the advance purchase of one year's of disk storage, reducing your total cost. When you purchase a disk reservation, you select a specific disk SKU in a target region. For example, you may choose five P30 (1 TiB) Premium SSDs in the Central US region for a one year term. The disk reservation experience is similar to Azure reserved VM instances. You can bundle VM and Disk reservations to maximize your savings. For now, Azure Disks Reservation offers one year commitment plan for Premium SSD SKUs from P30 (1 TiB) to P80 (32 TiB) in all production regions. For more information about reserved disks pricing, see Azure Disks pricing page.
See Managed Disks pricing to get started.
Submit and view feedback for