Azure Managed Disks

About Azure Managed Disks

Azure Managed Disks is Microsoft Azure's managed block storage service for Azure Virtual Machines. Instead of creating and maintaining storage accounts for individual virtual hard disks, teams choose a disk type, capacity and redundancy model while Azure manages the underlying storage placement. Managed Disks are used for operating system disks, persistent data disks and selected shared-disk scenarios. The main buying decision is not whether the service can store VM data, but which disk type, performance level, redundancy and protection model matches the workload without paying for capacity or I/O that the application does not need.

What are Azure Managed Disks used for?

Azure Managed Disks provide persistent block storage for Azure virtual machines and related IaaS workloads. Microsoft describes them as virtualized disks that behave like physical disks attached to a server, while Azure handles the underlying storage account management. Teams use managed disks for VM operating systems, application data, databases, development environments and workloads that need direct block storage rather than a file share or object store.

Managed disks are tightly connected to Azure Virtual Machines, but they are a separate product decision because disk type and performance can materially affect application responsiveness and cost. A VM that is sized correctly for CPU and memory can still perform poorly if the attached disk cannot deliver the required IOPS or throughput.

Which Azure Managed Disk types should buyers compare?

Microsoft currently documents five managed disk types: Ultra Disk, Premium SSD v2, Premium SSD, Standard SSD and Standard HDD. Ultra Disk is aimed at the most demanding I/O-intensive workloads and allows performance to be adjusted independently from capacity. Premium SSD v2 also separates capacity, IOPS and throughput so teams can tune performance without moving through fixed disk-size performance tiers.

Premium SSD uses predefined disk sizes and performance characteristics and is a common choice for production workloads that need consistent SSD performance. Standard SSD is positioned for lighter production or development workloads that benefit from SSD latency without Premium pricing. Standard HDD is the lowest-cost option for workloads that can tolerate higher latency and lower performance. Microsoft has announced that Standard HDD OS disk support retires on September 8, 2028, so new long-lived VM designs should account for that lifecycle change.

How do performance and pricing work?

Managed Disks do not have one fixed monthly price. Microsoft bills according to disk type, provisioned capacity and, for selected products, separately provisioned IOPS and throughput. Premium SSD and Standard tiers commonly use size-based SKUs, while Premium SSD v2 and Ultra Disk provide more independent performance configuration. Standard SSD and Standard HDD can also include transaction-related charges, and shared-disk mounts or snapshots can create additional meters.

Pricing was checked against Microsoft's current Managed Disks pricing page on August 26, 2026. Buyers should estimate storage capacity, required IOPS, sustained throughput, bursting behavior, snapshot growth and attachment pattern together. Selecting a larger fixed-tier disk only to gain more IOPS can waste capacity, while underprovisioning storage performance can leave expensive VM compute waiting on disk operations.

What availability and redundancy options are available?

Microsoft states that managed disks are designed for 99.999 percent availability and that Azure maintains three copies of managed disk data. Locally redundant storage keeps those copies inside one datacenter in the selected region. Zone-redundant storage synchronously replicates the disk across three availability zones in supported regions and provides higher durability against a zonal failure.

LRS generally offers lower write latency because all copies remain within one datacenter, while ZRS trades some latency for additional zone resilience. Redundancy should be selected from application requirements rather than by default. A database that already writes synchronously across zones may use a different disk strategy from a single VM that must survive a zone outage without rebuilding storage.

How do snapshots, backup and disaster recovery fit together?

Managed disk snapshots are read-only point-in-time copies that exist independently from the source disk and can be used to create new managed disks. Microsoft also supports incremental snapshots, Azure Backup, restore points and Azure Site Recovery in supported scenarios. These tools solve different recovery problems and should not be treated as interchangeable.

Snapshots are useful for point-in-time disk copies and operational workflows, but they do not coordinate application consistency across several striped disks by themselves. Azure Backup adds policy-driven protection and retention, while Site Recovery addresses replicated disaster-recovery scenarios. Teams should define recovery point and recovery time objectives first, then choose the protection method rather than relying on ad hoc snapshots as the complete backup strategy.

How are managed disks encrypted and secured?

Azure Managed Disks are encrypted at rest by default with Azure Storage server-side encryption. Microsoft also supports customer-managed keys through disk encryption sets for organizations that need control over encryption keys. Encryption at host is another VM-level option that extends protection to temporary disks and disk caches and keeps data encrypted as it moves from the host into Azure Storage.

The security model still requires careful identity and network design. Export and import operations, snapshot access, role assignments and customer-managed key permissions can expose data if configured too broadly. Microsoft has also announced the retirement of Azure Disk Encryption on September 15, 2028 and recommends newer designs use encryption at host or other supported encryption approaches where appropriate.

When should teams use shared managed disks?

Azure shared disks allow one managed disk to be attached to multiple virtual machines at the same time for clustered applications that expect shared block storage. Microsoft currently supports shared-disk scenarios on Ultra Disk, Premium SSD v2, Premium SSD and Standard SSD. The application still needs a cluster manager such as Windows Server Failover Cluster or Pacemaker to coordinate ownership and writes.

Shared managed disks are not the same as a managed file service. They expose shared block devices and use SCSI persistent reservations rather than SMB or NFS file semantics. Host caching is not supported on shared disks, and several disk-type-specific restrictions apply. Teams that simply need a shared folder should usually compare Azure Files instead of building a cluster around shared block storage.

What are the main limitations and migration tradeoffs?

Managed Disks simplify storage administration, but buyers still need to understand VM-level throughput limits, regional availability, attachment limits, caching behavior and disk-type restrictions. A disk capable of very high IOPS will not deliver that performance if the selected VM size has a lower storage throughput ceiling. Ultra Disk, Premium SSD v2 and shared-disk configurations also have feature and regional constraints that should be checked before standardization.

Migration planning should include disk sizing, operating system disk requirements, encryption, snapshots, availability zones and application downtime. Moving a legacy server to Azure without measuring its actual storage workload can lead to overspending or poor performance. Teams should benchmark representative reads and writes and use Azure Monitor data after migration to right-size both the VM and its disks.

Who should choose something else?

Choose Azure Files when applications need a managed SMB or NFS file share rather than block storage attached to a VM. Choose Azure Blob Storage for object data, media, archives or application content accessed through object APIs. Large environments that want pooled SAN-style storage across many workloads should also evaluate Azure Elastic SAN where its architecture and regional support fit.

Azure Managed Disks are strongest when the workload runs on Azure Virtual Machines and needs persistent block storage with a clear choice of capacity, performance and resilience. Buyers should choose the disk type from measured I/O requirements and recovery needs rather than treating Premium storage as automatically necessary for every production VM.