Azure Load Balancer and F5 Load Balancer (even when hosted in Azure as SaaS) are not the same.
Azure Load Balancer is a Microsoft-managed Layer 4 (TCP/UDP) platform service built into Azure. It handles traffic distribution at the network level and is fully managed by Microsoft, meaning customers don’t patch, update, or secure its underlying software — Microsoft does that as part of the Azure platform.
F5 Load Balancer, on the other hand, is a third-party Layer 4–7 application delivery solution. It can run as a virtual appliance in your subscription or as a SaaS service managed by F5. It offers advanced features such as SSL offloading, WAF, and custom traffic rules, but also comes with its own software stack and potential vulnerabilities.
If there is an F5 source code breach or security advisory, it only affects F5 products — not Azure Load Balancer. The two are completely separate codebases and managed by different entities.
For Azure Load Balancer, no action is required in response to an F5 issue. The only reasonable steps would be standard hygiene checks - such as monitoring diagnostic logs, and ensuring no dependency on affected F5 services - but you do not need to patch or harden Azure Load Balancer itself (that option doesn't exist to begin with)
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin