Direct answer: a Microsoft 365 backup price is not comparable until the buyer normalizes protected scope, retention, storage, operations, support, and exit. Microsoft's native product has a published consumption meter. Managed services commonly use per-user, storage, tenant, or bundled pricing. Self-managed software adds infrastructure and staff cost. A free edition can be appropriate for a small environment but is not zero-cost to operate.
Use official rates only where they are public and current. For every other product, use a dated written quote rather than a price copied from a reseller page. This guide does not claim that North Brook Vault, Microsoft, Veeam, or another option is cheapest. Compare product fit first using the M365 backup shortlist, then model only candidates that pass mandatory recovery and security requirements.
Four Pricing Models Buyers Encounter
| Model | Typical billing input | Costs easily missed | Current example |
|---|---|---|---|
| Consumption | Protected or retained GB per month | Deleted/versioned content, archives, growth, offboarded data retained for recovery, and minimum terms | Microsoft 365 Backup lists $0.15 per protected GB per month |
| Per-user managed SaaS | Billable protected users, sometimes with storage included or metered separately | Shared mailboxes, inactive users, storage allowances, overages, support tier, tenants, and retention | Use the current service quote and billable-user definition |
| Self-managed software | User license plus operated infrastructure | Compute, database, object storage, immutability, replication, egress, monitoring, upgrades, incidents, and recovery tests | Self-managed Veeam Backup for Microsoft 365 |
| Hybrid formula | Seats plus tenants, retained storage, retention, or account minimum | Storage growth assumptions, minimum charge, exceptional migration/restore work, taxes, and negotiated terms | North Brook Vault's published estimator |
Collect Comparable Inputs
| Input | How to measure it | Commercial evidence |
|---|---|---|
| Protected identities | Users, shared/resource mailboxes, inactive users, and tenants in scope | Vendor's exact billable-unit definition and minimum |
| Protected data | Exchange, archive mailboxes, OneDrive, SharePoint, recycle bins, versions, and required Teams data | Meter definition, included allowance, and storage rate |
| Growth and retention | Monthly live growth, churn, deleted data, versions, retention months, and legal holds | How retained and offboarded data continues to bill |
| Infrastructure | Compute, operating system, database, repository, replication, monitoring, and network | Cloud calculators, storage quote, licenses, support, and egress |
| Operations | Implementation, monitoring, upgrades, incidents, reporting, testing, and training hours | Loaded labor rate and provider responsibility matrix |
| Recovery and exit | Routine restores, incident surge, export, migration, contract termination, and historical access | Contract rates, format, retrieval window, and deletion terms |
Transparent Formulas
Annual consumption = average billable protected GB x monthly rate x 12
Annual per-user service = billable users x monthly user rate x 12 + storage + tenant + support + exceptions
Annual self-managed TCO = software + compute + database + storage + replication + egress + monitoring + labor + support
Three-year TCO = implementation + year 1 + year 2 + year 3 + migration/exit - committed discounts
Use average billable volume rather than today's value when data grows. Keep one-time implementation and exit costs visible instead of hiding them in a monthly equivalent. For architecture-related storage inputs, review where Microsoft 365 backup data lives.
Worked Example 1: Native Microsoft 365 Backup
Assume a tenant measures 6,000 GB of billable protected content after including the content Microsoft says contributes to the meter. At the official $0.15/GB/month list price documented in August 2026:
6,000 GB x $0.15 = $900 per month
$900 x 12 = $10,800 annualized
This is a static planning estimate, not projected first-year spend. Microsoft's documentation explains that protected size can include live content, specified recycle-bin content, mailbox archives, and deleted/versioned mailbox items. Growth and churn therefore matter. The product also has a one-year retention period, so this price must not be compared with a seven-year service as though coverage were equivalent.
Worked Example 2: North Brook Vault
Assume 100 protected seats, one tenant, 100 GB of new backup data per month, and 12-month retention. Under the public estimator dated August 21, 2026:
- Seat fee:
100 x $5 = $500. - Additional-tenant fee:
$0because the first tenant is included. - Estimated retained storage:
100 GB x 12 = 1,200 GB. - First retention month included: subtract
100 GB. - Tenant storage allowance: subtract
1 GB. - Billable retained storage:
1,099 GB x $0.12 = $131.88. - Monthly estimate:
$631.88; annualized run rate:$7,582.56.
Actual delta growth, compression, retained objects, taxes, exceptional work, and negotiated terms can differ. The interactive North Brook Vault calculator is the controlling public estimator; a written proposal controls the final offer.
Veeam Community Edition: The 10-to-11 Decision
Veeam's current downloads page describes Veeam Backup for Microsoft 365 Community Edition as free backup and recovery for up to 10 users. Veeam's licensing policy describes paid Veeam Backup for Microsoft 365 licensing per user with a minimum of 10 users. Crossing from 10 protected users to 11 is therefore not just an extra-user calculation. It is a decision about the paid license, repository capacity, support, and operating model.
For 10 users, record the value of administrator time, compute, database, storage, monitoring, upgrades, and restore testing even when the software charge is zero. For 11 or 100 users, obtain a current paid quote and compare self-managed TCO against Veeam Data Cloud and other managed routes. The Microsoft versus Veeam guide separates those delivery models.
Cost Comparison Procedure
- Apply product gates first. Eliminate candidates that miss required objects, restore destinations, retention, security controls, region, or operating model.
- Freeze one scope. Use the same identities, workloads, retention, growth, support, and recovery scenarios for every estimate.
- Collect primary evidence. Save official meter pages and dated quotes with edition, region, term, minimum, discounts, and renewal treatment.
- Measure operations. Estimate implementation and recurring hours with the team that will actually run monitoring, upgrades, incidents, and tests.
- Model three years. Include growth, price changes allowed by contract, storage expansion, support, and exit.
- Test sensitivity. Recalculate at low, expected, and high data growth and labor assumptions.
- Attach uncertainty. Mark unknowns and do not present the result as a quote or guaranteed saving.
Verification Checklist
- Every rate has an official source or dated written quote and an effective currency, region, and term.
- Billable users, protected GB, deleted data, versions, archives, tenants, and minimums are defined.
- Retention and object-level recovery are equivalent before totals are compared.
- Self-managed options include infrastructure, storage, monitoring, upgrades, support, and labor.
- Managed options identify included storage, support, exceptional restores, migration, export, and exit.
- Calculations distinguish static run rate, first-year cash spend, and three-year TCO.
North Brook Vault Fit and Current Gaps
North Brook Vault's public pricing is useful for organizations that want a managed service and can estimate protected seats, tenants, monthly backup growth, and retention. Price does not remove product-fit gates. North Brook Vault currently lacks native Object Lock configuration or enforcement, OneDrive file-version-history capture, Teams chat or channel-message restore, customer export, compliance reporting, and a zero-throttling guarantee. Review the managed backup service boundary, then confirm required handlers, support, unusual restore work, and contract terms in the proposal and recovery consultation.
Official Sources
- Microsoft 365 Backup pricing model, documentation dated July 14, 2026 and updated August 7, 2026; accessed August 21, 2026.
- Microsoft 365 Backup overview, updated July 30, 2026; accessed August 21, 2026.
- Veeam product downloads and Community Edition description; accessed August 21, 2026.
- Veeam licensing policy; accessed August 21, 2026.
- Veeam Data Cloud for Microsoft 365; accessed August 21, 2026.