Hello Emil Tsvetkov,
Greetings!
When adding new Public IPs to Azure Firewall, it's important to follow the correct configuration steps to avoid errors. If you are getting error messages during this process, the likely causes may include:
The Public IP address resource might not be correctly associated with your Azure Firewall.
The IPs being added do not meet the required criteria, such as Standard SKU or proper availability zone settings.
There could be subnet or route configuration issues that prevent the firewall from binding to the new IPs.
Azure Firewall may require a restart or redeployment to recognize changes in Public IP association.
To help you further, please share the exact message you receive when performing the addition. Double-check your resource associations and make sure all dependencies (like subnet and network settings) are correctly configured.
If you continue to face issues, try removing the problematic IP association and re-adding it after refreshing the Azure Portal or using PowerShell/Azure CLI for more detailed error feedback.
Best Regards,
Jerald Felix