VPN Point To Site configuration Error

Ameeth Balla 0 Reputation points
2025-01-13T09:14:14.0666667+00:00

I have created one vnet with two subnets one for virtul machine & another for vpn gateway & also created azure cretificate for vpn but while saving it in point to site configuration it is showing this error Deployment validation failed. Additional details from the underlying API that might be helpful: The template deployment 'Microsoft.Network-20250113144202' is not valid according to the validation procedure. The tracking id is 'a79d3938-bd4b-44a1-96ae-3c8ff90d1f5a'. See inner errors for details.

Help me troubleshoot

Azure VPN Gateway
Azure VPN Gateway
An Azure service that enables the connection of on-premises networks to Azure through site-to-site virtual private networks.
1,622 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Sai Prasanna Sinde 3,410 Reputation points Microsoft Vendor
    2025-01-13T21:53:26.9266667+00:00

    Hi @Ameeth Balla

    Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

    Please go through the following points:

    • Please review all address ranges involved and make sure that there are no overlaps.
    • The subnet designated for the VPN Gateway must be named exactly GatewaySubnet. Case-sensitive, no spaces or variations.
    • The GatewaySubnet should be at least /29 or larger
    • The GatewaySubnet should be exclusively for the VPN gateway. It cannot contain any other resources like VM.
    • Make sure that the client address pool is a valid private IP address range that doesn't overlap with anything.
    • The pool must have enough addresses for your expected number of concurrent VPN users.
    • Make sure that the pool address range falls within the address range of the VNet.
    • If the root certificate isn't uploaded correctly or is in the wrong format, the validation will fail, so please re-upload your root certificate, ensuring it's in the correct format (Base-64 encoded X.509 .CER) and that you're uploading the public key, not the private key.
    • If you're using an intermediate CA, make sure the entire certificate chain is correctly established.
    • Make sure your VPN Gateway SKU matches your Point to Site requirements. Consider upgrading to VpnGw1 or higher if you need more features or capacity. Also note that basic SKU does not support IKEv2 and Radius authentication. For your reference: https://learn.microsoft.com/en-us/azure/vpn-gateway/point-to-site-about#:~:text=The%20Basic%20SKU%20has%20limitations%20and%20does%20not%20support%20IKEv2%2C%20IPv6%2C%20or%20RADIUS%20authentication.%20For%20more%20information%2C%20see%20VPN%20Gateway%20settings.
    • Please copy the Base-64 encoded certificate data excluding -----BEGIN CERTIFICATE----- and -----END CERTIFICATE-----.

    Kindly let us know if the above helps or you need further assistance on this issue.

    If you feel that your queries have been resolved, please accept the answer by clicking the "Upvote" and "Accept Answer" on the post.

    Thanks,

    Sai.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.