Hello everybody,
I believe I have come across a bug with the Azure Internal Load Balancing. My situation is as follows:
- 2 ADFS servers have been created in Azure in the same subnet and dedicated Cloud Service/Domain Name
- In order to load balance/provide HA for these servers, I created an Azure Internal Load Balanced Set successfully using the following PS command:
- Add-AzureInternalLoadBalancer-ServiceName$svc-InternalLoadBalancerName$ilb–SubnetName$subnet–StaticVNetIPAddress$IP
- I then successfully added Endpoints to the 2 ADFS servers using the following PS command:
- Get-AzureVM -Name "$vm" -ServiceName "$svc" | Add-AzureEndpoint -LBSetName "$ilb" -Name "$name" -Protocol "http" -LocalPort 80 -PublicPort 80 -DefaultProbe | Update-AzureVM
- I then configured the DNS record for my ADFS service to point to the IP address assigned to the ILB, but when I navigate to the ADFS site it doesn't work at all. ADFS itself has been tested on both servers and is fully functional.
I believe this is a bug within Azure because if I look at the Preview Portal and the Load Balanced Endpoint, it reports it as a public endpointand shows me a public IP address, even though the endpoint was clearly added to an Internal Load Balancer. I have also run Get-AzureEndpoint which also shows me a Public IP address as the VIP...
If I remove the endpoint and try to add it through the Preview Portal by going to the VM>All Settings>Load Balanced Sets>Join and select Internal, it shows me the ILB I created as a selectable option but doesn't actually let me click OK.
This issue has been reproduced on my test Azure subscription also.
If anybody could assist it would be much appreciated :)
David