The Azure Storage integration provides you with a way to export your data to one of the most widely used cloud file storages, especially in situations where data from Bloomreach Engagement is joined with data from other sources (e.g., e-commerce platform, inventory software, ad costs data) and analyzed in one place.

Azure Storage integration supports both Azure Blob Storage and Azure Data Lake Gen2 type of storage accounts. Please refer to Azure documentation for more details on the differences in Blob Storage and Data Lake Gen2 type of storage accounts.

📘

Data Imports

This integration handles data exports. If you wish to import data from Azure storage into Bloomreach Engagement, use the separate Azure Storage integration for Imports.

Setup process

Azure Storage Integration for Exports can be added via Data & Assets -> Integrations -> Add new integration. To set up the integration, you need to enter your Azure Storage Account Name, Container name, and a Blob Shared Access Secret token that are generated within Azure Portal.

📘

If you want to use the integration, you need:

• Azure storage account
• Generate Shared Access Tokens using Azure Portal

You can specify authentication details, too, based on which type of authentication you prefer (either Shared Access Token or OAuth2 are available).

For Shared Access Token (SAS) authentication, you need to enter:

• Blob Shared Access Secret Token

For OAuth2 authentication, you need to enter:

• Application (client) ID
• Directory (tenant) ID
• Client secret

Setting up new integration using Shared Access Token Authentication

• Sign in to the Azure Portal.
• Open the Storage account you want to export data to.
• Copy the name of the Storage account in the field below.
• Click on Data storage -> Containers and choose the Container that you would like to use as a target destination for exports.
• Copy the name of the Container and paste it into the respective field on the integration screen.
• In the menu, choose Settings > Shared access tokens
• Select the Signing method to the Account key.
• Set Permissions so that Write permission is enabled.
• Copy the Blob SAS token and paste it into the respective field on the integration screen.
• Fill in the necessary data in Bloomreach Engagement.

You can specify the exact Azure Storage account name and container name where Bloomreach Engagement will look for files. The integration works the same as SFTP or Google Cloud Storage, including all features.

You can learn more about Exports and available features in our Data Exports documentation.

📘

Required permissions

The service account performing file read requests is required to have the ‘Write’ permission.

The shared access token usually has an expiration date set in the future. Keep in mind that once the token expires, your exports will fail.

Setting up new integration using OAuth2 Authentication

• Sign in to the Azure Portal.
• Decide which container in which storage account should be used as the destination for data export, then copy the storage account name and container name in the respective fields in the new integration screen.
• Register an application in the App registrations section of the Azure portal.
• Copy the Application (client) ID and Directory (tenant) ID to the respective fields in the new integration screen.
• Create a new client secret in the Certification & Secrets section of your App registration.
• Copy the value of the client secret into the respective field in the new integration screen.
• Click on Data storage -> Containers and choose the Container that you would like to use as a target destination for exports.
• Copy the name of the Container in the field in the new integration screen.
• In the Access Control (IAM) section of your storage account, assign a Storage Blob Data Contributor role to the app registration you created in the third step.
• Fill in the necessary data in Bloomreach Engagement.

📘

Required permission

The service account performing file read requests is required to have the following permissions:

• Storage Blob Data Contributor,
  or any kind of custom role that includes the “write” type of permission to Blob Storage.

🚧

Limitations

• Azure supports exporting up to 48.8GB of data.