Azure scale set how to enable outbound connectivity after adding internal load balancer?

0
votes

I found one answer which was for standalone virtual machines: "To make outgoing connections it is necessary to create a second Load Balancer with a public IP with the same backend pool and a dummy rule with a dummy probe. Once the rule is created then it will trigger the creation of an outbound SNAT."

However, it looks that this does not work with scale set. Is there any workaround for this? I have having to route traffic from Azure firewall to public load balancer.

1
azure
can you clarify this a bit, outbound* connectivity is there by default – 4c74356b41
I should have specified that the outbound connectivity in this case is internet. I can connect to virtual network just fine. Everything works well with scale set but if I add standard load balancer the internet connectivity disappears. – Kamsiinov
i dont see any evidence of what you are saying in the docs. and i dont remember my vms losing outbound connectivity – 4c74356b41
"Standard Load Balancer and Standard Public IP introduce new abilities and different behaviors to outbound connectivity." I believe this is the thing that is affecting scale set as well. – Kamsiinov
sure, but nothing in standard lb blocks outbound connectivity. docs.microsoft.com/en-us/azure/load-balancer/… – 4c74356b41

1 Answers

0
votes

I found ready made templates from someones github (https://github.com/MarekLani/AzureServiceFabricWithLoadBalancerStandard/blob/master/ServiceFabric.json). These seem to be working well for my cause.