Virtual Network WVD

%3CLINGO-SUB%20id%3D%22lingo-sub-1179127%22%20slang%3D%22en-US%22%3EVirtual%20Network%20WVD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1179127%22%20slang%3D%22en-US%22%3EHi%20Guys%2C%3CBR%20%2F%3E%3CBR%20%2F%3ECan%20we%20use%20Azure%20VNET%20(%20S2S%20)%20when%20creating%20a%20vdi%20host%20in%20wvd%20because%20issue%20is%20the%20azure%20vnet%20is%20grayed%20out%20and%20they%20all%20are%20in%20same%20region.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20checked%20the%20wvd%20document%20and%20they%20were%20more%20emphasising%20on%20hub-%20spoke%20model.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1188228%22%20slang%3D%22en-US%22%3ERe%3A%20Virtual%20Network%20WVD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1188228%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F232508%22%20target%3D%22_blank%22%3E%40Bharat%20Chand%3C%2FA%3E%20Can%20you%20elaborate%20a%20little%20more%3F%20I%20am%20confused%20on%20what%20the%20ask%20is%20here.%20When%20deploying%20a%20there%20is%20no%20way%20that%20the%20VNET%20is%20grayed%20out%20every%20VM%20needs%20a%20VNET.%20No%20if%20you%20want%20you%20VMS%20to%20be%20in%20a%20separate%20VNET%20as%20long%20as%20those%20VMs%20can%20see%20the%20domain%20controller%20(via%20any%20kind%20of%20piering)%20it%20will%20work.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1188375%22%20slang%3D%22en-US%22%3ERe%3A%20Virtual%20Network%20WVD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1188375%22%20slang%3D%22en-US%22%3EWe%20have%20a%20vnet%20xyz%20which%20is%20connected%20to%20our%20on%20premises%20via%20S2S%20and%20when%20we%20creating%20a%20wvd%20host%20pool%20this%20vnet%20xyz%20is%20grayed%20out.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3EIs%20hub%20n%20spoke%20is%20the%20only%20way%20to%20deploy%20wvd%20host%20pool.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1194020%22%20slang%3D%22en-US%22%3ERe%3A%20Virtual%20Network%20WVD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1194020%22%20slang%3D%22en-US%22%3EThat%20is%20the%20mode%20we%20recommend.%20I%20am%20not%20sure%20on%20why%20S2S%20will%20prevent%20the%20arm%20template%20from%20picking%20up%20the%20VNET.%20When%20you%20manually%20create%20VM%20does%20it%20allow%20you%20to%20select%20xyz%20vnet.%3C%2FLINGO-BODY%3E
Occasional Contributor
Hi Guys,

Can we use Azure VNET ( S2S ) when creating a vdi host in wvd because issue is the azure vnet is grayed out and they all are in same region.

I checked the wvd document and they were more emphasising on hub- spoke model.

3 Replies

@Bharat Chand Can you elaborate a little more? I am confused on what the ask is here. When deploying a there is no way that the VNET is grayed out every VM needs a VNET. No if you want you VMS to be in a separate VNET as long as those VMs can see the domain controller (via any kind of piering) it will work.

We have a vnet xyz which is connected to our on premises via S2S and when we creating a wvd host pool this vnet xyz is grayed out.



Is hub n spoke is the only way to deploy wvd host pool.
That is the mode we recommend. I am not sure on why S2S will prevent the arm template from picking up the VNET. When you manually create VM does it allow you to select xyz vnet.