Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more

Reply
Ninad-Mulik
Frequent Visitor

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

I’m using a single Copy Data activity with parameters to connect to different sources. However, when I add an internal or external connection, Fabric automatically sets the connection type to Lakehouse and doesn’t allow dynamic content for that field. Because of this, I’m forced to configure the connection manually, which limits the ability to build a truly dynamic, reusable Copy Data pattern for multiple sources.

 
 

NinadMulik_1-1761823040616.png

 

connection :- parameter : on prem sql db ( it may vary )

Is there an alternative approach to support this scenario, considering that the Copy Data activity is being used and the source connection can vary between runs?

 
 
 




 

1 ACCEPTED SOLUTION

Hi @Ninad-Mulik,

Just wanted to follow up. If the shared guidance worked for you, that’s wonderful hopefully it also helps others looking for similar answers. If there’s anything else you'd like to explore or clarify, don’t hesitate to reach out.

Thank you.

View solution in original post

4 REPLIES 4
v-kpoloju-msft
Community Support
Community Support

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=h... 

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.

 

Hi @Ninad-Mulik,

Just checking in to see if the issue has been resolved on your end. If the earlier suggestions helped, that’s great to hear! And if you’re still facing challenges, feel free to share more details happy to assist further.

Thank you.

Hi @Ninad-Mulik,

Just wanted to follow up. If the shared guidance worked for you, that’s wonderful hopefully it also helps others looking for similar answers. If there’s anything else you'd like to explore or clarify, don’t hesitate to reach out.

Thank you.

definitely, it was helpful.!!

Helpful resources

Announcements
December Fabric Update Carousel

Fabric Monthly Update - December 2025

Check out the December 2025 Fabric Holiday Recap!

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.