Allow the use of existing Resource Group when creating azure VNet Site (Console & Terraform)

Currently when you create a new Azure VNet site you can use an existing vNet and Subnets, but you cannot use an existing Resource Group. If you use an existing vNet when deploying and destroying with Terraform, you will have issues due to dependencies.

An example use-case would be for environments where an administrator wants to replace several native services in Azure and migrate to Voltmesh in the same RG as the applications and services currently reside.

  • Michael Coleman
  • Jul 22 2021
  • Attach files
  • Sean Stockert commented
    May 09, 2023 19:56

    This will become a technical gap for two of my customers in the near future. As a practice, the two customers create RSGs for teams and then provide them access based on role. Leveraging an existing RSG is a requirement.


    I believe this is a capability for AWS, use existing VPC.