Azure Activities: Blob Storage
This page covers the Azure Blob Upload feature from the Azure Activities Extension Library. If you want the parent overview or the Azure Service Bus feature, start at Azure Activities.
Download IntegrationSoup.AzureActivities.msi
Using It In A Workflow
1. Run the 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 text you want to upload.
4. 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.
5. 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.
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.
This activity uploads the current activity message as UTF-8 text, so it is best suited to text content rather than raw binary files.
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.