Support Dynamic Connection Switching in Copy Activity (like ADF Dynamic Linked Services)

[PeddolaAravind]

Idea:
In Fabric Pipelines, the Copy activity source  currently statically bound to specific connections created at the workspace level (e.g., a Salesforce connection named DEV_SALESFORCE).

When deploying the same pipeline from DEV to QA, UAT, or PROD, we must manually update the source and sink connections to match the appropriate environment. This process is error-prone, time-consuming, and not suitable for CI/CD automation.

In Azure Data Factory, this issue is solved through dynamic linked services — where connection names and properties can be parameterized and changed at runtime.

Proposed Solution:

Allow dynamic connection binding in Fabric Pipelines, so that the Copy activity (and other relevant activities) can select the connection name based on a parameter or expression.
Benefits:

• Enables seamless CI/CD and multi-environment deployments

• Reduces manual changes and risk of errors across environments

• Improves maintainability and scalability of Fabric pipelines

• Aligns with existing ADF best practices for environment-specific configurations

This feature is essential for enterprise-grade deployment and automation workflows.

Thanks for considering this improvement!