design considerations for Azure Load Balancer

%3CLINGO-SUB%20id%3D%22lingo-sub-3270305%22%20slang%3D%22en-US%22%3Edesign%20considerations%20for%20Azure%20Load%20Balancer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3270305%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3Ewe%20have%20a%20hub%20and%20spoke%20design%20of%20our%20Azure%20environment.%20We%20force%20by%20overwriting%20system%20defined%20routes%20so%20that%20any%20traffic%20to%20and%20from%20VM's%20in%20spoke%20subscriptions%20is%20routed%20via%20the%20Hub%20located%20PaloAlto%20Firewalls.%20In%20front%20of%20them%20there's%20a%20Azure%20Load%20Balancer.%20So%20for%20now%20what%20we%20do%2C%20we%20configure%20per%20each%20service%20a%20Public%20IP%20on%20the%20Load%20Balancer.%20Is%20this%20according%20with%20best%20practice%20or%20how%20to%20handle%20this%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Senior Member

Hi,

we have a hub and spoke design of our Azure environment. We force by overwriting system defined routes so that any traffic to and from VM's in spoke subscriptions is routed via the Hub located PaloAlto Firewalls. In front of them there's a Azure Load Balancer. So for now what we do, we configure per each service a Public IP on the Load Balancer. Is this according with best practice or how to handle this ?

0 Replies