The 4.3.0 release supports both standard mode and restricted mode.

This release of the Console agent includes security improvements, bug fixes, and the following features:

You can now validate network connections of connected Console agents directly from the NetApp Console. This feature helps verify connectivity and troubleshoot issues with Console agents.

Learn how to run configuration checks on Console agents.

To support Cloud Volumes ONTAP management in Google Cloud, the Console agent now requires an additional permission. The following permission has been added to the service account used by the Console agent: compute.forwardingRules.update

View the permissions change log.

This release includes the following:

You can now enable federation for a NetApp Console organization that is in restricted mode. This allows users to log in to the Console using their corporate credentials while maintaining the security benefits of restricted mode.

You can set a NetApp Console organization to read-only mode. In read-only mode, users can view resources and settings but cannot make any changes. An Org admin or Super admin can enable read-only mode for an organization. When read-only mode is enabled, users with administrative roles must manually elevate their permissions to make changes as needed.

Learn how to enable read-only mode for a Console organization.

Learn how to elevate your role when your organization is in read-only mode.

If you're using Disaster Recovery on-premises, you can now deploy a Console agent for each vCenter instance, improving resiliency.

For example, if you have two sites (Sites A and B), Site A can have Console agent A attached to vCenter 1, ONTAP deployment 1 and ONTAP deployment 2. Site B can have Console agent B attached to vCenter 2 and ONTAP deployments 3 and 4.

For information about the Console agent in Disaster Recovery, see Create the Console agent.

When failover is triggered, any replication plan using datastore-based protection includes VMs that have been added to the datastore, provided they have been discovered. You must provide mapping details for the added VMs before failover completes.

For more information, see Fail over applications.

Disaster Recovery now provides email notifications for the following events:

You can now access the Swagger documentation from within Disaster Recovery. In Disaster Recovery, select Settings then API documentation to link to the Swagger, or visit this URL in your browser's incognito/private mode: https://snapcenter.cloudmanager.cloud.netapp.com/api/api-doc/draas.

Disaster Recovery now provides improved warnings and error resolutions. This release fixes an error that prevented canceled jobs from displaying in the user interface. Canceled jobs are now visible. There's also a new warning when the same destination network is mapped to multiple different source networks.

When you create a replication, the new default is to retain the VM folder structure. If the recovery target does not have the original folder hierarchy, Disaster Recovery creates it. You can deselect this option to disregard the original folder hierarchy.

For more information, see Create a replication plan.

Ransomware Resilience now supports adding replication of snapshots to a secondary ONTAP site. You can create a ransomware protection strategy that includes replication or use the predefined strategy. With protection groups that use a replication policy, you can replicate to the same destination or different destinations for every workload.

For more information, see Protect workloads in Ransomware Resilience.

Ransomware Resilience now supports excluding specific workloads in a system from protection and the Ransomware Resilience dashboard. You can exclude workloads after discovery, and re-include them if you want to add ransomware protection. You aren't billed for excluded workloads.

For more information, see Exclude workloads.

Ransomware Resilience now allows you to mark alerts as "In review." Use the "In review" label to improve clarity across your team when triaging and managing active ransomware threats.

For more information, see Manage alerts in Ransomware Resilience.

You can now select a preferred billing option for calculating your Cloud Volumes ONTAP usage and overages. Since the limited availability of the Bring Your Own Licenses (BYOL) licensing model on June 25, 2025, NetApp has added preferred charging methods in the Licensing and Subscriptions section of the NetApp Console. You can use either your annual marketplace subscription for billing and overages or the existing BYOL model as the preferred option. This gives you the flexibility to choose the charging method that best fits your organization's financial strategy and usage patterns.

Billing preferences and overages.

The 4.2.0 release supports both standard mode and restricted mode.

This release of the Console agent includes security improvements, bug fixes, and the following features:

NetApp now uses Google Cloud Infrastructure Manager (IM) instead of Google Cloud Deployment Manager to deploy agents and manage agents in Google Cloud. This change was made because Google will be deprecating Cloud Deployment Manager.

When you need to manually install an agent, you can access agent software directly from the NetApp Console in addition to the NetApp Support site. Learn how to download the Console agent software directly from the NetApp Console.

This release includes the following:

Set notifications for expiring credentials on service accounts and federations. Choose between seven or 30 days. The Console displays notifications and emails users with the appropriate role. Org admins receive service account notifications. Org admins, Federation admins, and Federation viewers receive federation notifications.

After you turn on federation for a Console organization, users cannot use local logins and are sent to federation logins.

Detailed information about your ONTAP on-premises systems (and FSx for ONTAP) is now easier to view and manage from the Storage management pages.

The Systems page in NetApp Console has improvements for clarity and usability when managing volumes and clusters. These updates align the experience more closely with System Manager for newer ONTAP versions and simplify navigation.

The Systems > Overview page displays the cluster size alongside the ONTAP version for clusters running ONTAP 9.5 and higher.

For NetApp Console in restricted mode or ONTAP versions 9.5 and lower, the volume provisioned information remains unchanged.

When you have more than 20 on-premises ONTAP clusters managed in NetApp Console, the Volume tab defaults to grid view for easier navigation. Card view is disabled.

This change applies to standard mode only and for ONTAP versions 9.6 and higher.

By default, Disaster Recovery retains the VM inventory hierarchy (folder structure) on failover. If the recovery target doesn't have the required folder, Disaster Recovery creates it.

You can now override this setting by designating a new parent VM folder or by unchecking the Retain original folder hierarchy option.

For more information, see Create a replication plan.

Disaster Recovery now supports a streamlined process for using multiple Console agents in a working environment. To switch between Console agents, you must edit your vCenter configuration, rediscover the credentials, and refresh the replication plans to use the new Console agent.

For more information, see Switch Console agents.

The preview release of VMware workloads introduces the following enhanced capabilities:

Learn more about restoring VMware VMs with NetApp Backup and Recovery.

Learn more about restoring VMware virtual disks with NetApp Backup and Recovery.

This release of Data Classification includes bug fixes and the following updates:

Data Classification now provides a health monitoring dashboard, providing real-time monitoring of your resources and insights into memory usage, disk usage, disk utilization, and more. With insights from the health monitoring dashboard, you can review the infrastructure of your deployment and gain insights to optimize storage and performance.

For more information, see Monitor the health of Data Classification.

The loading performance for all pages in Data Classification has been improved to create a more efficient user experience.

When you enable extension blocking, it's now enabled at the workload level rather than the storage VM level.

Ransomware Resilience now enables you to edit the status of user behavior alerts. You can manually dismiss and resolve alerts.

For more information, see Manage alerts in Ransomware Resilience.

Ransomware Resilience now supports using multiple Console agents to manage the same systems.

For more information about Console agents, see Create a Console agent.

You can now enhance the performance of Premium SSD v2 Managed Disks in Azure by modifying the IOPS and throughput parameters. Using this capability, you can optimize the storage performance of your systems based on your workload requirements.

Manage Premium SSD v2 disk performance for Cloud Volumes ONTAP in Azure.

For Cloud Volumes ONTAP marketplace annual contracts/private offers, overage calculations for Essentials licenses is now aligned with Bring Your Own License (BYOL) packages. Previously, overages were billed at hourly marketplace rates for the exact Essentials package. Now, if your marketplace annual contract includes multiple Essentials packages, the NetApp Console charges overages for an Essentials package against the available capacity of a higher-priced Essentials package in your subscription. This simplifies overage calculations for Essentials packages and ensures a smooth transition from BYOL licensing to a subscription-based model.

How overages are charged for Essentials licenses

Beginning with Cloud Volumes ONTAP 9.17.1, you can deploy Azure Edsv6 series VMs through the NetApp Console for new Cloud Volumes ONTAP instances. Cloud Volumes ONTAP 9.17.1 and later will support only Generation 2 VMs for new deployments. These Generation 2 machines are compatible with the latest technologies, such as Unified Extensible Firmware Interface (UEFI), Azure Boost systems, and NVMe. They are ideal for memory-intensive systems and applications that need fast, local storage, such as database servers and analytics engines.

Supported configurations for Cloud Volumes ONTAP in Azure

The label Accrued burst capacity is renamed to Accrued burst.

NetApp Disaster Recovery now supports Google Cloud VMware Engine using Google Cloud NetApp Volumes for migration, failover, failback, and testing operations. This integration enables seamless disaster recovery workflows between on-premises environments and Google Cloud.

Ensure you review the prerequisites and limitations for Google Cloud.

As customers setup and authorize more Google Cloud NetApp Volumes systems, how credentials are managed have changed.

NetApp Volumes systems credentials are now stored on a Google cloud backend, such as Cloud Key Management service or similar, and service account impersonation credentials are used when creating a new system.

In the Complete your coverage notification box on Monitoring > Alert monitors, each subscription now displays its tracking ID beside the subscription number.

The ONTAP System Manager interface can be used with an AWS Lambda link to perform advanced ONTAP operations. This provides an alternative to using a Console agent with System Manager for managing an FSx for ONTAP file system directly from the Console. Learn about using links for advanced ONTAP operations

Data replication is available between an on-premises ONTAP system and an FSx for ONTAP file system from the NetApp Console Systems page.

Replicate data

You can now configure and manage Billing preferences directly within in NetApp Console.
This enhancement enables administrators to define and view how capacity usage, renewals, and costs are billed across direct NetApp licenses, cloud marketplace subscriptions, and Keystone agreement.

For more information, see the Billing preferences documentation.

This release of the Console agent includes security improvements, bug fixes, and the following features:

The 4.1.0 release is available for standard mode and restricted mode.

Renamed the status indicators for the Console agent from Active and Inactive to Connected and Disconnected to make their purpose more clear.

When manually installing a Console agent, the agent now supports RHEL 9.6 with Podman 5.4.0. In addition, when using RHEL 9 and higher, NetApp supports podman-compose 1.5.0. View operating system requirements.

This release includes the following:

The email address that sends NetApp Console notifications has changed to service@console.netapp.com from service@console.bluexp.netapp.com. NetApp recommends updating any email rules to allow service@console.netapp.com to ensure you continue to receive NetApp Console email notifications.

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

Scan configurations now include improved insights into scan completion. Previously, a progress bar only displayed while the scan was in progress. Now, the progress bar remains visible after completion to confirm scans were completed successfully. You're also able to view the number of files mapped and scanned.

For more information about scan settings, see Change the NetApp Data Classification scan settings for your repositories.

You can now configure a cascading relationship in ONTAP and use any leg of that replication relationship for disaster recovery.

Disaster Recovery now supports downgrading VMware hardware to an earlier version of vSphere during registration. This is useful when the source ESX host is running a later version than the disaster recovery site.

For more information, see Create a replication plan in NetApp Disaster Recovery.

Disaster Recovery now gracefully shuts down VMs instead of powering them off. If a given VM takes more than ten minutes to power down, Disaster Recovery powers it off.

You can now inject custom scripting into the failover workflow to run before creating a backup. Pre-backup scripting enables you to control the VM's state before a snapshot is replicated and prepare a VM for a transition. For example, you can inject a script that unmounts an NFS mount that will be remounted using a different script after failover.

For more information, see Create a replication plan in NetApp Disaster Recovery.

Earlier, when deploying Cloud Volumes ONTAP instances over NVMe-TCP, you would have to to manually obtain and apply NVMe licenses before deployment. With this update, Cloud Volumes ONTAP now automatically installs the required NVMe licenses during deployment, simplifying the setup process.

For existing NVMe-TCP deployments that lack licenses, Cloud Volumes ONTAP applies the licenses automatically. You must restart the system for the licenses to take effect.

For more information, see Supported client protocols for Cloud Volumes ONTAP: NVMe-TCP.

The Alerts monitors tab on the Monitoring page includes a Complete your coverage notification box that appears when coverage gaps exist. This box lists subscriptions missing capacity or expiration monitors, and monitors with no subscriptions. You can address the gaps by adding subscriptions to existing monitors, creating new monitors, or deleting unused monitors. To learn more, refer to Manage coverage gaps for alert monitors.

Cloud Volumes ONTAP deployments and upgrades in Azure through the NetApp Console are now restricted to the latest supported versions. This ensures compatibility with the latest generation hardware supported by Microsoft and provides the newest features and security enhancements. The Console will prompt you to upgrade to the supported versions.

For more details, refer to: