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:
change button slicer selected item color
jovanpop-msft
on:
Add native OPENROWSET(json) support in Fabric DW
miguel
on:
Need "deployment packages" for deployment pipeline...
Cristian_Angyal
on:
Org app and cross-item navigation