BlobBridge v2 improves day-to-day use of Azure Blob Storage from inside SharePoint, with better upload handling, improved file and folder compatibility, clearer diagnostics and new configuration options.
What's new in v2
- Better handling of special characters in file and folder names, including ampersands.
- Improved upload flow.
- Local upload and drag-and-drop upload remain supported.
- SharePoint file picker upload support, allowing users to select files from SharePoint and upload them into Azure Blob Storage.
- Optional overwrite handling during upload.
- Better empty-folder and error diagnostics.
- Sorting and filtering improvements.
- Pagination and performance tightening.
- Configuration options for file opening and download behaviour, including trying to open supported files in-browser versus forcing downloads.
- Version display and clearer version awareness.
- General stability and usability improvements from real customer testing.
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.