VPN in Azure Windows Virtual Desktop two different geo environments

%3CLINGO-SUB%20id%3D%22lingo-sub-1319693%22%20slang%3D%22en-US%22%3EVPN%20in%20Azure%20Windows%20Virtual%20Desktop%20two%20different%20geo%20environments%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1319693%22%20slang%3D%22en-US%22%3E%3CP%3EDear%20All%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20created%20a%20lab%20on%20Azure%20to%20test%20WVD%20and%20have%20IPSEC%20VPN%20connected%20to%20my%20on-premises%20Lab%20as%20the%20following%3A%3C%2FP%3E%3CP%3Eon%20Azure%20There%20is%26nbsp%3B%3C%2FP%3E%3CP%3E1-%20DC02%20%7C%20%3CSTRONG%3EVirtualNetwork%3A%20(VNET01)%20Location%3A%20(East%20US)%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E2-%20WVD%20Master%20VM%20%7C%20%3CSTRONG%3EVirtualNetwork%3A%20(VNET01)%20Location%3A%20(East%20US)%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E3-%20FSLogix%20Server%20%7C%26nbsp%3B%20%3CSTRONG%3EVirtualNetwork%3A%20(VNET02)%20Location%3A%20(East%20US%202)%3C%2FSTRONG%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EDue%20to%20Azure%20limitation%20on%20cores%20and%20CPUs%20on%20the%20same%20site%20I%20had%20to%20create%20FSLogix%20on%20a%20different%20site%20and%20setup%20Peering%20between%20both%20VNETs%20which%20worked%20fine%2C%20however%20from%20VNET2%20to%20my%20On-prem%20network%20it%20didn't%20work.%20I%20tried%20the%20gateway%20transit%20option%20but%20that%20didn't%20work%20either.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20tried%20adding%20the%20subnet%20on%20my%20on-premises%20IPSEC%20Firewall%20but%20didn't%20work%20too.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EWhat%20kind%20of%20solution%20is%20possible%20to%20get%20both%20networks%20and%20get%20access%20on%20my%20On-premises%20network%3F%20I%20know%20I%20can%20open%20a%20case%20with%20MS%20to%20expand%20my%20usage%20of%20resources%20on%20the%20same%20site%20but%20I%20would%20like%20to%20know%20if%20connecting%20both%20VNETs%20to%20the%20same%20VPN%20is%20possible%20or%20not%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThank%20you%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1319693%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzureWVD%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWVD%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1321154%22%20slang%3D%22en-US%22%3ERe%3A%20VPN%20in%20Azure%20Windows%20Virtual%20Desktop%20two%20different%20geo%20environments%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1321154%22%20slang%3D%22en-US%22%3ESign%20in%20to%20the%20Azure%20portal.%3CBR%20%2F%3E%3CBR%20%2F%3EIn%20Search%20resources%2C%20service%2C%20and%20docs%20(G%2B%2F)%2C%20type%20virtual%20network.%3CBR%20%2F%3E%3CBR%20%2F%3ELocate%20Virtual%20Network%20resource%20page%3CBR%20%2F%3E%3CBR%20%2F%3ESelect%20Virtual%20Network%20from%20the%20Marketplace%20results.%3CBR%20%2F%3E%3CBR%20%2F%3ESelect%20virtual%20network%3CBR%20%2F%3E%3CBR%20%2F%3EOn%20the%20Virtual%20Network%20page%2C%20select%20Create.%3CBR%20%2F%3E%3CBR%20%2F%3Evirtual%20network%20page%3CBR%20%2F%3E%3CBR%20%2F%3EOnce%20you%20select%20Create%2C%20the%20Create%20virtual%20network%20page%20opens.%3CBR%20%2F%3E%3CBR%20%2F%3EOn%20the%20Basics%20tab%2C%20configure%20Project%20details%20and%20Instance%20details%20VNet%20settings.%3CBR%20%2F%3E%3CBR%20%2F%3EBasics%20tab%20When%20you%20fill%20in%20the%20fields%2C%20you%20see%20a%20green%20check%20mark%20when%20the%20characters%20you%20enter%20in%20the%20field%20are%20validated.%20Some%20values%20are%20autofilled%2C%20which%20you%20can%20replace%20with%20your%20own%20values%3A%3CBR%20%2F%3E%3CBR%20%2F%3ESubscription%3A%20Verify%20that%20the%20subscription%20listed%20is%20the%20correct%20one.%20You%20can%20change%20subscriptions%20by%20using%20the%20drop-down.%3CBR%20%2F%3EResource%20group%3A%20Select%20an%20existing%20resource%20group%2C%20or%20click%20Create%20new%20to%20create%20a%20new%20one.%20For%20more%20information%20about%20resource%20groups%2C%20see%20Azure%20Resource%20Manager%20overview.%3CBR%20%2F%3EName%3A%20Enter%20the%20name%20for%20your%20virtual%20network.%3CBR%20%2F%3ERegion%3A%20Select%20the%20location%20for%20your%20VNet.%20The%20location%20determines%20where%20the%20resources%20that%20you%20deploy%20to%20this%20VNet%20will%20live.%3CBR%20%2F%3EOn%20the%20IP%20Addresses%20tab%2C%20configure%20the%20values.%20The%20values%20shown%20in%20the%20examples%20below%20are%20for%20demonstration%20purposes.%20Adjust%20these%20values%20according%20to%20the%20settings%20that%20you%20require.%3C%2FLINGO-BODY%3E
Highlighted
Contributor

Dear All,

 

I have created a lab on Azure to test WVD and have IPSEC VPN connected to my on-premises Lab as the following:

on Azure There is 

1- DC02 | VirtualNetwork: (VNET01) Location: (East US)

2- WVD Master VM | VirtualNetwork: (VNET01) Location: (East US)

3- FSLogix Server |  VirtualNetwork: (VNET02) Location: (East US 2)

 

Due to Azure limitation on cores and CPUs on the same site I had to create FSLogix on a different site and setup Peering between both VNETs which worked fine, however from VNET2 to my On-prem network it didn't work. I tried the gateway transit option but that didn't work either. 

 

I tried adding the subnet on my on-premises IPSEC Firewall but didn't work too. 

 

What kind of solution is possible to get both networks and get access on my On-premises network? I know I can open a case with MS to expand my usage of resources on the same site but I would like to know if connecting both VNETs to the same VPN is possible or not?

 

Thank you

1 Reply
Highlighted
Sign in to the Azure portal.

In Search resources, service, and docs (G+/), type virtual network.

Locate Virtual Network resource page

Select Virtual Network from the Marketplace results.

Select virtual network

On the Virtual Network page, select Create.

virtual network page

Once you select Create, the Create virtual network page opens.

On the Basics tab, configure Project details and Instance details VNet settings.

Basics tab When you fill in the fields, you see a green check mark when the characters you enter in the field are validated. Some values are autofilled, which you can replace with your own values:

Subscription: Verify that the subscription listed is the correct one. You can change subscriptions by using the drop-down.
Resource group: Select an existing resource group, or click Create new to create a new one. For more information about resource groups, see Azure Resource Manager overview.
Name: Enter the name for your virtual network.
Region: Select the location for your VNet. The location determines where the resources that you deploy to this VNet will live.
On the IP Addresses tab, configure the values. The values shown in the examples below are for demonstration purposes. Adjust these values according to the settings that you require.