Azure Storage Blob Data Lake Sink
Provided by: "Apache Software Foundation"
Support Level for this Kamelet is: "Stable"
Uploads each message as a file to a file system in Azure Data Lake Storage Gen2, named after the file header.
Use it to land data for analytics, such as exports, events or reports, in a data lake. For plain blob containers, use azure-storage-blob-sink.
Input: the body is the content of the file: text, bytes or a stream. A Map fails: turn it into JSON text first, for example with json-serialize-action. The optional file header (or ce-file) is the name of the file, such as sales-2026-05.csv. Without it, the file gets a generated unique name.
Output: the body afterwards is true.
Good to know: the file is written at the top of the file system, or in directoryName. By default it logs in as an app registration, with clientId, clientSecret and tenantId, so that app needs a role on the account that allows writing, such as Storage Blob Data Contributor. Headers that start with CamelAzureStorageDataLake are removed from the message first, so they cannot change what the Kamelet does. It can log in with an account key (accountKey) or a SAS token (sasSignature) instead.
Configuration Options
The following table summarizes the configuration options available for the azure-storage-datalake-sink Kamelet:
| Property | Name | Description | Type | Default | Example |
|---|---|---|---|---|---|
Account Name | Required The name of the storage account, an Azure Data Lake Storage Gen2 account (a storage account with hierarchical namespace), as shown in the Azure portal under Storage accounts. | string | mydatalake | ||
File System Name | Required The name of the file system (the container) in the account to write the files to. | string | raw-data | ||
Account Key | An access key of the storage account, from the Azure portal: the storage account, then Security + networking, then Access keys. Used when | string | |||
Client ID | The application (client) ID of an app registration (service principal) in Microsoft Entra ID that has access to the account, from the Overview page of the app registration in the Azure portal. Required when | string | |||
Client Secret | A client secret of the app registration, from the Azure portal: the app registration, then Certificates & secrets. Required when | string | |||
Credential Type | How to log in to the account. Enum values: * CLIENT_SECRET * SHARED_KEY_CREDENTIAL * AZURE_IDENTITY * AZURE_SAS * SERVICE_CLIENT_INSTANCE | string | CLIENT_SECRET | ||
Directory Name | The directory of the file system to write the files to, such as | string | exports/2026 | ||
SAS Token | A shared access signature (SAS) token that gives access to the account or the file system, such as | string | |||
Tenant ID | The directory (tenant) ID of the app registration, from its Overview page in the Azure portal. Required when | string |
Dependencies
At runtime, the azure-storage-datalake-sink Kamelet relies upon the presence of the following dependencies:
-
camel:azure-storage-datalake
-
camel:kamelet
Camel JBang usage
Prerequisites
-
You’ve installed JBang.
-
You have executed the following command:
jbang app install camel@apache/camel Supposing you have a file named route.yaml with this content:
- route:
from:
uri: "kamelet:timer-source"
parameters:
period: 10000
message: 'test'
steps:
- to:
uri: "kamelet:azure-storage-datalake-sink" You can now run it directly through the following command
camel run route.yaml Azure Storage Datalake Sink Kamelet Description
Authentication methods
In this Kamelet, you can use these Azure authentication methods:
-
Client secret:
CLIENT_SECRET(default) -
Azure SAS:
AZURE_SAS -
Azure Identity mechanism:
AZURE_IDENTITY -
Service client instance:
SERVICE_CLIENT_INSTANCE -
Shared key credentials:
SHARED_KEY_CREDENTIAL
The order of evaluation for AZURE_IDENTITY is the following:
-
Enviroment
-
Workload Identity
-
Managed Identity
-
Azure Developer CLI
-
IntelliJ
-
Azure CLI
-
Azure Powershell
For more information, see the Azure Identity documentation
Optional Headers
In the headers, you can set the file / ce-file property to specify the filename to upload. If you do not set it, the file gets a generated unique name.
Example with a Directory and an Account Key
- route:
from:
uri: "kamelet:timer-source"
parameters:
message: "id,amount"
period: 60000
steps:
- setHeader:
name: file
simple: "sales-$\{date:now:yyyyMMddHHmmss}.csv"
- to:
uri: "kamelet:azure-storage-datalake-sink"
parameters:
accountName: "mydatalake"
fileSystemName: "raw-data"
credentialType: "SHARED_KEY_CREDENTIAL"
accountKey: "the-account-key"
directoryName: "exports/2026" Each file is written to the exports/2026 directory of the raw-data file system, such as exports/2026/sales-20261118093000.csv. With credentialType AZURE_SAS, give a SAS token in sasSignature instead of accountKey. clientId, clientSecret and tenantId are needed only with CLIENT_SECRET, the default.