Quick‑start

Already comfortable with SharePoint App Catalogs and the Azure portal? These five steps usually take less than five minutes:

In the Azure portal open Storage accounts → select the account prepared for BlobBridge.
Choose Storage browser → Blob containers and open the container you plan to publish.
Select the three dots beside the container name and choose Generate SAS.
Pick User delegation key, tick Read and List, then add Write, Create and Delete if BlobBridge will handle uploads or clean-up.
Set start and expiry times, enforce HTTPS-only access, and scope the SAS to the minimum paths you need.
Click Generate and copy the query string starting with ?sv= into your secrets vault so you can paste it into the web-part properties.

You're done. The document library view now points directly at your blob container.

Full installation guide

1. Get the files

After checkout you receive an e‑mail with:

BlobBridge.sppkg – the SharePoint package.
BlobBridge.lic – tenant‑locked licence file.

Deployment pre-checks

Storage account configuration: Azure portal → Storage account → Configuration → confirm Storage account key access is Enabled.
Role assignment: Azure portal → Storage account → Access Control (IAM) → ensure the identity creating SAS tokens holds the Storage Blob Data Owner role.
Container readiness: Storage browser → Blob containers → create or select the container, then follow the SAS steps below to apply least-privilege access.

2. Upload to App Catalog

Navigate to https://<tenant>.sharepoint.com/sites/apps (or your chosen App Catalog), choose Upload and select BlobBridge.sppkg. Confirm the Deploy dialog.

3. Add web-part to a page

Edit a modern page → click + Add → search "BlobBridge" → select. Publish the page.

4. Upload licence file

The web‑part will look for BlobBridge.lic at runtime. Drop it into any library that all viewers can read (Site Assets works well). Note the folder path – you’ll reference it in properties.

Configure CORS

Allow SharePoint-hosted pages to call your storage account by setting Cross-Origin Resource Sharing (CORS) rules that match your tenant.

Recommended CORS policy

Storage account → Resource sharing (CORS): add https://yourtenant.sharepoint.com (or * for testing) to Allowed origins.
Select the HTTP verbs BlobBridge requires under Allowed methods (typically GET, POST, PUT, DELETE).
Set Allowed headers (use * for all) and optionally specify Exposed headers if your compliance team needs visibility.
Leave Max age at 3600 seconds unless your policy mandates a different cache duration.

Generate a SAS token

For additional security context, read the Security guide.

In the Azure portal open Storage accounts → select the account prepared for BlobBridge.
Choose Storage browser → Blob containers and open the container you plan to publish.
Select the three dots beside the container name and choose Generate SAS.
Pick User delegation key, tick Read and List, then add Write, Create and Delete if BlobBridge will handle uploads or clean-up.
Set start and expiry times, enforce HTTPS-only access, and scope the SAS to the minimum paths you need.
Click Generate and copy the query string starting with ?sv= into your secrets vault so you can paste it into the web-part properties.

Pre-checks

Access Control (IAM): the admin generating the token must hold the Storage Blob Data Owner role on the storage account.
Storage account → Configuration: confirm Storage account key access stays Enabled; you cannot generate SAS tokens when it is disabled.

Configuration options

Property	Description	Example
Storage URL	Base URL of your storage account.	`https://mystore.blob.core.windows.net`
Container	Name of the blob container (case‑sensitive).	`documents`
SAS token	Shared Access Signature – grants scoped access.	`?sv=2024-06-...`
Licence folder path	Full URL to the licence file folder.	`https://<tenant>.sharepoint.com/SiteAssets/Licences`

Create containers and organise access

In the Azure portal open Storage browser → Blob containers and create one container per SharePoint audience (for example media-library, engineering-drop).
Apply naming conventions and default access tiers before you generate any SAS tokens.
Document which containers map to which SharePoint pages so rotations and audits are straightforward.

Frequently asked questions

Does BlobBridge cache blobs inside SharePoint?

No. The web‑part streams files directly from Azure Blob Storage to the browser. Nothing is stored in SharePoint other than the web‑part and licence file.

Can I use multiple containers?

Add multiple instances of the web‑part to the same page – each can point to a different container or even a different storage account.

What happens when the SAS token expires?

Users will receive a “Forbidden” message. Generate a new SAS and paste it into web‑part properties; the page works instantly with no redeploy.

Troubleshooting

Check these common issues before raising a support ticket.

Symptom	Likely cause	Fix
“Licence not found” banner	Licence folder path incorrect or file name mismatch.	Confirm path in properties and ensure file is BlobBridge.lic.
Upload stalls at 100 %	Block list committed but container lacks Create permission.	Regenerate SAS with Create & Write scopes.
Breadcrumb shows wrong folder	SAS token missing List capability.	Include List when generating SAS.
HTTP 403 on every request	Token expired or clock skew > 15 minutes.	Regenerate token and sync server clocks.
Large file downloads are slow	Azure egress distance or SharePoint throttling.	Place storage account in same region as majority of users and enable CDN if necessary.

Still stuck? E‑mail [email protected] with your tenant ID, storage account region and detailed steps to reproduce.

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.”