Introducing Agents.·Read
OverviewAgentsWorkflowsExecutionDeveloper ToolsSecurityLibrary
Updated Jul 15, 2026

Utilities

Ship workflow artifacts to Azure Blob Storage

Upload a file or folder to Azure Blob with a SAS token.

Agent
Archive findings to your own cloudDeliver a report to a shared containerStage data for downstream Azure tooling

overview

What export-to-azure-blob does

export-to-azure-blob is the delivery step that lands workflow output in your Azure storage account. It wraps AzCopy around a file or recursive folder upload.

Set storage-account, blob, and path for the destination. Authenticate with sas-token-file so access stays scoped to that token rather than a full account key.

Versus mass3, this targets Azure Blob, not Amazon S3. Versus put-trickest-files, results leave the platform into storage you control.

source github.com/Azure/azure-storage-azcopy

use cases

Where export-to-azure-blob fits

Archive findings to your own cloud

Upload a scan's output file or folder to an Azure container so results live in storage you control after the workflow finishes.

Deliver a report to a shared container

Push a generated report to a destination path in a team's storage account so stakeholders can pull it from Azure directly.

Stage data for downstream Azure tooling

Land workflow output in a blob so an Azure function, pipeline, or analytics job can pick it up as its input.

Upload a whole results directory

Point the folder input at a results directory and AzCopy uploads it recursively in one step, preserving the structure.

reference

export-to-azure-blob inputs and flags

6 inputs
NameTypeFlagDescription
fileFILE·File to upload
folderFOLDER·Folder to upload recursively
storage-accountSTRING·Azure storage account
blobSTRING·Azure storage blob
pathSTRING·Path where the object should be uploaded on the blob
sas-token-fileFILE·SAS token file

Showing key inputs. export-to-azure-blob exposes 6 inputs in total.

example

Run export-to-azure-blob

export-to-azure-blob · command
# 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>"
sample output
examplestorage.blob.core.windows.netresults.blob.core.windows.netarchive.blob.core.windows.netreports.example.comartifacts.example.orgbackup.example.netstaging.example.comdev.example.com

guidance

Choosing export-to-azure-blob

Use export-to-azure-blob when run artifacts must land in Azure Blob Storage. Pick mass3 for S3, or put-trickest-files to keep files inside Trickest. Keep credentials in sas-token-file.

mass3

Bulk upload to Amazon S3. Use it when the destination is AWS, not Azure.

put-trickest-files

Writes artifacts back into the Trickest filetree. Stay on-platform instead of an external cloud.

wget

Generic HTTP transfer. Not an authenticated Azure Blob upload.

faq

export-to-azure-blob questions

Pass a SAS token as sas-token-file. Access follows that token's scope instead of embedding a full account key.

related

More Utilities tools

  1. browser-fetch

    Headless Chromium render: requested URL, final URL, status, and title next to the page.

  2. cewl

    Spider a URL and return a wordlist for password crackers.

  3. csvkit

    SQL on one CSV. The table name is the file stem.

  4. dnsgen

    Wordlist and mined-word subdomain permutation.

  5. duckdb

    In-process SQL on CSV, JSON, and Parquet. No server.

  6. edge-tts

    Microsoft Edge neural speech from text or a script file. No API key.

Run export-to-azure-blob yourself

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.

Run export-to-azure-blob in TrickestBrowse the library

Facts on this page come from the live Trickest tool library.