VpnGw1AZ gateway creation fails repeatedly with InternalServerError (empty error details)

I'm trying to create/recreate a route-based VPN Gateway (SKU: VpnGw1AZ, Generation2) in North Central US, and every deployment attempt fails with a generic InternalServerError and no further diagnostic detail.

Environment:

• Subscription type: MCPP Subscription
• Region: North Central US
• Gateway type: VPN, Route-based
• SKU: VpnGw1AZ (Generation2)
• Resource group: contains parentheses in name, e.g. MyRG(NEW)

Error returned (consistent across all attempts):

json

Plain Text

{"status": "Failed","error": {"code": "ResourceOperationFailure","message": "The resource operation completed with terminal provisioning state 'Failed'.","details": [{"code": "InternalServerError","message": "An error occurred."}]}}

What I've already verified/tried (all failed identically):

1. Confirmed GatewaySubnet is correctly sized (/24, well above the /27 minimum).
2. Confirmed Public IP is Standard SKU, zone-redundant (zones: null), correctly configured for an AZ SKU.
3. Deleted the gateway cleanly and recreated it from scratch via Azure CLI (az network vnet-gateway create) — same InternalServerError.
4. Created a completely new gateway with a different name and a separate, newly-created Public IP (to rule out resource-specific corruption) — same InternalServerError.
5. Tried Azure's own Support diagnostic-recommended PowerShell remediation:

powershell

Plain Text

   Get-AzVirtualNetworkGateway -ResourceGroupName "MyRG(NEW)" -Name "MyGateway" | Set-AzVirtualNetworkGateway

Same result:

Plain Text

   Set-AzVirtualNetworkGateway: Long running operation failed with status 'Failed'.
   ErrorCode: InternalServerError
   ErrorMessage: An error occurred.

This has now failed 6+ times over multiple hours across three different deployment mechanisms (CLI create, CLI delete+recreate, PowerShell PUT), ruling out configuration issues on my end.

Has anyone else hit this recently with VpnGw1AZ in North Central US? Is this a known regional/platform issue? Any guidance on working around it, or should this go straight to a support ticket?

Thanks in advance.I'm trying to create/recreate a route-based VPN Gateway (SKU: VpnGw1AZ, Generation2) in North Central US, and every deployment attempt fails with a generic InternalServerError and no further diagnostic detail.

Environment:

• Subscription type: MCPP Subscription
• Region: North Central US
• Gateway type: VPN, Route-based
• SKU: VpnGw1AZ (Generation2)
• Resource group: contains parentheses in name, e.g. MyRG(NEW)

Error returned (consistent across all attempts):

json

Plain Text

{"status": "Failed","error": {"code": "ResourceOperationFailure","message": "The resource operation completed with terminal provisioning state 'Failed'.","details": [{"code": "InternalServerError","message": "An error occurred."}]}}

What I've already verified/tried (all failed identically):

1. Confirmed GatewaySubnet is correctly sized (/24, well above the /27 minimum).
2. Confirmed Public IP is Standard SKU, zone-redundant (zones: null), correctly configured for an AZ SKU.
3. Deleted the gateway cleanly and recreated it from scratch via Azure CLI (az network vnet-gateway create) — same InternalServerError.
4. Created a completely new gateway with a different name and a separate, newly-created Public IP (to rule out resource-specific corruption) — same InternalServerError.
5. Tried Azure's own Support diagnostic-recommended PowerShell remediation:

powershell

Plain Text

   Get-AzVirtualNetworkGateway -ResourceGroupName "MyRG(NEW)" -Name "MyGateway" | Set-AzVirtualNetworkGateway

Same result:

Plain Text

   Set-AzVirtualNetworkGateway: Long running operation failed with status 'Failed'.

This has now failed 6+ times over multiple hours across three different deployment mechanisms (CLI create, CLI delete+recreate, PowerShell PUT), ruling out configuration issues on my end.

Has anyone else hit this recently with VpnGw1AZ in North Central US? Is this a known regional/platform issue? Any guidance on working around it, or should this go straight to a support ticket?

Thanks in advance.