When you create a connection to a warehouse, lakehouse or KQL DB, the connection is "absolute", meaning that the workspace ID is hardcoded into the connection.
This gives issues when you deploy the pipeline to another workspace with deployment pipelines, because ADF will try to resolve the connection using the original workspace, instead of the new workspace.
It can't find it, so the connection gives an error.
You can work around the issue by parameterizing the connection entirely, as described in this blog post:
https://sqlkover.com/dynamic-warehouse-lakehouse-connections-in-microsoft-fabric-data-pipelines/
However, it would be better if you could create a "relative" connection. This means: find the warehouse with the same name in the current workspace.
on:
In "Manage relationships" view I need to filter by...
ToddChitt
on:
The list of available connections via a pipeline C...
miyake-san
on:
Enable use of Entra ID groups as recipients for su...
on:
Enable Page-Level Security for Power BI Desktop an...