Forum Discussion
Copy activity fails with workspace level private link enabled (Error getting outbound access policy)
Hi all,
I've had contact with Microsoft support, and they have provided me with a solution for this issue. It appears to be a bug in the current copy data activity, for which they are currently developing a new version.
For now you can work around this issue by, in the destination settings, selecting a lakehouse connection from the dropdown instead of clicking 'browse all' and then selecting your lakehouse from the catalog. (see image)
Why this solves the issue i'm not sure, but i think that in this way the UI registers that it should use the connection instead of direct lakehouse access. Microsoft is aware of the issue and a more complete fix is on its way.
Super UserHello FabricConsult
I think you're hitting one of the limitations of using a workspace level private link of Microsoft Fabric. Please refer to this doc.
Supported scenarios for workspace private links - Microsoft Fabric | Microsoft Learn
It says, APIs with endpoints containing v1/workspaces/{workspaceId} support workspace-level private links because they operate within the context of a specific workspace. In contrast, admin APIs use admin/workspaces/{workspaceId} in their endpoints and aren't covered by workspace-level private links.
I think your pipeloine is referncing one of the admin APIs behind the scenes, hence it is failing.
Hope this helps - please appreciate leaving a Kudos or accepting as a Solution!