Keepit vs Veeam Data Cloud for Microsoft 365 Backup (2026)

If you came here expecting to read about self-managed Veeam backup software on a Windows server versus a SaaS platform, that is a different page. We have a separate comparison of Keepit versus Veeam Backup for Microsoft 365 (VB365) that covers the self-managed angle.

Veeam Data Cloud is Veeam's answer to the managed-SaaS market. It launched in 2024, and it removes the biggest operational argument against Veeam: you no longer need to provision servers, size storage, or patch anything. Veeam runs the infrastructure. You get a web portal, configure policies, and run restores.

That changes the comparison. The 'no infrastructure to manage' advantage that Keepit used to hold over Veeam is gone when you're comparing against VDC. What remains are two questions: where does the data live, and how many of your SaaS apps does the product actually cover?

VDC stores backups in Azure Blob Storage. Veeam is transparent about this. You pick an Azure region (Australia East is available), and your backup data lands there.

The problem is the same one we wrote about in the VB365 comparison, but harder to dismiss this time because VDC is supposed to be the 'fully managed, worry about nothing' product. If you are backing up Microsoft 365 because you are worried about a Microsoft-related incident, storing those backups inside Microsoft's infrastructure creates a logical dependency you may not want.

Three scenarios where this matters:

1. Tenant compromise. An attacker who has gained Global Admin in your Microsoft tenant may be able to reach Azure resources in the same subscription or directory. Your VDC backups are in Azure. Your Keepit backups are not. 2. Azure regional outage. If the Azure region your backups live in goes down, your M365 data and your backup of that data are both affected. Keepit's infrastructure is a different cloud entirely. 3. Commercial dispute. If Microsoft suspends your tenant or Azure subscription, you want backup data that is not gatekept by the same vendor. Keepit's billing relationship and infrastructure are separate.

VDC does offer cross-region replication as an option, but the replicas are still in Azure. Moving from one Azure region to another Azure region does not change the vendor dependency.

This is not a theoretical argument. Australian organisations subject to APRA CPS 234, the Privacy Act, or Essential Eight maturity assessments are already being asked by auditors to explain where their backup data lives and whether it shares a failure domain with production. Keepit makes that answer simple.

The workload count is where this comparison gets lopsided. Veeam Data Cloud covers 4 workloads: Microsoft 365, Entra ID, Salesforce, and Azure IaaS/PaaS. Fine if your world is Microsoft and Salesforce.

Keepit covers 15 workloads as of April 2026, and the number grows every quarter. The current list: Microsoft 365, Entra ID, Dynamics 365, Power Platform, Azure DevOps, Google Workspace, Salesforce, Jira, Confluence, Zendesk, Okta, DocuSign, BambooHR, Miro, and GitHub. New connectors ship every 4-6 weeks. Slack, GitLab, ServiceNow, HubSpot, Workday, Figma, and Notion are on the published roadmap, with a target of 100+ connectors by 2028.

Why does workload breadth matter? Two reasons.

For MSPs: every new Keepit connector is a new service you can bill for without deploying a new product. You are already managing the customer's M365 backup through Keepit's Partner Management Console. When Keepit ships the Slack connector next quarter, you add Slack backup to the customer's contract, flip a switch in the same portal, and start billing. With VDC, there is no path to backing up Slack, Jira, GitHub, or Google Workspace at all. You would need a second vendor.

For end users: adopting a new SaaS application is less risky when you know your backup platform already covers it. An IT team evaluating Jira or GitHub can factor in that Keepit will protect it from day one. With VDC, each new SaaS adoption outside the Microsoft/Salesforce ecosystem reopens the 'what do we do about backup' question.

Keepit does not back up Azure IaaS or PaaS. If you run VMs in Azure, Azure SQL databases, or Cosmos DB, VDC covers those workloads and Keepit does not. If you are heavily invested in Azure infrastructure beyond M365, having one product that backs up both your tenants and your VMs is genuinely useful.

VDC's Premium tier also includes integration with Microsoft 365 Backup Storage, which uses Microsoft's own backup APIs for restore speeds above 5 TB per hour. For very large tenants with tens of terabytes of SharePoint data, this can meaningfully reduce recovery time. Keepit's restore speed is good but does not use this proprietary API layer.

Then there is the Veeam brand. It is the market share leader in enterprise backup, and a lot of IT teams already know the interface and already run Veeam B&R for on-premises workloads. Adding VDC to the same management plane keeps things simple. If your organisation runs Veeam everywhere else and wants to keep the vendor count down, VDC is the obvious pick.

Finally, the VCSP programme means MSPs already in the Veeam ecosystem can add VDC to their existing rental billing without onboarding a new vendor relationship.

Both products price per user per month, but the structures are different.

VDC has three tiers. Foundation (M365 backup) runs USD 2.63-3.50 per user per month depending on volume. Advanced adds Entra ID. Premium adds the Microsoft 365 Backup Storage integration for faster restores and runs roughly USD 5-7 per user per month. Storage is included within fair-use limits.

Keepit does not publish pricing, but all workloads (currently 15+) are available at every plan tier. The difference between tiers is retention (1-year vs unlimited), support level, and compliance features. Storage and retention are genuinely unlimited on the Enterprise Unlimited and Governance Plus plans with no fair-use caveats.

The pricing comparison gets interesting when you count workloads. If you are only protecting M365, VDC Foundation is likely cheaper per user. But if you also need Google Workspace, Jira, GitHub, Dynamics 365, or any of the other SaaS apps Keepit covers that VDC does not, VDC cannot do the job at any price. You would need VDC plus a second product, and the combined cost almost certainly exceeds Keepit alone.

For MSPs, the maths is similar but the margin story matters more. Keepit's flat per-user rate across all workloads makes it simple to build a rate card. VDC's tiered pricing means more SKU management and more variability in your cost base as customers move between tiers.

Contact CRS for a side-by-side pricing comparison against your specific tenant size and workload mix.

Keepit is the better fit when:

• Independence from Azure is a compliance or risk requirement.
• You need to protect SaaS apps beyond M365 and Salesforce (Google Workspace, Jira, GitHub, Dynamics 365, Power Platform, Zendesk, Okta, or any of the others).
• You are an MSP and want a single backup platform that grows revenue as Keepit adds connectors.
• Immutability must be structural and non-configurable for audit purposes.
• You want one vendor, one portal, one billing relationship for all SaaS backup.

Veeam Data Cloud is the better fit when:

• You need Azure IaaS/PaaS backup alongside M365.
• You already run Veeam Backup & Replication and want one management plane.
• Restore speed for very large SharePoint tenants is a priority (Premium tier with Microsoft Backup Storage APIs).
• Your organisation is an existing VCSP partner and adding VDC keeps the vendor count at one.
• Your backup scope is strictly Microsoft and Salesforce with no plans to expand.