Microsoft Azure Storage connector

When to use this connector

Use this connector to create Flows that work with files in Microsoft Azure Storage.

You can also use it to create a Flow that loads data in Snowflake and Azure Synapse Analytics.

Create a Connection

Step 1. In the Connections window, click +, enter azure storage ,select Azure Storage SDK.

Step 2. Enter Connection parameters

Authentication

• Storage account: the storage account name.
• Autenticatin type: the following authentication types are available:
  • Access Key: authentication with Access Key.
  • SAS token: authentication with SAS token.
  • Client secret: authentication using custom Azure app and Client secret.

Authentication with Access Key

Step 1. SelectAccess key in Authentication type.

Step 2. Log in to the Azure portal.

Step 3. Select storage account.

Step 4. Select Access keys.

Step 5. Click Show keys.

Step 6. Copy key1 and paste it into the field Access Key or SAS token.

Authentication with SAS token

Step 1. SelectSAS token in Authentication type.

Step 2. Log in to the Azure portal.

Step 3. Select storage account.

Step 4. Select Shared access signature.

Step 5. Enables services, resources types, permissions, set expiration date in the future, and click Generate SAS and connection string.

Step 6. Copy SAS token and paste it into the field Access Key or SAS token.

Authentication using custom Azure app and Client secret

Step 1. SelectClient secret in Authentication type.

Step 1. Create an Azure app and give it access to the storage account(s).

Step 2. Paste Client ID, Client Secret, and Azure Tenant ID into the corresponding fields.

Other parameters

• Container: the container for files. It is similar to an Amazon S3 bucket.
• Directory: the directory under the container. This parameter is optional.
• Files: the actual file name or a wildcard file name, for example, *.csv.
• Add Suffix When Creating Files in Transformation: you can select one of the predefined suffixes for the files created, using this Connection. For example, if you select uuid as a suffix and the original file name is dest.csv, Etlworks Integrator will create files with the name dest_uuid.csv, where uuid is a globally unique identifier such as 21EC2020-3AEA-4069-A2DD-08002B30309D.

This parameter works only when the file is created using source-to-destination-transformation. Read how to add a suffix to the files created when copying, moving, renaming, and zipping files.

• Enable Wildcard File Name: if there are multiple source files in a folder, you can specify an algorithm which will be used to select the next actual source file to process. For example, if Files is set to *.csv and the oldest is selected, Etlworks Integrator will always select the oldest file in the folder which matches the wildcard *.csv.
• Override Wildcard File Name set for Connection: if Wildcard File Names are allowed, then Override Wildcard File Name set for Connection is enabled, and the file name, entered in the FROM field of the transformation is a wildcard file name, the system will override the file name entered at the Connection level. The default behavior is to use the wildcard file name entered when configuring a Connection.
• Archive file before copying to: Etlworks Integrator can archive files, using one of the supported algorithms (zip or gzip), before copying them to cloud storage. Since cloud storage is typically a paid service, it can save money and time if you choose to archive files.