Permit Outbound Rules to reference secondary IPconfigs
Is there any plan to permit an "Outbound Rule" on an External Standard Load Balancer to reference a backend address pool that is in turn referencing a Secondary IPconfig of a Network Interface?
Currently when I try this I get the following error:
OutboundRule <outbound rule name> cannot be used with Backend Address Pool <backend pool name> that contains Secondary IPConfig <ip config name within a NIC>
I am able to reference the first (primary) IP Configuration of a NIC - but this VM (a Palo Alto firewall) has multiple IP addresses on its external interface which we wish to translate to specific public IP addresses on outbound connections.
(These IP addresses are already used by same external Load Balancer for accepting incoming connections on these addresses; so I can't simply apply these public IP addresses to the corresponding IP configurations within the NIC as this causes Azure to complain about duplication of public IP addresses.)
Not on near term roadmap.
I feel this is a must now that https://feedback.azure.com/forums/217313-networking/suggestions/40288903-support-ip-address-in-backend-pool-azure-load-bal is available in a standard load balancer. Please reconsider this.