Skip to main content
The Azure Blob Storage destination writes pipeline output to an Azure container. It supports CSV, TSV, JSON, Parquet, and Fixed width output formats, with optional compression and PGP encryption. Once your connection is set up, see File Storage Options for the full set of write options (output formats, compression, PGP, and more) shared across every file storage provider.

Connection Setup

See Azure Blob Storage Source for steps to get your storage account credentials and create the connection in Integrate.io ETL.

Destination Configuration

Connection

Select your Azure Blob Storage connection from the dropdown, or create a new one.

Container

Enter the name of the Azure Blob container where output files will be written.

Target Directory

The path within the container where output files are created. One or more files will be written to this directory. By default, the job fails if the directory already exists. Use package variables to generate unique directory names per run (e.g. /output/${_JOB_ID}).

Destination Format


Delimited Values Options

Header names with spaces: use triple underscores (___) in the alias or column name in a Select component to produce a space in the output header. To use a different separator character, add a package variable _FS_REPLACE_WITH_SPACE_IDENTIFIER with the character you want to replace.

Output Compression

Available for Delimited values, JSON, and Fixed width formats. Not available for Parquet.

PGP Encryption

To encrypt output files with a trading partner's OpenPGP public key, select an active entry from the PGP Key dropdown. The entry must hold a public key. Files are encrypted before being written to the target path.
Paths that contain a space, semicolon, or parenthesis are not supported when a PGP key is set.
See PGP Keys for how to add and manage keys.

Destination Action

Controls what happens when the target directory already exists.

Merge Output to Single File

Check Merge output to single file to write all output to a single file rather than multiple part files. Note that file size limits on some platforms may cause the job to fail for large outputs.

Character Encoding

Available only when Destination action is set to Use intermediate storage, copy to existing directory.

Target File Names

Default pattern: output files are named part-[mr]-[0-9]{5} (e.g. part-m-00000). To use a custom pattern, select Custom pattern:

Fixed Width Layout

When Destination format is set to Fixed width, a Fixed width layout step appears. The layout is a table with one row per incoming field, in schema order. Every incoming field is written with no separators between columns. To write only some fields or in a different order, add a Select transformation before this destination. The total record width in characters is shown below the table and updates as you edit.

Preview with Data

Click Preview with data to run the component through the previewer and see the actual records the job would write. Rows whose sample value does not fit the configured width are marked with an advisory message. Blocking errors (invalid width, pad, or decimals) appear in the errors box and prevent saving.

Persisted Layout Format

The layout is stored as fixed_width_destination_type on the component. Example:
record_delimiter and char_encoding round-trip through the API but are not editable in the UI.

Skip Empty Output

Available for Delimited values, JSON, and Fixed width formats. When checked, no output files are written if the job produces zero records. Useful for downstream processes that should not receive empty files.

FAQ

Can I write to a different container than the one I read from? Yes. The source and destination components each have their own connection and container settings. Does Azure Blob Storage support all destination action options? Yes. All five destination action options are available for Azure Blob Storage.

Azure Blob Storage Source

File Storage Options

Using Variables in Packages

PGP Keys

Last modified on September 7, 2026