Advanced Analytica Advanced Analytica: IBOM
← All connectors
Azure Blob Storage logo

Destination connector

Azure Blob Storage

Send governed data into Azure Blob Storage with a clear, practical setup guide.

Version 1.1.11 certified generally available

Azure Blob Storage

Overview

Send your data to Azure Blob Storage with this destination.

Sync your data to Azure Blob Storage with the Airbyte Azure Blob Storage destination. Each stream is written to its own blob under the container as <stream_namespace>/<stream_name>/yyyy_mm_dd_<unix_epoch>_<part_number>.<file_extension>.

Network access

If you use Airbyte Cloud with IP-based access controls, add Airbyte’s IP addresses to your allowlist.

Supported sync modes

Sync modeSupported?
Full Refresh - OverwriteYes
Full Refresh - AppendYes
Full Refresh - Overwrite + DedupedNo
Incremental Sync - AppendYes
Incremental Sync - Append + DedupedNo

Configuration

ParameterTypeNotes
Azure Blob Storage Endpoint Domain NamestringThis is Azure Blob Storage endpoint domain name. Leave default value (or leave it empty if run container from command line) to use Microsoft native one.
Azure Blob Storage Container NamestringA name of the Azure Blob Storage container. If not exists - will be created automatically. If leave empty, then will be created automatically airbytecontainer+timestamp.
Azure Blob Storage Account NamestringThe account’s name of the Azure Blob Storage.
Azure Blob Storage Account KeystringAzure Blob Storage account key. If this is set, the Shared Access Signature, Azure Tenant ID, Azure Client ID, and Azure Client Secret fields must not be set. Example: abcdefghijklmnopqrstuvwxyz/0123456789+ABCDEFGHIJKLMNOPQRSTUVWXYZ/0123456789%++sampleKey==.
Shared Access SignaturestringAzure Blob Storage shared access signature (SAS). If this is set, the Azure Blob Storage Account Key, Azure Tenant ID, Azure Client ID, and Azure Client Secret fields must not be set. Example: sv=2025-01-01&ss=b&srt=co&sp=abcdefghijk&se=2026-01-31T07:00:00Z&st=2025-01-31T20:30:29Z&spr=https&sig=YWJjZGVmZ2hpamthYmNkZWZnaGlqa2FiY2RlZmdoaWp%3D.
Azure Tenant IDstringAzure Active Directory (Entra ID) tenant ID. Required for Entra ID authentication. If this is set, Azure Client ID and Azure Client Secret must also be set. Example: 12345678-1234-1234-1234-123456789012.
Azure Client IDstringAzure Active Directory (Entra ID) client ID. Required for Entra ID authentication. If this is set, Azure Tenant ID and Azure Client Secret must also be set. Example: 87654321-4321-4321-4321-210987654321.
Azure Client SecretstringAzure Active Directory (Entra ID) client secret. Required for Entra ID authentication. If this is set, Azure Tenant ID and Azure Client ID must also be set.
Azure Blob Storage Target Blob Size (MB)integerHow large each blob should be, in megabytes. Example: 500. After a blob exceeds this size, the connector will start writing to a new blob, and increment the part number.
FormatobjectFormat specific configuration. See below for details.

Output schema

CSV

The output contains your data and some metadata fields, as with most other Airbyte destination connectors. Select “root level flattening” to promote your data into additional columns. Select “no flattening” to keep your data as a JSON blob in the _airbyte_data column.

For example, start with this JSON object from a source:

{
  "user_id": 123,
  "name": {
    "first": "John",
    "last": "Doe"
  }
}

With no flattening, the output CSV is:

_airbyte_raw_id_airbyte_extracted_at_airbyte_generation_id_airbyte_meta_airbyte_data
26d73cde-7eb1-4e1e-b7db-a4c03b4cf206162213580500011{"changes":[], "sync_id": 10111 }{ "user_id": 123, name: { "first": "John", "last": "Doe" } }

With root level flattening, the output CSV is:

_airbyte_raw_id_airbyte_extracted_at_airbyte_generation_id_airbyte_metauser_idname.firstname.last
26d73cde-7eb1-4e1e-b7db-a4c03b4cf206162213580500011{"changes":[], "sync_id": 10111 }123JohnDoe

JSON Lines (JSONL)

JSON Lines is a text format with one JSON object per line. As with CSV, this connector writes your data with some metadata fields. Enable “root level flattening” to promote your data to the JSON object’s root. Use “no flattening” to keep your data inside the _airbyte_data object.

For example, start with these two JSON objects from a source:

{
  "user_id": 123,
  "name": {
    "first": "John",
    "last": "Doe"
  }
}
{
  "user_id": 456,
  "name": {
    "first": "Jane",
    "last": "Roe"
  }
}

With no flattening, the output JSONL is:

{ "_airbyte_raw_id": "26d73cde-7eb1-4e1e-b7db-a4c03b4cf206", "_airbyte_extracted_at": "1622135805000", "_airbyte_generation_id": "11", "_airbyte_meta": { "changes": [], "sync_id": 10111 }, "_airbyte_data": { "user_id": 123, "name": { "first": "John", "last": "Doe" } } }
{ "_airbyte_raw_id": "0a61de1b-9cdd-4455-a739-93572c9a5f20", "_airbyte_extracted_at": "1631948170000", "_airbyte_generation_id": "12", "_airbyte_meta": { "changes": [], "sync_id": 10112 }, "_airbyte_data": { "user_id": 456, "name": { "first": "Jane", "last": "Roe" } } }

With root level flattening, the output JSONL is:

{ "_airbyte_raw_id": "26d73cde-7eb1-4e1e-b7db-a4c03b4cf206", "_airbyte_extracted_at": "1622135805000", "_airbyte_generation_id": "11", "_airbyte_meta": { "changes": [], "sync_id": 10111 }, "user_id": 123, "name": { "first": "John", "last": "Doe" } }
{ "_airbyte_raw_id": "0a61de1b-9cdd-4455-a739-93572c9a5f20", "_airbyte_extracted_at": "1631948170000", "_airbyte_generation_id": "12", "_airbyte_meta": { "changes": [], "sync_id": 10112 }, "user_id": 456, "name": { "first": "Jane", "last": "Roe" } }

Get started

Requirements

  1. Create an AzureBlobStorage account.
  2. Check that it works under https://portal.azure.com/ -> “Storage browser”.

Setup guide

  • Enter your AzureBlobStorage information.
    • Azure Blob Storage Endpoint Domain Name
      • Keep the default value to use the Microsoft endpoint, or specify your own.
      • If you run the container from the command line, you can leave this empty.
    • Azure Blob Storage Container Name
      • If the container doesn’t exist, it will be created automatically.
      • If left empty, a container named airbytecontainer with a timestamp suffix will be created.
    • Azure Blob Storage Account Name
      • See this to create an account.
    • Authentication - you must use exactly one of these:
      • Shared Access Signature (recommended)
        • See this to create an SAS.
      • Azure Entra ID (Service Principal)
        • Provide the Azure Tenant ID, Azure Client ID and Azure Client Secret from an Azure service principal.
        • The service principal must have appropriate permissions.
        • See this to create a service principal.
      • Azure Blob Storage Account Key
        • Enter the key corresponding to the user above.
    • Format
      • Select the data format used to represent migrated data in the blob.
  • Make sure your user can access Azure from the machine running Airbyte.
    • Access depends on your network setup.
    • To verify Airbyte’s connection to your Azure blob storage container, use the check connection tool in the UI.

Namespace support

This destination supports namespaces. The namespace forms part of the output path structure.

Changelog

Expand to review
VersionDatePull RequestSubject
1.1.112026-10-2289649Upgrade to Bulk CDK 1.1.9: fix critical CVEs in Apache MINA (mina-core 2.0.31), MINA SSHD 2.20.0 and BouncyCastle 1.86; netty 4.1.139, Hadoop 3.4.3, Parquet 1.18.1, azure-identity 1.18.7
1.1.102026-10-0987614Upgrade to Bulk CDK 1.1.1.
1.1.92026-09-0184984Upgrade to Bulk CDK 1.0.25.
1.1.82026-08-1083810Upgrade CDK to 1.0.24
1.1.72026-05-1978243Upgrade CDK to 1.0.13
1.1.62026-01-2672355Fix sync failures for sources with empty schemas by upgrading CDK to 0.2.1
1.1.52026-01-2072301Upgrade CDK to 0.2.0
1.1.42025-11-0569127Upgrade to Bulk CDK 0.1.61.
1.1.32025-10-2167153Implement new proto schema implementation
1.1.22025-10-0667078Remove memory limit for sync jobs to improve performance and resource utilization.
1.1.12025-09-1066139Fix inconsistent field name casing and improve tooltip clarity. Field names now use consistent title casing and tooltips reference exact field names.
1.1.02025-09-0565933Add support for Azure Entra ID (Service Principal) authentication. You can now authenticate using Azure AD tenant ID, client ID, and client secret.
1.0.42025-08-0764556Promoting release candidate 1.0.4-rc.1 to a main version.
1.0.4-rc.12025-08-0559710Release Azure blob destination on latest CDK
1.0.32025-05-0759710CDK backpressure bugfix
1.0.22025-04-1457563Fix signature spec example
1.0.12025-04-0957541Fix metadata to actually certify.
1.0.02025-04-0356391Bring into compliance with modern connector standards; certify connector.
0.2.52025-03-2155906Upgrade to airbyte/java-connector-base:2.0.1 to be M4 compatible.
0.2.42025-01-1051507Use a non root base image
0.2.32024-12-1849910Use a base image: airbyte/java-connector-base:1.0.0
0.2.22024-06-12#38061File Extensions added for the output files
0.2.12023-09-13#30412Switch noisy logging to debug
0.2.02023-01-18#21467Support spilling of objects exceeding configured size threshold
0.1.62022-08-08#15318Support per-stream state
0.1.52022-06-16#13852Updated stacktrace format for any trace message errors
0.1.42022-05-1712820Improved ‘check’ operation performance
0.1.32022-02-1410256Add -XX:+ExitOnOutOfMemoryError JVM option
0.1.22022-01-20#9682Each data synchronization for each stream is written to a new blob to the folder with stream name.
0.1.12021-12-29#9190Added BufferedOutputStream wrapper to blob output stream to improve performance and fix issues with 50,000 block limit. Also disabled autoflush on PrintWriter.
0.1.02021-08-30#5332Initial release with JSONL and CSV output.
Advanced Analytica

Most businesses are sitting on information they can’t use at speed. The people who hold it are busy, and when they leave, the knowledge goes with them. The documents are static, and the processes around them weren’t designed for AI.

Advanced Analytica works with these businesses to turn that information into structured data assets. Once they're integrated, AI systems can govern it, and the business can use it. We bring in the strategy, the specification and the AI skills to rework how the business operates.

MOVE FAST. STAY SAFE.