Azure Blob Storage support in ezS3

ezS3 now supports Azure Blob Storage as a first-class provider. You get the same experience as with S3: role-based access, short-term audit logging, browser uploads and downloads, and a single place to manage who can see and change your data. No S3 compatibility layer required — we use Azure’s native APIs and terminology.

Why Azure Blob in ezS3?

Many teams already use Azure for apps and data. Adding Blob Storage to ezS3 means:

• One place for access control — Same roles, permissions, and audit trail whether the backend is S3, R2, or Azure Blob
• Native Azure — Containers and blobs, storage account and account key; no need to pretend it’s S3
• Same security model — Credentials encrypted at rest, scoped access, and short-lived signed URLs for downloads and uploads

What you can do

With an Azure Blob connection in ezS3 you can:

• Browse containers and blobs by prefix (with optional container scoping)
• Download files via short-lived signed URLs
• Upload files (including larger uploads) with the same progress and cancellation support as S3
• Delete blobs when your role has write permission
• Audit — All access is logged for your organisation’s audit trail

Permissions are allow-only and role-based: you define which containers (and optional prefixes) each role can read or write, and ezS3 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 safe — you won’t need to paste it again after saving in ezS3.
3. In ezS3, go to Storage Providers and click Add Provider.
4. Choose Azure Blob Storage.
5. Enter:
   • Storage account — Your Azure storage account name (e.g. mystorageaccount).
   • Account key — The Base64 account key from the Azure Portal.
   • Container scopes (optional) — Leave blank to let ezS3 list all containers the key can access. If the key can’t list containers, enter a comma-separated list of container names (e.g. media, backups).
6. Leave Allow ezS3 to update bucket CORS settings (recommended) on so ezS3 can add the ezs3.net origin to your container’s CORS rules for browser uploads.
7. Save. ezS3 will validate the connection and then you can assign containers to roles and start browsing.

Same security and features

Azure Blob in ezS3 uses the same patterns as our S3 providers:

• Encrypted credentials — Stored encrypted at rest in your organisation; keys never leave our secure environment.
• Scoped access — You can limit a connection to specific containers (and optionally prefixes) so roles only see what they need.
• Short-lived URLs — Downloads and uploads use time-limited Azure SAS URLs generated on demand.
• Audit log — Actions (list, download, upload, delete) are recorded for short-term auditing.

If you already use ezS3 with AWS S3, Cloudflare R2, or another provider, adding Azure Blob is the same workflow: add the provider, set up roles and permissions, and your team gets a consistent way to work with blobs and buckets from one place.

---

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