Example for Fabric Data Pipeline CICD with variable substitution.

Question

Example for Fabric Data Pipeline CICD with variable substitution.

John Aherne 176

Hi All,

I am hoping someone can help me figure out how to implement CICD with connection substitution for a Fabric Data Factory pipeline.

An example would be awesome - All I want to do is to promote a Data Factory pipeline to another environment and swap the connections automatically. Like how linked services were swapped in ADF when promoted - Anything using that linked service would now use the new connection.

I am using Azure DevOps and will have some complex data pipelines in a Fabric workspace.

Thanks!

John

SIVASANKAR YEDDULA 150 Reputation points Microsoft External Staff Moderator

2026-08-20T11:17:08.0033333+00:00
Hi John,

Thank you for reaching out to the Microsoft Q&A forum.

For Fabric Data Factory CI/CD, the recommended approach is to use Variable Libraries with Connection Reference variables rather than hard-coding connection details.

Create separate value sets for Dev, Test, and Prod, with each value set pointing to the appropriate environment-specific connection. Your pipelines can then reference the Variable Library, allowing the same pipeline definition to be promoted across environments without modifying the pipeline itself.

However, it's important to note that Connection Reference variables are static pointers to a specific connection ID and do not automatically rebind during deployment. When promoting to another environment, you must ensure that the appropriate environment-specific value set is configured and active for the target stage.

In summary:

Create separate connections for Dev, Test, and Prod.

Store the connection references in a Variable Library.

Create environment-specific value sets.

Reference the Variable Library in your Fabric pipeline.

During deployment, use the corresponding value set for the target environment.

This is currently the closest equivalent to ADF linked-service parameterization and is the recommended pattern for managing environment-specific connections in Fabric CI/CD.
John Aherne 176 Reputation points

2026-08-20T14:42:05.3166667+00:00

Those are not supported for data factory pipelines. CoPilot suggested the same answer before telling me they weren't supported.
John Aherne 176 Reputation points

2026-08-20T17:16:31.37+00:00

It looks like Gemini has answers for me. I will post an update here once I fully understand it. It's all in Azure DevOps with deployment pipelines there.
SIVASANKAR YEDDULA 150 Reputation points Microsoft External Staff Moderator

2026-08-21T09:17:43.42+00:00

Hi John,

Thanks for the update. No problem, please take your time to understand it fully. Once you have the details, please share the update. I’ll also review it from my side.
SIVASANKAR YEDDULA 150 Reputation points Microsoft External Staff Moderator

2026-08-24T17:35:30.26+00:00
Hi @John Aherne ,

Thank you for reaching out to the Microsoft Q&A forum.

After reviewing the current Fabric Data Factory CI/CD capabilities, it is important to note that Microsoft Fabric does not currently provide a direct equivalent to Azure Data Factory linked service parameterization, where connection references are automatically swapped during deployment.

For Fabric Data Factory pipelines, the recommended CI/CD approach is to use:

Git integration (Azure DevOps or GitHub)

Fabric Deployment Pipelines

Fabric CLI and Azure DevOps Pipelines for deployment automation

Variable Libraries where supported

If your goal is to promote the same pipeline across Dev, Test, and Prod environments while using different connections, the typical pattern is:

Create environment-specific connections in each workspace.

Deploy the pipeline artifact through Git integration or Deployment Pipelines.

Configure the connection references for the target environment.

For supported scenarios such as Copy Jobs, use Variable Libraries and environment-specific value sets to manage connection IDs.

For example:

Development Workspace

Dev_SQL_Connection

Test Workspace

Test_SQL_Connection

Production Workspace

Prod_SQL_Connection

The same pipeline definition is promoted between environments, while the target workspace contains the appropriate connection configuration for that environment.

For Azure DevOps automation, you can use Fabric CI/CD capabilities together with Fabric CLI to deploy and promote artifacts across workspaces. However, connection rebinding is not automatically performed in the same manner as ADF linked services and must be managed through the supported Fabric deployment and configuration mechanisms.

The following Microsoft documentation provides detailed implementation guidance:

CI/CD for pipelines in Data Factory in Microsoft Fabric

CI/CD for Copy Job in Data Factory in Microsoft Fabric

Variable Library configuration and deployment customization

Based on the current product capabilities, there is no fully equivalent replacement for ADF linked service swapping in Fabric Data Factory pipelines. Environment-specific connection management must be handled through workspace-specific connections, deployment automation, and supported parameterization features where applicable.

I hope this helps. Please let us know if you have any further questions.

If this answer helps, please consider clicking Accept Answer so that other community members with similar requirements can benefit from it as well. If you have any further questions, please let us know. We will be happy to assist.

https://learn.microsoft.com/en-us/fabric/cicd/variable-library/tutorial-variable-library

Answer accepted by question author

0 additional answers

Your answer

SIVASANKAR YEDDULA 150 Reputation points Microsoft External Staff Moderator

2026-08-20T11:17:08.0033333+00:00

Hi John,

Thank you for reaching out to the Microsoft Q&A forum.

For Fabric Data Factory CI/CD, the recommended approach is to use Variable Libraries with Connection Reference variables rather than hard-coding connection details.

Create separate value sets for Dev, Test, and Prod, with each value set pointing to the appropriate environment-specific connection. Your pipelines can then reference the Variable Library, allowing the same pipeline definition to be promoted across environments without modifying the pipeline itself.

However, it's important to note that Connection Reference variables are static pointers to a specific connection ID and do not automatically rebind during deployment. When promoting to another environment, you must ensure that the appropriate environment-specific value set is configured and active for the target stage.

In summary:

Create separate connections for Dev, Test, and Prod.

Store the connection references in a Variable Library.

Create environment-specific value sets.

Reference the Variable Library in your Fabric pipeline.

During deployment, use the corresponding value set for the target environment.

This is currently the closest equivalent to ADF linked-service parameterization and is the recommended pattern for managing environment-specific connections in Fabric CI/CD.
John Aherne 176 Reputation points

2026-08-20T14:42:05.3166667+00:00

Those are not supported for data factory pipelines. CoPilot suggested the same answer before telling me they weren't supported.
John Aherne 176 Reputation points

2026-08-20T17:16:31.37+00:00

It looks like Gemini has answers for me. I will post an update here once I fully understand it. It's all in Azure DevOps with deployment pipelines there.
SIVASANKAR YEDDULA 150 Reputation points Microsoft External Staff Moderator

2026-08-21T09:17:43.42+00:00

Hi John,

Thanks for the update. No problem, please take your time to understand it fully. Once you have the details, please share the update. I’ll also review it from my side.

Answer 1

Nandan Hegde 36,966 MVP Volunteer Moderator

You would need to set up Variable library and set up the connection details and the default value set which would be 1 time manual across the workspaces:

User's image

And then reference the variable library values across your connections :
User's image

This is the closest for CI CD.

John Aherne 176 Reputation points

2026-08-24T19:16:45.1433333+00:00

Yes, thank you! I was wrong originally (Apologies Siva!) and went down many many rabbit holes to eventually come right back here.

This link helped me immensely.

https://learn.microsoft.com/en-us/fabric/cicd/variable-library/tutorial-variable-library
SIVASANKAR YEDDULA 150 Reputation points Microsoft External Staff Moderator

2026-08-25T07:11:42.7966667+00:00

Hi @John Aherne ,

No problem at all! 😊 Glad the link helped and that you were able to get it sorted out. Thanks for the update!

If this answer helps, please consider clicking Accept Answer so that other community members facing similar issues can benefit from it as well. If you have any further questions, please let us know. We will be happy to assist.