Azure Cloud Storage Panel

Overview

The Azure Cloud Storage panel enables administrators and data engineers to securely integrate Microsoft Azure storage accounts (Azure Blob Storage / Azure Data Lake Storage Gen2) into the DataFloem platform using OAuth authentication.

Connections established through this interface serve as operational cloud storage endpoints, allowing pipelines to read, process, and write unstructured or semi-structured file formats (Parquet, CSV, JSON, etc.) to target Azure container locations.

Access Requirements

To access this page, the user must either have Administrator privileges or the CREATE permission for the Target module.

The CREATE permission allows users to create new groups. Users without administrator privileges or the required permission cannot access this page.

If you do not have the required permission, ask your administrator to grant it from one of the authorization pages below.

Authorization

Users without the required authorization will receive the following error:

Access Denied

You don't have access to this resource.

Prerequisites

Before establishing an Azure Cloud Storage connection, ensure that:

An App Registration is provisioned within Microsoft Entra ID (formerly Azure AD) for DataFloem integration.
You have retrieved the required OAuth parameters (Client Id, Client Secret, and Client Endpoint / Tenant Endpoint URL).
Proper IAM roles (such as Storage Blob Data Contributor or Storage Blob Data Reader) are granted to the application registration on the target Storage Account and Container.

Form Elements

The fields that need to be configured within the panel are as follows:

Field	Required?	Description
Connection Name	Yes	A unique alias identifying this Azure Cloud Storage connection across the platform.
Database Version	Yes (Dropdown)	Selects the precise version mapping to ensure correct Azure SDK/API client driver compatibility.
Is Active	Yes (Toggle)	Defines whether the connection is active immediately upon deployment. Enabled (`on`) by default.
Authentication Type	Read-only	Specifies the authentication protocol. Fixed to `OAuth` for this integration mode.
Client Id	Yes	The Application (Client) ID generated during app registration in Microsoft Entra ID.
Client Endpoint	Yes	The Entra ID OAuth token issuance URL endpoint (e.g., `https://login.microsoftonline.com/<tenant-id>/oauth2/v2.0/token`).
Client Secret	Yes	The secret client key associated with the registered application (Visibility can be toggled using the eye icon).
Storage Account	Yes	The exact name of the target Azure Storage Account.
Container Name	Yes	The target blob container or file system name to read from or write to.
Root Directory Path	Yes	The base folder path where file operations will be scoped. Defaults to `/` for container root.
Optional Parameters (Name / Value)	No	Dynamic entries used to pass fine-grained parameters (e.g., `timeout`, `sasToken`).
Is Secret (Optional Parameters)	Yes (Toggle)	Encrypts and masks the specific parameter value within internal stores.

Azure Cloud Storage Connection Deployment Process

Select Azure Cloud Storage from the cloud storage wizard to open this panel.
Enter a unique Connection Name and designate the target Database Version.
Fill in the OAuth credentials obtained from Microsoft Entra ID including Client Id, Client Endpoint, and Client Secret.
Specify the target Storage Account, Container Name, and set the appropriate Root Directory Path.
If required, add custom key-value arguments under Optional Parameters and toggle Is Secret appropriately.
Review all entered values and click Save to commit the asset to the platform, or click Cancel to abort the operation.

Validation Rules

Connection Name, Client Id, Client Endpoint, Client Secret, Storage Account, and Container Name fields cannot be left empty.
Client Endpoint must strictly adhere to a valid HTTPS URL format.
The Root Directory Path field must follow a valid path syntax (e.g., / or /raw/landing/).