You can now deploy Cloud Volumes ONTAP 9.12.1 GA and later in single and multiple availability zones in Azure in the Malaysia West (malaysiawest) region. This includes support for both single-node and high-availability (HA) deployments.

For a list of all regions, refer to the Global Regions Map under Azure.

In this release, ONTAP Volumes workloads introduces the following enhancement:

Support for S3-compatible cloud storage: NetApp Backup and Recovery for Volumes workloads now supports backing up to S3-compatible cloud storage.

For details about protecting ONTAP Volumes workloads, refer to Protect ONTAP Volumes workloads overview.

In this release, Hyper-V workloads introduces the following enhancements:

For details about protecting Hyper-V workloads, refer to Protect Hyper-V workloads overview.

This release of Data Classification includes security improvements and performance enhancements.

Disaster Recovery has introduced the following changes for Kubernetes-based workloads:

Ransomware Resilience now provides more flexibility in choosing ransomware detection strategies. Previously, all ransomware protection strategies had to include encryption detection. Now, you can enable a ransomware protection strategy with only user behavior detection.

Protection strategies can still include both encryption detection and suspicious user behavior detection. Blocking file extensions can also be added to any protection strategy.

If you disable part of the protection strategy for an existing policy, any extant alerts created under the previous iteration of the policy can only be marked as "Resolved" not "Dismissed." For example, if you had a protection strategy that included encryption detection and suspicious user behavior but you disabled encryption detection, you can only resolve an existing encryption alert for that workload.

For more information, see Protect workloads with NetApp Ransomware Resilience protection strategies.

Ransomware Resilience SOAR playbooks now provide remediation steps after you've blocked a user or taken a volume offline. You can now take a volume back online and unblock a user if the action was deemed not a ransomware threat.

Integrate a SOAR playbook.

Cloud Volumes ONTAP 9.16.1 and later support M6id and M6idn EC2 instance families for both new and existing single-node and high-availability (HA) pair deployments in AWS. These 6th-generation instances offer faster processing power, stronger networking capabilities, and higher performance compared to the 5th generation general purpose systems.

We do not recommend the smaller-sized m6id.xlarge, m6id.2xlarge, m6idn.xlarge, and m6idn.2xlarge instance types for high-performance or memory-intensive workloads. For these workloads, use an instance type with a higher core count and larger memory.

For more information, refer to Supported configurations for Cloud Volumes ONTAP in AWS.

The following Lifecycle planning features have name changes:

The following Digital Advisor features have name changes:

Ransomware Resilience now supports creating protection groups for workloads in Google Cloud NetApp Volumes systems, enabling you to organize multiple workloads under one policy to streamline management.

For more information, see Create a protection group in Ransomware Resilience.

The subscription timeline chart now shows a number when multiple subscription updates of different types occur on the same day, instead of separate icons. Hover over the number to see all update types for that day. The downloaded report includes a separate row for each update, giving you a complete record of all changes. To learn more, refer to View the timeline of your Keystone subscriptions.

Ransomware Resilience now supports Google Cloud NetApp Volumes systems, enabling you to efficiently detect and respond to ransomware threats in Google Cloud NetApp Volumes. When you conduct discovery, Ransomware Resilience automatically displays workloads from Google Cloud NetApp Volumes systems. When you discover the systems, they appear in the Ransomware Resilience dashboard. Support for Google Cloud NetApp Volumes in Ransomware Resilience is currently in preview.

For more information, see Learn about Ransomware Resilience. For information about the scope of Google Cloud NetApp Volumes support, review Limitations in Ransomware Resilience.

Clean restore now supports reports. With reports, you can review and assess clean restores, saving this information offline as a CSV file.

Clean restore also now support stopping the analysis. If you stop the analysis, you must begin the clean restore again.

To learn more about reports, see Download reports in Ransomware Resilience. To learn more about recovery, see Recover workloads with a clean restore.

You can now use Quick create to deploy Cloud Volumes ONTAP in Azure for both single-node and high-availability (HA) configurations. This streamlined process reduces the number of steps compared to the advanced method, automatically sets default values on a single page, and minimizes navigation, making deployment faster and easier.

Starting July 2026, the Wellness Review feature will no longer be available in Digital Advisor. For any questions, send an email to ng-activeiq-feedback@netapp.com.

NetApp offers enhanced billing options for your Cloud Volumes ONTAP subscriptions in AWS, giving you more control over how you pay for Cloud Volumes ONTAP capacity and NetApp data services, such as NetApp Backup and Recovery.
Previously, all Cloud Volumes ONTAP and data services usage were billed together through the NetApp Intelligent Services (NIS) listing in the AWS marketplace.

Due to changes in AWS Enterprise Discount Program (EDP), NetApp has introduced a standalone Cloud Volumes ONTAP subscription in the AWS marketplace that allows you to separate the billing of Cloud Volumes ONTAP capacity from data services. This separation gives you more flexibility in managing your EDP credits and costs. NetApp recommends using the standalone subscription for better cost management of your Cloud Volumes ONTAP usage, while continuing to use the NIS subscription for billing data services after July 31, 2026, when the EDP requirements take effect.

The standalone Cloud Volumes ONTAP subscription in AWS supports only valid capacity-based Essentials or Freemium license packages. The Professional package is not supported. You can select the billing method that best suits your needs:

Depending on your subscription type, you get these scenarios:

If you have only a standalone AWS subscription associated with your AWS account in the NetApp Console and no NIS subscriptions, you can select only the Essentials license package during deployment. The data services Backup and Recovery option is unavailable to you.

If you have both NIS and standalone subscriptions associated with your AWS account, and you haven't set a billing preference through the Billing preferences tab in the NetApp Console, Cloud Volumes ONTAP usage continues to bill through NIS by default. This is also the default for any Cloud Volumes ONTAP instance running the Professional package, because the standalone listing does not support Professional. You can set a billing preference and choose how to bill each service:

This is applicable if you are an existing customer with NIS subscriptions associated with the AWS account. You can continue billing both Cloud Volumes ONTAP and data services together as you do now. However, NetApp recommends switching to the standalone subscription approach for better cost management of your Cloud Volumes ONTAP usage:

The 4.7.0 release supports both standard mode and restricted mode.

This release of the Console agent includes security improvements and bug fixes.

This release includes the following new feature.

By default, Digital Advisor shows all NetApp accounts associated with your company, rather than just your Console organization. To limit what is shown in Digital Advisor to a specific account, verify the business account you want to use with your Console organization. Learn how to verify your Console organization

In this release, Hyper-V workloads introduces the following enhancements:

For details about protecting Hyper-V workloads, refer to Protect Hyper-V workloads overview.

In this release, KVM workloads introduces the following enhancement:

Restore to alternate location: You can now restore KVM VMs to an alternate destination (this feature is now generally available).

For details about protecting KVM workloads, refer to Protect KVM workloads overview.

In this release, Oracle Database workloads introduces the following enhancements:

For details about protecting Oracle Database workloads, refer to Protect Oracle Database workloads overview.

In this release, VMware workloads introduces the following enhancements:

For details about protecting VMware workloads, refer to Protect VMware workloads overview.

In this release, Kubernetes workloads introduces the following enhancements:

For details about protecting Kubernetes workloads, refer to Protect Kubernetes workloads overview.

Data Classification has updated and improved the Configuration page, enabling an improved usability experience to manage settings, systems, enable scanning, and monitor system health. The new Configuration page provides the existing functionality in an easier to use format in addition to the ability to filter systems by type, error status, and scan status. The new page also provides a summary of connected systems and overviews of active and configured scans.

Review a video walkthrough. For more information, see Scan data sources with Data Classification.

Data Classification now supports a Compliance admin role to manage permissions in Data Classification. The Compliance admin role doesn't have access to resources including Console agents and workspaces. Users with the Compliance admin role must be associated with at least one other role.

When installing Data Classification, you should have a Console platform admin role or the Compliance admin role.

If you're an existing user, access should continue as normal. For example, a platform role that has a folder or project admin role has existing access.

For more information, see Data Classification roles.

NetApp Data Classification now supports deployment with VMware Open Virtual Appliance (OVA), offering a simplified deployment strategy for on-premises VMware vSphere environments.

For more information, see Deploy Data Classification with OVA.

NetApp Disaster Recovery now includes support for Kubernetes-based workloads. With Kubernetes support, you can protect applications running on Kubernetes clusters, including OpenShift Virtualization environments. Disaster Recovery supports any version of Kubernetes currently supported by Trident Protect, ensuring seamless integration and robust disaster recovery capabilities for containerized applications.

Key features of Kubernetes-based workload support:

Support for Kubernetes-based workloads is currently in preview. To begin protecting Kubernetes-based workloads, see Kubernetes requirements for NetApp Disaster Recovery.

Clean restore now supports recovering to an alternate location, enabling you to restore volumes to different systems, storage VMs, and aggregates managed by the same Console agent. Additionally, clean restore has removed the seven-day limitation in searching for viable snapshots for recovery. Clean restore now continues looking through available snapshots for a viable recovery point regardless of distance from the ransomware event.

Recover workloads with a clean restore.

Ransomware Resilience now supports security information and event management (SIEM) with Google SecOps, enabling you to send data automatically to Google SecOps for streamlined threat analysis and detection.

For configuration information, see Connect Ransomware Resilience to a SIEM.

Ransomware Resilience now supports Azure NetApp Files systems, enabling you to efficiently detect and respond to ransomware threats in Azure NetApp Files. When you discover workloads, Ransomware Resilience now presents Azure NetApp Files and displays them in the protection dashboard. Ransomware Resilience support for Azure NetApp Files includes detection and protection strategies with snapshots only. Support for Azure NetApp Files is now generally available (GA).

For more information, see Learn about Ransomware Resilience.

Ransomware Resilience now supports blocking individual users with Google SecOps and Splunk SOAR playbooks. With this addition, you can automate blocking users when Ransomware Resilience detects suspicious user activity such as a data breach or mass deletion of data.

Integrate a SOAR playbook.

In this release, Kubernetes workloads introduces the following enhancements:

For details about protecting Kubernetes workloads, refer to Protect Kubernetes workloads overview.

The label Provisioned capacity is renamed to Provisioned volume capacity. The updated label is also reflected in the related CSV and Excel reports.

You can now use the Forecast toggle in the Accrued burst view of the Consumption trend tab to project accrued burst usage for the next 120 days from the current date. To learn more, refer to View forecast data.

In this release, VMware workloads introduces the following enhancement:

ASA r2 SAN support: VMware workloads now supports protecting VMs on VMFS datastores hosted by NetApp ASA r2 SAN-only environments.

For details about protecting VMware workloads, refer to Protect VMware workloads overview.

The 4.6.0 release supports both standard mode and restricted mode.

This release of the Console agent includes security improvements and bug fixes as well as the following new feature.

You can validate that the required disk space for the Console agent is available using configuration checks. You can perform configuration checks from the Console or the Agent maintenance console. Learn more about running configuration checks on the Console agent

If you deployed a Console agent in vCenter using an OVA, you can now upgrade it to a new version by mounting an ISO to the VM and running the upgrade from the VM maintenance console. Learn how to upgrade a vCenter-deployed Console agent

In this release, ONTAP Volumes workloads introduces the following enhancement:

NetApp MetroCluster active/active configurations supported: NetApp Backup and Recovery for Volumes workloads now supports MetroCluster in the active-active configuration.

For details about protecting ONTAP Volumes workloads, refer to Protect ONTAP Volumes workloads overview.

In this release, Kubernetes workloads introduces the following protection policy enhancements:

For more information about protection policies, refer to Create and manage protection policies in NetApp Backup and Recovery.

For details about protecting Kubernetes workloads, refer to Protect Kubernetes workloads overview.

In this release, Hyper-V workloads introduces the following enhancements:

For details about protecting Hyper-V workloads, refer to Protect Hyper-V workloads overview.

In this release, KVM workloads introduces the following enhancements:

For details about protecting KVM workloads, refer to Protect KVM workloads overview.

In this release, VMware workloads introduces the following enhancements:

For details about protecting VMware workloads, refer to Protect VMware workloads overview.

This release of Data Classification includes bug fixes, security improvements, and performance enhancements.

NetApp Cloud Tiering is no longer available for purchase or license renewal as of April 26, 2026.

Existing customers can continue to use and receive support for NetApp Cloud Tiering until their subscription or license contract expires. After the subscription expires, customers will no longer have access to NetApp Cloud Tiering features or support.

NetApp recommends customers work with their NetApp representative to transition their existing tiering licenses to ONTAP FabricPool licenses, which provides the functionality for data tiering in ONTAP. See Install a FabricPool license on an ONTAP cluster for more information on how to set up data tiering in ONTAP using FabricPool.

NetApp Disaster Recovery support for GCVE is now generally available (GA). With GA support, Disaster Recovery for GCVE now supports:

For more information about support for GCVE, learn about supported configurations for Disaster Recovery.

Ransomware Resilience now supports clean restores, a new recovery option that helps you quickly and easily recover from ransomware attacks. Clean restores offer guided workflows that identify optimal restore points to get your workloads up and running while minimizing downtime. The workflows in clean restore also provide file-level insights into your data, ensuring you can restore malware-free workloads that prevents reinfection and minimizes data loss.

To learn about supported configurations and how to configure your system for a clean restore, see Create an isolated recovery environment. To learn how to recover with a clean restore, see Recover workloads with a clean restore.

Ransomware Resilience now provides security information event management (SIEM) support for Splunk Enterprise, enabling you to centralize log and event data and streamline threat analysis and detection.

For more information, see Connect Ransomware Resilience to a SIEM.

Insights into data breach events are now retained for 13 months after an incident, enabling longer record-keeping for your reporting needs.

For more information, see Learn about user behavior detection.

Replication
:leveloffset: +1

Cloud Volumes ONTAP now has enhanced support for the Google Cloud C3 series VMs, enabling these additional capabilities:

In this release, Oracle Database workloads introduces the following enhancement:

For details about protecting Oracle Database workloads, refer to Protect Oracle Database workloads overview.

Ransomware Resilience now offers a security orchestration, automation, and response (SOAR) playbook for Google SecOps. The playbook enables easier threat response management, automating tasks and tests, and supporting essential ransomware response efforts including creating snapshots and taking a volume offline.

For more information, see Integrate SOAR playbooks.

The historical consumption chart in the Consumption trend tab now highlights usage that exceeds the burst limit. To learn more, refer to View consumption trends of your Keystone subscriptions.

You can use the Forecast toggle in the Historical consumption view of the Consumption trend tab to project capacity usage for the next 120 days from the current date. To learn more, refer to View forecast data.

The subscriptions report downloaded from the Subscriptions page now includes the Tracking ID in the performance service level data for both Excel and CSV formats.

On the Subscriptions page, the Keystone version column is now hidden by default, and the Linked subscriptions column appears only when linked subscriptions are available.

In this release, VMware workloads introduces the following enhancements:

VM consistency support per schedule tier: You can now enable VM-consistent and app-consistent backups for specific schedule tiers when configuring protection policies for VMware workloads. Yearly, monthly, and weekly tiers are supported.

For details about protecting VMware workloads, refer to Protect VMware workloads overview.