Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!View all the Fabric Data Days sessions on demand. View schedule
Within my Fabric workspace I have two workspaces(DEV & PROD) connected through deployment pipeline. In one of the pipelines the sink artifact for copy activity is warehouse . But after deploying the pipeline the pipeline is connected to warehouse in DEV work space instead of PROD workspaceNot having an option of creating deployment rules for Pipelines my CI/CD is kind of not dynamic/incomplete because we need manually choose the workspace
@Fabric #fabric #fabricdeployementpipelines
Solved! Go to Solution.
Hi @Anonymous,
I agree with you that the deployment pipelines are incomplete for the moment. As a workaround, you could use dynamic content as a sink in the copy activity and set the Warehouse id from a variable where the value of the variable is dependent on the different environments (Dev/Prod) the data pipeline is running in. This way, you do not manually set the sink Warehouse
HI @Anonymous,
As FabianSchut said, current deployment pipeline may not complete enough to support all type of workspace items. For your scenario, I'd like to suggest you to submit an idea for improving deployment pipeline usages.
Regards,
Xiaoxin Sheng
Hi @Anonymous,
I agree with you that the deployment pipelines are incomplete for the moment. As a workaround, you could use dynamic content as a sink in the copy activity and set the Warehouse id from a variable where the value of the variable is dependent on the different environments (Dev/Prod) the data pipeline is running in. This way, you do not manually set the sink Warehouse
Check out the November 2025 Fabric update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!