Can I upload a whole folder?

Yes. Set the folder input and AzCopy uploads it recursively to the path inside the named blob.

Do I need both file and folder?

No. Supply either file or folder. storage-account, blob, path, and sas-token-file define the destination.

When should I pick mass3 instead?

When the destination is Amazon S3. export-to-azure-blob is for Azure Blob Storage only.

What runs under the hood?

Microsoft AzCopy. The node wraps it so workflows can push artifacts without custom upload scripts.

Updated Jul 15, 2026

Utilities

Ship workflow artifacts to Azure Blob Storage

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

Archive findings to your own cloud Deliver a report to a shared container Stage 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

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

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.

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 Trickest Browse the library

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