Skip to content

Azure Activities: Blob Storage

This page covers the Azure Blob Upload feature from the Azure Activities extension library.

Use it to archive HL7 or FHIR messages, store exports or file content, or hand workflow output to another Azure-based process.

Download

Using it in a workflow

  1. Install the Azure Activities MSI on the Integration Soup server.
  2. Restart the Integration Soup service if needed.
  3. Add Azure Blob Upload after the step that produces the content you want to upload.
  4. In the activity message template, use Insert Activity Message to bring in the content from the receiver or earlier activity.
  5. Fill in the Azure parameter fields below. For reused values, insert workflow or global variables.

Parameters

Connection String

Paste the full Azure Storage connection string for the target storage account.

Container Name

Enter the destination container name, for example:

  • hl7-inbound
  • archive
  • exports

File Name

Enter the blob name to create, for example:

  • ADT_A01_20260320_120000.hl7
  • exports/2026/03/20/patient-export.json

You can include forward slashes to group blobs into virtual folders.

Activity message

Place the content you want stored in Azure Blob Storage into the activity message.

The incoming message type is selectable in the workflow designer.

Typical examples:

  • inbound HL7 from a receiver
  • XML or JSON generated by transformers
  • CSV or plain-text output from earlier workflow steps
  • binary file content from an earlier activity
  • DICOM content

Text-based message types are uploaded as UTF-8 bytes. Binary and DICOM messages upload their underlying file bytes.

Response message

The response message is a Text message confirming the upload succeeded.

Typical uses

  • Archiving inbound or outbound messages to Azure
  • Publishing CSV, XML, JSON, or other text output to Blob Storage
  • Storing documents, binary exports, or DICOM files in Azure Blob Storage
  • Dropping workflow output where other Azure services will pick it up