Fabric pipeline Deployment dev to prod

[AJAJ]

Hi there,

I have been developing fabric data pipelines, warehouse, lakehouse in a fabric dev workspace. I noticed when deployment is done from WS_Dev to WS_Prod, pipelines are still pointing to Dev workspace. I can parameterize it.

Where in Prod workspace do I need to configure that all objects should point to Prod workspace so code deployments from dev dont overwrite the variable in PROD. 

master pipeline with look up

After lookup -- invoke pipeline

child pipeline with copy activity.

[deborshi_nag · Accepted solution]

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

[stoic-harsh]

Hi @AJAJ,

Deployment Pipelines in Fabric doesn't automatically remap environment-specific references (Lakehouse, Warehouse, connections). This is by design.

The most reliable way to align pipelines across Fabric workspaces is to export the pipeline JSON, replace Dev artifact IDs with Prod IDs, then import it into Prod. Basically, configure Prod Pipelines using JSON templates from Dev after replacing IDs.

[v-saisrao-msft]

Hi @AJAJ,

Checking in to see if your issue has been resolved. let us know if you still need any assistance.

Thank you.

[v-saisrao-msft]

Hi @AJAJ,

Have you had a chance to review the solution we shared by @deborshi_nag? If the issue persists, feel free to reply so we can help further.

Thank you.

[deborshi_nag · Accepted solution]

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

[AJAJ]

Thanks @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 · Accepted solution]

Hi @AJAJ 

This is how you can ensure deployment pipeline doesn't overwrite the GUID

1. Open your Deployment Pipeline.
2. Go to the Test stage → Manage rules.
3. Add a rule for Variable Library Value Set.
4. Choose Value Set = Test.
5. Repeat for Prod.

Now:

Deploy Dev > Test > Dev GUID NEVER overwrites Test GUID
Deploy Test > Prod > Test GUID NEVER overwrites Prod GUID