(VmssGatewayDeploymentFailed) The gateway deployment operation failed due to an intermittent error. Please try again.

alexandr 0 Reputation points
2026-11-18T12:03:14.02+00:00

It is impossible to create a support ticket with a technical issue; however, it is.

So, I'm tried to delete azure vpn gateway with Basic sku and create a new one with Gateway SKUs attempted:
VpnGw2AZ and VpnGw1AZ.

Issue description

Multiple VPN Gateway deployments have failed with the following Azure platform error:

VmssGatewayDeploymentFailed

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

Azure accepts the create/update operations, but the deployments subsequently fail after approximately 11–13 minutes.

Failed deployment attempts (UTC, November 18, 2026)

  1. VpnGw2AZ:
    • Started: 09:16:23 UTC
    • Failed: 09:27:40 UTC
    • Correlation ID: 62e5b32e-81b4-4da5-9ff5-7bf8bdaa8bc3
    VpnGw1AZ: Started: 09:38:29 UTC
      Failed: 09:51:05 UTC
    
         Correlation ID: `527b7b81-9b42-41a3-8bbb-94383e10b310`
    

The failed deployments used Generation2, Active-Active and BGP, with custom APIPA BGP peering addresses.

Previous working configuration

On November 6, 2026, a VpnGw1AZ gateway was successfully provisioned in the same region and VNet with:

Generation1

Active-Standby (activeActive = false)

BGP enabled

ASN 65010

Custom BGP addresses: 169.254.21.2 and 169.254.21.6

One Public IP configuration

Our immediate priority is to restore production VPN connectivity. We are willing to use the previously working Generation1 Active-Standby configuration.

Troubleshooting completed

Confirmed that GatewaySubnet provisioningState is Succeeded.

Confirmed that no NSG or custom route table is attached to GatewaySubnet.

Confirmed that serviceAssociationLinks and resourceNavigationLinks are null.

Confirmed that the two IP configuration references visible during the failed deployment belong to the current failed VPN Gateway resource.

Verified that the Public IP resources are Standard, Static, and configured for availability zones 1, 2, and 3.

Confirmed that the previously deployed Basic VPN Gateway was deleted through Azure CLI before the new deployment attempts.

Attempted two different AZ gateway SKUs; both failed with the same VMSS deployment error.

Requested Microsoft investigation and action

Please escalate this case to the Azure VPN Gateway / Network Resource Provider engineering team and investigate:

The internal VMSS provisioning failure details associated with both correlation IDs.

Whether regional capacity, availability-zone placement, or infrastructure allocation issues in East US are preventing gateway creation.

Whether any orphaned backend resources, stale provisioning records, or incomplete cleanup remain from the previously deleted gateway.

Whether there is a platform-side provisioning regression affecting this subscription, VNet, or gateway configuration.

Whether the previously working Generation1 Active-Standby configuration can be safely redeployed, or whether backend remediation is required first.

Business impact

Production Site-to-Site VPN connectivity between Azure and AWS cannot be restored while VPN Gateway provisioning continues to fail. This impacts cross-cloud network connectivity and requires urgent resolution.

Please review the internal deployment logs, identify the actual root cause, and advise on or perform the necessary backend remediation. We would prefer to avoid repeated blind deployment attempts in our production environment.

We can provide the full Azure Activity Log JSON records and deployment error details upon request.

Thank you.Issue description

Multiple VPN Gateway deployments have failed with the following Azure platform error:

VmssGatewayDeploymentFailed

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

Azure accepts the create/update operations, but the deployments subsequently fail after approximately 11–13 minutes.

Failed deployment attempts (UTC, November 18, 2026)

VpnGw2AZ:

Started: 09:16:23 UTC

  Failed: 09:27:40 UTC
  
     Correlation ID: `62e5b32e-81b4-4da5-9ff5-7bf8bdaa8bc3`
     
     VpnGw1AZ:
     
        Started: 09:38:29 UTC
        
           Failed: 09:51:05 UTC
           
              Correlation ID: `527b7b81-9b42-41a3-8bbb-94383e10b310`
              

The failed deployments used Generation2, Active-Active and BGP, with custom APIPA BGP peering addresses.

Previous working configuration

On November 6, 2026, a VpnGw1AZ gateway was successfully provisioned in the same region and VNet with:

Generation1

Active-Standby (activeActive = false)

BGP enabled

ASN 65010

Custom BGP addresses: 169.254.21.2 and 169.254.21.6

One Public IP configuration

Our immediate priority is to restore production VPN connectivity. We are willing to use the previously working Generation1 Active-Standby configuration.

Troubleshooting completed

Confirmed that GatewaySubnet provisioningState is Succeeded.

Confirmed that no NSG or custom route table is attached to GatewaySubnet.

Confirmed that serviceAssociationLinks and resourceNavigationLinks are null.

Confirmed that the two IP configuration references visible during the failed deployment belong to the current failed VPN Gateway resource.

Verified that the Public IP resources are Standard, Static, and configured for availability zones 1, 2, and 3.

Confirmed that the previously deployed Basic VPN Gateway was deleted through Azure CLI before the new deployment attempts.

Attempted two different AZ gateway SKUs; both failed with the same VMSS deployment error.

Requested Microsoft investigation and action

Please escalate this case to the Azure VPN Gateway / Network Resource Provider engineering team and investigate:

The internal VMSS provisioning failure details associated with both correlation IDs.

Whether regional capacity, availability-zone placement, or infrastructure allocation issues in East US are preventing gateway creation.

Whether any orphaned backend resources, stale provisioning records, or incomplete cleanup remain from the previously deleted gateway.

Whether there is a platform-side provisioning regression affecting this subscription, VNet, or gateway configuration.

Whether the previously working Generation1 Active-Standby configuration can be safely redeployed, or whether backend remediation is required first.

Business impact

Production Site-to-Site VPN connectivity between Azure and AWS cannot be restored while VPN Gateway provisioning continues to fail. This impacts cross-cloud network connectivity and requires urgent resolution.

Please review the internal deployment logs, identify the actual root cause, and advise on or perform the necessary backend remediation. We would prefer to avoid repeated blind deployment attempts in our production environment.

We can provide the full Azure Activity Log JSON records and deployment error details upon request.

Thank you.

Azure Route Server
Azure Route Server

An Azure service that enables network appliances to exchange route information with Azure virtual networks dynamically.

0 comments No comments

1 answer

Sort by: Newest
  1. AI answer

    2026-11-18T12:04:48.89+00:00

    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:

    • VpnGw1AZ supports Generation1, not Generation2.
    • VpnGw2AZ supports 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:

    1. SKU: VpnGw1AZ
    2. Generation: Generation1
    3. VPN type: RouteBased
    4. Active-active mode: Disabled
    5. Public IP: One Standard, Static public IP
    6. BGP: Enabled
    7. ASN: 65010
    8. 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 GatewaySubnet succeeded and has no NSG, route table, service association links, or resource navigation links.
    • Confirmation that the Basic gateway was deleted and that both supported VpnGw2AZ and 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:

    1. Open the affected subscription or failed virtual network gateway.
    2. Select Support + Troubleshooting.
    3. Choose Technical and select the affected subscription and VPN Gateway resource.
    4. After recommended solutions appear, select Create a support request. If redirected to solutions again, select Return to support request, then Next.
    5. Enable advanced diagnostic collection if permitted.
    6. Select the highest severity available under the support plan that reflects the production outage.
    7. 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

    1. About gateway SKUs
    2. How to configure BGP for Azure VPN Gateway (azure-powershell)
    3. Upgrade a VPN Gateway SKU
    4. VPN VNG - Deployment Failing in Chile Central - Microsoft Q&A
    5. Create an Azure support request
    6. Support and troubleshooting for Azure VPN Gateway
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.