Hello @Mark Dayton
I think the issue is due to the load balancer distributing EAP packets across multiple upstream servers, causing fragmentation of the authorization requests. I am making some suggestions here that might I am hoping will guide you further.
One workaround for this issue is to configure the load balancer to use a consistent hashing algorithm for session affinity. This will ensure that all packets for a given session are sent to the same backend instance.
To configure session affinity in Azure Load Balancer, you can use the "hash-based" distribution mode. This mode uses a hashing algorithm to map each client IP address to a specific backend instance. You can follow the instructions in the "Configure session affinity" document to learn how to configure session affinity in Azure Load Balancer.
https://video2.skills-academy.com/en-us/azure/load-balancer/distribution-mode-concepts
Another workaround is to use a different load balancing solution that supports session affinity. For example, Azure Application Gateway supports session affinity using cookie-based or source IP-based affinity. You can follow the instructions from document https://video2.skills-academy.com/en-us/azure/application-gateway/configuration-http-settings to learn how to configure session affinity in Azure Application Gateway.
I am also thinking if this can be an option -Using a Single Backend Server?
If feasible, you could configure your load balancer to use a single backend server for handling EAP packets. This would eliminate the issue of packets being fragmented across multiple servers.
I hope this helps you resolve the issue you are facing with intermittent authorization requests.
If I have answered your query, please click "Accept as answer" as a token of appreciation