Current + Acronis Cyber Protect Cloud integration

Acronis Cyber Protect Cloud is a backup and cyber protection platform an MSP runs for every partner from one Management Portal. Current's Acronis integration reads that estate onto the company record, the strategic business review module, the roadmap and the company alert band. It is a reporting feed with two exceptions, both on a service desk ticket and both pressed by a person: Run backup now for one computer, and Dismiss for one alert.

What the integration does

Current connects with an API client created at your own top-level tenant in the Acronis Management Portal (Acronis calls it the partner tenant): a data center URL, a client ID and a secret. One client reaches every customer beneath your top-level tenant, so there is nothing to paste per partner. Every six hours Current reads your customer list, the protection status of every workload, the agents, the alerts and any EDR incidents, and once a day it reads usage. Instead of logging in to the portal the week of the review, the backup numbers are already on the company record when you open it.

What data flows

• Customers: every customer tenant under your top-level tenant, matched to your Current companies by name, with anything ambiguous left for a person to decide.
• Protection status: per computer or workload, the status and plan names Acronis reports, when a backup last ran and last succeeded, and its agent's version and online state.
• Alerts: the open Acronis alerts and those dismissed in the last 30 days, with their type, severity, computer and plan.
• EDR incidents: where a partner runs Acronis EDR, each incident's severity, state and host.
• Usage: every usage Acronis reports for the month, from workstations and servers to Microsoft 365 seats and storage in GiB, shown with Acronis's own note that it is a running count and not an invoice figure.

One definition of a failing backup

A computer counts as failing when Acronis rates it error, critical or needing interaction, or when its last successful backup is more than 48 hours old. A computer with no protection plan is a separate count, because nothing is scheduled to fail, and it is often the more urgent of the two. A status Current does not recognise counts as unknown rather than as a pass. The company card, the ticket, the backups-failing alert and the dashboards all use that one definition, so they never disagree, and Acronis counts alongside every other backup product you run, so a company raises one alert whichever tool saw the problem.

Two actions, where the work is

A ticket about a partner shows the computers that need attention and the open Acronis alerts for that partner. A technician can press Run backup now on a computer, which asks Acronis to run that computer's own protection plan for that computer only, or Dismiss on an alert, which dismisses that one alert. Each asks for confirmation, adds a line to the ticket's record and is written to the audit log. Those are the only two things Current can ask Acronis to do. Several Acronis addresses dismiss every alert or change usage when called the wrong way, so every request goes through a fixed list matched by method as well as address, and creating customers, editing plans, deleting workloads and changing an EDR incident are not in it.

Where the data appears

• In strategic business reviews, in the backup chapter beside other backup feeds such as Slide.
• On the company record, where the Acronis card shows the computers that need attention and why, the ones with no plan, agents offline, open alerts, EDR incidents and usage.
• In the company alert band, as backups failing and as an open high or critical EDR incident.
• On roadmaps, where failing computers and computers with no plan arrive as suggestions.
• On dashboards, in the backups-failing and open critical security figures.

Why it matters

An MSP running Acronis for a partner like Northwind Traders can open the account and see forty-two computers: thirty-eight backing up, two whose last good backup is four days old, and two that were never given a protection plan after a hardware refresh. The two failing machines are a ticket. The two with no plan are a conversation, because nobody knew they were unprotected, and the review that shows them is the one where the partner asks what else nobody knew.