No Copy job connection in pipeline

Hi ABSOmar2 ,

The behavior you observed is consistent with a metadata-sync issue on the pipeline side. When a Copy Job item is created before Fabric fully associates the underlying connection with the workspace, the pipeline UI may not display it in the Connection dropdown even though the job itself can run without any problems.

By creating a new Copy activity, Fabric refreshes the internal metadata bindings for that pipeline, which forces a new lookup of available connections. This is why the newly created activity was able to recognize and surface the connection immediately.

Your configuration is correct, and the outcome you saw is expected with the current UX behavior. If this occurs again, recreating the activity or refreshing the artifact configuration will typically resolve it.

If you have any additional questions or need further assistance, please feel free to reach out to the Fabric Community.

Thank you.

Hi ABSOmar ,

Yes, this can definitely happen, and it’s confusing the first time you hit it. The key thing to know is that the connection used inside the Copy job itself is not the same thing as the “Connection” the pipeline is asking for in the Settings tab. Even if your Copy job works perfectly on its own, the pipeline still needs its own connection context to “attach” to that job.

When the dropdown shows No results found, it usually means the pipeline can’t see any connections that belong to the same workspace or that it doesn’t have permission to use. This happens a lot when the Copy job was created in a different workspace, or when the connection exists but the pipeline owner doesn’t have rights on it.

What fixed it for us was:
We recreated the connection directly inside the same workspace where the pipeline lives, then refreshed the list. As soon as the connection existed in that workspace, it immediately appeared in the dropdown.

Another thing to check is ownership. If the connection belongs to a different user or was created by someone else, make sure you’ve been granted permission on it. Without that, it simply won’t show up in the picker — Fabric hides it instead of showing an error.

In short, even though the Copy job runs fine, the pipeline still needs:

• the connection to exist in the same workspace

• your user to have access to that connection

Once both are true, it should appear instantly.

If it still doesn’t show up after that, reopening the pipeline sometimes helps refresh the metadata cache.

– Gopi Krishna

Hi ABSOmar ,

Thank you for reaching out to the Microsoft Fabric Community Forum.

Could you please let us know if the issue has been resolved? I wanted to check if you had the opportunity to review the information provided by Ugk161610 and Mauro89 . If you still require support, please let us know, we are happy to assist you.

Thank you.

Hi ABSOmar ,

We haven’t received an update from you in some time. Could you please let us know if the issue has been resolved?
If you still require support, please let us know, we are happy to assist you.

Thank you.