loading
Loading content
loading
Utilities
Export a file or folder to Azure Blob Storage.
overview
export-to-azure-blob pushes a workflow's output into Azure Blob Storage so results leave the run and land in your own cloud. Built on Microsoft's AzCopy, it takes a single file or a whole folder and uploads it to a named storage account and blob container, authenticated with a SAS token you provide as a file.
It fits at the end of a pipeline as a delivery step. Point it at the artifact a scan or report stage produced, set the destination path inside the blob, and the data is in Azure for archival, sharing, or handoff to another system. Folder uploads recurse, so an entire results directory transfers in one node.
In a Trickest workflow, use export-to-azure-blob to persist findings, ship reports to a team's storage, or stage data for downstream Azure tooling, keeping the storage credentials scoped to the SAS token rather than baking in account keys.
use cases
Upload a scan's output file or folder to an Azure container so results live in storage you control after the workflow finishes.
Push a generated report to a destination path in a team's storage account so stakeholders can pull it from Azure directly.
Land workflow output in a blob so an Azure function, pipeline, or analytics job can pick it up as its input.
Point the folder input at a results directory and AzCopy uploads it recursively in one step, preserving the structure.
reference
| Name | Type | Flag | Description |
|---|---|---|---|
| file | FILE | · | File to upload |
| folder | FOLDER | · | Folder to upload recursively |
| storage-account | STRING | · | Azure storage account |
| blob | STRING | · | Azure storage blob |
| path | STRING | · | Path where the object should be uploaded on the blob |
| sas-token-file | FILE | · | SAS token file |
Showing key inputs. export-to-azure-blob exposes 6 inputs in total.
example
# export-to-azure-blob: upload report.txt to a container via AzCopy + SAS# storage-account=examplestorage blob=results path=scans/example.com/report.txtazcopy copy report.txt "https://examplestorage.blob.core.windows.net/results/scans/example.com/report.txt?<SAS>"examplestorage.blob.core.windows.netresults.blob.core.windows.netarchive.blob.core.windows.netreports.example.comartifacts.example.orgbackup.example.netstaging.example.comdev.example.comguidance
Use export-to-azure-blob as a delivery step when workflow results need to end up in Azure Blob Storage. For other destinations, pick the matching export node, and keep credentials in the SAS token rather than embedding account keys.
Bulk uploads to Amazon S3. Use it instead when the destination is AWS rather than Azure.
Saves artifacts back into the Trickest filetree. Stay inside the platform rather than an external cloud.
Transfers data over HTTP. A general fetch or push, not an authenticated blob upload.
faq
related
Import, export, and link workflow data with Airtable.
Decode Android APK files into smali sources and resources.
Check a file's values against conditions and exit with a matching code.
Extract all hosted zones from AWS Route53.
Output file lines by batch size, given START_LINE and END_LINE.
Extract a batch range from a file's lines or a folder's files, with parallel processing.
A report artifact feeds export-to-azure-blob, which uploads it to a named container with a SAS token so results land in Azure Blob Storage.
Facts on this page come from the live Trickest tool library.