- Source
- Warehouses and Lakes
- Generally available
Move Azure Blob Storage data anywhere it matters.
Move Azure Blob Storage data into your warehouse, lake or AI app.
Source
Azure Blob Storage

Snowflake
BigQuery
Postgres
Databricks
Claude
- Destinations
- 50+
- Certified support
- 0.8.39
Overview
What is the Airbyte Azure Blob Storage connector?
The Airbyte Azure Blob Storage connector extracts data from Azure Blob Storage and loads it into 50+ destinations such as Snowflake, BigQuery, Databricks or Postgres, with full refresh and incremental sync. It publishes tables and events you can select per connection.
- 01
Sync to your warehouse
Land Azure Blob Storage data in 50+ destinations on a schedule you control.
- 02
Incremental syncs
Pull only the records that changed since the last run instead of reloading everything.
- 03
File transfer
Move files through the pipeline as-is, without parsing them into records first.
- 04
One authorization
Authenticate Azure Blob Storage once and Airbyte keeps every scheduled sync running on it.
Setup
Live in nine steps
First, navigate to the Airbyte website and create an account.
Once you have logged in, click on the "Sources" tab on the left-hand side of the screen.
Scroll down until you find the "Azure Blob Storage" connector and click on it.
Click on the "Create Connection" button.
Enter a name for your connection and fill in the required fields, such as your Azure Blob Storage account name and access key.
Test the connection to ensure that it is working properly.
Once the connection has been successfully tested, click on the "Save & Sync" button to save your connection and begin syncing data.
You can then configure your sync settings, such as the frequency of syncing and which data to include.
Once you have configured your sync settings, click on the "Save & Sync" button again to start syncing your data from Azure Blob Storage to Airbyte.
Configuration fields
| Field | Type | Description |
|---|---|---|
| azure_blob_storage_account_name* | string | The account's name of the Azure Blob Storage. |
| azure_blob_storage_container_name* | string | The name of the Azure blob storage container. |
| credentials* | object | Credentials for connecting to the Azure Blob Storage |
| streams* | array | Each instance of this configuration defines a stream. Use this to define which files belong in the stream, their format, and how they should be parsed and validated. When sending data to warehouse destination such as Snowflake or BigQuery, each stream is a separate table. |
| azure_blob_storage_endpoint | string | This is Azure Blob Storage endpoint domain name. Leave default value (or leave it empty if run container from command line) to use Microsoft native from example. |
| delivery_method | object | Not documented. |
| start_date | string | UTC date and time in the format 2017-01-25T00:00:00.000000Z. Any file modified before this date will not be replicated. |
Hybrid deployment
Sovereign by architecture, not by policy.
The data plane runs in your environment. Records, credentials and keys stay with you; the control plane only receives configuration and job metadata.
- Cloud
- OSS
- Hybrid
Your environment
Airbyte control plane
FAQ
Azure Blob Storage connector questions
What data can I sync from Azure Blob Storage with Airbyte?
The Azure Blob Storage connector syncs the tables and events published in Airbyte docs.
Does the Azure Blob Storage connector support incremental sync?
Yes. The Azure Blob Storage connector supports incremental sync on selected streams, and full refresh on every stream.
Where can I run the Azure Blob Storage connector?
Run the Azure Blob Storage connector on Cloud, OSS, Hybrid. Hybrid deployments keep the data plane in your environment while the control plane orchestrates syncs.
Didn't find your answer? Talk to sales
Start syncing Azure Blob Storage in minutes.
Free 14-day trial. No credit card needed.