My app requires access to VMs (via individual public IPs) and L4 load balancing. I face an error on adding VMs; is an extra NIC needed for outbound connectivity?
hey, i think azure lb can use its frontend ip for outbound traffic if config is just rite. im curious how your NICs set up? did you try tweaking any routing rules? what peculiar errors did you get with the instance-level pubic ips?
My experience indicates that while the Azure load balancer can indeed use its frontend IP for outbound connections even when instance-level public IPs exist, careful configuration is required to avoid errors. In my case, incorrect outbound rule settings were at the root of issues when attaching VMs, which ultimately resolved when validating the association between the VMs’ NICs and the load balancing rules. An extra NIC is not necessary if all components are configured properly; it is crucial to ensure that the outbound traffic rules cater to both front-end and instance-level device settings without conflict.
i think azure can use its frontend ip if all rules are aligned properly; sometimes misconfigurations lead to errors so double check your nic routings. extra niC device isnt typically needed, though tweaking might help resolve those azure hiccups.