Azure Blob Storage support in quickS3

quickS3 now supports Azure Blob Storage. You get the same experience as with S3: role-based access, short-term audit logging, browser uploads and downloads, and one place to manage who can see and change your data. There’s no S3 compatibility shim involved. We talk to Azure’s native APIs and use Azure’s own terms.

Why we added it

A lot of teams already run their apps and data on Azure, and they kept asking us to cover Blob Storage directly instead of routing everything through S3. Now that it’s in quickS3, your access control lives in one place: the same roles, permissions, and audit trail apply whether the backend is S3, R2, or Azure Blob. And it’s genuinely Azure underneath. You work with containers and blobs, a storage account, and an account key, rather than pretending any of it is S3. The security model doesn’t change either. Credentials stay encrypted at rest, access is scoped, and downloads and uploads run through short-lived signed URLs.

What you can do

Once you’ve connected an Azure Blob account, you can browse containers and blobs by prefix (with optional container scoping), download files through short-lived signed URLs, and upload files with the same progress and cancellation handling you already get with S3. Larger uploads work too. If your role has write permission, you can delete blobs, and every action lands in your organisation’s audit trail.

Permissions are allow-only and role-based. You decide which containers, and optionally which prefixes, each role can read or write, and quickS3 enforces it.

How to connect Azure Blob Storage

1. In the Azure Portal, open your storage account (or create one).
2. Under Security + networking → Access keys, copy the storage account name and one account key (key1 or key2). Keep the key somewhere safe; you won’t need to paste it again after saving in quickS3.
3. In quickS3, go to Storage Providers and click Add Provider.
4. Choose Azure Blob Storage.
5. Enter:
   • Storage account is your Azure storage account name (e.g. mystorageaccount).
   • Account key is the Base64 account key from the Azure Portal.
   • Container scopes (optional): leave this blank to let quickS3 list every container the key can reach. If the key can’t list containers, enter a comma-separated list of names (e.g. media, backups).
6. Leave Allow quickS3 to update bucket CORS settings (recommended) on so quickS3 can add the quicks3.com origin to your container’s CORS rules for browser uploads.
7. Save. quickS3 validates the connection, and then you can assign containers to roles and start browsing.

Same security, same workflow

Azure Blob follows the same patterns as our S3 providers. Credentials are stored encrypted at rest in your organisation and never leave our secure environment. You can limit a connection to specific containers, and optionally prefixes, so roles only see what they need. Downloads and uploads use time-limited Azure SAS URLs generated on demand, and list, download, upload, and delete actions all get recorded for short-term auditing.

If you’re already running quickS3 on AWS S3, Cloudflare R2, or another provider, none of this will feel new. Add the provider, set up roles and permissions, and your team has one consistent way to work with blobs and buckets.

---

Ready to try it? Sign up for quickS3 and add an Azure Blob Storage connection.

For maintained setup steps and current limits, use the Azure Blob Storage documentation.