Skip to main content

Azure Blob Storage

Azure Blob Storage datasources allow CloudQuant Data Liberator to read CSV, TSV, and other delimited files from Azure Blob containers. CloudQuant Data Liberator mounts the container via FUSE.
See Supported Data Formats for every file extension Liberator can ingest on Azure Blob, including formats added in 2.1 and 2.2.

Connection configuration

Required fields

Optional fields

The endpoint field is only needed for non-standard Azure environments such as Azure Government, Azure China, or local development with Azurite. For standard Azure public cloud, CloudQuant Data Liberator derives the endpoint from the account name.

Example connection

Storage account keys grant full access to the entire storage account. Rotate keys regularly and use environment variables or a secrets manager to inject them at deployment time.

Dataset configuration (data_args)

The data_args fields are identical to all file-based sources. See Local File for the full reference. The file_pattern is evaluated relative to the prefix configured on the connection.

Required data_args

Optional data_args

Complete example

Connection

Dataset

Azure setup requirements

Ensure the following before configuring your Azure Blob connection:
  1. Storage account exists and is accessible from the CloudQuant Data Liberator host
  2. Container is created within the storage account
  3. Access key is available (found under Storage Account > Access Keys in the Azure Portal)
  4. Network access is permitted — if the storage account uses firewall rules, add the CloudQuant Data Liberator host’s IP to the allowed list
For initial testing, use Azure Storage Explorer to verify your files are accessible before configuring the CloudQuant Data Liberator connection. This eliminates credential and network issues early.
See the Azure Blob Storage integration guide for additional setup details.