Unable to delete public ip address. It's associated to a non existing vpngwLoadBalancer resource

Question

Unable to delete public ip address. It's associated to a non existing vpngwLoadBalancer resource

Thomas Meckel 16

As Torsten Egebirk (https://free.blessedness.top/en-in/answers/questions/5562809/unable-to-delete-public-ip-address-its-associated) I'm unable to delete public IP addresses which are bound to an orphaned (non-existing) vpngwLoadBalancer instance.

Because we have deployed those two Puplic IP addresses in a subscription that is part of a Microsoft Partner Program, there is no support contract available and I can't create a service request for getting the instances removed by Microsoft. So what is the way to proceed here?

When I follow the discussion on the thread of Torsten Egebirk's question, it seems that Microsoft removed the Public IP instances internally by a private message exchange. Is this feasible here as well?

Thomas Meckel 16 Reputation points

2025-09-30T20:30:38.6666667+00:00

@Ravi Varma Mudduluru Okay, well then I'll wait till tomorrow night, because I already tried to delete the dangling Public IP address (PIP) using Az PowerShell and Az CLI, but because the connected/associated vpngwLoadBalancer instance is located in a subscription to which I don't have any access, I simply can't de-associate this resource and delete the PIP.
Ravi Varma Mudduluru 1,790 Reputation points Microsoft External Staff Moderator

2025-09-30T20:36:43.4266667+00:00

Hello @Thomas Meckel

Thanks for the confirmation.

But you can try the below Get set command before performing the deletion tomorrow

Get-AzVirtualNetworkGateway -Name "your_resource_name" -ResourceGroupName "your_resource_group_name" | Set-AzVirtualNetworkGateway

Thanks
Thomas Meckel 16 Reputation points

2025-09-30T20:42:49.9466667+00:00

@Ravi Varma Mudduluru No I can't do this, because the VPN Gateway instance does not exist anymore. That's why this "strange" name vpngwLoadBalancer of the associated resource of the PIP is shown.

Normally you see the VPN Gateway instance name as associated resource for the PIP. But because the deletion of the VPN Gateway instance failed, some sort of cleanup process in the backend didn't run and eventually the PIP is left associated.

Well that's my personal hypothesis for this error so far. Happy to accept (hear) another explanation for this though! 😀
Ravi Varma Mudduluru 1,790 Reputation points Microsoft External Staff Moderator

2025-10-01T22:10:38.74+00:00

Hello @Thomas Meckel

Can you check and let me know if you're able to delete the Public IP?
Thomas Meckel 16 Reputation points

2025-10-01T22:33:28.16+00:00

Hi @Ravi Varma Mudduluru thanks for circling back on the topic. Bad news. Although more than 24 hours are passed since I created the dangling PIPs they still can't be deleted because they are still associated to this (orphaned) vpngwLoadBalancer.
Thomas Meckel 16 Reputation points

2025-10-01T22:35:53.5433333+00:00

Oh and when you look at the question that Torsten Egebirk opened (link on the top), you'll find someone else who's facing the same problem. Seems this is really an issue in the backplane of Azure regarding VPN Gateways.
Ravi Varma Mudduluru 1,790 Reputation points Microsoft External Staff Moderator

2025-10-01T22:37:30.7933333+00:00

Hello @Thomas Meckel

Could you follow the document I shared earlier and run the get set command?
Thomas Meckel 16 Reputation points

2025-10-01T22:44:01.1766667+00:00

@Ravi Varma Mudduluru Can you please explain to me how this should work, if the VPN Gateway, that has created this vpngwLoadBalancer association on the PIP, is already deleted. I don't even know the name of the VPN Gateway instance, because we deploy our infrastructure with Terraform and the Terraform code creates random resource names.

So what exactly should I put at the yellow marked text in the screenshot below? 🙏🏼
Ravi Varma Mudduluru 1,790 Reputation points Microsoft External Staff Moderator

2025-10-01T22:49:26.6833333+00:00

Hello @Thomas Meckel,

*/subscriptions/xxxxx-xxx-xxx-xxx/resourceGroups/xxxxxxxxxx/providers/Microsoft.Network/loadBalancers/xxxxxxxxx","resourceName":"vpngwLoadBalancer"

Your resource name is xxxxxxxx . Please add this name in yellow marked text*

PII masked
Thomas Meckel 16 Reputation points

2025-10-01T22:55:10.7333333+00:00

@Ravi Varma Mudduluru Okay, that surprises me. 😮😮 The resource group name should be what? The resource group of the PIP or the resource group where the initial VPN Gateway instance (that has been deleted) was deployed? Or something different?
Ravi Varma Mudduluru 1,790 Reputation points Microsoft External Staff Moderator

2025-10-01T23:04:10.5966667+00:00

@Thomas Meckel, Could you please check in the private message. i have shared the resource group name
Ravi Varma Mudduluru 1,790 Reputation points Microsoft External Staff Moderator

2025-10-06T10:42:03.66+00:00

Hello @Thomas Meckel,

I have requested few details in the private message could you please check and share me the requested details?

1 answer

Your answer

Thomas Meckel 16 Reputation points

2025-09-30T20:30:38.6666667+00:00

@Ravi Varma Mudduluru Okay, well then I'll wait till tomorrow night, because I already tried to delete the dangling Public IP address (PIP) using Az PowerShell and Az CLI, but because the connected/associated vpngwLoadBalancer instance is located in a subscription to which I don't have any access, I simply can't de-associate this resource and delete the PIP.
Ravi Varma Mudduluru 1,790 Reputation points Microsoft External Staff Moderator

2025-09-30T20:36:43.4266667+00:00

Hello @Thomas Meckel

Thanks for the confirmation.

But you can try the below Get set command before performing the deletion tomorrow

Get-AzVirtualNetworkGateway -Name "your_resource_name" -ResourceGroupName "your_resource_group_name" | Set-AzVirtualNetworkGateway

Thanks
Thomas Meckel 16 Reputation points

2025-09-30T20:42:49.9466667+00:00

@Ravi Varma Mudduluru No I can't do this, because the VPN Gateway instance does not exist anymore. That's why this "strange" name vpngwLoadBalancer of the associated resource of the PIP is shown.

Normally you see the VPN Gateway instance name as associated resource for the PIP. But because the deletion of the VPN Gateway instance failed, some sort of cleanup process in the backend didn't run and eventually the PIP is left associated.

Well that's my personal hypothesis for this error so far. Happy to accept (hear) another explanation for this though! 😀
Ravi Varma Mudduluru 1,790 Reputation points Microsoft External Staff Moderator

2025-10-01T22:10:38.74+00:00

Hello @Thomas Meckel

Can you check and let me know if you're able to delete the Public IP?
Thomas Meckel 16 Reputation points

2025-10-01T22:33:28.16+00:00

Hi @Ravi Varma Mudduluru thanks for circling back on the topic. Bad news. Although more than 24 hours are passed since I created the dangling PIPs they still can't be deleted because they are still associated to this (orphaned) vpngwLoadBalancer.
Thomas Meckel 16 Reputation points

2025-10-01T22:35:53.5433333+00:00

Oh and when you look at the question that Torsten Egebirk opened (link on the top), you'll find someone else who's facing the same problem. Seems this is really an issue in the backplane of Azure regarding VPN Gateways.
Ravi Varma Mudduluru 1,790 Reputation points Microsoft External Staff Moderator

2025-10-01T22:37:30.7933333+00:00

Hello @Thomas Meckel

Could you follow the document I shared earlier and run the get set command?
Thomas Meckel 16 Reputation points

2025-10-01T22:44:01.1766667+00:00

@Ravi Varma Mudduluru Can you please explain to me how this should work, if the VPN Gateway, that has created this vpngwLoadBalancer association on the PIP, is already deleted. I don't even know the name of the VPN Gateway instance, because we deploy our infrastructure with Terraform and the Terraform code creates random resource names.

So what exactly should I put at the yellow marked text in the screenshot below? 🙏🏼
Ravi Varma Mudduluru 1,790 Reputation points Microsoft External Staff Moderator

2025-10-01T22:49:26.6833333+00:00

Hello @Thomas Meckel,

*/subscriptions/xxxxx-xxx-xxx-xxx/resourceGroups/xxxxxxxxxx/providers/Microsoft.Network/loadBalancers/xxxxxxxxx","resourceName":"vpngwLoadBalancer"

Your resource name is xxxxxxxx . Please add this name in yellow marked text*

PII masked
Thomas Meckel 16 Reputation points

2025-10-01T22:55:10.7333333+00:00

@Ravi Varma Mudduluru Okay, that surprises me. 😮😮 The resource group name should be what? The resource group of the PIP or the resource group where the initial VPN Gateway instance (that has been deleted) was deployed? Or something different?
Ravi Varma Mudduluru 1,790 Reputation points Microsoft External Staff Moderator

2025-10-01T23:04:10.5966667+00:00

@Thomas Meckel, Could you please check in the private message. i have shared the resource group name
Ravi Varma Mudduluru 1,790 Reputation points Microsoft External Staff Moderator

2025-10-06T10:42:03.66+00:00

Hello @Thomas Meckel,

I have requested few details in the private message could you please check and share me the requested details?

Answer 1

Ravi Varma Mudduluru 1,790 Microsoft External Staff Moderator

Hello @Thomas Meckel,

Thanks for reaching out to Microsoft Q&A.

OP attempted the get-set command as suggested, which typically resolves this type of issue, but it did not work in this case. 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" if the information helped you. This will help us and others in the community as well.

Share via

Unable to delete public ip address. It's associated to a non existing vpngwLoadBalancer resource

1 answer

Your answer