BlobBridge v2 improves day-to-day use of Azure Blob Storage from inside SharePoint, with better upload handling, folder-level search, improved file and folder compatibility, sorting, local-time modified dates and simpler file opening behaviour.
What's new in v2
- Improved support for special characters in file and folder paths.
- Search now works across the current folder and its subfolders.
- Searching from the container root searches the full container.
- Large folders now support paged loading with Load more.
- Improved folder rename and delete handling, including empty folders created through BlobBridge.
- Improved upload experience, including upload from computer or selecting a file from SharePoint.
- Optional overwrite handling when uploading files.
- Sorting by name, type, size, and modified date.
- Modified dates now show in local time.
- Improved empty-folder and error messages.
- Simplified file opening behaviour with default browser behaviour or Prefer download.
Update instructions
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.
Permission reminder
BlobBridge uses the SAS token configured for each web part instance. Read/List allows browsing and downloading. Create/Write allows upload and overwrite scenarios. Delete allows deletion.
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.
Known limitations
- BlobBridge is not a full SharePoint document library replacement.
- Blob-stored files do not become SharePoint documents.
- SharePoint metadata, version history, co-authoring, retention labels and Microsoft Search should not be assumed to apply automatically to blob-stored files.
- If a SAS token expires, the web part configuration must be updated with a new valid SAS token.