Private bucket origin · Azure Blob Storage
Connect a private Azure Blob Storage container as your image CDN origin. Edge nodes sign each fetch with Shared Key authentication and serve AVIF or WebP.
For Azure Blob Storage, edge nodes fetch from https://<account>.blob.core.windows.net/<container>/ and sign every GET request with Azure's Shared Key scheme (HMAC-SHA256 over the canonicalised headers and resource, including conditional headers on revalidation). The container's public access level can stay set to Private.
Signing: Azure Storage Shared Key (HMAC-SHA256) with x-ms-version: 2021-08-06, signing If-None-Match and If-Modified-Since on cache revalidation.
| Field | What to give |
|---|---|
| Container | The Blob container name, such as my-images. |
| Storage account | The 3 to 24 character lowercase storage account name. |
| Folder (optional) | A virtual directory prefix inside the container, such as images/originals. |
| Storage account key | One of the storage account's base64 access keys, from Security + networking → Access keys. |
The secret is sealed at rest with the Data Protection key ring and never shown back in the console. Rotating credentials means entering a new key on the bucket row; edge nodes pick it up within a minute.
An account can configure up to 10 private buckets and point the account origin or individual custom hostnames at them.
Other private bucket origins: Amazon S3 & S3-compatible , Cloudflare R2 , Google Cloud Storage .