Azure Blob Storage Connector

Azure Blob Storage is a cloud solution for storing unstructured data, like large binary or text files.
It's often used to store blob data for web applications that don't store nicely in a relational database.

This component allows you to list, create and delete Azure containers, and create and modify blobs (files) within those Azure containers.

Connections

Connection String

Authenticates requests to Azure Blob Storage with a connection string.

Azure Blob Storage supports authentication using a Shared Access Signature (SAS) connection string. This method grants limited access to Azure Storage resources with fine-grained control over permissions and expiration.

A connection string containing a SAS token provides temporary, restricted access and is useful when full account key access is not required.

Prerequisites

• An active Azure account
• An existing Azure Storage Account
• Understanding of required permissions for the integration's operations

Setup Steps

To generate a SAS connection string:

1. Sign in to the Azure Portal
2. Navigate to Storage accounts from the main menu
3. Select the storage account to connect to
4. In the left sidebar, under Security + networking, select Shared access signature
5. Configure the SAS token settings:
   • Allowed services: Select Blob (at minimum)
   • Allowed resource types: Select the appropriate types (Container, Object, etc.)
   • Allowed permissions: Select the minimum required permissions for the integration
   • Start and expiry date/time: Set an appropriate expiration date
6. Click Generate SAS and connection string at the bottom
7. Copy the Connection string value (not the SAS token alone)

BlobEndpoint=https://account.blob.core.windows.net/;SharedAccessSignature=sv=...

Configure the Connection

• Enter the complete Connection string value into the connection configuration

For more information about SAS tokens, permissions, and security considerations, refer to the Azure SAS documentation.

Storage Shared Key

Authenticates requests to Azure Blob Storage with a Storage Shared Key of an account name and key.

Azure Blob Storage can use Shared Key authentication to authenticate requests. This authentication method uses a storage account name and account key pair.

For more information about storage account authentication, refer to the Azure Storage security guide.

Prerequisites

• An active Azure account
• An existing Azure Storage Account or permissions to create one
• Appropriate permissions to view and manage storage account access keys

Setup Steps

To obtain the storage account credentials:

1. Sign in to the Azure Portal
2. Navigate to Storage accounts from the main menu
3. Select the storage account to connect to
4. In the left sidebar, under Security + networking, select Access keys
5. Two keys are displayed: key1 and key2. Either key can be used for authentication
6. Copy the Storage account name (shown at the top of the page)
7. Click Show next to either key and copy the Key value

Configure the Connection

• Enter the Storage account name into the Account Name field
• Enter the copied Key value into the Account Key field

For additional information about managing storage account keys and security best practices, refer to the Azure documentation.

Actions

Append to Append Blob

Append blocks to an existing append blob

Create Append Blob

Create an empty append blob object (use "Append to Append Blob" to add blocks)

Create Container

Create a container

Create Page Blob

Create a page blob with a specific size (must be a multiple of 512 bytes)

Delete Blob

Delete a blob

Delete Container

Delete a container

Download Blob

Download a blob

Generate Shared Access Signature URL

Generate a pre-signed URL (Shared Access Signature or SAS) for a blob

List Blobs

Get a list of blobs in a container

List Containers

Get a list of containers available in the account

Resize Page Blob

Resize an existing page blob (must be a multiple of 512 bytes)

Upload Block Blob

Upload file data to a block blob object

Upload to Page Blob

Upload to an existing page blob (both data size and offset must be a multiple of 512)