Azure Container Storage is a volume management and orchestration service for containers on Kubernetes, including AKS. Version 2 uses local NVMe disks of the cluster nodes as backing storage.
Title graphic: Azure Container Storage (Product)
Relationships
Azure Container Storage is a product and part of Microsoft Azure.
Description
Azure Container Storage is a cloud-based service in Microsoft Azure for managing, provisioning and orchestrating volumes for containers. It integrates with Kubernetes, including Azure Kubernetes Service (AKS), and creates persistent volumes dynamically for stateful applications. Volumes are handled with standard Kubernetes tooling, so CSI drivers do not have to be installed manually. The product is part of Microsoft Azure and is documented on Microsoft Learn.
The current documentation covers version 2, which supports two storage types. The first is local NVMe, which uses local NVMe disks on AKS nodes of certain storage-optimized and GPU VM sizes. The documentation names latency-critical workloads such as PostgreSQL, and AI or machine learning frameworks such as Ray and Kubeflow, as typical fits. The second is Elastic SAN, a managed resource provisioned per volume or snapshot. Elastic SAN supports snapshots, replication with LRS and ZRS, and encryption. Volumes attach to the workload through NVMe over Fabrics or iSCSI.
The choice between the two types mainly follows from durability needs. Local NVMe volumes are ephemeral by default. They offer no snapshots or replication, and no data is kept after the pod is deleted unless the application replicates it itself. That makes local NVMe a fit for hot or temporary data, while Elastic SAN is the option when snapshots, replication and encryption are needed. Anyone planning a deployment should also know the stated limits: only Linux-based Kubernetes clusters are supported, version 2 does not support Azure Disks (which remain with version 1), and availability is limited to a subset of regions. Installation works as an AKS extension or through Helm, and the source is open. Licensing terms are not stated in the documentation, and prices are covered on a separate page.
The M365.FM episode "Speed Fabric and AKS Workloads with Local NVMe Storage" (2025-11-03) looks at the local NVMe side of version 2, which it abbreviates as ACStor v2. The episode argues that data-platform workloads are often slow because data sits far from compute, and that managed storage adds network hops, IOPS caps and latency on every read and write. Its proposed remedy is proximity: placing hot data on local NVMe inside the AKS nodes. According to the episode, this is done through a lean, CSI-based, ephemeral driver that stripes across all NVMe disks of a node, with throughput described as multi-GB/s and roughly one million IOPS. The episode also says that no SAN, LVM or etcd is involved and that the capacity comes from VM families such as L-series, Dv6 and NC, which are already paid for. It suggests uses such as Spark shuffles, Dataflows Gen2 staging and Direct Lake caches. These figures and recommendations are the episode's own statements rather than values from the product documentation.
Taken together, Azure Container Storage v2 is a storage layer for Kubernetes workloads that moves the choice of backing storage into a Kubernetes-native workflow. The local NVMe option trades durability for speed and proximity, so applications that use it need their own replication or a way to rebuild the data. The Elastic SAN option gives managed durability features instead. Teams evaluating the service typically weigh latency requirements, data-loss tolerance, VM size availability, region coverage and the Linux-only restriction against each other.
Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.
Your Fabric and Power Platform workloads aren’t slow because of Spark or DAX—they’re slow because your data lives far from your compute. Managed storage adds network hops, caps IOPS, and taxes every read/write with latency. The fix isn’t “more nodes”; it’s…
Frequently asked questions
Questions marked with AI were written with AI from the facts on this page.
What does Azure Container Storage version 2 use as backing storage? (AI)
Version 2 supports two storage types: local NVMe disks on AKS nodes of certain storage-optimized and GPU VM sizes, and Elastic SAN as a managed resource. Azure Disks are not supported in version 2 and remain with version 1.
Is data on local NVMe volumes kept after a pod is deleted? (AI)
No. Local NVMe volumes are ephemeral by default, offer no snapshots or replication, and keep no data after the pod is deleted unless the application replicates the data itself.
Which clusters and regions does Azure Container Storage support? (AI)
Only Linux-based Kubernetes clusters are supported, and availability is limited to a subset of regions. It can be installed as an AKS extension or through Helm.
What is Azure Container Storage v2?
ACStor v2 puts hot data on local NVMe inside AKS nodes using a lean, CSI-based, ephemeral driver. It stripes across all NVMe disks and needs no SANs, LVM or etcd. · From the episode: Speed Fabric and AKS Workloads with Local NVMe Storage
Related topics in brief
Topics linked to Azure Container Storage, each briefly explained:
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Experts and companies for this topic
Nobody has listed this topic yet. Add it to your profile.
Experts on related topics
Experts on topics related to Azure Container Storage, each with the topic that connects them: