Azure Blob Storage Integration

The Azure Blob 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. ecommerce platform, inventory software, ad costs data) and analysed in one place.

Azure Blob Storage also supports use cases, where Azure Data Lake Gen2 is needed, there are just minor differences in the way directory structure is handled inside the storage account.


This integration handles only exports - it is currently not possible to import data from Azure into Bloomreach Engagement.

Setup process

Azure Blob Storage can be added as any other integration, 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

Generating access tokens in Azure Portal

  • 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 in the respective field on the integration screen
  • In the menu, choose Settings > Shared access tokens
  • Select Signing method to Account key
  • Set Permissions so that Write permission is enabled
  • Copy the Blob SAS token and paste it in the respective field on the integration screen

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.


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.

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



Authorization is currently only possible using Shared Access Tokens.