Azure Marketplace
One Azure bill for managed Instaclustr services. Subscribing to NetApp Instaclustr through Azure Marketplace links your Instaclustr account to your Azure billing account. Usage of your managed data services then appears on your monthly Azure bill alongside the rest of your cloud spend, with no separate Instaclustr contract or payment method to set up.
The subscription is the only thing that changes. You still create and operate clusters in the Instaclustr Console, receive the same managed service and support, and pay the same charges as customers who sign up with Instaclustr directly. Marketplace is simply a different route to purchase and pay.
This guide walks through the five things you need to get right: choosing the deployment model that matches where your clusters will run, understanding pricing, invoicing, and scope, completing the Marketplace subscription, creating your Instaclustr account and linking it to the subscription, and cancelling cleanly if you ever need to. Each section first covers what is common to both deployment models, followed by the steps specific to the RIIA (Run in Instaclustr’s Account) and BYOC (Bring Your Own Cloud) deployment models.
Before you start
-
Private Plan
- If NetApp has offered you a BYOC private plan, follow the Private Plan guide (PDF) that was emailed to you by your NetApp Sales representative to accept and activate the private plan, instead of following this documentation page.
-
Azure
- Role: you need to have an Azure subscription and the Owner or Contributor role assigned directly to your own user on that subscription. A role on a resource group alone is not enough. A role on a resource group alone is not enough. A role inherited from a management group or group membership may not be applied in time, ensure you have direct assignment on the subscription instead. Azure can take up to 20 minutes to apply a new role assignment, so if you assigned the role recently, wait for it to take effect before you start.
- Azure policies: your policies must allow the following resources to be created. If any of these are blocked, arrange a policy exemption before you start.
- RIIA: a SaaS subscription resource, in a new or existing resource group. If your policies restrict creating resource groups, make sure there is an existing resource group you can use.
- BYOC: a managed resource group, a storage account and a container registry.
-
Instaclustr account
- Sign-up email (BYOC only): you have access to the mailbox that will receive the sign-up email.
- Existing Instaclustr users only: if you will sign in with an existing Instaclustr user instead of creating a new one, that user must have Organization Owner access to the intended Organization, and “Prevent organization users from creating accounts outside the organization” must be turned off under Account Controls. If not, ask an existing Organization Owner to grant you Owner access and turn off this setting before you create your Instaclustr account.
Choose your deployment model
Start from the corresponding Instaclustr product listing in Azure Marketplace.
BYOCBring Your Own CloudSelect this listing when your deployment will run in your own Azure account.View BYOC listing in Marketplace ↗
Run in Instaclustr’s Account (RIIA)
Instaclustr operates the service in an Instaclustr-managed Azure account. Azure creates only a SaaS subscription resource in the resource group you choose. It represents your Instaclustr subscription in Azure, and is where you cancel it. No clusters or other infrastructure are created in your Azure subscription.
Bring Your Own Cloud (BYOC)
Your deployment runs in your own Azure account. The deployment uses two resource groups:
- Resource group you select: holds the Instaclustr Managed Application, which represents your BYOC subscription and links your Azure subscription to Instaclustr.
- Managed resource group: created by Azure, with administrative access granted to Instaclustr. It holds the storage account that stores cluster backups and the container registry that stores container images. Your clusters’ virtual machines, disks and networking are added later, when you create clusters.

Understand billing
Pricing display
Cluster and add-on costs appear in Instacredits. Use the Plans + Pricing tab to convert Instacredits to USD.
Invoice route
Service usage charges are included on your monthly Azure bill.
Commercial parity
Marketplace charges are the same as signing up with Instaclustr directly.
Scope
A subscription purchased through Azure Marketplace can only be used to create clusters on Azure infrastructure.
Run in Instaclustr’s Account (RIIA)
Instaclustr operates the service in an Instaclustr-managed Azure account, so the cloud infrastructure your clusters run on is included in the Instaclustr charges.
Bring Your Own Cloud (BYOC)
Your deployment runs in your own Azure account. Instaclustr charges cover the managed service only. Azure bills you separately for the infrastructure in your subscription, such as virtual machines, disks, the storage account and the container registry.
Complete the subscription flow
-
Select Get It Now
Open the RIIA or BYOC listing from Choose your deployment model, review the Marketplace offer and select Get It Now to begin activation. In the Azure portal, select the name of your subscription and the name of the plan from the dropdown menus, and review the pricing information in the Plans + Pricing tab. Then press the Subscribe button (RIIA) or the Create button (BYOC).
Then continue with the steps for your deployment model:
Run in Instaclustr’s Account (RIIA)
-
Complete the purchase
Enter all required information:
- Subscription: the Azure subscription that is billed for your Instaclustr usage.
- Resource group: holds the SaaS subscription resource. You can use an existing resource group or create a new one. No clusters are created in it.
- Name: a name for the SaaS subscription, so you can find it later in the Azure portal. It cannot be changed after purchase.
- Contact details: your name, email and an optional phone number, which Azure shares with NetApp Instaclustr after purchase.
Review the terms of use, then complete the purchase. This can take up to a minute, so keep the browser window open until it finishes.
Bring Your Own Cloud (BYOC)
-
Enter the application details
Enter all required information. The deployment uses two resource groups, as shown under Choose your deployment model. If you do not already have a resource group that you wish to use, you can press Create new to create a new resource group. Then press the Next button, and enter values into the Application Settings fields. The fields are used as follows:

- Subscription: the Azure subscription where your clusters and their resources are created and billed.
- Resource group: holds the Managed Application resource that links your Azure subscription to Instaclustr. A new, dedicated resource group is recommended.
- Region: where the storage account and container registry are created. Choose the region where you plan to create your clusters. To create clusters in another region later, contact Instaclustr Support first so that a storage account can be set up in that region.
- Application name: a new name that you choose. It identifies this deployment in Azure. Do not enter the name of an existing application.
- Managed resource group: created by Azure, with administrative access granted to Instaclustr. Keep the default, and do not change or delete anything inside it.
- Email (Application Settings): the address Instaclustr sends the sign-up link to. It must exactly match the address you will use to sign up, or to sign in if you already have an Instaclustr user.
- Storage account name: a new name that you choose. Azure creates a new storage account with this name, which Instaclustr uses to store cluster backups. Do not enter the name of an existing storage account. The name must be globally unique in Azure, 3 to 24 characters long, and use only lowercase letters and numbers.
- Container registry name: a new name that you choose. Azure creates a new container registry with this name, which holds the container images your clusters use. Do not enter the name of an existing registry. The name must be globally unique in Azure, 5 to 50 characters long, and use only letters and numbers.
- Managed identity: keep the default.
-
Review and create
Next, go to the Review + create page. Review the summary of your new subscription including the Terms of use, and then press the Create button. Wait until the deployment status shows ‘Succeeded’ before continuing. A newly created Managed Application can take a few minutes to appear in the Azure portal.
Create your Instaclustr account
Run in Instaclustr’s Account (RIIA)
- If you already have an Instaclustr user, sign in to the Instaclustr Console first.
- Select Configure account now in the Azure portal. You are redirected to Instaclustr to create an account and link it to your Azure account.
- If you are creating a new Instaclustr user, sign up with SSO or enter your details. Your Instaclustr user does not need to use the same email as the Azure contact details.
- You can now create clusters in the Instaclustr Console.
Bring Your Own Cloud (BYOC)
- Wait until the deployment shows Succeeded. You will then receive an email from [email protected].
- Follow the instructions in the email to create a new Azure Marketplace account on the Instaclustr Console. If the email does not arrive, see Troubleshooting below.
- Before creating clusters, you will need to configure your Azure account to give Instaclustr’s systems the access they need to provision, monitor, configure, and manage your clusters. Sign in to the Instaclustr Console and follow the Azure Marketplace Setup BYOC guide.
- Once you have completely followed the Azure Marketplace BYOC guide, you can now create clusters in the Instaclustr Console.
Note: Creating multiple Azure apps on the same plan will allow you to have multiple environments charged under the same plan (e.g. Production and Testing).
How to cancel a subscription
Run in Instaclustr’s Account (RIIA)
Cancel the SaaS subscription in the Azure Portal. Sign in, search for ‘SaaS’, open your Instaclustr SaaS subscription, then select Cancel subscription.
When the SaaS subscription is cancelled, your Instaclustr account is unlinked from your Azure subscription, and:
- Non-production clusters in the linked account are deleted straight away.
- Production clusters are not deleted straight away. Instaclustr emails a deletion request to the cluster’s deletion verification contact, or to your account’s support contacts, and deletes the clusters once you confirm the request by replying to that email.
The SaaS subscription resource is the only thing in your Azure subscription. Your clusters run in Instaclustr’s Azure account, so there is nothing else to clean up in Azure.
Bring Your Own Cloud (BYOC)
Delete the Instaclustr Managed Application from the Azure Portal. Sign in, open Managed applications or the resource group that contains your Instaclustr Managed Application, select the Instaclustr Managed Application, then select Delete.
Deleting the Managed Application in Azure also deletes its managed resource group and everything in it, including your clusters’ virtual machines, the storage account that holds your backups, and the container registry. This cannot be undone. Deleting the Managed Application also disconnects it from its Instaclustr account. The account can still appear in the Instaclustr Console, but it can no longer create clusters. Contact Instaclustr Support to have the account disabled.
Troubleshooting
Sign-up link does not allow account creation
If a message says you cannot create an account in your Organization, confirm that your Instaclustr user is an Owner of the intended Organization and that “Prevent organization users from creating accounts outside the organization” is turned off under Account Controls. Ask an Organization Owner to grant you Owner access and turn off this setting, or contact Instaclustr Support. Then open your sign-up link again: for RIIA, select Configure account now on your SaaS subscription in the Azure portal; for BYOC, open the link in the sign-up email from Instaclustr.
Run in Instaclustr’s Account (RIIA) issues
Purchase fails with an authorization error
Ask your Azure administrator to assign the Owner or Contributor role to your own user directly on the subscription. Wait 20 minutes for the change to take effect, then try again.
You closed the page before creating your Instaclustr account
In the Azure portal, search for ‘SaaS’, open your Instaclustr SaaS subscription, and open the account configuration link from there.
Bring Your Own Cloud (BYOC) issues
Deployment fails with an authorization error
The deployment fails with an error saying your account does not have authorization to perform an action. This usually means your role is inherited from a management group or a group membership, and Azure did not apply it to the new managed resource group in time.
- Ask your Azure administrator to assign the Owner or Contributor role to your own user directly on the subscription.
- Wait 20 minutes for the change to take effect.
- Open the failed deployment and press the Redeploy button. You do not need to delete anything first, and redeploying keeps the values you already entered. Do not delete the Managed Application merely to retry the deployment. Deleting a Managed Application that shows Succeeded is interpreted as unsubscribing from the Instaclustr BYOC plan and deletes its managed resource group and associated cluster resources. Delete it only when you intend to cancel the subscription.
Deployment fails because of an Azure policy
The deployment fails while creating a resource, such as the storage account, and the error names a policy assignment.
- Ask your Azure administrator to add a policy exemption for this deployment.
- Open the failed deployment and press the Redeploy button.
Policy validation warnings on their own do not always stop a deployment. If the final status is ‘Succeeded’, the deployment worked and you can continue.
Sign-up email not received
- Check that the deployment status is ‘Succeeded’. Instaclustr only sends the email after Azure reports that the deployment is complete.
- Check your spam or junk folder, and whether your mail system quarantines external email.
- If the email has still not arrived, contact your NetApp Sales team or Instaclustr Support with the following details:
- Managed Application name and resource group: to look them up, search for ‘Managed applications’ in the Azure portal and open your application.
- Azure subscription ID: shown on the Overview page of the Managed Application.
- Email address entered in the Application Settings: to look it up, open the resource group, select ‘Deployments’, open the Instaclustr deployment, and select ‘Inputs’.
While waiting for the email, do not delete the Managed Application and deploy again. A new deployment creates a new Managed Application with its own sign-up link, and the original link cannot be used once its Managed Application is deleted.
Managed Application was deleted
Deleting the Managed Application disconnects it from its Instaclustr account (see How to cancel a subscription). Contact Instaclustr Support to have the account disabled, then deploy the plan again and wait for ‘Succeeded’ before using the new sign-up link.
Need help?
Email [email protected] or raise a support ticket. You can also contact your NetApp Sales team if you require assistance at any time.