Azure Data Lake Integration

This feature is currently in the BETA version.

The Azure Data Lake Integration provides a way to import your data from one of the most widely used cloud file storages into the Bloomreach Engagement, to have your customer and event data in one place and ready to fully analyze them in the app.


The integration handles only imports. If you wish to export your data from Bloomreach Engagement to Azure Storage, use the separate Azure Blob Storage integration.

Setup Process

The Azure Data Lake Integration can be added as any other integration, so go to Data & Assets -> Integrations -> Add new integration. After that, you need to enter your Azure STorage account name, container name, Application (client) ID, Directory (tenant) ID, and your client secret. All of this is generated by your Azure Portal account.

Integrating the Azure Data Lake Storage for Imports in the Azure Portal

  1. First, you need to sign in to the Azure Portal.
  2. Decide which container in which storage account should be used as a data source for your imports. Then copy the storage account name and container name into the respective fields.
  3. Register the application in the App registration section of the Azure Portal.
  4. Copy the Application (client) ID and Directory (tenant) ID to the respective fields.
  5. In the Certifications & Secrets section of your app registration, create a new client secret.
  6. Then copy your newly created client secret into the respective field.
  7. Click on Data Storage -> Containers and choose the container that you want to use as a target destination for exports.
  8. Copy the container name from the respective field.
  9. In the Access Control (IAM) section of your storage account, assign Storage Blob Data Reader role to the app registration that you have created in the third step.


Required permissions

To register the application in the App registration section, you need to have assigned roles with permission for the Azure Blob Storage Reader.


  • Authorization is currently only possible using OAuth2.


Keep in mind that your client's secret has an expiration date set in the future. Once the token expires, your import may stop working due to authentication issues.