In Azure DevTest labs why are multiple Load Balancers and Public IP Addresses created?

Question

• My lab is set to have All virtual machines in one resource group.
• My network has a single virtual network with a single subnet.
• The subnet is set:
  • Use in virtual machine creation: Yes
    • Enable shared public IP: Yes
      • Allow public IP creation: No
• I am the only user of the lab for the time being.

After a while I noticed additional Availability Set, Public IP address, and Load balancer groups being created. All VMs I create for the lab are with Advanced settings to use the single Virtual network and Subnet and use Shared IP address.

My expectation is that for this lab and it's resource group there will be a single instance each of Availability Set, Public IP address, and Load balancer. And that every VM created with setting for Shared IP address will use that single set of resources.

Any idea what is triggering the creation of the additional resources?

Answer 1

Hi @Joel Kruse

As per the information you provided, it's possible that the additional resources you are seeing are being created automatically by Azure DevTest Labs. DevTest Labs can automatically create additional resources such as availability sets, public IP addresses, and load balancers when you create VMs in your lab.

When you create a VM in DevTest Labs, you can choose to use a shared IP address, which will automatically create a load balancer and assign a public IP address to the VM. If you create multiple VMs with shared IP addresses, DevTest Labs will automatically create additional load balancers and public IP addresses as needed to support the VMs.

Similarly, when you create a VM in DevTest Labs, you can choose to use an availability set, which will automatically create an availability set for the VM. If you create multiple VMs in the same availability set, DevTest Labs will automatically create additional availability sets as needed to support the VMs.

If you want to avoid the automatic creation of additional resources, you can try creating your VMs without using shared IP addresses or availability sets. Alternatively, you can try creating your VMs outside of DevTest Labs and then adding them to your lab manually.

If you are satisfied with the answer, please "Accept as Answer" and give a thumbs up, so that you can help others in the community looking for remediation for similar issues.