Open ssisjoost opened 8 months ago
@ssisjoost Thanks for your feedback! We will investigate and update as appropriate.
@ssisjoost I've delegated this to @liudan66, a content author, to review and share their valuable insights.
Followed up with author.
@ssisjoost - When you say "It doesn't seem to work", I assume the resource is deploying successfully without a managed private endpoint?
Or are you getting an error?
I too face this issue. Synapse deployment task doesn't recognize managed private endpoint artifacts. Rest of the artifacts are successfully deployed without managed private endpoint.
I am looking into it. It may be that this is something we don't currently support for Azure Synapse Analytics deployments. I'll update you here.
Some explanation on overriding the property privateLinkResourceId of the Managed Private Endpoint during deployment would be nice.
I would expect something like this, but it doesn't seems to work
"Microsoft.Synapse/workspaces/managedVirtualNetworks/managedPrivateEndpoints": { "properties": { "privateLinkResourceId": "=" } }
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.