Sixty-three percent of enterprises I assess are relying on Exchange Online Archiving as their primary "backup" for Exchange data. This is a dangerous misunderstanding of what archiving is and what it isn't. Exchange Online Archiving is a compliance and retention tool. Microsoft 365 Backup is an operational recovery tool. They solve fundamentally different problems, and conflating them creates genuine legal and operational risk that becomes apparent only when an incident occurs — at which point it's too late to fix the licensing gap.
This guide draws on 500+ EA engagements and $2.1B in managed Microsoft spend to clarify the product boundaries, licensing models, cost implications, and the decision framework for determining whether your enterprise needs one or both tools. At scale, the wrong licensing decision here routinely costs enterprises either $200,000–$800,000 in unnecessary spend or equivalent exposure in uncovered recovery scenarios.
Independent Advisory. Zero Vendor Bias.
500+ Microsoft EA engagements. $2.1B in managed spend. 32% average cost reduction. We structure backup and archiving licensing to cover your real risk — without paying for overlap you don't need.
View Advisory Services →The Core Distinction: Retention vs Recovery
The confusion between archiving and backup stems from a surface-level similarity: both tools preserve email data beyond the primary mailbox. But the mechanisms, purposes, and legal implications are completely different.
Exchange Online Archiving (EOA) is a compliance-driven tool that copies or moves messages to an archive mailbox based on retention policies. It is designed for: long-term retention to meet regulatory requirements (7–10+ years for financial services, healthcare, government); eDiscovery and litigation hold compliance; reducing primary mailbox quotas; and meeting audit obligations. The key characteristic of archiving is that it preserves data for compliance purposes — it is not designed to recover data to a specific operational state.
Microsoft 365 Backup is an operational recovery tool that creates point-in-time snapshots of Exchange Online mailbox content. It is designed for: recovering accidentally deleted items or mailboxes; restoring from ransomware that has encrypted or corrupted mailbox data; recovering from admin errors (mistaken bulk deletions, misconfigured retention policies applied incorrectly); and providing granular item-level restore within a 180-day window. The key characteristic of M365 Backup is operational recovery to a specific moment in time — not compliance retention.
Feature Comparison: What Each Product Actually Does
| Capability | Exchange Online Archiving | Microsoft 365 Backup |
|---|---|---|
| Primary purpose | Compliance retention | Operational recovery |
| Retention period | Unlimited (auto-expanding with E3+) | 180 days |
| Restore granularity | eDiscovery export only (not native restore) | Item-level, folder-level, mailbox-level |
| Restore speed | Hours to days (via eDiscovery workflow) | Minutes to hours |
| Ransomware protection | Partial — archive may also be encrypted | Yes — immutable point-in-time snapshots |
| Admin error recovery | Limited — depends on retention policies | Yes — restores to pre-error state |
| eDiscovery support | Full — primary use case | Not a primary function |
| Litigation hold | Yes — preserves in-place | No — separate compliance feature |
| Regulatory admissibility | High — designed for compliance | Not a compliance record |
| Storage model | Archive mailbox (auto-expanding at E3) | Per-user per-month, usage-based storage |
Licensing and Cost Models
Exchange Online Archiving: What You're Actually Paying For
EOA is not a standalone product for most enterprises — it is included in or available as an add-on to several M365 plans:
| Plan/SKU | EOA Included? | Archive Type | List Price |
|---|---|---|---|
| M365 E3 / Office 365 E3 | Yes | Auto-expanding (unlimited) | Included |
| M365 E5 / Office 365 E5 | Yes | Auto-expanding (unlimited) | Included |
| Exchange Online Plan 2 | Yes | Auto-expanding (unlimited) | Included (~$10/user/month) |
| M365 Business Premium | Yes | 50GB archive (not auto-expanding) | Included |
| M365 E1 / Office 365 E1 | No | Add-on required | ~$3/user/month (list) |
| EOA Standalone Add-on | Add-on | Auto-expanding (unlimited) | ~$3/user/month (list) |
| Exchange Online Plan 1 | No | Add-on required | ~$3/user/month (list) |
Under EA, standalone EOA for E1 users typically negotiates to $2.40–$2.70/user/month at 2,000+ user volumes. The critical trap: auto-expanding archiving requires Exchange Online Plan 2, E3, or E5. E1 users with the standalone EOA add-on get a 50GB archive cap — which is insufficient for heavy-email environments (financial services, legal, healthcare) and triggers expensive mailbox growth issues within 2–3 years.
For a 1,000-user E1 estate adding EOA standalone: $2,700–$3,000/month = $32,400–$36,000/year. But if 20% of users exceed 50GB within 2 years, the remediation cost — either upgrading 200 users to E3 or managing archive mailbox overflow — exceeds the initial saving from choosing E1 over E3 in the first place.
Microsoft 365 Backup: The Pricing Reality
Microsoft 365 Backup uses a consumption-based pricing model layered on top of any existing M365 plan:
| Workload | What's Protected | Pricing Model | List Price |
|---|---|---|---|
| Exchange Online mailboxes | All mailbox items, 180-day window | Per user per month | ~$0.07/GB/month of protected data |
| OneDrive for Business | All files, 180-day window | Per user per month | ~$0.07/GB/month of protected data |
| SharePoint Online | All sites, 180-day window | Per site per month | ~$0.07/GB/month of protected data |
The challenge with M365 Backup pricing is data size estimation. Average Exchange Online mailbox: 8–15GB. For a 1,000-user estate at 10GB average: 1,000 × 10GB × $0.07 = $700/month = $8,400/year for Exchange protection alone. At 12GB average (more realistic for E3 users with 100GB mailbox quotas and heavy usage): $1,008/month = $12,096/year.
The 180-day retention window means Microsoft stores approximately 3–5× the active mailbox size in backup snapshots depending on change frequency. High-activity mailboxes (executives, compliance officers) carry disproportionate backup costs. A proper cost model must account for this distribution.
Get an Independent Second Opinion
Before adding Exchange Online Archiving or M365 Backup to your EA, speak with an adviser who has modelled the actual cost impact at your specific usage profile. The difference between right-sizing and over-buying is often $100,000–$400,000 over three years.
Request a Consultation →When You Need Archiving Only
Some enterprises can legitimately operate with archiving alone and do not need M365 Backup for Exchange. The conditions that make this defensible are narrow:
- No regulatory recovery requirement: Your industry does not require point-in-time restore (no financial services, healthcare, or government mandate for operational recovery timelines)
- Ransomware risk mitigated elsewhere: You have air-gapped backups of Exchange data via third-party tools (Veeam, AvePoint, Metallic) that provide the operational recovery layer
- Low admin-error risk: Tight RBAC controls mean accidental bulk deletions by admins are extremely unlikely and your native 30–93 day recycle bin covers routine user errors
- Compliance-only driver: Your archiving requirement is purely about retention for regulatory review — not operational business continuity
Organisations that fit this profile are typically: small enterprises (<250 users) with mature third-party backup, non-regulated industries with simple retention policies, and organisations already using third-party backup tools that include Exchange coverage.
When You Need Backup Only (Without EOA)
The inverse scenario — M365 Backup without EOA — applies when: all users are on E3 or higher (which includes EOA), operational recovery is the priority, and compliance archiving needs are met by M365 plan retention features. This is the most common EA scenario for large enterprises with mature M365 deployments — E3/E5 users already have unlimited archiving included, so the only question is whether to add M365 Backup for the operational recovery layer.
When You Need Both
The "both" scenario is mandatory for a specific set of enterprise profiles. In my experience, approximately 40% of regulated enterprises require both tools, yet fewer than 15% are correctly licensed for both. The gaps create legal and operational exposure that typically materialises during an audit, litigation hold, or ransomware event.
You need both Exchange Online Archiving and Microsoft 365 Backup when any of the following apply:
- Financial services with 7–10 year email retention: FINRA Rule 17a-4, SEC 17 CFR 240.17a-4, MiFID II — all require immutable archives. EOA provides the compliance record. M365 Backup provides the operational recovery separate from the compliance record.
- Healthcare with HIPAA archive obligations: The HIPAA Security Rule requires backup and recovery procedures (§164.308(a)(7)). EOA for the compliance record, M365 Backup for operational recovery.
- Legal sector with matter-based retention: Client matter files retained indefinitely require long-term archiving that M365 Backup's 180-day window cannot provide. EOA + M365 Backup creates the complete coverage.
- Any enterprise using E1 with 5-year+ retention: EOA standalone on E1 provides archiving but the 50GB cap will fail. Upgrading to E3 gets unlimited EOA; add M365 Backup for recovery.
- Ransomware-sensitive regulated data: Ransomware can encrypt live mailboxes and, in some cases, corrupt archive data if improperly configured. M365 Backup's immutable snapshots provide the recovery layer that compliance archiving cannot guarantee.
3-Year Cost Model: Typical Enterprise Scenarios
| Scenario | Users / Config | Year 1 Cost | 3-Year Total | Coverage |
|---|---|---|---|---|
| E1 + EOA standalone only | 1,000 E1, EOA add-on | $34,200 | $102,600 | Compliance only, 50GB cap risk |
| E3 (EOA included, no backup) | 1,000 E3 | $0 incremental | $0 incremental | Compliance only, unlimited archive |
| E3 + M365 Backup for Exchange | 1,000 E3, 10GB avg mailbox | $8,400–$12,000 | $27,000–$39,000 | Compliance + operational recovery |
| E1 + EOA + M365 Backup | 1,000 E1, both tools | $42,600–$46,200 | $129,600–$141,000 | Full coverage, 50GB archive cap risk |
| E3 + M365 Backup (full suite) | 1,000 E3, Exchange+OneDrive+SPO | $24,000–$36,000 | $78,000–$117,000 | Full compliance + full recovery |
The analysis reveals a recurring pattern: enterprises on E3 already have the compliance archiving component covered — the marginal cost question is purely about M365 Backup. For a 1,000-user E3 estate, adding full M365 Backup (Exchange + OneDrive + SharePoint) costs $24,000–$36,000/year, or $2–$3/user/month. For regulated industries where a ransomware incident costs an average of $4.5M in recovery, legal fees, and downtime, that coverage cost is trivial.
The "Litigation Hold vs Backup" Misconception
Some IT and legal teams conflate litigation hold with operational backup. They are not interchangeable. Litigation hold preserves mailbox data in a hidden, immutable state for legal purposes — but this data is not readily restorable to a working mailbox without going through the eDiscovery workflow, which requires Purview eDiscovery Standard (included with E3) or Premium (add-on). The process takes hours to days, involves legal review workflows, and is not designed for rapid operational recovery.
If an admin accidentally deletes 500 mailboxes that are under litigation hold, the data still exists — but recovering it requires an eDiscovery export, re-import, and potentially legal sign-off on the recovery process. In a business continuity scenario, that delay is unacceptable. M365 Backup restores affected mailboxes directly to a point-in-time state without touching the litigation hold data, preserving both the operational mailbox and the compliance record simultaneously.
EA Negotiation: Structuring the Right Coverage
When structuring EA coverage for email protection, the leverage points differ by scenario:
For E1-Heavy Estates Considering E3 Upgrade
The EOA add-on cost ($2.40–$2.70/user/month under EA) is approximately 60% of the incremental cost to upgrade from E1 to E3 (~$4–$6/user/month). For E1 users who need EOA plus have high email volumes, the E3 upgrade frequently costs less over 3 years than E1 + EOA add-on, once you account for the unlimited archive benefit and avoided mailbox management overhead. Use this analysis as leverage to upgrade the plan rather than stack add-ons.
For E3 Estates Adding M365 Backup
M365 Backup is currently excluded from standard EA discounting and priced as a consumption service through the Azure billing framework. Negotiate storage commitment tiers: committing to a specific protected-data volume (e.g., 15TB) for 3 years unlocks 10–15% storage discounts. MACC-eligible organisations can route M365 Backup storage through their Azure Consumption Commitment, reducing effective cost further.
Competitive Leverage
Veeam Backup for Microsoft 365 (VBO) and AvePoint Cloud Backup both offer Exchange Online backup at lower per-user costs than M365 Backup for large volumes. A credible VBO or AvePoint proposal in your EA negotiation will prompt Microsoft to reduce M365 Backup storage pricing by 12–20%. This is a well-established negotiating tactic — use it even if you prefer the native Microsoft solution.
📄 Free Guide: Microsoft Backup Licensing Guide
Complete coverage of all Microsoft backup products, cost models, third-party comparisons, and EA negotiation tactics for enterprise buyers.
Download Free Guide →Implementation: How to Configure Both Tools Without Overlap
When running both EOA and M365 Backup, configuration decisions matter for both cost and compliance. Key guidance:
- Do not rely on M365 Backup as the primary compliance record. EOA with defined retention policies and litigation hold provides the admissible compliance record. M365 Backup is the recovery layer — treat it as infrastructure, not compliance documentation.
- Set retention policies before enabling M365 Backup. If your M365 Backup data captures mailbox state after a misconfigured retention policy has already deleted items, the backup won't recover what retention already removed. Sequence: configure retention, validate, then enable backup.
- Test restore procedures quarterly. The value of M365 Backup is only realised if restore procedures are tested and documented. Many enterprises have paid for M365 Backup but never validated whether their IT team can execute a restore within the required RTO.
- Monitor storage growth monthly. M365 Backup costs scale with data volume. Set Azure Cost Management alerts at 80% of your committed storage tier to avoid surprise overages.
Frequently Asked Questions
Is Exchange Online Archiving the same as a backup?
No. Exchange Online Archiving is a compliance and retention tool — it preserves email according to policy rules and supports eDiscovery. It does not provide point-in-time restore, ransomware recovery, or protection against admin errors. Microsoft 365 Backup provides operational recovery from accidental deletions, ransomware, and admin errors with granular restore.
Do I need both Exchange Online Archiving and Microsoft 365 Backup?
Many regulated enterprises need both. Archiving handles compliance obligations (10-year email retention, eDiscovery holds, litigation hold). M365 Backup handles operational recovery (restoring accidentally deleted mailboxes, recovering from ransomware). They serve distinct purposes and neither replaces the other.
What does Exchange Online Archiving cost in an Enterprise Agreement?
EOA is available standalone at approximately $3/user/month list price, or is included in M365 E3, E5, Exchange Online Plan 2, and M365 Business Premium. Under EA, standalone EOA for E1 users costs approximately $2.50–$2.80/user/month after negotiation. Unlimited archiving (auto-expanding) requires E3 or higher.
What is the Microsoft 365 Backup retention window?
Microsoft 365 Backup for Exchange Online provides a 180-day backup retention window with restore point granularity down to individual items. This is distinct from compliance retention which can extend to 10+ years under EOA. The 180-day window covers most operational recovery scenarios but cannot substitute for long-term compliance archives.
Can I use litigation hold instead of Microsoft 365 Backup?
Litigation hold preserves email for legal purposes but does not provide operational backup. If an administrator deletes a mailbox with litigation hold, the data is retained but is not readily restorable without eDiscovery tools. M365 Backup provides faster, point-in-time operational restore independent of litigation hold status.
Related Microsoft Backup & Recovery Guides
- Microsoft Backup & Disaster Recovery Licensing: Complete Guide
- Azure Backup Licensing & Pricing Guide
- Azure Site Recovery Licensing Guide
- Veeam vs Azure Backup: Enterprise Licensing Comparison
- SharePoint Backup Licensing Guide
- OneDrive Versioning vs Backup: What Enterprises Need to Know
- Purview eDiscovery Premium vs Standard
- Microsoft Backup Third-Party Alternatives