FTK deployment with private network setting blocked by policy - due to ADF Management service is public available

[DUeffing]

📝 Scenario

Customer tried to deploy the latest FTK version with private network configuration. Unfortunately an Azure Policy blocked the deployment of the Data Factory.

That's because we don't stick the ADF management service behind a private endpoint, just the runtimes. Same deal with KQL, you can get to the management interface, but the data is behind the PE

💎 Solution

It should be configurable if the ADF Management shall be accessible via a Private Endpoint or not.

🙋‍♀️ Ask for the community

We could use your help:

1. Please vote this issue up (👍) to prioritize it.
2. Leave comments to help us solidify the vision.

[MSBrett]

The future plan is to provide an option to create PE's on the customer vNet for storage and ADX. I'll include ADF in that too.

Not sure if we'll ever end up with a PE on the FTK vNet as we're going to depreciate the vNet peering option and just use Private Link to get to the endpoints we need to get to. It's part of a larger plan to allow the IT to manage the PE's and DNS on their end without impacting the internals of the FTK.