Dynamically set Copy data Destination Connection or Notebook Workspace.

MisterSmith, I see parameterization of pipeline connections is on the release plan, but in the interim you should be able to use the Use Dynamic Content option (assuming no limitations due to your using On-Prem) Once you input a value, it will reveal a variety of other fields depending on your connection type.

In my scenario, I need to deploy these pipelines across multiple workspaces, so I created a separate "Environment Variables" pipeline that has a set of return values with the IDs needed for the current workspace. Then, I just have my triggering pipeline invoke that "global" pipeline to get the IDs shown above for my lakehouses, workspaces, etc. This can then pass these variables to other child/downstream pipelines through parameters.