Azure Files vs Azure Blob vs SharePoint — what actually works

When you need SharePoint’s interface but Azure’s cost and scale, surfacing Azure storage is usually the right move.

Approaches

  1. Migrate to SharePoint: simple, but expensive at scale; file size/type limits and versioning costs.
  2. Sync (SharePoint <→ Azure): complex; duplication and consistency issues.
  3. Surface Azure in SharePoint (BlobBridge): zero duplication, keep Azure governance, SharePoint UX.

Step‑by‑step setup

  1. In Azure portal, generate a container SAS. Prefer User delegation key. Start with Read/List.
  2. Deploy BlobBridge.sppkg to your App Catalog and add the web part to a page.
  3. Paste Storage URL, Container, SAS and licence folder URL. Publish.
  4. Optionally enable uploads by adding Write/Create/Delete permissions to the SAS.

Security patterns

FAQ

Search indexing? SharePoint search won’t index Azure content; use Azure search if indexing is required.

Storage accounting? Files remain in Azure; SharePoint storage is unaffected.

Large files? Blob storage supports large objects; throughput depends on region and egress.


Ready to try it? Go to the landing page or buy a licence.

What customers say

“Went live same day. Users thought it was just SharePoint—exactly the goal.”
“Eliminated duplicate storage and shadow copies. Security signed off in one review.”
“From pilot to production in hours. Browsing large containers is snappy.”