Skip to main content
Cloud Volumes ONTAP release notes

Known limitations for Cloud Volumes ONTAP in Azure

PDFs

The following known limitations are specific to Cloud Volumes ONTAP in Microsoft Azure. Be sure to also review Limitations for Cloud Volumes ONTAP in all cloud providers.

Limitations with using Azure VM extensions

Cloud Volumes ONTAP does not support Azure virtual machine (VM) extensions because they affect BlueXP management operations. During deployment, BlueXP prevents the installation of any extensions on your VMs. If extensions are already installed on your existing Cloud Volumes ONTAP VMs, contact Microsoft Azure Support to remove them. For guidance, refer to the knowledge base (KB) article Can Azure VM Management Extensions be installed into Cloud Volume ONTAP?

Starting July 14, 2025, NetApp will send emails and notify you in BlueXP if VM extensions are detected on your Cloud Volumes ONTAP VMs.

Flash Cache limitations

Cloud Volumes ONTAP uses the local NVMe storage in some VM types as Flash Cache. Note this limitation:

  • Cache rewarming after a reboot is not supported.

Limitations with high-availability deployments

High-availability (HA) pairs aren't supported in some regions.

View the list of supported Azure regions.

Limitations with HA deployments in single availability zones

Beginning with Cloud Volumes ONTAP 9.15.1, you can deploy virtual machine (VM) instances in HA mode in single availability zones (AZs) in Azure. For information about the criteria supporting this feature, refer to Deploy HA pairs in single availability zones in Azure.

If the Cloud Volumes ONTAP version is earlier than 9.15.1 or if any of these conditions are not met, the previous deployment model utilizing availability sets becomes effective. This applies to only HA configurations.