Unable to delete Azure VPN gateway

Andrei 21 Reputation points
2026-08-06T18:15:20.56+00:00

Hello,

I created an Azure Virtual Network Gateway in North Europe.

The initial deployment failed with:

  • Provisioning state: Failed
  • Error code: InternalServerError

The gateway resource still exists, but I cannot update or delete it.

I have already tried:

  1. Deleting it from the Azure Portal
  2. Remove-AzVirtualNetworkGateway -Force
  3. az resource delete
  4. Re-submitting the configuration with Get-AzVirtualNetworkGateway | Set-AzVirtualNetworkGateway
  5. GET/PUT through Azure Resource Explorer

The resource temporarily changes to Updating, then returns to Failed.

Delete operations fail with InternalServerError.

Some update attempts also fail with:

ConflictError:
The current provisioning status of the gateway prevents this operation.

There are no VPN connections associated with the gateway.

The Public IP is still linked to the gateway IP configuration, so it cannot be detached or deleted separately.

Has anyone encountered this issue, and is there any supported way to force-delete or reset the gateway?

Thanks!

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.

0 comments
Answer accepted by question author
Allan Solomon Mejia 5,420 Reputation points
2026-08-06T19:08:03.5733333+00:00

Hello @Andrei

Based on the symptoms you've described, this appears to be a stuck provisioning state rather than a configuration issue.

Since the gateway is in a Failed provisioning state and every update/delete operation returns either InternalServerError or ConflictError, there isn't a supported customer-side method to force-delete or reset the resource. The resource provider (Microsoft.Network) still considers the gateway to be in an active provisioning workflow, which prevents modification or deletion.

Before opening a support request, I'd recommend verifying a few things:

  • Check Activity Log for the Virtual Network Gateway to identify the operation that failed and capture the Correlation ID and timestamp.
  • Run Get-AzVirtualNetworkGateway or az network vnet-gateway show and confirm the provisioningState and whether any background operation is still in progress.
  • Verify that no resource locks exist on the resource group or gateway.
  • If the deployment was created via ARM/Bicep/Terraform, review the deployment operation history for the original failure.

If the gateway remains stuck in the Failed state after these checks, the recommended approach is to open an Azure Support request. Microsoft can perform a backend cleanup or repair of orphaned network resources, which isn't exposed through Azure Portal, PowerShell, Azure CLI, or Azure Resource Explorer.

If you have the Correlation ID, Subscription ID, and the approximate deployment time, include those in the support request, as they'll help the Networking team locate the failed provisioning operation more quickly.

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

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

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.