Azure Blob adapter
Bidirectional integration with Azure Blob Storage. Listener reads blobs from a container; Caller writes them.
The Azure Blob adapter binds to a single container on a storage account and treats blobs in it as messages: each one becomes a bus message inbound, or each outbound message becomes a blob.
Blobs live in containers; containers live in storage accounts. The adapter is scoped to one container per binding. Blob name prefixes act like folder paths and are how you partition the contents of a busy container.
Two pickup strategies are supported. Poll lists the container at a configurable interval and picks up new blobs matching the prefix and pattern. Event-driven subscribes to the storage account's BlobCreated events through Event Grid — no polling, immediate pickup, but requires an Event Grid topic and a system topic subscription configured outside the adapter.
On successful publish, the blob is handled per the Post-Publish Action: Delete, Move to a different container or prefix, or Tag (apply a blob index tag like processed=true so the listener's prefix/tag query excludes it next time).
On a send port, the adapter writes the message body as a block blob into the configured container. Blob name and content type are templatable; content tier (Hot / Cool / Cold / Archive) is settable for storage-cost optimisation. Idempotent re-runs are supported via the If-None-Match precondition, which prevents overwriting an existing blob when needed.
The Azure Blob adapter pairs with an Azure Blob Authentication. Three credential shapes are supported: Storage account key, Shared Access Signature (SAS), and Managed Identity (preferred when the runtime has an Entra identity assigned Storage Blob Data Contributor / Reader). The Authentication object identifies the storage account; the adapter binds to a specific container under it.
Placeholder field set — verify against the running product. Beta details may change before GA.
Blob Prefix — optional; narrows the binding to a path-like subset of the container.
Blob Pattern — optional on Listener; glob-style match against the blob name suffix.
Pickup Strategy — required on Listener; Poll or Event-driven.
Poll Interval — required when Pickup Strategy is Poll.
Event Grid Topic — required when Pickup Strategy is Event-driven; the Event Grid system topic that fans out BlobCreated events.
Post-Publish Action — required on Listener; Delete, Move, or Tag.
Blob Name — required on Caller; templatable.
Content Type — optional on Caller; defaults to
application/octet-stream.Access Tier — optional on Caller; Hot, Cool, Cold, Archive.
Overwrite Policy — required on Caller; Fail if exists, Overwrite, If-None-Match.
Metadata — optional on Caller; key/value pairs templated against the message.
Authentication — required; picker filtered to Azure Blob Authentication objects in the same Application.
That is the Azure Blob adapter
Container-scoped reads and writes against Azure Blob Storage. Poll or Event-driven pickup; templated writes; managed identity available. Beta until GA. Back to Adapters.