Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AzureFirewallManagementSubnet with Azure Firewall Standard #901

Open
2 tasks done
gerrynicol opened this issue Nov 11, 2024 · 3 comments
Open
2 tasks done

AzureFirewallManagementSubnet with Azure Firewall Standard #901

gerrynicol opened this issue Nov 11, 2024 · 3 comments
Labels
Area: Networking 🌐 Issues / PR's related to Networking Type: Feature Request ➕ New feature or request

Comments

@gerrynicol
Copy link

gerrynicol commented Nov 11, 2024

What happened? Provide a clear and concise description of the bug, including deployment details.

The Management subnet and public IP address is not associated with the Azure Firewall when the standard SKU is seletced. It is when the Basic SKU is selected.

Unsure if its related to this link where it seems that there may have been a change to Azure Firewall? - https://learn.microsoft.com/en-us/azure/firewall/management-nic

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

No error, this looks like configuartion.

What was the expected outcome?

The Management IP and subnet are associated with the AzureFirewallManagementSubnet

Relevant log output

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 oZakari added the Area: Networking 🌐 Issues / PR's related to Networking label Nov 12, 2024
@oZakari
Copy link
Contributor

oZakari commented Nov 12, 2024

Hey @gerrynicol, appreciate you calling this out and sharing the documentation as it does appear related to upcoming changes to firewall that the management IP is now going to be required for standard and premium skus for certain features. Will put this in the backlog to fix.

@oZakari oZakari added the Type: Feature Request ➕ New feature or request label Nov 12, 2024
@gerrynicol
Copy link
Author

gerrynicol commented Nov 12, 2024

No problem @oZakari.

As a workaround at present I have changed the value here from Basic to Standard and the resource has deployed with the management PIP assigned to the subnet.

Assume there will be changes required to factor in all SKU types im the code going forward.

resource resAzureFirewall 'Microsoft.Network/azureFirewalls@2023-02-01' = if (parAzFirewallEnabled) {
dependsOn: [
resGateway
]
name: parAzFirewallName
location: parLocation
tags: parTags
zones: (!empty(parAzFirewallAvailabilityZones) ? parAzFirewallAvailabilityZones : [])
properties: parAzFirewallTier == 'Standard' ? {
ipConfigurations: varAzFirewallUseCustomPublicIps
? map(parAzFirewallCustomPublicIps, ip =>
{

@gerrynicol
Copy link
Author

On further testing, when I then subsequently try to add an additional custom Public IP into the parameter file as below, I get an error.

cannot have more than one subnet reference, please ensure only one IpConfiguration contains a subnet reference","details"

"parAzFirewallCustomPublicIps": {
"value": [

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Networking 🌐 Issues / PR's related to Networking Type: Feature Request ➕ New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants