Azure Activities: Blob Storage
The Azure Activities Extension Library provides Azure Blob Upload and Azure Blob Download. See Azure Activities for installation and Azure Service Bus support.
Download Azure Activities 5.0.12 for Blob Upload and Blob Download.
Download Blob Content
- Install the Azure Activities MSI on the Integration Soup server and reopen the Workflow Designer.
- Add Azure Blob Download where the workflow needs the stored content.
- Set Connection String, Container Name and File Name. File Name is the exact, case-sensitive blob key, including prefixes and significant spaces; for example,
inbound/orders/order001.hl7. - Keep the default Binary response to preserve file bytes, or select a text response such as HL7, JSON or Text and set Text Encoding if needed.
- Bind the response into the next workflow step to transform or send the downloaded content.
Each invocation retrieves one named blob using the connection and path settings; an input message is optional. A connection string with a read-only SAS is sufficient. To retrieve files on a schedule, run a workflow with the appropriate trigger and supply the blob key for each download.
Maximum Download MB defaults to 8 MiB and accepts 1–8. Larger blobs fail before content is returned. Optional Version ID selects a stored version while preserving the exact blob key, including leading and trailing slashes. Expected ETag requires the specific ETag of the content you expect; wildcard * is rejected for both Download and Upload. Every download checks that the blob remains unchanged between its properties and content reads. Keys containing URI-normalized dot segments, such as a/../b, are rejected before a read or write.
An interrupted download can resume up to five times while retaining the selected version and ETag. A two-minute limit covers the entire download. In version 5, an earlier workflow deadline or cancellation also stops it. A cancelled or exhausted transfer fails without returning partial content.
Text responses use strict UTF-8 when Text Encoding is blank. Invalid text bytes fail; a UTF-8 byte-order mark is preserved as a text character. Binary and DICOM responses preserve the bytes. AzureBlobMetadataJson supplies name, size, ETag, content type, version and modification time; content type does not choose the text encoding.
Upload Workflow Content
- Run the MSI on the Integration Soup server.
- Restart the Integration Soup service if needed.
- Add Azure Blob Upload after the step that produces the content you want to upload.
- Open the activity message template, right click, and choose Insert Activity Message to bring in the text from the receiver or earlier activity you want to store in Azure.
- Fill in the Azure parameter fields described below. For values you reuse often, right click in the parameter field and insert a global variable instead of typing the value directly.
What To Place In The Parameters
- Connection String: paste the full Azure Storage connection string for the storage account that should receive the upload.
- Container Name: enter the destination container name, for example
hl7-inbound,archive, orexports. - File Name: enter the blob name you want Azure to create, for example
ADT_A01_20260320_120000.hl7. You can include forward slashes if you want to group blobs into virtual folders. - New Container Access: blank or
Privaterequests private access when creating a container. SelectBlobonly to allow anonymous reads of blobs in a newly created container. Azure account policy must permit public access; a denied public creation request fails. - Create Container If Missing: blank or
Falseuses an existing container. SelectTrueto permit container creation and use New Container Access. Selecting Blob access requires explicit creation. Provisioning separately allows the workflow to use narrower write credentials. - Overwrite Existing Blob: blank or
Falsefails if the blob exists. SelectTrueto replace it. Optional Expected ETag then replaces only the matching version of the content.
Existing containers keep their permissions, including existing public access. Saved workflows with no creation option require an existing container. Select Create Container If Missing=True to create future containers and select Blob explicitly if they must serve anonymous blob reads. Azure's $web static website endpoint has separate public-serving behavior, so private creation is not a privacy guarantee for that endpoint or an existing public container.
Uploads accept up to 8 MiB and use one content write, without deleting the blob or its snapshots first. Azure retains existing snapshots. Replacement uses default content properties and empty metadata; do not rely on it preserving existing metadata or tags. ETag matching does not guard tag-only changes. AzureBlobETag and AzureBlobVersionId expose the write result.
Saved workflows with no replacement option fail on duplicate names. Select True explicitly where replacement is intended. If a response is lost, inspect the blob before retrying: the write may have completed, and a later failed condition does not prove otherwise.
What To Place In The Activity Message
Place the text you want stored in Azure Blob Storage into the activity message. A common setup is to insert the inbound HL7 message from the receiver, or insert the output from an earlier step that has prepared XML, JSON, CSV, or another text payload.
Text message types are uploaded as UTF-8. Binary and DICOM message types upload their file bytes.
What The Activity Returns
The response message is a simple text result confirming the upload completed successfully.
Typical Uses
- Archiving inbound or outbound messages to Azure.
- Publishing CSV files, XML payloads, JSON payloads, or text reports to Azure.
- Dropping workflow output where other Azure services can process it later.