Billing for Customers Using a Cloud Solution Provider (CSP)

Billing for Customers Using a Cloud Solution Provider (CSP)

If you are an end customer purchasing a SaaS subscription through a Cloud Solution Provider (CSP), there are some nuances related to the Azure Marketplace specific to your scenario.

Billing Process Overview

When you purchase Azure resources, including the Cybersecurity Office SaaS subscription, through a CSP, the billing process differs from purchasing directly via the Microsoft Azure Marketplace.
These differences include:
  1. Resource Charges: All charges for Azure resources, including your SaaS subscription, are initially billed to your CSP.
  2. CSP Invoicing: The CSP will then invoice you, the end customer, for the services.
  3. Support: See the Roles & Responsibilities section below.

Purchasing the Cybersecurity Office SaaS Subscription

If we have provided you with a private offer, refer to the steps in the associated article. Otherwise the purchasing process follows the typical Azure Marketplace flow.
Within the context of those two approaches, there are two potential different ways to complete the purchase:
  1. The customer has Owner, Contributor or Billing Administrator permissions on the associated Azure subscription managed by the CSP. In this case, the customer may complete the purchase directly. Billing will be via the CSP rather than to the customer directly.
  2. The CSP will initiate the purchase on behalf of the customer and, again, billing will be via the CSP rather than to the customer directly.

Roles & Responsibilities

If the CSP is a reseller of the Cybersecurity Office service, they may also be providing support services to the customer directly. The CSP will notify the customer if this is the case
However, if the customer has initiated the Cybersecurity Office purchase directly and happens to be leveraging a CSP for their Azure tenant, the responsibilities of the CSP ends once the purchase has been made.

    • Related Articles

    • Using Custom Attributes on Information Assets

      Overview Custom Attributes let you store additional structured metadata on each Information Asset using the Custom Attributes section in the Information Asset dialog. Use this when the standard fields (for example Name or Summary) are not enough, and ...

    • Role Based Access Control Management

      Manage roles via Entra ID Application Roles Cybersecurity Office utilises Role Based Access Control to grant and constrain which of your Azure Entra ID users are able to access which parts of the application and uses your organisation’s Microsoft ...

    • Protective Data Security Plan (PDSP) 2024

      The Protective Data Security Plan (PDSP) Every 2 years, each Victorian Public Agency (VPA) is required to produce a Protective Data Security Plan (PDSP). OVIC provides guidance and templates for how to achieve this. It is typically produced via one ...

    • Define Platform Teams: Option 1: Asset Hierarchy Holistic Entry - Manual Entry

      This is one of the primary approaches to for utilising the Asset Hierarchy Holistic Entry. Asset Hierarchy Holistic Entry Manual Platform Team Entry Similar to Option2, the asset hierarchy panel has an Add button near the bottom right, above the main ...

    • Define Platform Teams: Option 1: Asset Hierarchy Holistic Entry - Assistant Recommended Asset Hierarchy

      This is one of the primary approaches to for utilising the Asset Hierarchy Holistic Entry. Asset Hierarchy Holistic Entry Assistant Recommended Asset Hierarchy The asset hierarchy panel has a sub-menu accessible via the triangle to on the right of ...