How Microsoft 365 Backup Is Priced
Microsoft 365 Backup launched as a generally available service in 2024 and uses a pure consumption-based pricing model. You pay $0.15 per gigabyte per month of content that has been added to backup protection. The content that counts toward your billing includes OneDrive accounts, SharePoint sites (as reflected in the usage reports including the first-stage recycle bin), and Exchange mailbox content. There are no additional Azure API costs or storage fees beyond the per-GB rate — the billing runs through an Azure subscription, but Microsoft absorbs the underlying Azure storage cost within the $0.15 rate.
The retention period is 365 days. Once backed-up content expires beyond that window, it is no longer counted in your consumption and no longer billed. Deleted or versioned content in the recycle bin ages out after 365 days from the backup timestamp, which means your storage footprint for billing purposes is a rolling 12-month snapshot of your active protected data, not a cumulative archive.
The consumption model sounds simple but the cost can be deceptive. Enterprises routinely underestimate their per-user data footprint. Exchange mailboxes alone, with journaling enabled or large attachment histories, can run 50 to 150GB per user. OneDrive for Business with desktop sync enabled often adds another 50 to 200GB per active user. SharePoint site collections compound this further at the organisational level. For a 5,000-user enterprise with a realistic average footprint of 120GB per user, the annual M365 Backup cost runs to approximately $1.08 million.
What M365 Backup Covers and Where the Gaps Are
Microsoft 365 Backup covers three workloads: OneDrive for Business, SharePoint Online, and Exchange Online (mailboxes). The service is managed from the Microsoft 365 admin centre and provides point-in-time restore capability within the 365-day retention window. For each workload, you can restore content to a specific point in time rather than only to the most recent backup — which is meaningfully better than Microsoft’s standard recycle bin or deleted item recovery capabilities.
What M365 Backup does not cover is equally important. Teams chat history, Teams channel messages stored in Exchange, Planner data, Forms responses, and data held in third-party connectors within M365 are not within scope. Viva Engage (formerly Yammer) content is not covered. Power Automate flow history and Power Apps data are not covered. For organisations that have moved substantial business processes into the M365 platform beyond core email and file storage, native M365 Backup may leave significant data exposure unaddressed.
The second gap is compliance versus recovery. Microsoft 365 Backup is a data recovery tool, not a compliance archive. Organisations with legal hold, eDiscovery, or regulatory retention requirements above 365 days need Microsoft Purview (specifically Microsoft 365 retention policies or Compliance Archive) for those use cases, which carries separate licensing costs. M365 Backup and Purview retention are complementary, not interchangeable, and conflating the two is a common error in enterprise data governance discussions.
Veeam Data Cloud for M365: The Comparison
Veeam Data Cloud for Microsoft 365 uses a per-user pricing model rather than a per-GB consumption model. Pricing is approximately $18 to $22 per user per year depending on tier and volume. The Foundation tier covers standard backup; Advanced and Premium tiers add orchestration, compliance features, and expanded retention capabilities. Critically, Veeam includes unlimited storage within the per-user fee — storage costs are absorbed rather than metered separately.
For a 5,000-user estate, Veeam at $20 per user per year is approximately $100,000 annually with storage included. The equivalent M365 Backup spend at a 120GB average user footprint is $1.08 million. The gap is an order of magnitude. For large enterprises with high per-user data volumes, the per-user model that Veeam offers is structurally cheaper than Microsoft’s per-GB model — and that gap widens as data volumes grow over time.
Veeam also covers a broader workload scope than M365 Backup natively. Teams data, Planner, and other M365 workloads outside the core three (Exchange, OneDrive, SharePoint) are covered under Veeam’s backup scope, addressing some of the coverage gaps in Microsoft’s native offering. Veeam offers longer retention options that extend beyond 365 days, which is relevant for organisations with regulatory retention requirements above one year.
Evaluating M365 Backup vs third-party alternatives for your estate?
Our Microsoft licensing advisory specialists model the total cost and coverage comparison for your specific data profile.When M365 Backup Makes Sense
Despite the cost premium for large estates, M365 Backup has legitimate use cases. For small organisations (under 200 users) with moderate data volumes, the consumption model may actually be cheaper than a per-user Veeam subscription, particularly if data per user is below 50GB on average. The administrative simplicity of a native M365 tool managed from the admin centre — without a separate Veeam deployment, Azure storage account configuration, or partner integration — has genuine value for lean IT teams.
M365 Backup also makes sense as a complement to Veeam rather than a replacement, for organisations that want to apply selective high-granularity backup to specific high-value content areas (such as the SharePoint sites used for board materials or critical contract repositories) while using a cheaper per-user model for general user data. The ability to selectively activate M365 Backup on specific sites or mailboxes — rather than deploying it across the entire estate — allows for a tiered approach that can make the economics more attractive.
The final legitimate use case is hybrid compliance: organisations that need both backup recovery and Purview compliance archiving for specific user populations can use M365 Backup for recovery and Purview for regulatory retention within a unified Microsoft management plane. For organisations heavily invested in Microsoft’s compliance stack, the operational consolidation has value beyond pure cost.
How This Fits Into Your Microsoft EA and M365 Licensing Strategy
M365 Backup is not included in any M365 plan — not in E3 ($39 per user per month from July 1, 2026), not in E5 ($60 per user per month), and not in the new E7 ($99 per user per month, GA May 1, 2026). It is a separately purchased consumption service billed through Azure. This means that enterprises upgrading to E5 or E7 for security and compliance capabilities do not receive backup as a side effect of the upgrade — they still need to make a separate procurement decision about backup strategy.
This distinction matters at EA renewal time because Microsoft’s field teams sometimes present E5 or E7 as a comprehensive platform upgrade without being explicit about which data protection capabilities are and are not included. Purview compliance archiving and retention are included in E5 compliance features. Backup and recovery are not. Understanding that separation — and building it into your EA negotiation — ensures you are not paying for redundant or insufficient data protection coverage.
From a negotiation standpoint, M365 Backup is consumption-priced and therefore not subject to the same EA discount structure as seat-based M365 licences. The elimination of Level B through D volume discounts (effective November 1, 2025) does not directly affect consumption-priced services. However, the total Microsoft spend context — including backup consumption commitments — can be used to support the case for incremental discounts on the seat-based components of your EA, particularly in Q4 (April to June) when Microsoft’s field team has maximum discount authority before the June 30 fiscal year close.
The Decision Framework
The backup procurement decision reduces to three questions. First: what is your per-user data footprint across Exchange, OneDrive, and SharePoint? If you do not know this number, get it from your M365 admin centre before making any cost comparison. Second: do you need backup retention beyond 365 days for any portion of your estate? If yes, M365 Backup alone is insufficient and a Purview or third-party solution is required regardless. Third: do you need backup coverage for workloads beyond Exchange, OneDrive, and SharePoint — specifically Teams messages, Planner, or custom M365 data stores? If yes, M365 Backup alone is insufficient for your full data protection requirement.
For most large enterprises answering those three questions honestly, Veeam or an equivalent third-party solution remains the more cost-effective and comprehensive choice. For small organisations and for selective high-value use cases, M365 Backup is a viable option. The decision should be made from data rather than assumption — and the right time to make it is during your EA renewal cycle, when the full Microsoft licensing and service cost picture is visible and negotiable together.
Download the Microsoft EA Renewal Playbook
Includes the M365 backup decision framework and service cost model — independent, buyer-side only.