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 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.
That's an interesting finding with the way to select destination lakehouse, I've examined json code and indeed - sink settings do differ depending on approach taken (e.g. feels like properties "linkedService" vs "connectionSettings" are treated differently by backengine).
Although as a temporary solution I'm currently taking a bit simpler path : just using python/pyspark notebook where I have slightly more control over endpoint addresses.