0

I have referred to this link but that solution does not work. Basic Load Balancer with scale set "Virtual Machine Scale Set cannot use a basic SKU load balancer when singlePlacementGroup property is false (lar)."

Issue: Azure forcing to create a Standard LB instead of Basic LB. I created a VMSS with SinglePlacement Group = Enable However while creating Basic Load Balancer, Azure does not allow me to add this VMSS to the backendpool and forces me to Create a STANDARD Load balancer and says “Single Placement Group is set to False” on the VMSS. While it is not true, see attached below screenshots.

Thanks Venkat

https://i.stack.imgur.com/lRSsF.jpg
https://i.stack.imgur.com/HEV24.jpg
https://i.stack.imgur.com/iV0sQ.jpg
Venkat
  • 3
  • 1

1 Answers1

0

I tried to reproduce the same in my environment I am getting the same error as below:

enter image description here

To resolve this issue, try to recreate a virtual machine scale set in advance -> click fixed spreading and uncheck the Enable scaling beyond 100 instances

enter image description here

And networking tab check whether you have provided correct virtual network from your resources as below. I have created load balancer -> vmss -> networking tab select load balancer created backend pool

enter image description here

Created virtual machine scale set:

enter image description here

After unchecking Enable scaling beyond 100 instances -> networking -> add load balancing -> use existing -> save

enter image description here

My load balancing has been successfully added in virtual machine scale set in Basic SKU

enter image description here

Additional details, I have created separate load balancer as basic and added to virtual machine scale set and check whether you have given correct frontend Ip as public, backend pool, health probes

enter image description here

Make sure to create load balancing rules as below:

enter image description here

Reference: Virtual machine scale sets and placement groups - | Microsoft Docs

Imran
  • 3,875
  • 2
  • 3
  • 12
  • 1
    Hi Imran, You figured out a way. It is bit flaky though, you need to configure it in a certain way - first create Basic LB, then force it in VMSS (Networking). If I created VMSS first (not adding LB) and then created LB and added VMSS to bkpool, it doesn't (Either case, singlePlacementGroup was enabled). Maybe Azure team needs to be aware?? Your soln worked. Thanks! – Venkat Sep 13 '22 at 19:02