Fabric 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:

1. Navigate to Manage connections and gateways
2. Select the relevant connection
3. 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