vpn gateway provisioning issues in west europe

Klinge 5

dears, i tried several times to setup vpn gateway in west europe - it failed repeatingly - and a small web searchs offers.... well, it sounds that ressources are limited in west europe right now. (as well as in former times for germany west...) - well, all my ressources, storages, and sqlsresists in west europe, so - when will i be able to provision that gateway - or how to setup a vpn gateway with peering, because, moving all ressources from that groups is not possible (the move assistant stated out that it is not possible for storage and sql server).
it is a S2S VPN capable Gateway, USG with nebula. it tried to follow the proces of creating, extend it with network peering (means, vpn gateway resists in germany west, the technical ressources are in west europe) - and it doesn'T work.

ChaitanyaNaykodi-MSFT 23,031 Reputation points Microsoft Employee

2024-01-20T04:02:25.0766667+00:00

@Klinge
Thank you for reaching out. I understand you are facing issue in deploying Azure VPN Gateway in West-Europe Region. I checked internally and found other customers reporting the same issue. It is an ongoing issue with VPN gateway deployments in "West-Europe" region. And the current workaround is to create your VPN gateway in another region. I understand it is not possible for you to move the resources, you can follow this tutorial here to Configure VPN gateway transit for virtual network peering. If you have already configured VPN gateway transit for virtual network peering but are still facing issue. Can you please share more details on the issue faced? Thank you!
Klinge 5 Reputation points

2024-01-21T19:36:44.6466667+00:00

Hi @ChaitanyaNaykodi-MSFT , i knew that other customers are still facing the same issue - means in common - vpn is available, but not possible. well, nice...
anyhow, it is not possible to move the ressources from a region to another because - well the moving wizard stated out that it is not possible for the sql ressource and the server ressource - so , what else?
as far as i know, vpn gateway transit is not recommended or supported by Microsoft, is it?
i will try to peer - nevertheless, are there other prcing tags on this one due to your limitations ob not been able to deploy a gateway in the correct region (this seems to be also a money maker for the stocks - we don't have ressources, but wait - peer , thats something cool for our network traffic == bills); or should i recommend to use AWS instead?
ChaitanyaNaykodi-MSFT 23,031 Reputation points Microsoft Employee

2024-01-23T00:52:44.4233333+00:00

@Klinge

Thank you for getting back.

I understand your concern here, I think it will be helpful if you could create a support request for this issue as a support engineer can through your set-up in detail and provide a more optimized solution. If you have a support plan you may file a support ticket, else could you please send an email to azcommunity@microsoft.com with the below details and I will enable a one-time free support for you in this case.

Subject : Attn Chaitanya

Thread URL: Link to this thread.

Subscription ID

Please let me know once you have done the same.

1 answer

Cedric Ahlers 15 Reputation points

2024-04-24T09:08:57.3666667+00:00
Hi @ChaitanyaNaykodi-MSFT

I'm facing the same error and was wondering if you know if your mentioned issue form January still persists ?

To be more precise the API is giving me the following error msg:

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

I have checked my Status Health and the global Azure Status, but there is no ongoing incident that's affecting Virtual Networks or Virtual Network Gateways.
Please sign in to rate this answer.
Eduardo Valderrama Murillo (AIDA) 0 Reputation points

2024-04-24T12:34:53.79+00:00

Hi @cedric Ahlers:

On my team we are having the same problem since yesterday with the same error:

Code="VmssGatewayDeploymentFailed" Message="The gateway deployment operation failed due to an intermittent error. Please try again."

Creating it by hand through the Azure interface we don't have any problems and if we create it in another region we don't have any problems either.

@ChaitanyaNaykodi-MSFT Could you help us?

Cedric Ahlers 15 Reputation points

2024-04-24T17:35:49.63+00:00

@Eduardo Valderrama Murillo (AIDA) thanks for letting me know. I first though my configuration was the reason. I saw this error yesterday the first time too, but deploying via the Portal has failed with the same error. It even fails in other Tenants. Running the terraform deployment in another region was successful, so im pretty sure it has to do with the Region.

B. CALLUY 0 Reputation points

2024-04-26T11:56:02.7566667+00:00

Hi @Cedric Ahlers
I faced exactly same issue last week.
Was resolved by creating the the VnG in North Europe, so I'd say yes.. it is still persists.
Sign in to comment