Pritunl-link question on Cloud Advertisement in Azure

Pritunl Pritunl VPN
1

Now that I have pritunl-link working in both Azure and AWS, everything works except the Cloud Advertisement only for Azure. The issue that I am conflicted is the following:

I have 3 Resource Groups in Azure which hold 3 separate databases, another 3 Resource Groups for VM of different varieties, 1 Resource Group containing the VM of pritunl-link-dev-vm, and finally have my 1 last Resource Group with our vnets. I tested pritunl-link where the Cloud Advertisement worked where I had the Route Table AND the Virtual Network in the same Resource Group of let’s say pritunl-link-dev-rg. However, best practices has it where the vnets are held in 1 Resource Group where other Resource Groups can reference. The error I receive:

Oct 10 04:58:28 pritunl-link-dev-vm pritunl-link[24625]: [2025-10-10 04:58:28]
[ERRO] ▶ ipsec: Failed to update route advertisementOct 10 04:58:28 pritunl-link-
dev-vm pritunl-link[24625]: azure: Azure networks request errorOct 10 04:58:28 
pritunl-link-dev-vm pritunl-link[24625]: network.VirtualNetworksClient#Get: 
Failure responding to request: StatusCode=404 – Original Error: autorest/azure: 
Service returned an error. Status=404 Code=“ResourceNotFound” Message=“The 
Resource ‘Microsoft.Network/virtualNetworks/useast1-dev-vnet’ under resource group 
‘pritunl-link-dev-rg’ was not found. For more details please go to https://aka.ms/
ARMResourceNotFoundFix”

Is it possible in pritunl-link to input the Resource Group of where the vnet resides, or do I need to restructure my outlook of Resource Groups in Azure?

2

This has been added with the command sudo pritunl-link azure-net-resource-group <resource_group_name>. The release is currently in the unstable repository it will be moved to the stable repository next week.

1 Like
3

Perfect! Will wait on this feature to be in stable so I can upgrade our pritunl-links!