Cyberduck Help / Howto / Windows Azure Storage

Connecting to Azure Cloud Storage

Hostname

Edit the hostname to connect to your account in the format <account>.blob.core.windows.net.

Credentials

Account and Key

You must obtain the login credentials (Account Name and Primary Access Key) from ​manage.windowsazure.com/. In the login prompt of Cyberduck upon connecting to Windows Azure you enter the Storage Account Name for the username and Primary Access Key for the password.

Shared access signatures (SAS)

Version 6.5.1 or later required

You can use a ​SAS when you want to provide access to resources in your storage account to any client not possessing your storage account's access keys.

• ​Download the Azure (Shared Access Signature Token) profile

Access Control (ACL)

You can edit ACLs in File → Info (⌘-I) → Permissions. To make objects in a container publicly accessible, choose Everyone → READ. Note that this applies to all files in a container.

Containers

To create a new container in your account, browse to the root and choose File → New Folder... (⌘-N).

Metadata

You can edit standard custom metadata. Choose File → Info → Metadata to edit custom headers.

Default metadata

Currently only possible using a hidden configuration option you can define default headers to be added for uploads. Multiple headers must be separated using a whitespace delimiter. Key and value of a header are seperated with =. For example if you want to add a HTTP header for Cache-Control and one named Creator you would set

defaults write ch.sudo.cyberduck azure.metadata.default "Cache-Control=public,max-age=86400 Creator=Cyberduck"

Shared Access Signature URLs

A private object stored in Azure Storage can be made publicly available for a limited time using a signed URL. The signed URL can be used by anyone to download the object, yet it includes a date and time after which the URL will no longer work. Copy the signed URL from Edit → Copy URL→ Signed URL.

Access Logs

Configure access logging for buckets in the Info panel.

Limitations

• Container and blob naming ​conventions.
• ​CDN configuration is currently only possible using the ​web interface.

Problems

One of the request inputs is out of range

Please follow the ​Naming and Referencing Containers, Blobs, and Metadata guidelines.