Prophecy supports direct integration with Azure Data Lake Storage (ADLS), allowing you to read from and write to ADLS containers as part of your data pipelines. This page explains how to configure the connection, what permissions are required, and how ADLS connections are managed and shared within your team.Documentation Index
Fetch the complete documentation index at: https://docs.prophecy.ai/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
Prophecy connects to ADLS using the credentials you provide. These are used to authenticate requests and authorize all file operations during pipeline execution. To ensure Prophecy can read from and write to your storage account, you must have the following Azure RBAC role or equivalent permissions:- Storage Blob Data Contributor: Read, write, and delete access to Blob storage containers and blobs.
Feature support
The table below outlines whether the connection supports certain Prophecy features.| Feature | Supported |
|---|---|
| Read data with a Source gem | Yes |
| Write data with a Target gem | Yes |
| Browse data in the Environment browser | Yes |
| Trigger scheduled pipeline upon file arrival or change | Yes |
Connection parameters
To create a connection with your ADLS account, enter the following parameters:| Parameter | Description |
|---|---|
| Connection Name | Unique name for the connection. |
| Client ID | Your Microsoft Entra app client ID |
| Tenant ID | Your Microsoft Entra tenant ID |
| Client Secret (Secret required) | Your Microsoft Entra app client secret |
| Account Name | Name of your ADLS storage account that hosts the container |
| Container Name | Name of the container within the storage account |