Problem
Renaming a Library Variable in Microsoft Fabric does not update pipelines that reference it. The pipeline continues to contain the old expression name and only fails at runtime. There is also no warning during publish or validation.
In real projects this creates silent breaking changes. A simple refactor can cause multiple pipelines to fail in production without any design time indication.
Why this matters
This affects maintainability and safe refactoring. Large Fabric workspaces often contain many pipelines and variables. Currently teams must manually search every pipeline JSON to avoid outages.
Typical scenarios impacted:
• Renaming variables to follow naming standards
• Environment standardization
• CI/CD promotion between environments
• Shared library cleanup
Suggested solution
Fabric should track Library Variable usage as a dependency rather than plain text and support safe rename operations. Possible implementations:
Option A
When renaming a Library Variable, automatically update all pipeline expressions referencing it.
Option B
Show a dependency impact list before rename and allow refactor confirmation.
Option C
At minimum, show validation warnings for broken references during publish.
Expected benefit
This would significantly reduce production failures caused by refactoring and align Fabric behavior with modern IDE refactor capabilities.
Current behavior makes variable rename a breaking change, which discourages proper governance and cleanup of shared libraries.
