Mar 27, 2026 - For details about updated CVE-2025-53521 (BIG-IP APM vulnerability), refer to K000156741.

Lightboard Lessons: BIG-IP Deployments in Azure Cloud

In this edition of Lightboard Lessons, I cover the deployment of a BIG-IP in Azure cloud. There are a few videos associated with this topic, and each video will address a specific use case.  Topics ...
Published 6 years ago
Version 1.0
application delivery
Azure
big-ip
cloud
high availability
Jeff_Giroux_F5's avatar
Jeff_Giroux_F5
Ret. Employee
3 years ago

You will need to choose the correct affinity at the Azure LB side to maintain persistence when BIG-IP is active-active. Affinity is a separate LB setting from DSR floating IP. As for round-robin, Azure LB by default uses hash which sends to any healthy node. There is no typical round-robin. To stick to a certain BIG-IP, the source affinity will be required.

"The hash is used to route traffic to healthy backend instances within the backend pool. The algorithm provides stickiness only within a transport session. When the client starts a new session from the same source IP, the source port changes and causes the traffic to go to a different backend instance."

https://learn.microsoft.com/en-us/azure/load-balancer/distribution-mode-concepts

By default, Azure Load Balancer uses a five-tuple hash.

The five tuple includes:

  • Source IP address
  • Source port
  • Destination IP address
  • Destination port
  • IP protocol number to map flows to available servers