NetworkingInternalOperationError on new VM w/Load Balancer

Karel (Raskenlund) 0 Reputation points
2024-10-30T12:18:13.8+00:00

We've had an environment running for ~2 years but since a few days ago suddenly we can no longer launch VMs that are attached to the Load Balancer. We have not made changes to the environment.

If we set up a new VM from an image and configure it to be in the Network Load Balancer Backend Pool, the VM will fail to start with a NetworkingInternalOperationError

We tried redeploy, reapply, restart, etc. without any success.

When we set up a new VM without connecting it to the Load Balancer, it can start, and is healthy. And if we later manually connect it to the LB, all is fine.

Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
2,575 questions
Azure Load Balancer
Azure Load Balancer
An Azure service that delivers high availability and network performance to applications.
463 questions
{count} votes

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.