For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Practical considerations for using Azure internal load balancer and BIG-IP

Background I recently had a scenario that required me to do some testing and I thought it would be a good opportunity to share. A user told me that he wants to put BIG-IP in Azure, but he has a few...
0151T000003lDVGQA2.jpg
Updated Feb 12, 2024
Version 4.0
Azure
cloud
MichaelOLeary's avatar
Icon for Employee rankEmployee
I'm a Solution Architect at F5. Over the years I've become an expert in Kubernetes and cloud architectures. I publish articles and blog posts to share as much knowledge as possible. I love hanging out with colleagues and customers, so reach out any time!
View Profile
MichaelOLeary's avatar
MichaelOLeary
Icon for Employee rankEmployee
Apr 19, 2020

Hi Sajid,

If you have an existing VNET, I recommend you start with a template from F5 Networks' official repo. This does deploy an External Azure Load Balancer, but you could edit the template to deploy an internal load balancer. Assuming you want an HA pair of 3-NIC devices licensed via BYOL into an existing VNET, this is the template I recommend starting with:

https://github.com/F5Networks/f5-azure-arm-templates/tree/master/supported/failover/same-net/via-lb/3nic/existing-stack/byol

 

You might deploy this template and then delete the external Load Balancer and deploy an internal Load Balancer instead, if you are uncomfortable with editing a template yourself. I am unable to customize a template specifically for your individual situation.

 

Does that make sense? You could also ask your F5 account about professional services if you need.