Set-AzVirtualNetworkGateway: Long running operation failed with status 'Failed'. Additional Info:'An error occurred.'

Question

Set-AzVirtualNetworkGateway: Long running operation failed with status 'Failed'. Additional Info:'An error occurred.'

mrmnrs 30

Trying to deploy a virtual network gateway under Basic SKU with a Standard Public IP with zone redudancy using below:

$gwpip = New-AzPublicIpAddress -Name "ProdGateway-PIP" -ResourceGroupName Applications-Prod -Location "Central US" -AllocationMethod Static -Sku Standard -Zone 1,2,3

$vnet = Get-AzVirtualNetwork -Name network-prod -ResourceGroupName Applications-Prod

$subnet = Get-AzVirtualNetworkSubnetConfig -Name 'GatewaySubnet' -VirtualNetwork $vnet

$gwipconfig = New-AzVirtualNetworkGatewayIpConfig -Name prodvgwipconfig -SubnetId $subnet.Id -PublicIpAddressId $gwpip.Id

New-AzVirtualNetworkGateway -Name vNet-Gateway-Prod-PolicyBased -ResourceGroupName Applications-Prod -Location "Central US" -IpConfigurations $gwipconfig -GatewayType "Vpn" -VpnType "PolicyBased" -GatewaySku Basic

However, we are getting this error. User's image

Shows this in azure portal
User's image

Same issue when running below

Get-AzVirtualNetworkGateway -ResourceGroupName applications-prod -Name vNet-Gateway-Prod-PolicyBased | Set-AzVirtualNetworkGateway

Need help in resolving this issue

Accepted answer

0 additional answers

Your answer

Answer 1

TP 131.6K Volunteer Moderator

Hi @mrmnrs

UPDATE: I ran my script against centralus and it failed in similar way, please see screenshot below:

User's image

Text version of error:

New-AzVirtualNetworkGateway: Long running operation failed with status 'Failed'. Additional Info:'The operation failed due to following errors: 'One or more operations failed'.'
StatusCode: 200
ReasonPhrase: OK
Status: Failed
ErrorCode: OperationFailureErrors
ErrorMessage: The operation failed due to following errors: 'One or more operations failed'.

There hasn't been official announcement that Basic SKU VPN Gateway supports Standard SKU Public IP, so it is possible that it hasn't fully rolled out to all regions or maybe isn't ready for production yet.

I checked Activity Log and didn't find anything helpful in the JSON.

Have you tried adding -Debug to your New-AzVirtualNetworkGateway command? Also, have you checked activity log entries to see if there are any more details to help with troubleshooting?

I had success in westus3 region using below script:

$location = "westus3"
$resourceGroup = "basic-vnet-gateway-group"
$vnetAddressSpace = "10.20.0.0/16"
$gatewaySubnet = "10.20.0.0/27"
New-AzResourceGroup -Name $resourceGroup -Location $location
$subnetConfig = New-AzVirtualNetworkSubnetConfig -Name GatewaySubnet -AddressPrefix $gatewaySubnet
$vngwPIP = New-AzPublicIpAddress -Name myvngw-ip -ResourceGroupName $resourceGroup -Location $location -Sku Standard -AllocationMethod Static -Zone 1,2,3
$vnet = New-AzVirtualNetwork -Name myvngw-vnet -ResourceGroupName $resourceGroup -Location $location -AddressPrefix $vnetAddressSpace -Subnet $subnetConfig
$subnet = Get-AzVirtualNetworkSubnetConfig -Name GatewaySubnet -VirtualNetwork $vnet
$vngwIpConfig = New-AzVirtualNetworkGatewayIpConfig -Name vngwipconfig -SubnetId $subnet.Id -PublicIpAddressId $vngwPIP.Id
New-AzVirtualNetworkGateway -Name myvngw-gw -ResourceGroupName $resourceGroup -Location $location -IpConfigurations $vngwIpConfig -GatewayType Vpn -VpnType RouteBased -GatewaySku Basic

Please click Accept Answer and upvote if the above was helpful.Thanks.

-TP

TP 131.6K Reputation points Volunteer Moderator

2025-08-01T14:06:04.8533333+00:00

@mrmnrs Please see my update above. I ran script against centralus and it failed with a little different error.
mrmnrs 30 Reputation points

2025-08-01T14:10:56.4033333+00:00

Alrighty, I will go ahead and deploy using Basic IP address. I wanted to avoid deploying in Basic and do a migration next month.

Thank you!
TP 131.6K Reputation points Volunteer Moderator

2025-08-01T14:20:51.14+00:00

You have until end of January 2026 to migrate Basic SKU Public IP used with VPN Gateway, so there is still time. Screenshot from timeline article below:

I think they are running behind schedule. They were supposed to publish update on July 30th.
mrmnrs 30 Reputation points

2025-08-01T16:00:09.25+00:00

Got it, thank you
TP 131.6K Reputation points Volunteer Moderator

2025-08-05T16:49:34.31+00:00
The latest update published today states, in regards to Basic SKU VPN Gateway:

Your actual IP address will not change, and connectivity will not be interrupted.

An automated capability to remove the Basic public IP from your gateway will be available in Sept/Oct 2025

Deprecation timeline of Basic IP for all VPN Gateways is moved from Sep 2025 to end of Jan 2026

Because Microsoft is retiring Basic public IP resources, we’re updating the Basic VPN Gateway construct. You’ll see the Basic public IP reference as an attribute on your virtual network gateway.

If you have scripts, ARM templates, or monitoring solutions that reference the Basic public IP resource, update them to use the IP address property of the virtual network gateway instead.

No action needed at this time. I just wanted to give you latest update.

Share via

Set-AzVirtualNetworkGateway: Long running operation failed with status 'Failed'. Additional Info:'An error occurred.'

0 additional answers

Your answer