Internal error when creating a VPN gateway

Question

Internal error when creating a VPN gateway

Benjamin 31

Hey all,

I am currently having a very big problem creating a VPN connection between two subscriptions.

I have created all the required resources as described by Microsoft in the docs. In the Azure Public Cloud, everything works as it should. But when I create a VPN gateway in the Azure Germany Cloud, I get a permanent "internal error" - there is no further description of the error.

When I go to the activity logs, it says as an error message "
The resource operation completed with terminal provisioning state 'Failed'".

Since I can't open a technical support ticket, as I also think it's stupid to buy a support plan for $100/month now that the Azure Germany subscription is being closed, I hope that someone has had the same problem and can tell me how they solved it.

Best regards,

Andreas Baumgarten 132.1K Reputation points MVP Volunteer Moderator

2020-12-26T09:37:26.72+00:00

Are you creating the VPN Gateway in the Azure Portal or via PowerShell?
What kind of VPN Gateway SKU are you using?

(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

Regards
Andreas Baumgarten
Benjamin 31 Reputation points

2020-12-26T12:17:53.98+00:00

Hey,

I have tried both ways, via Powershell and in the Azure Portal.
Both end with the same error.

The VPN GW SKU is "VpnGw1" and the VPN-Type is "RouteBased".
Can the SKU cause an internal error?

Best regards,
GitaraniSharma-MSFT 50,197 Reputation points Microsoft Employee Moderator

2020-12-29T10:04:43.407+00:00

Hello @Benjamin ,

May I know the address space of your Vnet where you are trying to deploy the VPN gateway?

Also make sure the subnet for the VPN gateway is named as "GatewaySubnet".
Refer : https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-vpn-gateway-settings#gwsub

VPN gateway provisioning also fails due to VNet address space overlap. You may encounter this issue when the VPN local address spaces overlap with the connected VNet address space. You mentioned you are creating a VPN connection between two subscriptions. So make sure that the address spaces of Vnets in both subscriptions are not overlapping.

Thanks,
Gita

Answer accepted by question author

Andreas Baumgarten 132.1K MVP Volunteer Moderator

The question regarding the SKU was just to make sure it's not a "special" SKU that might be not available in the sovereign German Azure region.

I think with just the "internal error" message, without any additional details, you have to open a support ticket at Microsoft.

(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

Regards
Andreas Baumgarten

0 comments

2 additional answers

Your answer

Andreas Baumgarten 132.1K Reputation points MVP Volunteer Moderator

2020-12-26T09:37:26.72+00:00

Are you creating the VPN Gateway in the Azure Portal or via PowerShell?
What kind of VPN Gateway SKU are you using?

(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

Regards
Andreas Baumgarten
Benjamin 31 Reputation points

2020-12-26T12:17:53.98+00:00

Hey,

I have tried both ways, via Powershell and in the Azure Portal.
Both end with the same error.

The VPN GW SKU is "VpnGw1" and the VPN-Type is "RouteBased".
Can the SKU cause an internal error?

Best regards,
GitaraniSharma-MSFT 50,197 Reputation points Microsoft Employee Moderator

2020-12-29T10:04:43.407+00:00

Hello @Benjamin ,

May I know the address space of your Vnet where you are trying to deploy the VPN gateway?

Also make sure the subnet for the VPN gateway is named as "GatewaySubnet".
Refer : https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-about-vpn-gateway-settings#gwsub

VPN gateway provisioning also fails due to VNet address space overlap. You may encounter this issue when the VPN local address spaces overlap with the connected VNet address space. You mentioned you are creating a VPN connection between two subscriptions. So make sure that the address spaces of Vnets in both subscriptions are not overlapping.

Thanks,
Gita

Answer 1

Benjamin Meyer 1

Hello Andreas,

After a long back and forth with Microsoft support, the deployment of the VPN gateway is working. As far as I understood, there were problems with the deployment service in the Azure Germany Cloud when deploying the VPN gateway.

So if anyone has the same problem, unfortunately the only thing that helps is to open a ticket at Microsoft.

Best regards,

0 comments

Answer 2

Benjamin 31

Hello both,

Thank you very much for trying to help me. As Andreas has already written, I have created a support ticket and now the issue is going through several departments at Microsoft - since the "normal" support is unfortunately also overwhelmed with it.

Best regards,

Andreas Baumgarten 132.1K Reputation points MVP Volunteer Moderator

2020-12-29T18:38:23.947+00:00

Maybe it's possible to post an update here when this is resolved? It would be really appreciated.
I would like to know what was/is the issue.

Kind regards
Andreas Baumgarten
Benjamin 31 Reputation points

2020-12-29T18:45:57.65+00:00

Hi Andreas,

of course, as we have found a solution, I will post it. If there is a solution that the administrator can do himself, I will try to document it in as much detail as possible.

Best regards,

Share via

Internal error when creating a VPN gateway

2 additional answers

Your answer