Azure Storage

Filestack can also be configured to store files directly into your Microsoft Azure account. This storage option requires a custom plan.

To begin configuring storage to your own Azure application you will need admin access to Azure account and to your Filestack Developer Portal

Azure Storage Configuration

To start storing your uploads to Azure:

1. Log into the Azure Dashboard.

2. Click on the Green Plus Sign in the side menu and then select Storage and then Storage Account in the panels that open. Enter the details requested for the new storage account and click create.

Screenshot showing the Azure developers home screen

Screenshot showing the Azure developers home screen

3. Use the settings shown here:

Screenshot showing the Azure developers storage settings

4. Click containers and then click the plus sign to make a new container. The Access Type should be Private

Screenshot showing the Azure developers storage settings

5. Once you click create you will be brought back to the containers section where your new container will be listed. Now click on Access Keys in the side panel above containers. Copy the Storage Account Name and Key 1.

Screenshot showing the Azure access settings

4. Go to the Filestack Developer Portal and click on Azure. You need to enter the Storage Account Name and Key 1 from the Access Keys section. You also need the name of the container you created. Enter them all in the developer portal and save each field. Click the Test Azure Settings button to confirm successful configuration.

Screenshot showing the Azure section of the Filestack portal

Storing to Azure Blob Storage using the Javascript API

You can store your files to Storage with the client.pick Javascript API method.

  storeTo: {
    location: 'azure',
    path: '/myfiles/1234.png',
}).then(result => {

Azure Storage Options for Javascript API

storeTo Object

storeTo: { parameter: value }

Accepts an optional dictionary of key-value pairs that specify how the picker should store files once they are selected for upload.

Location String

storeTo: { location: 'azure' }

Where to store the file. The default is s3. Other options are 'azure', 'dropbox', 'rackspace' and 'gcs'. You must have configured your storage in the developer portal to enable this feature.

Note: Azure, Dropbox and Google Cloud are only available on custom plans.

Path String

storeTo: { path: '/myfiles/1234.png' }

The path to store the file at within the specified file store. For S3, this is the key where the file will be stored at. By default, Filestack stores the file at the root at a unique id, followed by an underscore, followed by the filename, for example '3AB239102DB_myphoto.png'.

If the provided path ends in a '/', it will be treated as a folder, so if the provided path is 'myfiles/' and the uploaded file is named 'myphoto.png', the file will be stored at 'myfiles/909DFAC9CB12_myphoto.png', for example.

Important: If the maxFiles parameter is greater than one, be sure to only use paths that end in '/' or else all uploaded files will be written to the same object in your bucket. In other words, the files will overwrite each other.

Container String

storeTo: { container: 'user-photos' }

The bucket or container in the specified file store where the file should end up. This is especially useful if you have different containers for testing and production and you want to use them both on the same Filestack app. If this parameter is omitted, the file is stored in the default container specified in your developer portal.