Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!View all the Fabric Data Days sessions on demand. View schedule
Hello,
It's been days since I try to use the Lakehouse connector with a dataflow gen2. When I try to select the lakehouse I want to connect to, the cursor goes round and round for minutes and I get this error :
Do you know if I need to do some complementary configurations to resolve that issue please ?
Notes : Both Lakehouse and dataflow originate from the same workspace; I use a trial Fabric
Solved! Go to Solution.
Hello,
Thank you for your help.
I tried these recommandations but it was still not working.
So I reached the support and after some verifications it was said that I can't use these gen2 dataflows since I am using a guest account. This is not mentioned in the official documentation but seems like an issue that has been reported before.
Thank you for sharing this. I've passed this feedback internally to the product group.
Hi @Joh24
Thanks for using Microsoft Fabric Community.
Apologies for the inconvenience that you are facing here.
As I understand that you are encountering a connection issue with the Lakehouse connector with a dataflow Gen2 in Microsoft Fabric.
To diagnose the cause of the connection error and establish a successful connection, please review these troubleshooting steps:
Temporary glitch : Clearing your browser's cache and cookies can sometimes fix connection problems. This is because it removes temporary files that might be outdated or causing conflicts. Try it, then restart Fabric and reconnect to the Lakehouse.
Review Authentication Types : Ensure compatibility between the authentication method you've chosen for the Azure Blob Storage connector is compatible with both the Copy Activity and Dataflow Gen2 activities.
Please refer for more details : Set up your Lakehouse connection.
Check the Gateway Configuration : For successful data transfer, confirm that the firewall on the server running the on-premises data gateway allows outbound traffic on port 1433 (TCP) to the following endpoints: *.datawarehouse.pbidedicated.windows.net, *.datawarehouse.fabric.microsoft.com, *.dfs.fabric.microsoft.com
For more details please refer : Set new firewall rules on server running the gateway
I hope this information helps. Please do let us know if you have any further questions.
Thanks.
Hello,
Thank you for your help.
I tried these recommandations but it was still not working.
So I reached the support and after some verifications it was said that I can't use these gen2 dataflows since I am using a guest account. This is not mentioned in the official documentation but seems like an issue that has been reported before.
Thank you for sharing this. I've passed this feedback internally to the product group.
Hi @Joh24
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.
In case if you have any resolution please do share that same with the community as it can be helpful to others.
Otherwise, will respond back with the more details and we will try to help.
Thanks.
Hi @Joh24
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others.
If you have any question relating to the current thread, please do let us know and we will try out best to help you.
In case if you have any other question on a different issue, we request you to open a new thread.
Thanks.
I'm still seeing this issue in 2025! does anyone know if this is going to be fixed?