Feature Request: Use private subnet for connectivity resources

[w3b3rf]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

The recent November 2024 update introduced a new policy "Subnets should be private".
Connectivity resources (AzureFirewallSubnet, GatewaySubnet, possibly more) are not compliant with this policy since the subnets are not created with private subnet enabled.

If I try to enable private subnet for the subnets manually, they will be reset on next deployment.

Is your feature request related to a problem?

As described above: I cannot configure the subnets to be private and therefore my policy will never be compliant :(

Describe the solution you'd like

Create the connectivity subnets as private subnets by default

Alternatively, a parameter could be added to specify whether the subnets should be private.

Additional context