search

Azure / ALZ-Bicep

This repository contains the Azure Landing Zones (ALZ) Bicep modules that help deliver and deploy the Azure Landing Zone conceptual architecture in a modular approach. https://aka.ms/alz/docs
MIT License
754 stars 506 forks source link

Support for deploying multiple vWAN Hubs in regions which may or may not support Azure Firewall Availability Zones #759

Closed simonhutson closed 2 months ago

simonhutson commented 5 months ago

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

/config/custom-parameters/vwanConnectivity.parameters.all.json provides the ability to create multiple vWAN hubs via the parVirtualWanHubs parameter, but only allows you to specify a single Availability Zone configuration via the parAzFirewallAvailabilityZones parameter.

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?

Many Azure paired regions have a primary region which supports AZs and a satellite region which doesn't (e.g. uksouth and ukwest), and customers often deploy vWAN hubs across paired regions. This means that you can only choose non-zonal Azure Firewall deployments if you are also deploying multiple vWAN hubs in regions with mixed support for AZs.

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?

No response

Feature Implementation

No response

Check previous GitHub issues

Code of Conduct

oZakari commented 5 months ago

Good callout on this as this! I have added this to the backlog to be prioritized.