Current + Veeam Service Provider Console integration

Veeam Service Provider Console is the one Veeam surface that knows what a partner is. Backup & Replication manages a single backup server; Veeam Backup for Microsoft 365 manages a single Microsoft 365 server. The console sits in front of both and stamps every job, workload and alarm with the partner it belongs to. Current's Veeam integration is a view-only feed from that console into the SBR/QBR module and the company alert band. It reads what Veeam already knows and never writes back.

What the integration does

Current authenticates to your console with a single API key — one that Veeam can issue as read-only — walks your companies and their estate every six hours, and stages the result as evidence for AI-assisted Strategic Business Reviews. Instead of exporting a backup report the week of the review, the recoverability numbers are already on the company record when you open it.

What data flows

• Companies — the partner roster from your console, matched to your Current companies so every signal below lands on the right record, with each partner's subscription status alongside.
• Protected workloads — servers, workstations and virtual machines, with the age of the newest and oldest restore points, how many restore points exist, and their size.
• Immutability — which virtual machines hold at least one restore point an attacker cannot delete.
• Malware state — what Veeam's scanning concluded about each workload, stored as Veeam reported it.
• Backup jobs — backup-server jobs, agent jobs and Microsoft 365 jobs, each with its own status, last run, duration and failure text.
• Microsoft 365 objects — the mailboxes, groups, teams and sites under protection, and how recent their restore points are.
• Alarms — what the console has raised, counted by what is actually lit rather than by how many rows it returns.

The feed is one-way. Current does not start or stop jobs, edit a job or a policy, restart an agent, install software, reboot a machine, acknowledge or resolve an alarm, change a partner's status, or issue an invoice. Those addresses are not in the connector's code, so a bug cannot reach them either. Veeam stays the source of truth; Current uses the evidence.

Recoverable, not just backed up

A backup report that says every job succeeded answers a smaller question than the one a partner is actually asking. Current reads the estate behind the jobs: how far back each workload can be restored to, how many of a company's virtual machines hold an immutable restore point, and which machines Veeam is watching that it has never actually copied. That last one is the finding nobody exports on purpose — a server the console tracks with no restore point at all is a server that would not come back, and it appears on the company record without anyone going looking.

Unknown reads as unknown

A workload Veeam has no malware verdict for shows as unknown in Current, not as clean. A company with nothing mirrored yet shows as not reporting, not as zero problems. A run that was cut short publishes no count at all rather than a low one. That distinction matters in a review: a backup number built by treating silence as a pass is a number you cannot defend when a partner asks which machines it covers. Immutability follows the same rule — Veeam reports it for virtual machines, so a company running agent-backed computers shows no immutability figure rather than a zero that would describe the connector instead of the partner.

Alarms that clear themselves

Current mirrors the alarm set the console reports at each sync, so an alarm that clears in Veeam leaves Current on the next run instead of accumulating as history. Two details make that count trustworthy. The console's active-alarm list also returns alarms that have already been resolved or acknowledged, so Current counts what is genuinely lit rather than counting rows. And a large share of console alarms are about the console itself — licensing notices scoped to the provider rather than to any partner — so those are dropped before they can appear on a partner's card.

Matching companies

Each company in your console is one end-customer. Current links them to your companies by normalized name — punctuation and Inc/LLC/Ltd-style suffixes stripped — and only when exactly one company matches. Where two could both be the answer, the company waits on an unmapped list for a person to decide rather than being paired on a guess. A mapping set by hand is never overwritten by a later automatic match. Companies your console has deleted are left off that list so it stays short; expired and disabled ones are kept, because a lapsed subscription is a renewal conversation rather than a missing partner.

Where the data appears

• On the company record, on a Veeam card showing protected workloads by kind, jobs failing now, immutability coverage, the oldest restore point, and lit alarms.
• In the Backup cluster of Infrastructure & security, alongside your other backup feeds such as Axcient x360Recover and Datto Backup.
• In Strategic Business Reviews, in the backup and continuity chapter.
• In dashboard metrics for protected workloads, failing jobs, immutability coverage and Microsoft 365 objects.
• In the company alert band, through the backups-failing alert.

Why it matters

The backup section is where most business reviews get vague, because the evidence lives in the backup console and the review lives somewhere else. An MSP running Veeam for a partner like Northwind Traders can open the account and see 84 protected workloads, the two whose newest restore point is eleven days old, 31 of 48 virtual machines holding an immutable copy, and the Microsoft 365 job that has been sitting unconfigured since August — without anyone assembling an export first. That last line is also the one that sells: their backups exist, and today an attacker with domain admin could delete most of them.