Azure Blob Storage Setup Guide

Follow our setup guide to connect Azure Blob Storage to Fivetran.

Prerequisiteslink

To connect Azure Blob Storage to Fivetran, you need:

• An Azure Blob Storage container holding files with supported file types and encodings
• The ability to grant Fivetran the ability to read and list files from this container

Setup instructionslink

Create a Shared Access Signature in Azurelink

IMPORTANT: You can re-use the Shared Access Signature (SAS) across multiple Fivetran connectors.

1. Open the Azure Portal.

2. Select your storage account and click Shared access signature.

   

3. Select Blob from the Allowed services options.

   

4. Select Container and Object from the Allowed resource types options.

5. Select Read and List from the Allowed permissions options.

6. Choose the appropriate start and expiry dates of your SAS.

   IMPORTANT: When the SAS expires, you will have to update your Azure Blob Storage connector to resume syncing files.

7. (Optional) To enhance security, safelist Fivetran’s IP address range under Allowed IP addresses. Azure only allows one IP range per SAS token.

   IMPORTANT: Use the IP range format to safelist the IP addresses, for example, 35.234.176.144 - 35.234.176.151, because the CIDR format, for example, 35.234.176.144/29, is not supported in Azure Portal.

8. Select HTTPS only from the Allowed protocols options. We recommend to select the HTTPS option to ensure the security of your files.

   

9. Click Generate SAS and connection string.

10. Make a note of the Connection string value. You need to enter this value in the Connection String field in the connector setup form.

Finish Fivetran Configurationlink

1. In the connector setup form, enter your Destination schema name.

2. Enter your Destination table and your Container Name.

3. Enter the Connection String you found in Azure.

4. Choose your configuration options. Using these configuration options, you can select subsets of your folders, certain types of files, and more to sync only the files you need in your destination. Setting up multiple connectors targeted at the same container, but with different options, can allow you to slice and dice a container any way you’d like.

   • Folder Path (Optional) This folder path is used to specify a portion of the container in which you’d like Fivetran to look for files. Any files under the specified folder and all of its nested subfolders will be examined for files we can upload. If no prefix is supplied, we’ll look through the entire container for files to sync.

   • File Pattern (Optional) The file pattern is a regular expression that we use to decide whether or not to sync certain files. It applies to everything under the prefix. For instance, suppose under the prefix logs you had three folders: 2017, 2016, and errors. Using the pattern \d\d\d\d/.*, you could exclude all the files in the errors folder, because \d\d\d\d only applies to the folders whose name consists of four consecutive digits, and because .* after / applies to any files in these folders. If you’re not sure what regular expression to use, you can leave this field blank, and we’ll sync everything under the prefix. If you’re feeling particularly bold, you can learn to write your own regex here and test it out using this tool.

   • File Type The file type is used to let Fivetran know that even files without a file extension ought to be parsed as this file type. For example, if you have an automated CSV output system that saves files without a .csv extension, you can specify the CSV type and we will sync them correctly as CSVs. Selecting “infer” will let Fivetran infer from a file’s extension (.csv, .tsv, .json, .avro, or .log) what to sync. If you do choose a file type, every file we examine will be interpreted as the file type you select, so make sure everything Fivetran syncs has the same file type!

   • Compression The compression format is used to let Fivetran know that even files without a compression extension should be decompressed using the selected compression format. For example, if you have an automated CSV output system that GZIPs files to save space, but saves them without a .gzip extension, you can set this field to GZIP. The integration will then decompress every file that it examines using GZIP. If all of your compressed files are correctly marked with a matching compression extension (.bz2, .gz, .gzip, .tar, or .zip), you can select “infer”.

   • Error Handling Selecting skip ignores any improperly formatted data within a file, allowing you to sync only valid data. Choosing fail enables you to prevent a file from syncing if any improperly formatted data is detected. With either option you will receive a notification on your dashboard if errors are encountered.

5. (Optional) If you’d like, you can set the Show Advanced Options toggle to ON. Note that these options are for advanced configuration, and are only necessary in highly specific cases.

   • Modified File Merge When a previously synced file is modified, should the rows in the destination be replaced or should the new rows be appended to the table. upsert_file option will replace records in destination, using the filename and line number as the primary key. append_file option will append records.

   • Archive Folder Pattern If there are multiple files within archive (TAR or ZIP) folders, you can use the archive folder pattern to filter those as well. For example, the archive folder pattern .*json will sync from an archive folder only those files that end in a .json file extension.

   • Null Sequence (Optional) CSVs have no native notion of a null character. However, some CSV generators have created one, using characters such as \N to represent null. Note: text is un-escaped before the null sequence is matched, so don’t use the escape character in your null sequence. Only use this field if you are sure your CSVs have a null sequence.

   • Delimiter (Optional) The delimiter is a character used in CSV files to separate one field from the next. If this is left blank, Fivetran will infer the delimiter for each file, and files of many different types of delimiters can be stored in the same folder with no problems. If this is not left blank, then all CSV files in your search path will be parsed with this delimiter.

   • Escape Character (Optional) CSVs have a special rule for escaping quotation marks as opposed to other characters - they require two consecutive double quotes to represent an escaped double quote. However, some CSV generators do not follow this rule and use other characters like backslash for escaping. Only use this field if you are sure your CSVs have a different escape character.

   • Skip Header Lines (Optional) Some CSV generating programs include additional header lines at the top of the file. They consist of few lines that do not match the format of the rest of the rows in the file. These header rows can cause undesired behavior in Fivetran because we attempt to parse them as if they were records in your CSV. By setting this value, you can skip fixed-length headers at the beginning of your CSV files.

   • Skip footer Lines (Optional) Some CSV generating programs include a footer at the bottom of the file. It consists of a few lines that do not match the format of the rest of the rows in the file. These footer rows can cause undesired behavior in Fivetran because we attempt to parse them as if they were records in your CSV. By setting this value, you can skip fixed-length footers at the end of your CSV files.

   • Headerless Files (Optional) Some CSV generating programs do not include column name headers for the files — they only contain data rows. By setting this value, you request Fivetran to generate generic column names following the convention of column_0, column_1, … column_n to map the rows.

6. Click Save & Test. Fivetran will take it from here and sync your data from your Azure Blob storage account.

Related Contentlink

description Connector Overview

assignment Release Notes

settings API Connector Configuration

home Documentation Home