Blog

Why this discussion matters

After publishing a recent article on SharePoint Online storage costs, people reached out with the same question:

It is a fair question.

Identifying inactive content is only half the problem. The second challenge is getting that content into the right destination without creating a governance nightmare, breaking business processes, or introducing an expensive migration project.

The right approach depends largely on:

• Data volume
• Frequency of movement
• Archive requirements
• User access expectations
• Compliance considerations
• Operational maturity

There is no single correct answer.

Before moving anything: ask three questions

Before discussing technology, start with business requirements. The wrong destination can create more problems than it solves.

Question 1: Does anyone actively collaborate on this content?

If users still need coauthoring, Teams integration, SharePoint search, metadata, sharing links, or sensitivity labels, then the content probably belongs in SharePoint.

Question 2: Does anyone still access the content?

If content is accessed monthly or quarterly, Azure Files or Blob Cool Storage may be appropriate. If content has not been touched in years, Blob Cold or Blob Archive become stronger candidates.

Question 3: How quickly must it be retrieved?

Retrieval expectations often determine the destination.

Option 1: manual download and upload

Best for: small migrations, department archives, and one-time projects.

The simplest solution is still available: download content from SharePoint and upload it to Azure Files or Azure Blob Storage.

Advantages:

• No development required
• No automation required
• Easy for small projects

Disadvantages:

• Not scalable
• Time consuming
• Error prone
• Difficult to repeat

For a few gigabytes, this may be perfectly acceptable. For multiple terabytes, it becomes painful quickly.

Option 2: Power Automate

Best for: ongoing archive workflows, citizen developer solutions, and department-level automation.

Power Automate is often the first solution administrators consider when they want a low-code archive workflow.

File created or modified
          ↓
Evaluate file age or metadata
          ↓
Copy to Azure Blob
          ↓
Notify owner
          ↓
Optionally remove from SharePoint

This works particularly well when files exceed a retention threshold, projects are marked closed, or documents enter an archive status.

Advantages:

• Low code
• Microsoft-native workflow model
• Easy to demonstrate and maintain for smaller scenarios

Disadvantages:

• Can become complex at scale
• Not ideal for massive migrations
• Platform limits may become relevant

For many small and midsize organizations, this can be enough. For very large migrations, I would usually look at more robust orchestration options.

Option 3: Azure Logic Apps

Best for: enterprise workflows, complex business processes, and advanced integrations.

Think of Azure Logic Apps as a more enterprise-focused workflow option. Logic Apps can support archive workflows that monitor content sources, move files, apply classifications, trigger approvals, and interact with Azure services.

Advantages:

• Scalable
• Flexible
• Cloud native
• Better suited for enterprise automation patterns

Disadvantages:

• Requires Azure expertise
• Creates more operational ownership
• Needs good monitoring, error handling, and cost awareness

Logic Apps share the same SharePoint connector size constraints described above, so the same ~100 MB download ceiling and chunking guidance apply here as well. When organizations are already invested in Azure integration services, Logic Apps can become a strong long-term solution.

Option 4: Azure Data Factory

Best for: multi-terabyte migrations, enterprise archives, and scheduled bulk transfers.

When migration sizes reach several terabytes, Azure Data Factory deserves attention. It is designed around data movement, orchestration, monitoring, and repeatable data pipelines.

A common pattern is:

SharePoint Online
        ↓
Azure Data Factory
        ↓
Azure Blob Storage
        ↓
Lifecycle policies
        ↓
Cold or Archive tier

Advantages:

• Monitoring
• Scheduling
• Retry-oriented pipeline thinking
• Enterprise orchestration

Unlike smaller automation methods, Data Factory is usually better aligned with large-scale movement and repeatable processing.

Option 5: PowerShell and PnP PowerShell

Best for: consultants, service providers, and large tenant assessments.

PowerShell remains one of the most flexible options because it allows administrators and consultants to build logic around the specific tenant, site structure, library naming, metadata, and archive requirements.

With a scripted approach, you can design workflows to:

• Inventory sites
• Analyze storage growth
• Identify stale content
• Export files
• Upload content to Azure storage targets

Typical examples include closed projects older than a defined age, historical media libraries, migration leftovers, and legacy repositories.

Option 6: third-party migration platforms

Many organizations already own tools that can help with migration, reporting, governance, and operational visibility.

Examples often include:

• ShareGate
• AvePoint
• Quest
• Migration Manager platforms

These products frequently provide scheduling, reporting, error handling, large-scale movement, and governance-related capabilities.

The biggest benefit is usually operational simplicity. The biggest downside is licensing cost. For organizations that already own one of these platforms, it may be worth evaluating before building a custom migration pipeline from scratch.

Option 7: Azure Files

Best for: traditional file shares, legacy applications, and SMB access.

Many organizations do not actually need object storage. They need file shares.

In these situations, Azure Files can be a strong destination. Common use cases include:

• Department archives
• Legacy application storage
• Engineering repositories
• File-share replacement projects

Users can continue working with familiar file-share style access rather than learning a new retrieval process. That is useful when the data is no longer a collaboration library, but still needs to behave like a file share.

Option 8: Blob Storage with lifecycle policies

My favorite long-term archive approach.

If the objective is reducing storage cost over time, Blob Storage with lifecycle policies is often the most elegant architecture.

SharePoint
      ↓
Blob Hot
      ↓ 30 days
Blob Cool
      ↓ 90 days
Blob Cold
      ↓ 180 days
Blob Archive

Lifecycle policies can help move content between storage tiers as it ages. The value is that content naturally becomes cheaper as it becomes less active, assuming retrieval expectations are documented and the archive design is understood by the business.

Advantages:

• Highly automated
• Low operational effort after implementation
• Strong long-term economics
• Scalable archive pattern

Other practical methods to consider

The eight options above cover the major patterns, but a few additional approaches may be useful depending on the environment.

Staging library approach

Create a dedicated SharePoint archive staging library where site owners move content after approval. Automation can then process only the content in that library instead of scanning the entire tenant.

Site closure workflow

For project-based organizations, archive movement can be built into a project closure process. When a project closes, the owner confirms what remains active, what is archived, and what can be removed.

Metadata-driven archive process

If libraries already use metadata, an archive process can be based on fields such as status, project phase, document type, owner, or last review date.

Report-first strategy

Before moving data, produce reports that show site size, library size, version history exposure, last activity, and ownership. This prevents the archive process from becoming a blind bulk move.

Governance still matters

One of the biggest mistakes organizations make is focusing exclusively on storage.

Moving data does not solve governance. You still need:

• Content owners
• Retention decisions
• Access reviews
• Backup strategy
• Recovery procedures
• Archive retrieval processes

A poorly governed archive can become just as expensive and difficult to manage as an oversized SharePoint tenant.

My practical recommendation

When I evaluate storage issues, I rarely start by looking for ways to move everything.

Instead, I work through a progression:

1. Identify growth drivers.
2. Eliminate obvious waste.
3. Review version history settings.
4. Classify active versus inactive content.
5. Keep collaborative content in SharePoint.
6. Move file-share workloads to Azure Files.
7. Move preservation and archive content to Blob Storage.
8. Use lifecycle policies wherever possible.
9. Buy additional SharePoint storage only after cleanup and classification are complete.

The goal is not simply reducing storage cost. The goal is ensuring every piece of data is stored in the platform that provides the best balance of collaboration, governance, accessibility, and cost.

Sources and references

• Microsoft Learn - Add more OneDrive and SharePoint storage to your Microsoft 365 subscription.
• Microsoft Learn - Plan for SharePoint storage.
• Microsoft Learn - Azure Files documentation.
• Microsoft Learn - Introduction to Azure Files.
• Microsoft Learn - Access tiers for blob data (Hot, Cool, Cold, and Archive).
• Microsoft Learn - Azure Blob Storage lifecycle management overview.
• Microsoft Learn - Configure a lifecycle management policy.
• Microsoft Learn - PnP PowerShell overview.
• Microsoft Learn - Azure Data Factory documentation.
• Microsoft Learn - Copy data from SharePoint Online List (Azure Data Factory) — list vs. file support.
• Microsoft Learn - SharePoint connector reference (file-size limits).