Feature - Azure Firewall - Multiple Public IPs

[gerrynicol]

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

Does the current hubNetworking module support the deployment of multiple Public IP's or would A loop need to be created for that? I see the parameter parAzFirewallCustomPublicIps but I assume this is to assign an owned range of public IPs.

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?

This is to support conenctivity through the Azure firewall to multiple SFTP sites

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?

Nothing yet.

Feature Implementation

No response

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

[gerrynicol]

I see that with further testing that parameter (parAzFirewallCustomPublicIps) does actually enable you to add additional Public IP's. Would be nice to have the names parameterised rather than using ipconfig

[gerrynicol]

To ensure the names of the custom public ips match the names of the public IP resource themselves I have added changed the hubnetworking.bicep file to

ipConfigurations: varAzFirewallUseCustomPublicIps
 ? map(parAzFirewallCustomPublicIps, ip =>
   {
    name: last(split(ip, '/'))