Copy activity error when Destination is on prem SQL Server

Hi schneiw, as mabdollahi mentioned, the connection for Lakehouse in Fabric had multiple changes over the last few months. If your implementation was working a few months ago it could be outdated now. Rather then use a previously created connection, you need to reconfigure your Source in the Copy activity. In the new style you actually don't need to create a connection to the Lakehouse for the copy activity data source if you have access to the Lakehouse. You can just select a Lakehouse directly from the list of data sources in Fabric without having an connection object. First click Browse All

and then View More

On the next screen you'll the list of all your available data sources that you can just select as a data source in the Copy activity.
Keep in mind, with this configuration the data pipeline will try to use your connection to the Lakehouse when executing. It amy not work in all scenarios. If you are building an automated pipeline then you do need to create a Lakehouse connection and use that instead preferrably using a different organizational account.

If you find this answer useful or solving your problem please consider giving kudos and/or marking as a solution.