MicrosoftFYI, the official release notes do not mention that the "intent is for private endpoints to be the only option going forward." This can be a very jarring surprise/experience when deploying v0.7.
There is also no supported options (yet) for using existing VNets, Private DNS Zones, etc.
Join in the discussion on what is needed to use the FinOps Toolkit in a regulated/governed CAF-implemented environment here: https://github.com/microsoft/finops-toolkit/issues/1183
MicrosoftPrivate endpoints are not required. The change was to put hub resources into a dedicated VNet. We definitely need to add documentation for how to connect this to an existing network. We opted for the dedicated VNet route because it offers improved security and works better with the wide variety of network configurations that exist in the wild, which made it difficult to support reliably.
Thanks micflan
But if Private Endpoints are not required, why does v0.7 force the deployment of them? I agree, updating the FinOps Toolkit architecture to be more secure is very important (after all, it does hold financial data).
We can continue discussing this topic via the GitHub Issue, if preferred.
MicrosoftMaybe we're speaking about different things. Access is still public by default, which is my point. But, yes, we can continue to discuss on GitHub.
