An Azure service that enables network appliances to exchange route information with Azure virtual networks dynamically.
Redeploy VpnGw1AZ as Generation1, active-standby, route-based, with one Standard static public IP and BGP enabled; if that supported baseline again returns VmssGatewayDeploymentFailed, stop retrying and open an Azure technical support request for backend Network Resource Provider investigation.
Supported recovery baseline
The supported SKU matrix is important here:
-
VpnGw1AZsupports Generation1, not Generation2. -
VpnGw2AZsupports either Generation1 or Generation2. - Both support BGP and zone redundancy. ^1^
Therefore, a Generation2 VpnGw1AZ request is not a valid SKU/generation combination. The Generation2 VpnGw2AZ failure remains significant because that combination is supported.
For the immediate recovery attempt, reproduce the previously working topology with:
- SKU:
VpnGw1AZ - Generation:
Generation1 - VPN type:
RouteBased - Active-active mode: Disabled
- Public IP: One Standard, Static public IP
- BGP: Enabled
- ASN:
65010 - Azure APIPA BGP address: A unique address in
[IP Address]–[IP Address], matching the AWS-side design
An active-standby gateway has one gateway BGP peer address, while active-active has two. Custom Azure APIPA addresses must be unique across connected gateways and peer devices. With APIPA, AWS/on-premises must initiate BGP peering. ^2^
Before submitting the deployment, verify that the active-standby resource contains only one gateway IP configuration and one Azure APIPA address. Do not reuse the two-instance active-active configuration unchanged.
Do not attempt to “upgrade” the deleted Basic gateway. Basic-to-AZ migration requires deleting Basic and creating a new gateway, which has already been done in this case. ^3^
If the supported baseline fails
A further VmssGatewayDeploymentFailed on the baseline above requires Microsoft backend investigation. A similar failure in another region was confirmed by the backend team as a capacity constraint and resolved by increasing capacity, but that does not establish capacity as the cause in East US. ^4^
Microsoft Q&A cannot inspect the internal VMSS allocation logs or perform backend cleanup. Avoid further production retries and preserve the failed gateway resource and deployment records, if possible, until Support reviews them.
Include the following in the case:
- Both correlation IDs and exact UTC start/failure times.
- Subscription, resource group, VNet, gateway, and East US region.
- Complete Activity Log JSON for each failed
Microsoft.Network/virtualNetworkGateways/write. - The ARM/Bicep/CLI request payload with secrets removed.
- The exact SKU, generation, active-active setting, IP configurations, BGP ASN, and APIPA addresses for each attempt.
- Confirmation that
GatewaySubnetsucceeded and has no NSG, route table, service association links, or resource navigation links. - Confirmation that the Basic gateway was deleted and that both supported
VpnGw2AZand recovery-baseline attempts failed. - Business impact: production Azure-to-AWS S2S connectivity unavailable.
Request explicit routing to Azure VPN Gateway / Microsoft.Network Resource Provider engineering, asking Support to inspect:
- Internal VMSS provisioning details for each correlation ID.
- East US capacity and zone-placement allocation.
- Stale or orphaned gateway backend records.
- Cleanup completion from the deleted Basic gateway.
- Subscription-, VNet-, or configuration-specific provisioning failures.
Creating the technical support request
In the Azure portal:
- Open the affected subscription or failed virtual network gateway.
- Select Support + Troubleshooting.
- Choose Technical and select the affected subscription and VPN Gateway resource.
- After recommended solutions appear, select Create a support request. If redirected to solutions again, select Return to support request, then Next.
- Enable advanced diagnostic collection if permitted.
- Select the highest severity available under the support plan that reflects the production outage.
- Upload a ZIP containing the Activity Log JSON and sanitized deployment payload. ^5^
Creating a subscription-scoped request requires Owner, Contributor, Support Request Contributor, or a custom role containing Microsoft.Support/*. Technical support also requires an eligible support plan. If the option is missing despite the expected plan, ask the subscription owner or support-agreement administrator to verify that the plan is linked and that the signed-in account has access. ^5^
Also change the Q&A tag from Azure Route Server to Azure VPN Gateway; VPN Gateway is the designated tag for this product. ^6^
References