Troubleshoot common Azure deployment errors with Azure Load Balancer

This article describes some common Azure Load Balancer deployment errors and provides information to resolve the errors. If you're looking for information about an error code and that information isn't provided in this article, let us know. At the bottom of this page, you can leave feedback. The feedback is tracked with GitHub Issues.

Error codes

Error code Details and mitigation
DifferentSkuLoadBalancersAndPublicIPAddressNotAllowed Both Public IP SKU and Load Balancer SKU must match. Ensure Azure Load Balancer and Public IP SKUs match. Standard SKU is recommended for production workloads. Learn more about the differences in SKUs
DifferentSkuLoadBalancerAndPublicIPAddressNotAllowedInVMSS Virtual machine scale sets default to Basic Load Balancers when SKU is unspecified or deployed without Standard Public IPs. Re-deploy virtual machine scale set with Standard Public IPs on the individual instances to ensure Standard Load Balancer is selected or simply select a Standard LB when deploying virtual machine scale set from the Azure portal.
MaxAvailabilitySetsInLoadBalancerReached The backend pool of a Load Balancer can contain a maximum of 150 availability sets. If you don't have availability sets explicitly defined for your VMs in the backend pool, each single VM goes into its own Availability Set. So deploying 150 standalone VMs would imply that it would have 150 Availability sets, thus hitting the limit. You can deploy an availability set and add additional VMs to it as a workaround.
NetworkInterfaceAndLoadBalancerAreInDifferentAvailabilitySets For Basic Sku load balancer, network interface and load balancer have to be in the same availability set.
RulesOfSameLoadBalancerTypeUseSameBackendPortProtocolAndIPConfig You cannot have more than one rule on a given load balancer type (internal, public) with same backend port and protocol referenced by same virtual machine scale set. Update your rule to change this duplicate rule creation.
RulesOfSameLoadBalancerTypeUseSameBackendPortProtocolAndVmssIPConfig You cannot have more than one rule on a given load balancer type (internal, public) with same backend port and protocol referenced by same virtual machine scale set. Update your rule parameters to change this duplicate rule creation.
AnotherInternalLoadBalancerExists You can have only one Load Balancer of type internal reference the same set of VMs/network interfaces in the backend of the Load Balancer. Update your deployment to ensure you are creating only one Load Balancer of the same type.
CannotUseInactiveHealthProbe You cannot have a probe that's not used by any rule configured for virtual machine scale set health. Ensure that the probe that is set up is being actively used.
VMScaleSetCannotUseMultipleLoadBalancersOfSameType You cannot have multiple Load Balancers of the same type (internal, public). You can have a maximum of one internal and one public Load Balancer.
VMScaleSetCannotReferenceLoadbalancerWhenLargeScaleOrCrossAZ Basic Load Balancer is not supported for multiple-placement group virtual machine scale sets or cross-availability zone virtual machine scale set. Use Standard Load Balancer instead.
MarketplacePurchaseEligibilityFailed Switch to the correct Administrative account to enable purchases due to subscription being an EA Subscription. You can read more here.
ResourceDeploymentFailure If your load balancer is in a failed state, follow these steps to bring it back from the failed state:
  1. Go to, and sign in with your Azure portal credentials.
  2. Select Read/Write.
  3. On the left, expand Subscriptions, and then expand the Subscription with the Load Balancer to update.
  4. Expand ResourceGroups, and then expand the resource group with the Load Balancer to update.
  5. Select Microsoft.Network > LoadBalancers, and then select the Load Balancer to update, LoadBalancer_1.
  6. On the display page for LoadBalancer_1, select GET > Edit.
  7. Update the ProvisioningState value from Failed to Succeeded.
  8. Select PUT.
LoadBalancerWithoutFrontendIPCantHaveChildResources A Load Balancer resource that has no frontend IP configurations, cannot have associated child resources or components associated to it. In order to mitigate this error, add a frontend IP configuration and then add the resources you are trying to add.
LoadBalancerRuleCountLimitReachedForNic A backend pool member's network interface (virtual machine, virtual machine scale set) cannot be associated to more than 300 rules. Reduce the number of rules or leverage another Load Balancer. This limit is documented on the Load Balancer limits page.
LoadBalancerInUseByVirtualMachineScaleSet The Load Balancer resource is in use by a virtual machine scale set and cannot be deleted. Use the ARM ID provided in the error message to search for the virtual machine scale set in order to delete it.

Next steps