Share via

Unable to delete Public IP address because it is still associated with orphaned vpngwLoadBalancer after VPN Gateway deletion

Wikash Chander 25 Reputation points
2026-04-14T10:18:56.9966667+00:00

Hello,

As Thomas Meckel (https://learn.microsoft.com/en-in/answers/questions/5571096/unable-to-delete-public-ip-address-its-associated?source=docs) and Simon Jule (https://learn.microsoft.com/en-sg/answers/questions/5854810/unable-to-delete-public-ip-address-its-associated?source=docs), I'm unable to delete a public IP address which is bound to a vpngwLoadBalancer instance which is part of another subscription which I don't have access to.

However, the original VPN Gateway ithat the public UP belonged to has already been deleted successfully. In the activity log I can see that the virtualNetworkGateway delete succeeded earlier, but the Public IP remains stuck with this stale association.

Current behavior: Deleting the Public IP fails because Azure says it is still allocated to the vpngwLoadBalancer frontend IP configuration.

I have already tried:

  • deleting the resource group again
  • deleting the Public IP directly
  • checking whether the referenced resource still exists from my side
  • waiting for backend cleanup
  • CLI update attempts on the Public IP

The remaining resource in the resource group is only this Public IP.

Because this is a public forum, I am not posting full subscription and tenant details here, but I can share them privately if needed.

Important: I cannot open an Azure support request in this subscription. If this needs backend cleanup by Microsoft, could a moderator please advise how to proceed and, if needed, enable private message so I can share the full resource IDs, subscription ID, tenant ID, correlation IDs, and contact details?

Thank you.

Azure VPN Gateway
Azure VPN Gateway

An Azure service that enables the connection of on-premises networks to Azure through site-to-site virtual private networks.

Answer accepted by question author

  1. Ravi Varma Mudduluru 11,475 Reputation points Microsoft External Staff Moderator
    2026-04-23T14:49:19.5666667+00:00

    Hello @ Wikash Chander,

    Thank you for reaching out on Microsoft Q&A forum.

    The product group team has removed the associations from the PIPs on the backend, allowing the customer to delete the PIPs.Kindly let us know if the above helps or you need further assistance on this issue.

    Please "Accept the Answer" and "Upvote" if the information helped you. This will help us and others in the community as well.

    Was this answer helpful?

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Alex Burlachenko 20,825 Reputation points MVP Volunteer Moderator
    2026-04-14T14:15:22.14+00:00

    Wikash Chander hi,

    try force delete via REST (sometimes works if backend already detached partially)

    az rest --method delete
    --uri "https://management.azure.com/<PUBLIC_IP_ID>?api-version=2023-09-01"

    check if gateway is really gone

    az network vnet-gateway show --ids <GATEWAY_ID>

    if not found confirms stale backend reference

    try update Public IP to clear LB reference (rarely sticks, but worth 1 try)

    az network public-ip update
    --ids <PUBLIC_IP_ID>
    --remove ipConfiguration

    wait a bit (Azure sometimes cleans LB artifacts async), but if already waited move on

    if Public IP points to vpngwLoadBalancer in another subscription so it is 100% backend inconsistency, u cannot access or fix that resource. u said u cant open support then go via Azure portal > Help + Support > Billing / Subscription issue (free) or ask a subscription owner / admin to raise ticket

    rgds,

    Alex

    Was this answer 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.