User Story:

As ARO/HCP provider, I want to be able to:

• receive a customer's subnet id 

so that I can achieve

• parse out the resource group name, vnet name, subnet name for use in CAPZ (creating VMs) and Azure CCM (setting up Azure cloud provider).

Acceptance Criteria:

Description of criteria:

• Customer hosted cluster resources get created in a managed resource group.
• Customer vnet is used in setting up the VMs.
• Customer resource group remains unchanged.

Engineering Details:

• bvesel@redhat.com said the managed resource group and customer resource group would be under the same subscription id.
• We are only supporting BYO VNET at the moment; we are not supporting the VNET being created with the other cloud resources in the managed resource group.

This requires a design proposal so OCM knows where to specify the resource group
This requires might require a feature gate in case we don't want it for self-managed.