Forum Discussion
Helper IVFabric pipeline Deployment dev to prod
Hello AJAJ
You can utilise parameter variables within the connection field of Fabric Data Factory activities, though only in certain circumstances. At present, Microsoft Fabric does not support full parameterisation of the connection object itself; however, it is possible to parameterise the connection ID by leveraging dynamic content, pipeline parameters, or—preferably—Variable Libraries.
How you can use this approach:
1. Using parameters within the “connection” field
Fabric permits the use of dynamic content (parameters) in the connection field, provided the value supplied is the Connection ID (GUID).
Community feedback affirms that you may assign the connection field to @pipeline().parameters.<yourParam>, assuming the parameter contains the connection GUID.
2. Locating the connection ID
To obtain the connection ID:
- Navigate to Manage connections and gateways
- Select the relevant connection
- Copy the Connection ID (GUID)
3. Variable Libraries (recommended practice)
As direct parameterisation of connections is not currently supported, Microsoft recommends the use of Variable Libraries as the endorsed solution.
- Store connection IDs in the variable library
- Maintain different value sets for Dev, Test, and Prod environments
- Reference these variables within your activities
Hi AJAJ
This is how you can ensure deployment pipeline doesn't overwrite the GUID
- Open your Deployment Pipeline.
- Go to the Test stage → Manage rules.
- Add a rule for Variable Library Value Set.
- Choose Value Set = Test.
- Repeat for Prod.
Now:
Deploy Dev > Test > Dev GUID NEVER overwrites Test GUID
Deploy Test > Prod > Test GUID NEVER overwrites Prod GUID
Super UserHello AJAJ
You can utilise parameter variables within the connection field of Fabric Data Factory activities, though only in certain circumstances. At present, Microsoft Fabric does not support full parameterisation of the connection object itself; however, it is possible to parameterise the connection ID by leveraging dynamic content, pipeline parameters, or—preferably—Variable Libraries.
How you can use this approach:
1. Using parameters within the “connection” field
Fabric permits the use of dynamic content (parameters) in the connection field, provided the value supplied is the Connection ID (GUID).
Community feedback affirms that you may assign the connection field to @pipeline().parameters.<yourParam>, assuming the parameter contains the connection GUID.
2. Locating the connection ID
To obtain the connection ID:
- Navigate to Manage connections and gateways
- Select the relevant connection
- Copy the Connection ID (GUID)
3. Variable Libraries (recommended practice)
As direct parameterisation of connections is not currently supported, Microsoft recommends the use of Variable Libraries as the endorsed solution.
- Store connection IDs in the variable library
- Maintain different value sets for Dev, Test, and Prod environments
- Reference these variables within your activities
AJAJThanks deborshi_nag . I never thought i should use the connection guid instead of connection name.
How about work space parameterization?
How to make sure fabric deployment pipeline does not overwrite parameter value from dev pipeline.
- deborshi_nag
Hi AJAJ
This is how you can ensure deployment pipeline doesn't overwrite the GUID
- Open your Deployment Pipeline.
- Go to the Test stage → Manage rules.
- Add a rule for Variable Library Value Set.
- Choose Value Set = Test.
- Repeat for Prod.
Now:
Deploy Dev > Test > Dev GUID NEVER overwrites Test GUID
Deploy Test > Prod > Test GUID NEVER overwrites Prod GUIDHi deborshi_nag ,
any idea why I cannot find or add rules for my variable library?
I open the rules on our prod workspace here:
But in the dialog our variable library is not even listed.Feedback much appreciated!
