Bug Report

[RobinsonMW]

Describe the bug

During a redeployment of the alz-CorpPeering operation the alz-vnet step failed with the following:

{ "code": "MinimumApiVersionNotSpecifiedForAddressSpaceUpdateInPeeredVnet", "message": "Address space update operation on virtual network can not be performed as the minimum required API version for working with Vnet Peering is 2021-01-01, and the provided client API version is 2020-06-01.", "details": [] }

I think the source of the problem is at line 110 of the eslzArm/subscriptionTemplates/vnetPeering.json file

Steps to reproduce

1. change a CORP vnet address space
2. redeploy

Screenshots

[arjenhuitema]

Hi @RobinsonMW,

Thank you for reporting this issue and providing detailed information. It appears that the API version requires updating. We invite you to submit a PR for this matter if possible. Otherwise, we will review and provide an update.

[Springstone]

@RobinsonMW I'll be updating the API versions for vnetPeering.json. However, it is important to note that this is not a supported scenario - as you can't change address space if subnets are configured through the ALZ portal experience. The fringe case that you may have run into is running the same greenfield deployment again, adjusting the address space for corp networks. I will share a link you can test from shortly.

[Springstone]

@RobinsonMW I've updated the Microsoft.Network/virtualNetworks API version throughout the ALZ Portal Accelerator. You can test the change from my working branch here: https://portal.azure.com/#view/Microsoft_Azure_CreateUIDef/CustomDeploymentBlade/uri/https%3A%2F%2Fraw.githubusercontent.com%2FSpringstone%2FEnterprise-Scale%2FNetworkPeeringAPI%2FeslzArm%2FeslzArm.json/uiFormDefinitionUri/https%3A%2F%2Fraw.githubusercontent.com%2FSpringstone%2FEnterprise-Scale%2FNetworkPeeringAPI%2FeslzArm%2Feslz-portal.json

In my own testing, I cannot change the address space of a peered corp subscription, but I am testing with all networking provisioned. In my case, it now fails because I have Bastion deployed in the connectivity subscription (so not getting the API version error).

As I've stated before, this isn't a supported scenario, so don't think there is much more we can do to address the ask. I'll leave this issue open for the rest of the week looking for your feedback.

[microsoft-github-policy-service[bot]]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 5 days.