Druva inSync & Phoenix
Run Druva inSync endpoint backup and Phoenix server backup conversationally - users, devices, backup status, restores, and legal holds for one customer.
Dex connects to Druva inSync (endpoint and SaaS backup) and Phoenix (Enterprise Workloads server backup) for a single customer through the MSP per-customer token. Admins can manage inSync users and devices, check last successful backups, run restores, work legal holds, and read reports - plus answer "did backups succeed and what failed" across Phoenix workloads, start on-demand backups, cancel jobs, and restore files or VMs. This is an MSP global app with no master mode: one shared MSC API credential, and each Dex tenant is confined by a required per-customer Druva Customer ID, so you only ever see that customer's users, devices, and backup organizations. Admin-only - every write shows an inline approval card naming the consequence before it runs.
What Dex does with Druva inSync & Phoenix
Dex handles both admin workflows and employee self-service — all policy-guardrailed and audit-logged.
For admins (Dex Pro)
- Find inSync users by email, review their devices, and check last successful backups
- Create, update, preserve, activate, reset passwords for, and delete inSync users - with an approval card
- Disable, enable, decommission, upgrade the client on, or delete inSync devices - with an approval card
- Start inSync restores to a device, and review restore history and status
- Manage legal holds and custodians, and look up the holds covering a user
- Read inSync profiles, storage, CloudCache, events, and Druva reports
- Answer "did backups succeed and what failed" across Phoenix workloads from backup-failure alerts and job reports
- Start on-demand Phoenix backups, cancel running jobs, and restore files to the original server or a VM to its original location - with an approval card
- Deploy as an MSP global app - one MSC API credential, each tenant confined to its 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
- >Find the inSync user a.user@contoso.com and show their devices and last successful backup
- >The laptop for j.smith@example.com was stolen - decommission the device
- >Preserve the inSync user who left, d.levi@acme.com, and tell me what that stops
- >Did Phoenix backups succeed last night? List any failures by server and error message
- >Start an on-demand backup for the file server backup set, then read the job status back
- >Which legal holds cover a.user@contoso.com right now?
Policy actions
Every action Dex can take on Druva inSync & Phoenix is declared, scoped, and guardrailed. Admins control which apply, who approves them, and whether they're limited to self-service.
| Action | What it does |
|---|---|
druva_insync_read_users | List and get inSync users |
druva_insync_create_user | Create an inSync user (consumes a licence) |
druva_insync_update_user | Change an inSync user's name, profile, or storage |
druva_insync_delete_user | Delete an inSync user, all their backups and devices |
druva_insync_preserve_user | Preserve an inSync user (stops their backups) |
druva_insync_activate_user | Re-activate a preserved inSync user (consumes a licence) |
druva_insync_reset_user_password | Email an inSync user a reset link |
druva_insync_read_devices | List and get inSync devices |
druva_insync_disable_device | Disable an inSync device (stops its backups) |
druva_insync_enable_device | Re-enable an inSync device |
druva_insync_decommission_device | Remotely wipe inSync-protected data on a device |
druva_insync_upgrade_client | Upgrade the inSync client on a device |
druva_insync_delete_device | Delete a device and all its backup data |
druva_insync_read_backups | Read last successful inSync backups |
druva_insync_read_restores | List and get inSync restores |
druva_insync_restore | Start an inSync restore to a device |
druva_insync_read_legal_holds | List and get legal holds and custodians |
druva_insync_find_user_legal_holds | List legal holds for given users (read via POST) |
druva_insync_create_legal_hold | Create a legal hold |
druva_insync_update_legal_hold | Edit a legal hold |
druva_insync_delete_legal_hold | Delete a legal hold |
druva_insync_manage_legal_hold_custodians | Add or remove legal hold custodians |
druva_insync_read_profiles | List and get inSync profiles |
druva_insync_read_storage | List and get inSync storages and CloudCache |
druva_insync_read_events | Read inSync events |
druva_list_reports | List Druva reports |
druva_get_report | Read a Druva report |
druva_phoenix_list_orgs | List Phoenix organizations |
druva_phoenix_read_alerts | Read Phoenix alerts including backup failures |
druva_phoenix_read_reports | Read Phoenix job, backup-set, server, and usage reports |
druva_phoenix_read_snapshots | List Phoenix snapshots |
druva_phoenix_backup_now | Start an on-demand Phoenix backup |
druva_phoenix_cancel_job | Cancel a Phoenix job |
druva_phoenix_restore | Phoenix restore to the original server or VM |
How to configure Druva inSync & Phoenix
Onboarding takes minutes. Dex validates your credentials before saving them.
Setup steps
- 1In Druva MSC, open Manage API Credentials and create (or reuse) an MSC API credential; copy its Client ID and Secret Key.
- 2Get the target customer's Druva Customer ID from the Druva MSP app (GET /msp/v3/customers on the master) or the MSC UI - it looks like a UUID plus a numeric suffix.
- 3In Dex, enable the Druva inSync & Phoenix integration and paste the Client ID, Secret Key, and Customer ID.
- 4Dex mints an MSP token, then a customer-scoped token for exactly that Customer ID, and validates it with a live product read before saving.
- 5For MSPs, deploy as a global app: one shared MSC credential, with each tenant mapped to its own Customer ID.
Credentials required
- client_id
- MSC API Client ID (Druva MSC > Manage API Credentials)
- client_secret
- MSC API Secret Key for the same credential (shown once; rotate in MSC if lost)
- customer_id
- Required Druva Customer ID (UUID plus numeric suffix) - confines every call to that one customer; this app has no MSP-master mode
Requirements
- •A Druva MSC API credential (Client ID and Secret Key), the same one used by the Druva MSP app
- •A per-customer Druva Customer ID - required; a blank id fails closed with no MSP-master fallback
- •The customer token must carry Cloud Administrator rights (inSync endpoint APIs and Phoenix reports need them)
- •Admin-only app - every write is gated by an inline approval card; Hyper-V, SQL, and NAS Phoenix workloads are read-only here
- •Customer and tenant management lives in the separate Druva MSP app
Related integrations
Security & BackupAcronis Cyber Protect
Manage Acronis tenants, devices, backups, and protection plans from chat.
Learn more →
Security & BackupMSP360 Managed Backup
Run your MSP360 Managed Backup fleet conversationally - companies, backup users, endpoints, plans, licenses, and nightly backup status.
Learn more →
Security & BackupKeepit
Monitor your Keepit SaaS backups from Dex - connector health, backup summaries, latest history, and job information across accounts.
Learn more →
See Dex run Druva inSync & Phoenix
Book a 30-minute walkthrough with our team and see how autonomous IT works in your environment — or get started for free.