Forum Discussion
Dataflow Gen2 Not loading and refreshing data
- 1 year ago
Hello balafbm
DataflowLakehouseInternalSqlNotProvisioned” is associated with SQL analytics endpoint provisioning failures during Dataflow Gen2 refreshes, particularly in migration scenarios from Fabric trial to paid capacity.
Dataflow Gen2 automatically creates a staging lakehouse, but prior to January 2025, a known issue caused the SQL analytics endpoint for this lakehouse to fail provisioning. This led to refresh errors like:
`Refresh failed. The staging lakehouse is not configured correctly` .While this was officially fixed in January 2025, migration from trial to paid capacity can reintroduce configuration mismatches if the workspace or lakehouse isn’t properly reassigned to the new capacity .
Workspaces migrated from trial to paid capacity may retain outdated references to trial resources, causing conflicts in SQL endpoint provisioning
Please check:
Verify workspace assignments to the new paid capacity in the Fabric Admin Portal
Possible solutions:
Existing Lakehouse artifacts in the new Fabric Capacity workspace may lack proper SQL endpoint provisioning.
• Delete the current Lakehouse and create a new one. Republish the Dataflow Gen2 to reference the new LakehouseDisable Staging in Power Query
Please try these and let us know if this works.
Thanks
Hi balafbm ,
Thanks for reaching out to the Microsoft fabric community forum.
Is there any update regarding your issue, are you still encountering the same error after trying nilendraFabric's Suggestions?
In addition to their points, if you check the Known issue - Dataflow Gen2 refresh fails due to missing SQL analytics endpoint - Microsoft Fabric | Microsoft Learn document in the solution and workarounds part it is mentioned that "The issue only affects existing staging lakehouses. If you create a new dataflow, it won't have this issue."
if by removing lakehouse and creating a new one doesnt fix it, you may consider creating a new dataflow with the same transformations as the existing one so as to mitigate the issue
If you find this post helpful, please mark it as an "Accept as Solution" and consider giving a KUDOS.
Thanks and Regards