Share via

load balancer of a unknow subscription using our vnet - cant delete

ADRIAN FUMERO VALDES (TES) 20 Reputation points
2026-03-24T14:01:21.9133333+00:00

Hi, we have a Load Balancer related to our vnet (it-coms-eu-w-tes-vnet01)in the subscription with name: PII

The Load Balancer have the name: lbi-prod-westeurope-main-ept-f7e1xxxxxxx

Belong to a subscription that we are not the owners:

subscriptions/xxxxxxxxxxxxxx/resourceGroups/rg-prod-westeurope-main-endpoints/providers/Microsoft.Network/loadBalancers/lbi-prod-westeurope-main-ept-f7e1xxxxxxxxb5e16a2

We did a lookup of this subscription and find that apparently belong to

MS Azure Cloud

Tenant ID: xxxxxxxxxxxxxxxxxxxx

Could you help us to identify what it´s for this resource? Why is related to our vnet? Who and what is the use of this?

Thanks in advance

Azure Load Balancer
Azure Load Balancer

An Azure service that delivers high availability and network performance to applications.

0 comments No comments

Answer accepted by question author
  1. Vallepu Venkateswarlu 6,995 Reputation points Microsoft External Staff Moderator
    2026-03-24T14:15:28.51+00:00

    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.

    Please210246-screenshot-2021-12-10-121802.pngand “up-vote” wherever the information provided helps you, this can be beneficial to other community members.


0 additional answers

Sort by: Most helpful

Your answer

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