Forum Discussion
PowerRangers
Cirrostratus
Mar 10, 2026F5 in AZ
We are building F5 BIG-IP in Azure. Our long term intention is Active-Active or Active-Standby HA, but to kick start we are deploying a single standalone instance first. The F5 is not exposed to ...
Mar 11, 2026
Hi PowerRangers ,
Here are some pointers you can follow:
Standalone deployment:
- Backend pool should reference the F5’s Primary Self‑IP (10.1.1.10), NOT the VIP secondary IPs.
- DO NOT put the VIPs (10.1.1.11 / 10.1.1.12) in the Azure Load Balancer backend pool.
- One ALB can handle multiple VIPs == > YES — A single Azure Load Balancer can forward to multiple VIPs on the same F5.
Future Active/Standby HA:
- Both F5 devices will have the same VIP secondary IPs on their NICs (Azure requirement).
- F5 Cloud Failover Extension (CFE) or Azure LB health probes will determine which is active.
- Backend pool of Azure LB should contain Primary Self‑IPs of BOTH devices.
- Failover is handled by Azure LB + CFE (no floating IPs, no gratuitous ARP in Azure) and Azure health probes determine F5 active node
let me know if you are looking for more details.
HTH
F5 Design Engineer
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects