Forum Discussion
How to set ADLS as a destination in Dataflows Gen 2 ?
Hi,
I did what I thought was the complete setup to be able to save data tables in an ADLS Gen 2 but it still doesn't work. Can someone help me find the part I'm missing please?
Here's what I did :
- Azure portal : Created a Storage account with an Azure blob ressource. I enabled Hierarchical namespace since Copilot told me that is what makes it an ADLS Gen 2.
- Fabric Admin portal : I setup the Azure connection at the Tenant-level.
- Fabric enabled workspace : I setup the Azure connection to the one I just created in the Admin portal.
After step 3 above, I used Microsoft Azure Storage Explorer to see if anything happened. As as matter of fact, 3 folders where created: power-bi-backup/<my-workspace-name>, powerbi. But there's only the structure, no files.
Folder structure create in ADLS Gen 2 after setting up the connection in the workspace
Then I went to the workspace and created a Dataflow Gen2. I tried a few things.
- First, I left the query without any destination.
query without destination
2. Then I tried setting up a destination but I couldn't see anything that looks like it would go to the ADLS. I ended up picking up Lakehouse.
3. I also tried Warehouse but it was obvous it wasn't gonna work.
At the end, I installed the OneLake tool for Windows Explorer and I can see the parquet files for my query did make it to OneLake but the folders in Azure are still empty. Not even a model.json file or anything like that.
Though nothing went to the Azure storage, the data files made it to the OneLake
What part am I missing? What can I do to set the ADLS Gen 2 as a destination?
Thanks,
--mo
Hi molegris
Fabric writes data to OneLake by default, even if ADLS Gen2 is connected.
To resolve:
Check ADLS Gen2 Permissions: Ensure the user has Storage Blob Data Contributor access.
Direct Write to ADLS: Not supported; use Azure Data Factory or scripts to sync OneLake data to ADLS Gen2.
Verify Hierarchical Namespace: Confirm it’s enabled for ADLS Gen2.
Export Data: Use tools to move data periodically from OneLake to ADLS Gen2.
Fabric doesn’t mirror data to ADLS Gen2 automatically; external sync is required.
Did I answer your question? Mark my post as a solution, this will help others!
If my response(s) assisted you in any way, don't forget to drop me a "Kudos" 🙂
Kind Regards,
Poojara
Data Analyst | MSBI Developer | Power BI Consultant
Consider Subscribing my YouTube for Beginners/Advance Concepts: https://youtube.com/@biconcepts?si=04iw9SYI2HN80HKS
2 Replies
- Poojara_D12
Super User
Hi molegris
Fabric writes data to OneLake by default, even if ADLS Gen2 is connected.
To resolve:
Check ADLS Gen2 Permissions: Ensure the user has Storage Blob Data Contributor access.
Direct Write to ADLS: Not supported; use Azure Data Factory or scripts to sync OneLake data to ADLS Gen2.
Verify Hierarchical Namespace: Confirm it’s enabled for ADLS Gen2.
Export Data: Use tools to move data periodically from OneLake to ADLS Gen2.
Fabric doesn’t mirror data to ADLS Gen2 automatically; external sync is required.
Did I answer your question? Mark my post as a solution, this will help others!
If my response(s) assisted you in any way, don't forget to drop me a "Kudos" 🙂
Kind Regards,
Poojara
Data Analyst | MSBI Developer | Power BI Consultant
Consider Subscribing my YouTube for Beginners/Advance Concepts: https://youtube.com/@biconcepts?si=04iw9SYI2HN80HKS- molegris
Advocate IV
Hi Poojara_D12 ,
Thanks for your reply.
I have follow-up question though. Since ...
Direct Write to ADLS: Not supported; use Azure Data Factory or scripts to sync OneLake data to ADLS Gen2.
Then do you know a situation where setting up an Azure connection in a Power BI / Fabric Workspace would be advantageous?
Best regards,
--mo