Skip to content

Commit 014c2fb

Browse files
authored
Update load-balancer-common-deployment-errors.md
1 parent b90c7b7 commit 014c2fb

File tree

1 file changed

+1
-8
lines changed

1 file changed

+1
-8
lines changed

articles/load-balancer/load-balancer-common-deployment-errors.md

Lines changed: 1 addition & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -29,14 +29,7 @@ This article describes some common Azure Load Balancer deployment errors and pro
2929
|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. |
3030
|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. |
3131
|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. |
32-
|ResourceDeploymentFailure| If your load balancer is in a failed state, follow these steps to bring it back from the failed state:<ol><li>Go to https://resources.azure.com, and sign in with your Azure portal credentials.</li>
33-
<li>Select **Read/Write**.</li>
34-
<li>On the left, expand **Subscriptions**, and then expand the Subscription with the Load Balancer to update.</li>
35-
<li>Expand **ResourceGroups**, and then expand the resource group with the Load Balancer to update.</li>
36-
<li>Select **Microsoft.Network** > **LoadBalancers**, and then select the Load Balancer to update, **LoadBalancer_1**.</li>
37-
<li>On the display page for **LoadBalancer_1**, select **GET** > **Edit**.</li>
38-
<li>Update the **ProvisioningState** value from **Failed** to **Succeeded**.</li>
39-
<li>Select **PUT**.</li></ol>|
32+
|ResourceDeploymentFailure| If your load balancer is in a failed state, follow these steps to bring it back from the failed state:<ol><li>Go to https://resources.azure.com, and sign in with your Azure portal credentials.</li><li>Select **Read/Write**.</li><li>On the left, expand **Subscriptions**, and then expand the Subscription with the Load Balancer to update.</li><li>Expand **ResourceGroups**, and then expand the resource group with the Load Balancer to update.</li><li>Select **Microsoft.Network** > **LoadBalancers**, and then select the Load Balancer to update, **LoadBalancer_1**.</li><li>On the display page for **LoadBalancer_1**, select **GET** > **Edit**.</li><li>Update the **ProvisioningState** value from **Failed** to **Succeeded**.</li><li>Select **PUT**.</li></ol>|
4033
| | |
4134

4235
## Next steps

0 commit comments

Comments
 (0)