Devices are not enrolled into Backups manually — they appear automatically once you connect a backup vendor and the first sync runs. The vendor connection is the enrollment step. This article covers connecting a vendor so its devices and jobs start flowing into Backups.
⚠️ This whole vendor path is built but not yet collecting — no tenant has a vendor configured and end-to-end collection has not been proven — so a vendor connection shows no devices today. Do not plan a migration around it yet. The platform's own capture paths (the endpoint agent, and SaaS connections) do not depend on a vendor connection and enroll their own devices.
Vendor credentials are stored in Azure Key Vault and never written to the database in plaintext.
Connecting a Backup Vendor
- Open Backups and go to Vendors.
- Click New Vendor.
- Select the vendor type from the list (Veeam, Datto, Acronis, Cove, Backup Exec, or others).
- Enter a friendly display name for the connection.
- Paste the API credentials when prompted. The UI saves them to Azure Key Vault and stores only a reference name in the database.
- Set the sync frequency. The default is every 60 minutes. Reduce this if you need more frequent job updates.
- Save. The first sync runs immediately.
Mapping Vendor Companies to Clients
If your vendor organizes devices under company accounts, you need to map those companies to the clients you have set up in Backups. Without this mapping, jobs land as unmapped.
- Open the vendor record after the first sync.
- Find the Company Mappings section.
- For each vendor company ID, select the matching Backups client from the dropdown.
- Save. Jobs from those companies now appear under the correct client in the dashboard.
Verifying the First Sync
⚠️ Because the vendor path is not yet collecting, this step will show nothing today — it describes the intended behaviour once collection is proven.
- Go to Jobs.
- Filter by the date range of the most recent backup window.
- Confirm that devices from the new vendor appear with their correct status (success, failed, missed, or running).
- If nothing appears, open the vendor record and check Last Sync Error for a diagnostic message.
Adding a Client for the New Devices
If the devices belong to a client that does not yet exist in Backups:
- Go to Clients and click New Client.
- Enter the client name, domain, primary contact name, and PSA company ID.
- Save, then return to the vendor and complete the company mapping.
After the First Sync
Once jobs are flowing in, review the Dashboard for the seven-day coverage rollup. Any devices that show as Missed were flagged by the missed-backup detector during the initial import. Open the device's job history to see when it last succeeded.
FAQ
Do I install an agent on each device? Not for a third-party vendor connection. Backups connects to the vendor API directly and the vendor's own software handles the backup; Backups reads the results through the vendor API. The platform's own endpoint backup is different — it runs a per-device agent (a module of the One Agent) that performs the file and folder capture, and that agent is what enrolls the device.
A device appears under the wrong client after sync. Update the company mapping on the vendor record. Once the mapping is corrected, re-run the sync manually from the vendor page (click Sync Now) and the device will move to the correct client.
The vendor says "pending" and never moves to "connected." Pending means the initial sync has not returned successfully. Check Last Sync Error on the vendor record — the most common causes are an expired API key, insufficient permissions on the vendor account, or a vendor API outage.