loading
Loading content
loading
Utilities
Upload a file or folder to Azure Blob with a SAS token.
overview
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.
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 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.
Bulk upload to Amazon S3. Use it when the destination is AWS, not Azure.
Writes artifacts back into the Trickest filetree. Stay on-platform instead of an external cloud.
Generic HTTP transfer. Not an authenticated Azure Blob upload.
faq
related
Spider a URL and return a wordlist for password crackers.
Wordlist and mined-word subdomain permutation.
Import, export, and upsert workflow data against an Airtable base.
Decode Android APK files into smali sources and resources.
Check a file's values against conditions and exit with a matching code.
Authenticated Route53 hosted-zone inventory.
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.