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.
Hi deborshi_nag,
Thanks for reaching out.
If i continue reading in the same documentation you quoted i see: Admin APIs remain accessible even for restricted workspaces, because the tenant-level setting for blocking public access governs them.
It would seem that admin api's should always be available, and the other api's should be accessible through private link
Besides, pipelines are documented as a supported feature. What use are pipelines if i can't even access data in a lakehouse