Hi,
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
-
mattlee
on:
“Add Value” in Textbox Not Visible in Dark Theme
- mattin on: Report Server Permissions Jan/May 2025
-
bhalicki
on:
Bi Crashes on launch with (AS Process PID=XXXXXX H...
- stanteitelbaum on: authenticator wont trigger after purchase of new p...
-
Stinkys
on:
Fix the Date function in DAX
-
Stinkys
on:
Cannot login to community site
-
reubwork
on:
May 25 update for Snowflake Connector v2 has broke...
-
dmkblesser
on:
Unable to open existing PBIP files
- DamoUK on: Gateway issues
- davidebacci on: Total Labels not following dynamic formatting rule...