An Azure service that delivers high availability and network performance to applications.
Hi @ ADRIAN FUMERO VALDES (TES),
Welcome to Microsoft Q&A Platform.
As discussed, The behavior observed was due to a dependency created by the Azure Private DNS Resolver associated with your virtual network (it-coms-eu-w-tes-vnet01).
When a Private DNS Resolver is deployed, Azure automatically provisions and associates underlying platform-managed resources to support DNS resolution functionality. This includes internal components such as Load Balancers, which may appear under Microsoft-managed subscriptions (e.g., “MS Azure Cloud”) and are not directly visible or manageable by customers.
The Load Balancer you identified:
lbi-prod-westeurope-main-ept-xxxx
is one such platform-managed resource, used to handle DNS query routing and ensure high availability for the resolver endpoints.
Because the Private DNS Resolver endpoints were linked to your VNet, this created a dependency that made the Load Balancer appear associated with your network, even though it is owned and managed by Microsoft.
After removing the Private DNS Resolver and its associated DNS forwarding rules, the dependency was eliminated.
As a result, the related platform-managed resources were automatically cleaned up, resolving the issue.
Please
and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.