Azure Blob Storage to Google BigQuery Integration
AI-first ETL from Azure Blob Storage into Google BigQuery. Governed entities, incremental sync, typed landing tables.
How Datrise loads Azure Blob Storage into Google BigQuery
Datrise syncs Azure Blob Storage's containers, blobs, blob metadata, snapshots, access tiers, and blob versions into Google BigQuery as a partitioned table per source entity. Flexible or custom fields land in JSON or nested/repeated (STRUCT) columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP.
Sync is incremental: Datrise uses appends to a staging table, then MERGE on stable id into the partitioned target, so re-runs update only what changed. Partition by ingestion or event date and cluster by entity id to keep scanned bytes low. BigQuery bills by bytes scanned, so Datrise partitions and clusters every table to keep query costs predictable.
Ideal for Google-stack analytics and ML on serverless infrastructure.
Endpoints
Azure Blob Storage: Object storage for blobs and data lake files on Azure.
Google BigQuery: Serverless analytics warehouse on GCP.
How Azure Blob Storage entities map to Google BigQuery
| Azure Blob Storage entity | Google BigQuery object | Notes |
|---|---|---|
| containers | azureblobstorage_containers | id PK · custom fields → JSON or nested/repeated (STRUCT) columns |
| 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 Google BigQuery?
Flexible values are stored as JSON or nested/repeated (STRUCT) columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Google BigQuery types.
How does the Azure Blob Storage to Google BigQuery sync stay up to date?
It runs incrementally — Datrise uses appends to a staging table, then MERGE on stable id into the partitioned target.
Related pipelines
More destinations for Azure Blob Storage
- Azure Blob Storage → Amazon Redshift
- Azure Blob Storage → Databricks SQL Warehouse
- Azure Blob Storage → ClickHouse
- Azure Blob Storage → DuckDB
- Azure Blob Storage → Amazon Athena
- Azure Blob Storage → Amazon S3 Data Lake
- Azure Blob Storage → Azure Data Lake Storage
- Azure Blob Storage → Azure Synapse
- Azure Blob Storage → Spreadsheets
- Azure Blob Storage → Airtable
- Azure Blob Storage → CSV Files
- Azure Blob Storage → MongoDB
More sources for Google BigQuery
- Babelforce → Google BigQuery
- BigCommerce → Google BigQuery
- Google BigQuery → Google BigQuery
- Branch → Google BigQuery
- Braze → Google BigQuery
- Bronto → Google BigQuery
- CallRail → Google BigQuery
- Campaign Monitor → Google BigQuery
- Cart → Google BigQuery
- ChartMogul → Google BigQuery
- CircleCI → Google BigQuery
- CleverTap → Google BigQuery
Early access
Connect Azure Blob Storage to Google BigQuery 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.