Separate Zilliz Cloud Billing on Azure Marketplace

If you need to separate Zilliz Cloud billing on Azure Marketplace by business unit, team, use case, application, or cost center, the recommended pattern is to use one Azure subcription, one Azure Marketplace subscription and one Zilliz Cloud organization per business unit.

Azure provides the billing view. Zilliz Cloud provides the usage view. For Azure-side billing separation, use one organization per business unit.

Overview

To separate Zilliz Cloud billing on Azure Marketplace, you should map each billing unit to one Azure subscription, one Azure Marketplace subscription for Zilliz Cloud, and one Zilliz Cloud organization.

With this setup:

• Azure Cost Management shows Marketplace charges under the selected Azure subscription.

• Each Azure Marketplace subscription maps to one Zilliz Cloud organization.

• Zilliz Cloud provides project-level and cluster-level usage drill-down inside that organization.

The following is an example of separating the billing for 3 different teams.

  Azure billing account
  +-- Azure subscription: team-a
  |   +-- Azure Marketplace SaaS subscription: Zilliz Cloud - team-a
  |       +-- Zilliz organization: org-team-a
  |           +-- Project: project-team-a
  |               +-- Cluster(s)
  +-- Azure subscription: team-b
  |   +-- Azure Marketplace SaaS subscription: Zilliz Cloud - team-b
  |       +-- Zilliz organization: org-team-b
  |           +-- Project: project-team-b
  |               +-- Cluster(s)
  +-- Azure subscription: team-c
      +-- Azure Marketplace SaaS subscription: Zilliz Cloud - team-c
          +-- Zilliz organization: org-team-c
              +-- Project: project-team-c
                  +-- Cluster(s)

📘Note

If you only need internal usage separation, a simpler alternative is to use one organization with multiple projects. In that model, Azure Marketplace charges remain combined under one subscription, and the usage split is visible only through Zilliz Cloud usage analysis.

Comparison

Model	Separates Azure Marketplace charges	Separates Zilliz usage by project or team	Best for
One organization per business unit	Yes	Yes	Teams or cost centers that need separate Azure billing
One organization with multiple projects	No	Yes	Internal usage split only

Multi-organization setup

Use this model when each business unit needs separate Azure Marketplace billing.

Prepare multiple organizations

A new Zilliz Cloud account registration automatically creates one default organization.

To prepare multiple organizations:

1

Register separate Zilliz Cloud accounts with separate company email accounts, or contact Zilliz Cloud support team to prepare additional organizations.

2

Confirm that each business unit has its own Zilliz Cloud organization.

3

Invite the required users into each organization.

4

Assign the billing operator as Organization Owner or Organization Billing Admin in each target organization.

Each organization has its own:

• billing and payment method

• users and RBAC

• projects

• clusters

• usage analysis data

Bind one Marketplace subscription to each organization

For each business unit:

1

On Zilliz Cloud, navigate to the corresponding Zilliz Cloud organization for your target billing unit.

2

On the Zilliz Cloud Billing page, click + Add Payment Method, and then select Marketplace. Click Subscribe Now.

3

You will be redirected to Azure Marketplace. Complete your purchase there.

For details, see Subscribe on Azure Marketplace.

4

After you click Configure account now, select the matching Zilliz Cloud organization.

5

Confirm the organization ID if needed.

6

Complete authorization.

📘Note

• Each Marketplace subscription can be linked to only one Zilliz Cloud organization.

• To bind a Marketplace subscription to a Zilliz Cloud organization, you must be an Organization Owner or Organization Billing Admin in that organization.

Receive Azure invoices and view charges separately

• Invoices are issued through Azure, not through Zilliz Cloud.

• Azure Cost Management shows Marketplace charges under each Azure subscription.

• The Zilliz Cloud spend of each business unit appears under its own Azure Marketplace subscription.

• Azure-side cost allocation can follow the Azure subscription, resource group, and tag model.

• Invoice presentation still depends on your Azure billing account configuration.

Check usage separately in each organization

Inside each Zilliz Cloud organization, use Zilliz Cloud usage analysis to drill down by:

• Project

• Cluster

• Time range

• Cost type

• Region

This provides the detailed usage view that Azure billing does not show.

📘Note

• Use Azure Cost Management for billed Marketplace charges and invoices.

• Use Zilliz Cloud Usage page for project-level and cluster-level usage inside each organization.

Reconcile Azure billing and Zilliz Cloud usage

Use the following components to reconcile the Azure billing view and the Zilliz Cloud usage view:

• Azure subscription

• Azure Marketplace subscription

• Zilliz Cloud organization name and organization ID

• Zilliz Cloud project name and project ID

• Zilliz Cloud cluster name and cluster ID

Considerations

• If Azure-side Marketplace spend must be separated by team, use one Azure Marketplace subscription and one Zilliz Cloud organization per business unit.

• If you only need internal usage separation, one organization with multiple projects is simpler, but it does not separate Azure Marketplace charges.

• Separate Azure invoice PDFs depend on the Azure billing account type and are not guaranteed by Zilliz Cloud architecture alone.

• Commercial terms such as committed spend, private offers, or shared commitments across multiple Marketplace subscriptions should be confirmed with Microsoft Azure Sales or Marketplace Operations.