Forum Discussion
Parameterizing connection data
Thanks for raising - it got my vote!
Hi pmscorca
In Microsoft Fabric, workspace‑level connections don’t support dynamic content for individual properties such as server name or database name — these values are static by design and can’t be parameterised like ADF linked services. The only supported dynamic behaviour is choosing which existing connection to use at runtime (by name or ID), not changing its internal settings.
The recommended approach today is to create separate static connections per environment or target (e.g. Dev/Test/Prod) and use pipeline parameters, variable libraries, or deployment automation to switch between them. True runtime parameterisation of connection properties is a known limitation in Fabric and has been confirmed by Microsoft as an area still under development.
This has been raised in the past on Fabric community, and the position has not changed since then.
Solved: Dynamic connection to sources in Fabric - Microsoft Fabric Community
Hi, thanks for your reply.
Is it an architectural limitation or a more solvable issue? Does it exist any ideas about this subject?
Thanks
Hi pmscorca I could not find any Idea pertaining to this. I don't think it is a critical limitation - enterprises have been using the recommended approach of maintaining separate connections per environment.
I would recommend raising an Idea if you're keen to use parameterised connections - if the Idea gets enough vote, the feature might get added into Fabric.
Hi, thanks for you reply.
I've created the related idea: Parametric connection data - Microsoft Fabric Community
Please vote it, thanks!
