Azure Blob Storage to Amazon S3 Data Lake Integration
AI-first ETL from Azure Blob Storage into Amazon S3 Data Lake. Governed entities, incremental sync, typed landing tables.
How Datrise loads Azure Blob Storage into Amazon S3 Data Lake
Datrise syncs Azure Blob Storage's containers, blobs, blob metadata, snapshots, access tiers, and blob versions into Amazon S3 Data Lake as columnar Parquet objects partitioned per source entity. Flexible or custom fields land in nested struct/map fields in Parquet, and timestamps such as created, updated, and status changes are typed as ISO-8601 timestamp columns.
Sync is incremental: Datrise uses writes new date partitions and compacts small files on a schedule, so re-runs update only what changed. Hive-style path partitioning (entity/date) for engine-agnostic reads. A lake has no schema enforcement, so Datrise writes a schema manifest alongside the data to keep downstream engines consistent.
Ideal for an open, engine-neutral storage layer for Spark, Athena, Trino, or DuckDB.
Endpoints
Azure Blob Storage: Object storage for blobs and data lake files on Azure.
Amazon S3 Data Lake: Object storage landing zone for parquet and snapshots.
How Azure Blob Storage entities map to Amazon S3 Data Lake
| Azure Blob Storage entity | Amazon S3 Data Lake object | Notes |
|---|---|---|
| containers | azureblobstorage_containers | id PK · custom fields → nested struct/map fields in Parquet |
| 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 Amazon S3 Data Lake?
Flexible values are stored as nested struct/map fields in Parquet, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Amazon S3 Data Lake types.
How does the Azure Blob Storage to Amazon S3 Data Lake sync stay up to date?
It runs incrementally — Datrise uses writes new date partitions and compacts small files on a schedule.
Related pipelines
More destinations for Azure Blob Storage
- 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
- Azure Blob Storage → Supabase
- Azure Blob Storage → Neon
- Azure Blob Storage → PlanetScale
- Azure Blob Storage → Amazon DynamoDB
- Azure Blob Storage → Looker
- Azure Blob Storage → Looker Studio
More sources for Amazon S3 Data Lake
- Babelforce → Amazon S3 Data Lake
- BigCommerce → Amazon S3 Data Lake
- Google BigQuery → Amazon S3 Data Lake
- Branch → Amazon S3 Data Lake
- Braze → Amazon S3 Data Lake
- Bronto → Amazon S3 Data Lake
- CallRail → Amazon S3 Data Lake
- Campaign Monitor → Amazon S3 Data Lake
- Cart → Amazon S3 Data Lake
- ChartMogul → Amazon S3 Data Lake
- CircleCI → Amazon S3 Data Lake
- CleverTap → Amazon S3 Data Lake
Early access
Connect Azure Blob Storage to Amazon S3 Data Lake 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.