Azure Blob Storage to Redash Integration

How Datrise loads Azure Blob Storage into Redash

Datrise syncs Azure Blob Storage's containers, blobs, blob metadata, snapshots, access tiers, and blob versions into Redash as SQL tables Redash queries and visualizes. Flexible or custom fields land in flattened columns for query results, and timestamps such as created, updated, and status changes are typed as temporal columns.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for scheduled queries. Redash caches query results on a schedule, so Datrise keeps tables incrementally fresh so cached dashboards reflect reality.

Ideal for lightweight, query-driven dashboards.

Endpoints

Azure Blob Storage: Object storage for blobs and data lake files on Azure.

Redash: Open-source SQL client for queries, visualizations, and dashboards.

How Azure Blob Storage entities map to Redash

Azure Blob Storage entity	Redash object	Notes
containers	`azureblobstorage_containers`	id PK · custom fields → flattened columns for query results
blobs	`azureblobstorage_blobs`	id PK · linked to azureblobstorage_containers
blob metadata	`azureblobstorage_blob_metadata`	id PK · linked to azureblobstorage_containers
snapshots	`azureblobstorage_snapshots`	id PK · linked to azureblobstorage_containers

FAQ

How does Datrise handle Azure Blob Storage's custom fields in Redash?

Flexible values are stored as flattened columns for query results, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Redash types.

How does the Azure Blob Storage to Redash sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the connected tables.

Related pipelines

Early access

Connect Azure Blob Storage to Redash the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.