HA Ports for Standard load balancers with Public IP
Current review of HA ports only supports Internal LB without any public IP attached. The majority of NVA deployments are with Public IP attached to the LB.
Not currently in plan. We are exploring other solutions for this scenario.
Dale Renaud commented
What is the road map for this "Plan"?
André Coelho commented
Any news for this?
Hi, was there any update for this?
Azure Standard LoadBalancers with Public IP in front can't have backend pools with HA loadbalancing rule configured !!
We deployed NVA firewalls in the backend of Public IP ALB and everytime for inbound connection we have to change the config of ALB for adding new Port !!!
HA should be an option there to send all Ports to backend so backend can take care of filtering in our model firewalls
Any timeline on when this will be available? All appliances that need to have HA need this for the public IPs they expose!
Very disappointed in the new Standard Load Balancer and the fact that the HA feature can't be used externally. Based on conversations with Palo Alto and Fortinet, this was their plan to provide seamless firewall high availability without trickery.
Please fast track this feature adding HA Ports to Standard External load balancers. Maintaining more than a few public IPs with the current system is an overhead nightmare.
Jeremy Wilton commented
This is very much needed in order to use HA firewalls normally.
Raman @ MSFT commented
Thank you. We're considering this for future enhancements.
The solution with ILB is focused on the scenario with on-prem connectivity.