Forum Discussion

nitrox2000

Copper Contributor

Mar 13, 2026

Azure VM Persistent Route Setup

Hi I hope to get some advice on a routing issue from Azure to an on-premises system. A little background first, please bear with me: We have an on-premises VM that connects to an isolated Thirdpar...

Kidd_Ip

MVP

Mar 14, 2026

Persistent routes cannot be configured in Azure VMs in the same way as on-premises. In Azure, routing is managed at the network level through User Defined Routes (UDRs) and VPN Gateway configuration, rather than by static routes inside the virtual machine. The gateway address you specified (10.100.10.190) is not directly accessible from the Azure VM, which is why the persistent routes fail. To achieve the required connectivity, you must configure Azure route tables (UDRs) and ensure that the VPN Gateway advertises the appropriate on-premises subnets.

Tutorial - Create S2S VPN connection between on-premises network and Azure virtual network: Azure portal - Azure VPN Gateway | Microsoft Learn

https://learn.microsoft.com/en-us/azure/vpn-gateway/

nitrox2000

Copper Contributor

Mar 16, 2026

Thanks for your reply.

I have the S2S VPN in place and working fine and all local routes have been advertised across the VPN, for example 10.110.10.190 (10.110.10.0/24 advertised).

All local subnets are also added via the Local Network Gateway in Azure and 10.110.10.190 can ping fine from the VM.

I have added some UDR's for the additional networks but currently I'm using 10.110.10.190 as the next hop after the Virtual Appliance (Azure FW) but it is not working. I have also tried using the gateway from the VM subnet lets say Azure VM is 10.123.100.10 so I'm using 10.123.100.1 as the next hop, neither are working.

Can someone advise further as a little perplexed as I simply need to route via an onpremises IP 10.110.10.190 to 10.10.227.0/20.10.227.0/10.110.255.0 from Azure VM?

Thanks again

Nitrox