Druva User Provisioning - Version 1.2

Overview

The Druva User Provisioning - Version 1.2 collector retrieves user provisioning and backup storage data from Druva’s managed service provider (MSP) platform, covering Microsoft 365, Endpoints, and Google Workspace backup products.

This collector provides visibility into which users are provisioned for backup across each Druva product, along with the storage consumed by each user. For every provisioned user, the collector submits two records: one representing the backup license (quantity of 1) and one representing the backup storage consumed (quantity in gigabytes).

The collector retrieves unrated allocation data, meaning no monetary values are supplied by the source system. Pricing and billing calculations are applied within Varibill based on configured contracts and pricing rules.

This is a point-in-time collector, meaning each execution retrieves the current state of user provisioning at the time of collection. A configurable report start date filters the results to include only users whose provisioning data has been updated on or after that date.

For general instructions on creating and running Source Collectors, see: Configuring a New Cloud Source Collector

Collector Summary

About Druva

Druva is a cloud data protection and management company that provides backup, disaster recovery, and data governance solutions delivered as a software-as-a-service (SaaS) platform. Druva’s platform protects data across endpoints, cloud applications, and data centre workloads without the need for on-premises hardware or software.

Druva’s MSP (Managed Service Provider) platform enables service providers to manage backup and data protection services for multiple customer organizations from a single console. The MSP platform provides centralized administration, reporting, and billing across all managed customers and their protected workloads.

The Druva MSP Reporting API provides programmatic access to provisioning and usage data across the managed customer base, covering Microsoft 365, Endpoints (device backup), and Google Workspace products.

Data Collected

The Druva User Provisioning - Version 1.2 collector retrieves unrated user provisioning data from the Druva MSP platform. The collector queries three Druva MSP reporting endpoints and produces two records per provisioned user from each product:

Microsoft 365 Backup

For each user with an active Microsoft 365 backup license: - A license record with a quantity of 1, representing the backup license assignment - A storage record with a quantity representing the total backup data consumed in gigabytes

Endpoints Backup

For each user with an active Endpoints backup license: - A license record with a quantity of 1, representing the backup license assignment - A storage record with a quantity representing the endpoint backup storage consumed in gigabytes

Google Workspace Backup

For each user with an active Google Workspace backup license: - A license record with a quantity of 1, representing the backup license assignment - A storage record with a quantity representing the total backup data consumed in gigabytes

Each record includes the customer name and user name from the Druva MSP platform. Users whose license state is not assigned (indicated by a dash value in Druva) are excluded from the collection.

The identifiers submitted to Varibill for each record are constructed as follows:

• Product Identifier — constructed as {Product Identifier Code}{Product}#{Type}#{License State}, where Product is one of M365, Endpoints, or GoogleWorkspace, Type is either License or Storage, and License State is the user’s license state from Druva (for example, Active Licensed Users or Licensed). Examples: Druva#M365#License#Active Licensed Users, Druva#Endpoints#Storage#Licensed, Druva#GoogleWorkspace#License#Active Licensed Users
• Client Identifier — the Druva customer global ID, a GUID identifying the customer organization within the Druva MSP platform
• Record Identifier — describes the individual record (for example, Microsoft 365 Backup License for user@example.com or Endpoints Backup Storage for user@example.com)
• Unique Identifier — constructed as {customer global ID}#{CRC of user email}#{product type}, where product type is one of M365License, M365Storage, EndpointsLicense, EndpointsStorage, GoogleWorkspaceLicense, or GoogleWorkspaceStorage

Prerequisites

Before configuring this collector, ensure that:

• You have access to the Druva MSP Console as an administrator
• You have created API credentials (Client ID and Secret Key) for the Druva MSP API
• You have noted the Druva API host URL (typically https://apis.druva.com)
• You have access to the Varibill Source Collector configuration screen

Configuration Parameters

The parameters below are entered when configuring the collector in Varibill. They are grouped by function.

Connection Parameters

These parameters identify and authenticate against the Druva MSP API using OAuth 2.0 client credentials.

Product and Reporting Parameters

Operational Parameters

These parameters control file management behavior.

Configuration Steps

Step 1: Prepare Your Druva MSP Environment

1. Sign in to the Druva MSP Console.
2. Navigate to the API Credentials section and create a new set of API credentials.
3. Note the Client ID and Secret Key — the secret is displayed only once when created.
4. Confirm the Druva API host URL (typically https://apis.druva.com).

For detailed instructions on creating API credentials, see the Druva MSP API Getting Started Guide.

Step 2: Configure the Collector in Varibill

1. In the Varibill User Interface, open the Source Collector configuration screen.

2. Enter the required field values under the Details tab:

   • Hosting Provider: Select Varibill Cloud
   • Source Collector Name: Select Druva User Provisioning - Version 1.2

3. Enter the connection parameters:

   • Druva Host: The Druva API host URL (typically https://apis.druva.com)
   • Druva Username: The Client ID from the Druva MSP Console
   • Druva Secret: The Secret Key from the Druva MSP Console

4. Configure the product and reporting parameters:

   • Product Identifier Code: The prefix for all Product Identifiers (for example, Druva#)
   • Druva Report Start Date: The cutoff date for including provisioning data (format: YYYY-MM-DD)

5. Save the collector configuration.

Step 3: Run the Collector

Run or schedule the collector according to your standard Source Collector execution process.

For detailed instructions, see: Configuring a New Cloud Source Collector

Troubleshooting

If the collector fails to connect to Druva, verify that:

• The Druva Host URL is correct (typically https://apis.druva.com).
• The Druva Username (Client ID) is correct and the API credentials are active.
• The Druva Secret (Secret Key) is valid and has not been revoked.
• The API credentials have sufficient permissions to access MSP reporting data.

If the collector connects successfully but returns no data, verify that:

• The Druva Report Start Date is set to a date on or before the last update of the provisioning data you expect to collect.
• There are users with active backup licenses (Microsoft 365, Endpoints, or Google Workspace) in the Druva MSP platform.
• The managed customer accounts in Druva have users provisioned for at least one backup product.

Druva References

The following resources may assist with locating values or configuring your Druva MSP API credentials.

Druva Documentation (External)

• Druva Website
• Druva MSP API Getting Started Guide