BlobBridge Documentation

Quick start

BlobBridge is a SharePoint SPFx web part that surfaces customer-owned Azure Blob Storage containers inside SharePoint using a document-library-style interface.

1. Upload BlobBridge.sppkg to the SharePoint App Catalog and deploy it.
2. Add the BlobBridge web part to a modern SharePoint page.
3. Upload BlobBridge.lic to a SharePoint library that viewers can read.
4. Configure the web part with Storage URL, Container, SAS token and licence folder path.
5. Publish the page and test browsing, downloading and any enabled write actions.

New installation

1. Prepare Azure Blob Storage

• Create or choose the storage account and blob container.
• Keep files in the customer's Azure Blob Storage account. BlobBridge does not host customer files.
• Configure CORS before testing from SharePoint.

2. Generate a SAS token

BlobBridge can use any valid SAS token that grants the permissions required for the intended actions. Read/List is enough for read-only archive access. Add Create/Write for uploads and overwrite scenarios. Add Delete only where deletion is required.

3. Deploy the SharePoint package

Upload BlobBridge.sppkg to the tenant or site collection App Catalog and approve deployment. Add the BlobBridge web part to a modern SharePoint page.

4. Configure and publish

Open the web part properties, enter the storage and licence settings, then publish the page. SharePoint page permissions and audience targeting control who can see the page or web part. Actual blob access capability is governed by the configured SAS token permissions.

Update BlobBridge

Existing customers update by uploading the new BlobBridge .sppkg package over the existing BlobBridge package in the SharePoint App Catalog.

• Existing web part instances should normally update automatically.
• If a site does not pick up the update, go to Site contents, open the BlobBridge app entry and choose Update.
• No file migration is required. Files remain in Azure Blob Storage.

Configuration options

SAS permissions and actions

Separate groups can use separate SharePoint pages, page permissions, audience targeting or separate BlobBridge web part instances. SharePoint controls who can see the page or web part. The configured SAS token controls what actions are possible against the Azure Blob container.

CORS guidance

Azure Storage CORS must allow requests from the SharePoint tenant domain where BlobBridge is used, such as https://yourtenant.sharepoint.com. Required methods depend on enabled actions, such as listing/downloading, uploading and deletion.

• For testing, some teams temporarily use broader origins or headers, then narrow them before production.
• For production, restrict allowed origins to the SharePoint domains where BlobBridge pages are hosted.
• If browsing works but upload or delete fails, confirm the CORS methods match the actions you enabled.

SAS renewal and rotation

BlobBridge uses the SAS token configured for each web part instance. If the token expires, the web part configuration needs to be updated with a new valid SAS token.

SAS token rotation can be fully automated by your own scripting or deployment process. The automation generates the new token and updates the BlobBridge web part configuration in SharePoint, so users continue accessing the same SharePoint page while the configured token is refreshed behind the scenes.

The rotation process can use tooling such as PnP PowerShell, Microsoft Graph, SharePoint scripting, Azure CLI, Azure Automation, CI/CD or another controlled deployment process. If automation is not in place, an administrator can also update the token manually by editing the SharePoint page, updating the BlobBridge web part properties and publishing the page. BlobBridge does not need a custom token service for this model to work.

Trial setup

The trial uses the current BlobBridge package. It can list and display files so you can validate setup. Write actions are blocked in the trial.

1. Download BlobBridge.Trial.sppkg from the trial page.
2. Upload it to the SharePoint App Catalog and deploy it.
3. Add the BlobBridge Trial web part to a modern page.
4. Configure Storage URL, Container and a read/list SAS token.

FAQ

Does BlobBridge replace SharePoint document libraries?

No. BlobBridge is not a full SharePoint document library replacement. It is designed to provide SharePoint-based access to blob-stored files where cost, scale or archive access makes SharePoint storage less suitable.

Does BlobBridge store customer files?

No. Files remain in the customer's Azure Blob Storage account. BlobBridge does not store or host customer files.

Do users need Azure portal access?

No. Users access blob-stored files from SharePoint. Their available actions are governed by the configured SAS token permissions.

Do I need one licence per user or site?

No. One BlobBridge licence covers one Microsoft 365 tenant, with unlimited users and unlimited SharePoint sites.

Can users upload SharePoint files into BlobBridge?

Yes. BlobBridge supports SharePoint file picker upload, allowing users to select files from SharePoint and upload them into Azure Blob Storage when the configured SAS token permits upload.

Can files open in the browser instead of downloading?

BlobBridge includes configuration options for file opening and download behaviour, using default browser behaviour or Prefer download.

Can BlobBridge handle large containers?

BlobBridge includes paged loading with Load more for larger folders. Actual performance still depends on container structure, browser conditions, network conditions and Azure Storage responses.

Troubleshooting