Microsoft Fabric
Bring customer profiles, events, catalogs, and item collections from Microsoft Fabric into Bloomreach. You export your data from Fabric as files to your Azure Storage account. Bloomreach then imports those files on a schedule or when your pipeline finishes.
Learn more about how other warehouses connect and how zero-copy personalization works.
How it works
- Export from Fabric to Azure Storage. You or your partner build a Fabric pipeline that exports data from your Lakehouse or Warehouse as files to your Azure Data Lake Storage Gen2 account.
- Import customers and events from Azure Storage. Bloomreach connects to your storage account and imports the files directly. Imports run on a schedule, or your pipeline can start one when it finishes by calling the Marketing API.
- Import catalogs and item collections through SFTP. You enable SFTP on the same storage account, and Data hub imports the files through it. Imports run on a schedule, or your pipeline can start one when it finishes by calling the Data hub API.
| Data | Import path | Setup guide |
|---|---|---|
| Catalogs and item collections | SFTP | Configure imports, SFTP, and Import catalogs |
| Customers and events | Azure Storage | Azure Storage for imports and Data imports |
Before you start
You need:
- Data in a Fabric Lakehouse or Warehouse.
- An Azure Data Lake Storage Gen2 account with the hierarchical namespace enabled.
- OAuth2 credentials for the storage account. This is the only supported authentication method for imports from Azure Storage.
- SFTP enabled on the same storage account, if you import catalogs or item collections. Azure requires the hierarchical namespace for SFTP.
Also check these settings on your storage account:
- If the account restricts access by IP, add your Bloomreach outbound IP addresses to the allowed list. See Outbound IP addresses.
- If imports from Azure Storage fail with a soft delete error, disable soft delete on the account.
Export from Fabric to Azure Storage
In Fabric, create a data pipeline with a copy activity. Set your Lakehouse or Warehouse as the source and your Azure Data Lake Storage Gen2 account as the destination. Microsoft documents this in Configure Azure Data Lake Storage Gen2 in a copy activity.
You or your partner build and maintain this pipeline. Bloomreach doesn’t manage it.
Import customers and events
Connect Bloomreach to your storage account with the Azure Storage integration, then create an import for customers or events. Follow Azure Storage for imports to set up the connection and Data imports to create the import.
When you export events, include only the events added since your last export. Don’t use overlapping time windows.
Import catalogs and item collections
Enable SFTP on your storage account and create a local user for Bloomreach. Azure SFTP authenticates local users with a password or an SSH key. Then add the SFTP integration in Bloomreach and create the import in Data hub. Follow SFTP and Import catalogs.
Good to know
- Imports run in batches, on a schedule or when your pipeline starts them. They aren’t real time.
- Azure charges for SFTP while it's enabled on a storage account.
- Client secrets for Azure Storage imports expire. Renew yours before imports stop working.
Updated about 1 hour ago

