Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredJoin us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered
Hi,
I just posted this idea, if you think it's useful, could you vote for it? Link: https://community.fabric.microsoft.com/t5/Issues/Idea-Allow-easier-connection-to-lakehouse-and-data-...
Description:
The connections from pipelines to lakehouse or data warehouse are only possible if the pipeline is located in the same workspace as the lakehouse/data warehouse.
This prevents us to try to make a better organization of the objects. For example, if we would like to break down the objects according to their type (lake house in one workspace, pipelines and dataflows in a different one and so on) we can't, because this will affect the connection between the pipelines and dataflows to the lake house and data warehouse.
There are two possibilities:
If this kind of limitation really needs to exist, instead of using the workspace as a limit, the pipelines could use the domain as a limit, allowing the pipeline to connect to other objects inside the same domain.
No limitation at all. In a Data Mesh scenario, cross domain access will be needed and the pipeline will need to connect to lake houses or data warehouses belonging to different domains.
The limitation appear in objects related to connection as the choice between "Workspace Connection" and "External Connection", with no option in between.
Kind Regards,
Dennes
You do have an alternative/workaround to create a shortcut to the remote lakehouse, in your local lakehouse workspace, did you try that ?
Thank you for the feedback.
Fabric Ideas is where we collect new feature asks. OneLake Connector to work across workspaces in Data Factory in Fabric should be the same as the capability that you are looking for. Could you vote on this?