Advance your Data & AI career with 50 days of live learning, dataviz contests, hands-on challenges, study groups & certifications and more!
Get registeredGet Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Learn more
Hi Fabric Community,
I'm using Deployment Pipelines in Microsoft Fabric to move my project from Dev → Test → Prod environments. I noticed there’s no option to configure Deployment Rules for:
Pipelines
Dataflow Gen2
Lakehouse or Warehouse connections
Other environment-specific configurations
This makes it difficult to handle scenarios where resource names or connections differ between environments (e.g., Dev_LH → Prod_LH), and we’re forced to manually update settings post-deployment — which is error-prone and not scalable for enterprise solutions.
Why isn’t the Deployment Rule feature available yet for pipelines, Dataflow Gen2, and other key assets?
Is support for these in the Fabric roadmap?
What are the current best practices or workarounds to automate environment-specific behavior during deployment?
Solved! Go to Solution.
Hi @bhavya5903
Yes, you are absolytely correct. Deployment rules not configurable for
-Pipelines
-Dataflow Gen2
-Lakehouse or Warehouse connections
-Other environment-specific configurations
I agree it's a not scalable option to chnage it manually. Please have a look on my comments below.
Please go thorugh this Microsoft Fabric Roadmap for more details
My recommendation is use worksapce parameters and workspace varaiables where it is possible for your workloads. If you want to submit any idea about your query. Please submit it here Fabric Ideas - Microsoft Fabric Community
Please let me know if it helps you.
Thank you!
Did I answer your question? Mark my post as a solution!
Proud to be a Super User!
Hi @bhavya5903
Yes, you are absolytely correct. Deployment rules not configurable for
-Pipelines
-Dataflow Gen2
-Lakehouse or Warehouse connections
-Other environment-specific configurations
I agree it's a not scalable option to chnage it manually. Please have a look on my comments below.
Please go thorugh this Microsoft Fabric Roadmap for more details
My recommendation is use worksapce parameters and workspace varaiables where it is possible for your workloads. If you want to submit any idea about your query. Please submit it here Fabric Ideas - Microsoft Fabric Community
Please let me know if it helps you.
Thank you!
Did I answer your question? Mark my post as a solution!
Proud to be a Super User!
Hi @bhavya5903,
Great question — and yes, Microsoft Fabric now supports environment-specific configuration management through the Variable Library feature (currently in preview), which addresses the exact challenge you're describing.
This topic has already been addressed in detail here : https://community.fabric.microsoft.com/t5/Fabric-platform/How-to-Handle-Dynamic-Environment-Configur...
It covers the current support for environment-specific configuration using Variable Libraries in Deployment Pipelines, and how to handle dynamic connections across Dev → Test → Prod.
Hope it helps!
Best regards,
Antoine
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!
Check out the October 2025 Fabric update to learn about new features.