Basic LoadBalancer Upgrade - no outbound rule created

Question

The AzureBasicLoadBalancerUpgrade module used for upgrading load balancer from basic to standard sku. It doesn't seem to create outbound rule when there's no existing backend pool in the basic LB. It can create the outbound rule if there is pre-existing backendpool in the basic lb.

I know the outbound connection is implicit in the basic LB and I want to maintain the outbound connection after upgrading to standard sku. So my question is whether it's ok to create a backendpool for the standard LB using all the nics from inbound NAT rule then create a outbound rule based on the new backend pool? Is there's any security concern by doing this way?

Answer 1

Hello @James Hao

Thanks for posting your question in the Microsoft Q&A forum.

Yes, it is generally acceptable to create a backend pool using the NICs from the inbound NAT rule and then configure an outbound rule for the Standard Load Balancer. This approach ensures that outbound connectivity is maintained after the upgrade.

When upgrading an Azure Basic Load Balancer to a Standard SKU, maintaining outbound connectivity is crucial because the Standard SKU requires explicit configuration for outbound connections, unlike the Basic SKU where outbound connectivity is implicit. Your approach of creating a backend pool using all the NICs from the inbound NAT rule and then creating an outbound rule based on this backend pool is a valid and common practice.

The Microsoft link also may help you in this upgrade - https://learn.microsoft.com/en-us/azure/load-balancer/upgrade-basic-standard-with-powershell

Does the response help answer your question? Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution. Thanks 🙂

Answer 2

Hello @James Hao

I am glad I could help in this matter. Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution. Thanks! 🙂