Connect Acronis Cyber Protect Cloud to Conduit
This walkthrough connects Acronis Cyber Protect Cloud (backup, disaster recovery and endpoint protection) to Conduit. Acronis authenticates with an API client (Client ID + Client Secret) that is exchanged for a short-lived token against your data center URL.
Before you start
Section titled “Before you start”You need:
- A Conduit role that can manage connections — owner or admin on your organization.
- An Acronis management portal login that can create API clients.
- Your data center URL, which Acronis shows when you create the API client
in Step 1, for example
https://us5-cloud.acronis.com. It must behttps://onacronis.com. Don’t use a custom-branded portal sign-in address.
Step 1 — Create an API client in Acronis
Section titled “Step 1 — Create an API client in Acronis”- Sign in to the Acronis management portal.
- Go to Settings → API clients and create a new API client. Expected: a Client ID, a Client Secret and a Data center URL.
- Copy all three values. The secret is shown only once.
Step 2 — Connect Acronis in Conduit
Section titled “Step 2 — Connect Acronis in Conduit”- In Conduit, go to Connections (
/org/catalog). - Find Acronis Cyber Protect Cloud (under BCDR) and click Connect.
- Fill the fields:
- Data center URL (required) — from Step 1, e.g.
https://us5-cloud.acronis.com. - Client ID (required) — from Step 1.
- Client Secret (required) — from Step 1.
- Data center URL (required) — from Step 1, e.g.
- Click Connect. Expected: Conduit performs a real token exchange with your data center and shows a green Connected status. A bad client, or the right client on the wrong data center, is rejected here.
The credential is stored at the organization scope, so every technician in your org shares this connection.
What the tools can do
Section titled “What the tools can do”Reads (technician tier) cover tenants and users, alerts, protection policies, resources and protection status, agents, and EDR incidents. Three tools make changes: marking an alert as a false positive, changing an investigation state, and running a protection policy. All three are off by default. When they’re turned on, only admins can run protection policies.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Likely cause |
|---|---|
| “Data center URL must be an https:// address on acronis.com” | The URL is http://, or not an *.acronis.com host. Use the data center URL shown when you created the API client. |
| “Acronis rejected the API client credentials (HTTP 401)” | Wrong or deleted Client ID/Secret, or the data center URL doesn’t match the region the client was created in. Check Settings → API clients. |
| “Acronis returned an unexpected error (HTTP NNN)” | Unexpected response from Acronis, often transient. Retry after a few minutes. |
| Need to rotate the secret | Create a new API client, then update the credential at /org/catalog. |
Related
Section titled “Related”- Vendor connections — credential scopes, rotation, and the full vendor catalog.
- Security — how Conduit encrypts the credential you just stored.

