Skip to content

Storage

The Storage App lets you define storage endpoints other than Webfuse’s default storage. It is useful when data is supposed to be stored in certain locations.

The following storage providers are supported:

  • S3-compatible storage — AWS S3, Cloudflare R2, Supabase Storage and MinIO.
  • Azure Blob Storage — Microsoft Azure Blob Storage.

Enable the Storage App in the Session Editor.

Azure Blob Storage is connected using OAuth 2.0 with a service principal (Microsoft Entra ID app registration). Provide the following details:

  • Account name — the storage account name.
  • Container name — the blob container to use.
  • Tenant ID — the directory (tenant) ID of the app registration.
  • Client ID — the application (client) ID of the app registration.
  • Client secret — a client secret of the app registration.

The service principal must be granted the Storage Blob Data Contributor role on the storage account (or container). This role is required both for reading and writing blobs and for issuing the temporary download links Webfuse hands out for recordings, audit logs and uploaded files (it grants the user delegation key used to sign them). A service principal that can authenticate but lacks this role is rejected when the connection is saved.

Using a service principal means you do not need to enable account key access (“Allow storage account key access”) on the storage account.