Microsoft 365 Archive vs Backup for MSPs: Cheap Storage Is Not Recovery

Microsoft 365 Archive vs Backup is going to create a lot of bad client conversations.

Archive sounds like backup to a CFO. Backup sounds like retention to an operations manager. Retention sounds like legal hold to a client who just wants old files to exist somewhere. MSPs know those are different things, but clients often hear one big promise: our Microsoft 365 data is safe.

That promise is too vague to quote.

Microsoft 365 Archive can be useful. It moves inactive SharePoint files or sites into colder storage so clients can reduce active storage pressure without dumping content into some side bucket nobody can search. But archive is not a time machine. It is not a clean ransomware recovery story. It is not a substitute for retention policy design, legal hold, or backup restore testing.

Quick answer: Microsoft 365 Archive is cheaper cold SharePoint storage. Microsoft 365 Backup is point-in-time recovery. Retention and legal hold preserve content for compliance and eDiscovery, but they are not a restore plan for ransomware, accidental deletion, or a bad migration. MSPs should quote archive cleanup and backup recovery as separate scopes.

The client does not need a product lecture. They need a simple map of what each control is for, what it costs, and what happens when someone asks for data back.

Microsoft 365 Archive vs Backup: the practical difference

Start with the job each tool is hired to do.

According to Microsoft's Microsoft 365 Archive overview, Archive is for inactive SharePoint files and sites that still need Microsoft 365 search, security, and compliance handling. Archived content moves into a colder tier, no longer consumes active tenant storage quota, and is not directly accessible until reactivated.

Microsoft 365 Backup is different. Microsoft's Backup FAQ says backup is built for restoring content to a previous healthy state, with short recovery point objectives and restore tooling for large accidental or malicious deletion scenarios.

That gives MSPs the clean comparison:

Need	Better fit	Why
Lower active SharePoint storage pressure	Microsoft 365 Archive	It moves inactive SharePoint content into colder archive storage.
Restore from ransomware or mass deletion	Microsoft 365 Backup	It is designed for point-in-time recovery and admin-driven restore.
Keep records for policy or regulation	Retention policies or labels	They retain or delete content based on compliance rules.
Preserve mailbox data for litigation	Litigation hold	It preserves deleted items and original versions for discovery.
Prove a client approved what moved cold	MSP scope and signoff	Microsoft will not fix a vague client agreement.

The last row is the one that matters in QBRs.

If a client says, "Can we archive old SharePoint stuff to save money?" the answer should not be yes or no. The answer should be: we can assess candidates, check holds and retention, calculate the storage case, define retrieval expectations, and quote the cleanup work.

That is a paid scope, not a free admin favor.

Archive can cut storage cost, but the math has traps

Microsoft's Archive pricing page says archive storage is charged only when archived plus active SharePoint storage exceeds the tenant's included or licensed SharePoint storage capacity. Microsoft also shows archive storage at $0.05 per GB per month in its Archive FAQ, compared with $0.20 per GB per month for standard storage.

That looks simple. It is not.

Microsoft's SharePoint storage support page says non-EDU tenant quota is based on 1 TB plus 10 GB per eligible license, plus any extra file storage add-ons. If the client is still under that combined quota, archive may not create a new storage bill at all. If they are over, archive can be cheaper than buying more standard storage.

File-level archive adds another wrinkle. Microsoft's Archive FAQ says file-level archive does not change site storage usage or site quota behavior. The archived file is still accounted for in site storage. It can reduce active tenant storage classification, but it will not magically fix every site-level storage problem.

So the MSP pricing question is not, "Is archive cheaper?"

It is:

• Which sites or libraries are actually inactive?
• Is the tenant above licensed SharePoint storage?
• Is the pain tenant quota, site quota, messy ownership, or user behavior?
• Who approves archive candidates?
• How often will users ask for reactivation?
• Who pays when the cleanup takes eight hours instead of two?

Standalone quote for clients: Archive is a storage lifecycle tool, not a backup policy. It can lower active SharePoint storage pressure when the storage math works, but it does not prove the business can recover from deletion, corruption, ransomware, or a bad admin change.

That sentence belongs in the QBR deck before anyone starts clicking Archive.

Retention and legal hold are not backup either

This is where clients get dangerous confidence.

Microsoft Purview retention documentation says retention settings can retain content, delete content, or retain and then delete content. Retention keeps copies in places like the Preservation Hold library for SharePoint and OneDrive or Recoverable Items for Exchange.

That is useful. It is also not the same as a clean restore workflow.

Microsoft's own Backup FAQ says legal holds retain data, but they are optimized for export through eDiscovery, not mass restore. Backup is the tooling Microsoft points to for ransomware and large accidental or malicious deletions.

Litigation hold is narrower still. Microsoft's Exchange litigation hold documentation says it preserves mailbox content, including deleted items and original versions of modified items. It may take up to 60 minutes to apply, and Microsoft recommends monitoring Recoverable Items quotas because held mailboxes can grow quickly.

For MSPs, the message is blunt:

• Retention answers, "What must we keep or delete by policy?"
• Legal hold answers, "What must we preserve for a legal matter?"
• Archive answers, "What inactive SharePoint content can move cold?"
• Backup answers, "How do we get back to a known good point?"

If the client wants all four outcomes, sell all four scopes. Do not bury them in one Microsoft 365 cleanup line item.

Backup has recovery limits too

Backup is not magic. It just has a different job.

Microsoft says Microsoft 365 Backup has a 10-minute recovery point objective for Exchange Online. For SharePoint and OneDrive, Microsoft says the trailing two weeks can go back to 10-minute periods, then weekly periods from two to 52 weeks in the past.

Microsoft's Backup pricing page lists Microsoft 365 Backup at $0.15 per GB per month of protected content. It also says backup storage includes live protected content plus deleted and versioned data held for recovery, such as second-stage recycle bin data and deleted or versioned mailbox items.

That means clients need the same boring scope discipline they need for archive:

1. Decide which SharePoint sites, OneDrive accounts, and mailboxes are protected.
2. Define restore scenarios, not just retention periods.
3. Price protected storage and expected growth.
4. Document who can request restores and who approves them.
5. Test recovery before the first angry Friday afternoon.

The MSP that skips step five is selling hope with an invoice attached.

How to explain it in a QBR

Use a four-box model. Clients can understand it in two minutes.

Control	Plain-English client explanation	MSP quote boundary
Archive	We move inactive SharePoint content cold to reduce active storage pressure.	Assessment, candidate list, owner approval, reactivation rules.
Backup	We keep recovery points so we can restore from bad changes or deletions.	Protected workloads, restore testing, recovery labor, retention period.
Retention	We keep or delete content based on policy.	Policy design, label strategy, review cadence, exceptions.
Legal hold	We preserve content for legal discovery.	Legal trigger, mailbox scope, counsel direction, export support.

Then ask the client the question they actually need to answer:

"Are we trying to lower storage cost, meet a policy, preserve evidence, or recover from damage?"

If they say "all of it," fine. That is not a blocker. It is a bigger scope.

This is where Microsoft 365 Archive file-level archiving becomes a useful client project instead of another free admin chore. Archive candidates need business owners. Backup needs restore assumptions. Retention needs policy review. Legal hold needs actual legal direction.

And if the conversation turns into backup vendor selection, compare the recovery model and billing shape before the logo. We covered that in our MSP backup solution comparison and Wasabi vs Backblaze B2 backup storage guide.

The scope MSPs should quote

For a client with messy SharePoint growth and vague backup expectations, quote a Microsoft 365 data protection cleanup package with four deliverables:

1. Storage and archive assessment: active storage, archive candidates, site owners, stale content, and storage cost scenarios.
2. Recovery design: protected workloads, restore point expectations, excluded data, and restore test cadence.
3. Retention and hold review: active policies, labels, legal hold assumptions, Recoverable Items risk, and owner exceptions.
4. Client decision record: what gets archived, what gets backed up, what stays active, what gets deleted, and who approved each category.

Do not call this "Microsoft 365 optimization." That phrase is how scope gets eaten.

Call it what it is: storage cleanup, recovery planning, and governance review.

If you want a cleaner way to turn those findings into roadmap items, budgets, project scopes, and client approvals, join Scopable early access. The archive decision should not live in one technician's notes after the QBR ends.