Integrating with OneLake

Hi teolachev ,

Hello!!! You have asked very pertinent and detailed questions about integration with OneLake. I have tried to answer each one separately below:

1. OneLake Connection with ADF Pipeline
Currently, Azure Data Factory (ADF) does not directly recognize OneLake as a Linked Service. However, since OneLake is actually an ADLS Gen2 compliant fabric, it can be accessed indirectly through ADLS Gen2 connectivity. In this case, the endpoint and authorization information required for access must be carefully configured.

2. Non-AAD Authentication (Shared Key / SAS / SDK)
OneLake currently only supports Azure Active Directory (AAD) based authentication.
Alternative authentication methods such as Shared Key or SAS Token are not supported.
On the SDK side, the Azure SDK for Python (for example azure-storage-file-datalake) is available. However, these SDKs also rely on AAD authentication.

3. Power BI Workspace Security and Folder Based Authorization
Yes, that's right: OneLake security is integrated with Power BI Workspace security. Because Workspaces do not offer folder-based security, more granular folder-based access control is not available. This is a limitation in terms of flexibility, especially in multi-user environments.

4. Security Settings in Subfolders
You can create subfolders within OneLake, but security settings are inherited from the root directory and overriding them requires manual intervention. No automated or policy-managed folder-based security is currently deployed.

5. Geo-Distribution and Replication
Yes, OneLake can be geographically distributed. However, this cannot be done directly in the OneLake settings. For this you need to purchase

You need to purchase Power BI Premium capacity.
You must position this capacity as a regional tenant and
You should allocate workspaces according to the relevant regions.
This way, data access and replication delays can be optimized.