VPN VNG - Deployment Failing in Chile Central

Question

VPN VNG - Deployment Failing in Chile Central

Suellen Ferreira 20 Microsoft Employee

We are facing a situation where a customer needs to deploy a VPN Gateway in Chile Central. Although the service is confirmed as available in the region according to Product Availability by Region, they are unable to deploy Generation 1 or Generation 2 SKUs.

Additional observations:

Gen2 SKUs are not available for selection in the Azure portal. Only Basic and Gen1 SKUs are visible.
The only SKU that could be deployed successfully was Basic, without errors.
This Basic SKU is currently being used for a PoC, but it will need to be migrated to Gen1 or Gen2 in the coming days due to Basic SKU limitations.
To further validate the issue, I attempted to deploy a VPN Gateway in my own subscription and encountered the same deployment errors. Screenshots have been added below for reference.

Error:

{

"status": "Failed",

"error": {

"code": "VmssGatewayDeploymentFailed",

"message": "The gateway deployment operation failed due to an intermittent error. Please try again.",

"details": []

}

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Hi @ Suellen Ferreira,

Welcome to Microsoft Q&A Platform

As discussed offline, the issue was encountered due to capacity constraints, as confirmed by the backend team. The issue has now been resolved after increasing the capacity.

If you are still facing any issues, please follow the steps below

Validate exactly which SKUs your subscription can see in Chile Central:

Run in Azure Cloud Shell or locally: az network vpn-gateway list-skus --location chilecentral --output table
Any Gen-2 SKUs (VpnGw2, VpnGw3, VpnGw4, etc.) will show up there if they’re ready.

Check your subscription quotas

In the portal: Subscriptions > Usage + quotas > filter by Chile Central.
Make sure you have enough Public IP and VPN gateway quota. If you don’t, request an increase:

Verify your GatewaySubnet:

It must be named exactly “GatewaySubnet” and be at least a /27 (you can go /28 if you only need one gateway, but /27 is safest). From the CLI:

az network vnet subnet show --resource-group --vnet-name --name GatewaySubnet

Retry the deployment or upgrade path If you have a Basic gateway running already, you can upgrade in-place when Gen-1/Gen-2 become available:

az network vpn-gateway update --resource-group --name --sku VpnGw1 (for Gen-1) az network vpn-gateway update --resource-group --name --sku VpnGw2 (for Gen-2, once available)

If Gen-2 still isn’t visible, you have two options: a. Deploy your Gen-2 gateway in a region that already supports it. b. Open an Azure support request to get timeline or preview-enablement in Chile Central.

Reference docs:
Troubleshoot OperationFailureErrors in Azure VPN Gateway

Azure VPN Gateway SKUs and regions

CLI quota increase request

Pleaseand “up-vote” wherever the information provided helps you, this can be beneficial to other community members.