Connect Azure Blob Storage

quickS3 connects to Azure with a storage account name and an account key. Azure calls buckets “containers”, and quickS3 does the same for Azure connections.

An account key gives full control of the whole storage account. quickS3 doesn’t support Microsoft Entra ID or SAS tokens yet, so the safest setup is a storage account used only for the files you share through quickS3.

1. Get the account name and key

In the Azure portal, open your storage account, then Security + networking → Access keys. Copy the Storage account name and one of the two Key values.

2. Add the connection

1. In quickS3, open Connections, select New connection, and pick Azure Blob Storage.
2. Enter a Name.
3. Enter the Storage account name. quickS3 works out the endpoint from it.
4. Paste the Account key.
5. To show only some containers, type their names into Container scopes, separated by commas.
6. Keep CORS updates on and select Connect provider.

Then select Test connection. You want Connection verified with “CORS allows direct uploads”.

If uploads are blocked by CORS

Azure sets CORS for the whole storage account, not per container. To add the rule by hand, open the storage account, go to Settings → Resource sharing (CORS), select the Blob service tab, and add a row:

Field	Value
Allowed origins	https://quicks3.com
Allowed methods	GET, HEAD, PUT, OPTIONS
Allowed headers	content-type,x-ms-blob-type
Exposed headers	ETag
Max age	3600

Keep any rows already there, save, and run Test connection again.

Good to know

• File size. Large uploads to Azure go up in one piece, so each file can be at most 5 GiB. Other providers split big files into parts and go well beyond that.
• Containers. Owners can create private containers from Overview with Create bucket.
• Rotating the key. Azure gives you two keys so you can swap without downtime. Paste the second key into the connection, test it, then regenerate the first one in the portal.