You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update Deploy-FinOpsHub command with additional parameters to allow the user to specify:
the resource group & virtual network (or resourceID) to be used by the FinOps Hub.
resourceIDs of Private DNS Zones to be linked to the Private Endpoints created on deployed resources.
ℹ️ Additional context
My company has strict controls on who/how virtual networks, peering & Private DNS Zones are created, so these cannot be performed by 3rd-party toolkits.
🙋♀️ Ask for the community
We could use your help:
Please vote this issue up (👍) to prioritize it.
Leave comments to help us solidify the vision.
The text was updated successfully, but these errors were encountered:
The Microsoft documentation says you can create your own vnet & peering to use for a FinOps Hub (https://learn.microsoft.com/en-gb/cloud-computing/finops/toolkit/hubs/private-networking#finops-hub-virtual-network) but the toolkit does not appear to provide the ability to deploy/upgrade a FinOps Hub into an existing vnet. Have I missed something?
🛠️ Solution
Update Deploy-FinOpsHub command with additional parameters to allow the user to specify:
ℹ️ Additional context
My company has strict controls on who/how virtual networks, peering & Private DNS Zones are created, so these cannot be performed by 3rd-party toolkits.
🙋♀️ Ask for the community
We could use your help:
The text was updated successfully, but these errors were encountered: