Azure Blob Storage to Domo Integration

How Datrise loads Azure Blob Storage into Domo

Datrise syncs Azure Blob Storage's containers, blobs, blob metadata, snapshots, access tiers, and blob versions into Domo as datasets in Domo's cloud store via connector. Flexible or custom fields land in flattened columns for Magic ETL, and timestamps such as created, updated, and status changes are typed as date/time columns.

Sync is incremental: Datrise uses partitioned dataset updates rather than full replaces, so re-runs update only what changed. Domo dataset partitions keyed on load date. Domo stores its own copy of data, so Datrise sends incremental partitions to avoid re-uploading whole datasets.

Ideal for all-in-one cloud BI with built-in ETL.

Endpoints

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

Domo: Cloud BI platform combining data integration and executive dashboards.

How Azure Blob Storage entities map to Domo

Azure Blob Storage entity	Domo object	Notes
containers	`azureblobstorage_containers`	id PK · custom fields → flattened columns for Magic ETL
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 Domo?

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

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

It runs incrementally — Datrise uses partitioned dataset updates rather than full replaces.

Related pipelines

Early access

Connect Azure Blob Storage to Domo 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.