You can integrate the Azure Load Balancer with Cisco ISE for load balancing RADIUS traffic. However, these caveats are applicable:

• The Change of Authorization (CoA) feature is supported only if client IP preservation is enabled when you configure Session Persistence property in the load balancing rule in the Azure portal.
• Unequal load balancing might occur as the Azure Load Balancer supports only source IP affinity and does not support calling station ID-based sticky sessions.
• Traffic can be sent to a PSN even if the RADIUS service is not active on the node, because the Azure Load Balancer does not support RADIUS-based health checks.

For more information on the Azure Load Balancer, refer to What is Azure Load Balancer?.

You can integrate the Azure Load Balancer with Cisco ISE for load balancing TACACS traffic. However, traffic might be sent to a Cisco ISE PSN even if the TACACS service is not active on the node, because the Azure Load Balancer does not support health checks based on TACACS+ services.