Active Active Advanced WAF behind Azure LB Best Practice

Its unfortunate that the mechanism available to get F5 native clustering working in Azure, using API calls, is so slow to fail over. It would make things simpler otherwise.

For that reason, i am still using a load balancer sandwich approach. This article is useful

F5 High Availability - Public Cloud Guidance DevCentral

The port address translation ability of Azure load balancer is handy. Instead of binding a secondary IP to each of my F5 for each new virtual, i can use a single pair of IP and use differing ports.

I too would value some best practice input, as the documented approaches seem far too 'workaround' for an enterprise grade product.