MultiRegion - Separate regional VNETs into their own RG

[integyjc]

Describe the feature end to end, including deployment scenario details under which the feature would occur.

Having just deployed v20.0 in a MultiRegion configuration, the VNET for the primary and secondary regions are placed in the same resource group in the primary region. In our case UK South Primary, UK West Secondary

Please can a dedicated connectivity resource group for the secondary region be created to contain the secondary region vnet and any associated resources such as network watcher.

Why is this feature important. Describe why this would be important for your organization and others. Would this impact similar orgs in the same way?

Having a vnet in region B in a resource group in region A is against best practice and also causes one of the ALZ policies to show as non compliant

"Audit that the resource location matches its resource group location"

Please provide the correlation id associated with your error or bug.

xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

Can you describe any alternatives that you have taken since this feature does not exist?

We may create our own secondary region RG and move the vnet post deployment although we are wary of any ongoing impact to doing this in regards to re-deploying Bicep-ALZ for updates

Feature Implementation

Check previous GitHub issues

• I have searched the issues for this item and found no duplicate

Code of Conduct

• I agree to follow this project's Code of Conduct

[oZakari]

Valid ask and something we will be incorporating into the new Azure Verified Modules framework.