License and subscription information is displayed automatically only when your Console account is also associated with a NetApp Support Site (NSS) account. If your Console account is not associated with an NSS account, you need to manually add licenses. Usage, capacity, and other details also won't automatically update. Learn how to add your NetApp Support Site account to Console credentials.

You need a Console agent deployed to view subscription information. An agent is also required to view direct licenses for Cloud Volumes ONTAP.

You can manage licenses and subscriptions for Backup and Recovery, Cloud Tiering, Cloud Volumes ONTAP, Disaster Recovery (BYOL only), and Ransomware Resilience.

Users with the Licenses and subscriptions admin role can add, edit, and remove direct licenses, and associate or disassociate Marketplace and Keystone subscriptions.

Users with the corresponding viewer permission can view licenses and subscriptions but cannot make changes.

The Overview dashboard is intended for reviewing and resolving existing licensing issues. To add a direct license, go to Direct licenses. To add or associate a Marketplace subscription, go to Marketplace subscriptions.

The Overview dashboard's Requires action tile alerts you to licenses and subscriptions that are expiring or reaching capacity limits. If Resolve doesn't display, there are no issues requiring action. Selecting Resolve takes you to a page where you can view and address issues from the Licenses or Subscriptions tab.

Associating your Console account with an NSS account lets the Console automatically detect and update your licenses. It is also required when you enter a serial number to add or update a license.

You need to manually obtain and upload a NetApp license file when the Console does not have internet access or when your Console account is not associated with an NSS account. In these cases, the Console cannot automatically query or update your licenses.

Node-based licensing is the previous-generation model. NetApp recommends capacity-based licensing for all new deployments, and existing node-based licenses must be converted. Learn how to convert a node-based license to a capacity-based license.

Exchanging an unassigned Cloud Volumes ONTAP license revokes that license and creates a dollar-equivalent license for the new service (NetApp Backup and Recovery, Data Classification, or Cloud Tiering).

The converted license keeps the same expiration date as the original Cloud Volumes ONTAP license.

The Console attempts to charge usage against an available NetApp license first. If sufficient license capacity is not available, it charges usage against a linked Marketplace PAYGO subscription.

Changing the capacity-based licensing package does not change whether usage is billed through a NetApp-purchased license (BYOL) or a Marketplace PAYGO subscription. You do not need to convert a BYOL license to a Marketplace subscription, or vice versa.

If you select a charging method that is not included in your Marketplace private offer or contract, that Marketplace package cannot be used. Usage is charged against a NetApp license, if available, or through PAYGO instead.

An Azure subscription or Google Cloud project can be associated with only one Marketplace subscription. If you want to use two different Marketplace subscriptions for workloads under the same Azure subscription or Google Cloud project, you must create two separate Console accounts, one for each subscription.

You can only remove subscriptions with a status of Unsubscribed, and all related settings, data, and configuration must be cleared or reset before removal. If the subscription is still configured, the Remove option is not available. Learn how to remove a subscription.

Accepting and activating a private offer multiple times can result in double charging. Skipping required steps in the acceptance process can also result in billing errors or activation issues.

If you notice discrepancies in the offer terms, pricing, or details, or you are unsure which offer to accept, do not accept the offer. Contact your NetApp sales or account team for clarification before proceeding.

If you already have an active PAYGO subscription or an amended private offer, you only need to perform the acceptance steps. In these cases, Google Cloud Marketplace updates the plan within the same listing and retains the same subscription ID, so the subscription association in the Console remains intact.

No. Your Google Cloud billing account must not be on a free trial, since free trial accounts cannot accept private offers. Attempting to use a trial billing account results in an error requiring assistance from the NetApp cloud team.

No duplicate metering occurs when you use multiple subscription types or migrate between listings.

NetApp must authorize your Console account for your Keystone subscriptions before you can use or manage them. This authorization makes eligible Keystone subscriptions available in NetApp Console. If the Welcome to NetApp Keystone page appears, follow the contact instructions on that page to request authorization. Learn more about authorizing your account for Keystone subscriptions.

Linking a Keystone subscription associates it with your Console organization or account and makes it available as a charging method when you create a new Cloud Volumes ONTAP working environment.

You can unlink a Keystone subscription only when it is not attached to an existing Cloud Volumes ONTAP subscription.

You can send a request to NetApp directly from the Console by entering the requested committed capacity for one or more subscriptions and submitting additional details. This creates a ticket in NetApp's system for processing.

"NetApp licenses first" prioritizes billing through your active NetApp licenses, and once that capacity is exhausted, usage rolls over to the linked Marketplace subscription. "Marketplace subscriptions only" directs all billing through Marketplace contracts, bypassing NetApp licenses entirely; this is common for organizations that standardize procurement through cloud provider billing.

Enable Custom CVO configuration if your organization needs to:

For example, if Business Unit A bills to one Azure subscription and Business Unit B bills to another, Custom CVO configuration lets you map each business unit's Cloud Volumes ONTAP instances to its own subscription.

Disabling Custom CVO configuration resets all Cloud Volumes ONTAP billing to the global billing mode (NetApp licenses first or Marketplace subscriptions only) used for your other data services, instead of the per-instance subscription mappings Custom CVO configuration allowed.

If both subscriptions are available for your AWS account, you can use Billing preferences to select which subscription is used for Cloud Volumes ONTAP capacity billing. For existing Cloud Volumes ONTAP systems already billed through NIS, adding the standalone subscription does not change billing unless you update Billing preferences. For new deployments created after the standalone subscription is available, the standalone subscription is used by default for capacity billing (Essentials/Freemium) unless you override it. Learn more about Cloud Volumes ONTAP licensing packages.

No. The standalone Cloud Volumes ONTAP subscription supports only capacity-based Essentials and Freemium packages; the Professional package is not supported and continues to bill through the NIS subscription. If you have only the standalone subscription associated, you can deploy Cloud Volumes ONTAP using Essentials, but configuring Backup and Recovery requires a different subscription. Learn more about Cloud Volumes ONTAP licensing packages.

Keystone fields connect metered service usage to your Keystone billing profile. The Agreement ID is a unique identifier that links the billing record in NetApp Console with your Keystone agreement and allows synchronization of usage reporting. Service scope lists the services or capacity pools covered by the Keystone agreement, clarifying which workloads or deployments are included and ensuring only eligible resources are billed through Keystone.