Forum Discussion
Helper IVParameterized connections in Data pipelines
Hello v-saisrao-msft ,
sorry, but your answer doesn't help me.
I don't know if it is working or not, and it is no documentation how it works...
For all others who want to use the feature: For my case i works, when i use the connection id as parameter in "connection". To get the connectionid, I stored the fixed connection and found the id in the json.
Community SupportHi cw88,
Thank you for reaching out to the Microsoft Fabric Forum Community.
Just to better understand your scenario and possibly help further:
- Could you please share which type of connection or data source you're trying to parameterize?
- Are you currently working with Microsoft Fabric Data Pipelines or Azure Data Factory?
- Also, may I ask what your intended use case is for parameterizing the connection?
Thank you.
cw88I want to parametrize a connection to an onprem sql server, working with Fabric Data Pipeline. Use case: general parameterization of connections to be more flexible in case of changes.
First question: Do i have to enter the connectionid or the name? If it is the ID: Where do I get the ID of a connection?
-
- v-saisrao-msft
Hi cw88,
Thank you for reaching out to the Microsoft Fabric Forum Community.
Parameterized connections in Microsoft Fabric Data Pipelines offer a way to pipeline flexibility, especially across different environments or datasets. When working within the Fabric UI, you should reference the connection name, not the connection ID. The connection name can be found under Settings > Manage connections and gateways, and it must match exactly.
For on-premises SQL Server connections, ensure the connection is configured through an On-premises Data Gateway using Basic authentication, which is currently required. To implement parameterization, you can define pipeline parameters such as Database Name and reference them using dynamic expressions like @pipeline().parameters.DatabaseName within the source settings of your Copy Data activity. This enables scenarios such as dynamically switching between databases without modifying the pipeline structure.If you need to switch entire connections, you can also parameterize the connection name using a parameter like Connection Name and reference it as @pipeline().parameters.ConnectionName.
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
- cw88
Hello v-saisrao-msft ,
for me it does not work to parameterize the connection name using a parameter
When I start the pipeline, the status of the used activity lookup remains on Queued, nothing happens...