Dynamic Copy Data Limitation: Connection Type Auto-Defaults to Lakehouse, Preventing Fully Parameter

Hi Ninad-Mulik,

Thank you for reaching out to the Microsoft Fabric Community Forum and for sharing the details and screenshot.

I can see you are trying to build a parameterized Copy Data pattern that dynamically connects to different sources (like various on-prem SQL databases).

Now, this behaviour is expected. The Connection type field in Copy Data cannot be parameterized it automatically defaults (for example, to Lakehouse) and does not support dynamic content. Because of this, it isn’t currently possible to switch between different connector types (SQL Server, Lakehouse, Oracle, etc.) within a single Copy Data activity.

If all sources share the same connector type (e.g., SQL Server): Create one linked service and parameterize Server, Database, and Table names. This keeps the “Connection type” fixed but still allows dynamic behaviour between runs.

If sources use different connector types: Use a Switch or If condition activity that checks the SourceType parameter. Each branch calls a separate Copy Data activity configured with the appropriate linked service (SQL, Oracle, Lakehouse, etc.).

Use Variable Libraries (preview) to centralize connection definitions this helps manage multiple environments but doesn’t yet allow changing connector types dynamically.

Refer these links:
1. https://learn.microsoft.com/en-us/fabric/data-factory/parameters 
2. https://learn.microsoft.com/en-us/fabric/data-factory/copy-data-activity 
3. https://learn.microsoft.com/en-us/fabric/cicd/variable-library/get-started-variable-libraries?tabs=home-page 

Hope this clears it up. Let us know if you have any doubts regarding this. We will be happy to help.

Thank you for using the Microsoft Fabric Community Forum.