SQL Server 2017 AlwaysOn in Azure on VMs
When in Azure, do I also need a load balancer for the windows cluster with a probe port? I have a SQL Server listener and in the Azure portal I created a LoadBalancer with probe port of 59999, however when I attempt to perform a fail-over from SQL1 -> to -> SQL2 the availability group hangs and does not fail over without me having to open cluster manager and bring resources online. I think this might be due to the windows cluster not having a probe port and being under a load balancer.
Can anybody confirm this and point me to some good articles on the proper way to create an AlwaysOn Availability Group in Azure.