Security & Backup

Druva

Manage your Druva MSP customers and tenants from Dex - read status, run backup and consumption reports, and provision or suspend tenants with approval.

Dex connects to the Druva MSP API so admins can run their Druva customer accounts conversationally - read a customer and its tenants, pull backup activity, last-backup status, alert, licence usage, and consumption reports, and provision, update, suspend, or unsuspend tenants with approval. This is an MSP global app: one shared MSC OAuth client covers every customer under the MSP, and each Dex tenant is confined to its own Druva customer via its customer_id. Service-plan and storage-region catalogs are read-only and shared MSP-wide. Admin-only - Druva is not available in Dex Go, so there are no employee self-service workflows.

Start free →

What Dex does with Druva

Dex handles both admin workflows and employee self-service — all policy-guardrailed and audit-logged.

For admins (Dex Pro)

Read a Druva customer record and its tenants, plus customer-level events
Pull backup activity, last-backup status, alert, licence usage, and itemized consumption reports
Update the customer record (full-replace PUT) with approval
Create and update tenants - set licence expiry, quota, service plan, and storage regions - with approval
Suspend and unsuspend tenants with approval (suspend is disabled by default)
Browse the MSP-wide service-plan and storage-region catalogs, read-only
Confirm async writes through the task API, then report the result
Deploy as an MSP global app - one shared MSC OAuth client, each Dex tenant confined to its own Druva customer_id

Just ask Dex

Your team types a request in plain language. Dex investigates, plans, and executes — with the right guardrails.

Admin prompts

>Show me this customer's Druva tenants and their current status
>Which Enterprise Workloads backup jobs failed in the last day?
>Pull the last-backup status for all Endpoints devices - flag anything that missed files
>What's our licence usage and consumption looking like for this customer?
>Create a new SaaS Apps and Endpoints tenant with a licence expiry of 2026-12-31
>Suspend the tenant we provisioned for the decommissioned site

Policy actions

Every action Dex can take on Druva is declared, scoped, and guardrailed. Admins control which apply, who approves them, and whether they're limited to self-service.

Action	What it does	Guardrails
`druva_list_customers`	List Druva MSP customers (MSP master connection only)	—
`druva_get_customer`	Get one Druva customer by customer_id (path-forced)	—
`druva_list_customer_events`	List customer-level Druva events (path-forced)	—
`druva_create_customer`	Create a Druva customer (MSP master only) - billing impacting	approval
`druva_update_customer`	Update this Druva customer record (full-replace PUT)	approval
`druva_list_tenants`	List this customer's Druva tenants (customerIds forced on a child)	—
`druva_get_tenant`	Get one Druva tenant of this customer (ownership-checked)	—
`druva_create_tenant`	Create a tenant under this customer - licence/billing impacting	approval
`druva_update_tenant`	Update a tenant's quota/licence under this customer (ownership-checked)	approval
`druva_suspend_tenant`	Suspend a tenant under this customer - stops service, disabled by default	approval
`druva_unsuspend_tenant`	Unsuspend a tenant under this customer - restores service	approval
`druva_get_task`	Get the status of an async Druva write by task id	—
`druva_list_service_plans`	List MSP service plans (MSP-wide catalog, read-only)	—
`druva_get_service_plan`	Get one MSP service plan (MSP-wide catalog, read-only)	—
`druva_list_storage_regions`	List MSP storage regions (MSP-wide catalog, read-only)	—
`druva_list_admins`	List MSP administrators (MSP master connection only)	—
`druva_list_msp_events`	List MSP-level Druva events (MSP master connection only)	—
`druva_report_backup_activity`	Druva backup activity report (customer filter forced on a child)	—
`druva_report_last_backup_status`	Druva last backup status report (customer filter forced on a child)	—
`druva_report_alerts`	Druva alert report (customer filter forced on a child)	—
`druva_report_license_usage`	Druva licence usage report (customer filter forced on a child)	—
`druva_report_consumption`	Druva itemized consumption report (customer filter forced on a child)	—
`druva_report_global_usage`	Druva global usage report across all customers (MSP master connection only)	—

How to configure Druva

Onboarding takes minutes. Dex validates your credentials before saving them.

Setup steps

1
In the Druva MSC Portal, open Manage API Credentials and generate API credentials for Dex.
2
Copy the Client ID and the Secret Key (the Secret Key is shown once - store it securely).
3
For the MSP-master connection, leave customer_id blank so Dex can list customers and map each tenant.
4
For each tenant connection, set customer_id to that customer's Druva Customer ID from GET /msp/v3/customers or the MSC UI.
5
In Dex, enable the Druva integration and paste the Client ID and Secret Key; Dex validates them with a live read before saving.

Credentials required

client_id: MSC API Client ID generated in the Druva MSC Portal (Manage API Credentials)
client_secret: MSC API Secret Key from the same registration (shown once - rotate via Druva if breached)
customer_id: This tenant's Druva Customer ID (e.g. bde7f8c2-d063-4a4a-9a8f-c2ea5aff42f3-198); leave blank on the MSP-master connection

Requirements

•A Druva MSP account with MSC API credentials (client_credentials)
•Each Dex tenant mapped to one Druva customer_id; blank customer_id is the MSP-master connection
•Admin-only - Druva is not available in Dex Go, so there are no employee self-service workflows
•For MSPs, the integration deploys as a global app with per-customer scoping by customer_id