[AVM Module Issue]: Support StandardV2 SKU for NAT Gateway and Public IP

[lopf]

Check for previous/existing GitHub issues

• I have checked for previous/existing GitHub issues

Issue Type?

Feature Request

Module Name

avm/res/network/nat-gateway

(Optional) Module Version

2.0.0

Description

The current module hardcodes the NAT Gateway SKU to Standard. This prevents using StandardV2, which enables a zone-redundant NAT Gateway and improves resilience against Availability Zone failures:
https://learn.microsoft.com/en-us/azure/reliability/reliability-nat-gateway#resilience-to-availability-zone-failures

To use StandardV2, the associated Public IP must also be created with the StandardV2 SKU, which is currently not possible with the module.

Proposed change:

• Make the NAT Gateway SKU configurable instead of hardcoded
• When StandardV2 is selected:
  • Ensure the Public IP is also created with StandardV2
  • Optionally validate this in the module to prevent misconfiguration

(Optional) Correlation Id

No response

[microsoft-github-policy-service]

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

[avm-organizer]

@lopf, thanks for submitting this issue for the avm/res/network/nat-gateway module!

Important

A member of the @Azure/avm-res-network-natgateway-module-owners-bicep team will review it soon!

[rickschwabe]

@lopf There is already an open issue for the public IP. Standard V2 has already been implemented for the public IP prefix.

#6455