SOLVED

Connecting to the broker over "private links" (WVD Network Reference architecture)

%3CLINGO-SUB%20id%3D%22lingo-sub-1026453%22%20slang%3D%22en-US%22%3EConnecting%20to%20the%20broker%20over%20%22private%20links%22%20(WVD%20Network%20Reference%20architecture)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1026453%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EReading%20this%20network%20architecture%20for%20WVD%20document%20on%20github%20I%20am%20wondering%20if%20the%20author%20made%20a%20mistake.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%22WVD%20URLs%20%E2%80%93%20If%20private%20link%20is%20not%20used%20for%20the%20broker%20service%20or%20for%20all%20other%20WVD%20URLs%20these%20can%20be%20specified%20with%20*.wvd.microsoft.com%20in%20an%20NVA%20or%20using%20the%20App%20Service%20service%20tag%20built%20into%20Azure%20Firewall.%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EHow%20do%20you%20establish%20a%20private%20link%20to%20the%20WVD%20broker%3F%3F%3F%20Is%20there%20a%20step%20by%20step%20guide.%20I%20tried%20to%20create%20one%20using%26nbsp%3Bthe%20standard%20private%20link%20portal.%20But%20got%20stuck%20on%20picking%20a%20resource.%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fmicrosoft%2FWVD_Network_Reference_Architecture%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2Fmicrosoft%2FWVD_Network_Reference_Architecture%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1053081%22%20slang%3D%22en-US%22%3ERe%3A%20Connecting%20to%20the%20broker%20over%20%22private%20links%22%20(WVD%20Network%20Reference%20architecture)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1053081%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F330735%22%20target%3D%22_blank%22%3E%40dtg123%3C%2FA%3E%20-%20this%20was%20in%20a%20preview%20state%20at%20the%20time%20this%20document%20was%20written%20however%2C%20since%20its%20completion%20we%20have%20found%20an%20issue%20with%20this%20and%20are%20working%20on%20resolving%20it.%26nbsp%3B%20This%20is%20probably%20the%20challenges%20you%20are%20currently%20facing.%26nbsp%3B%20We%20will%20make%20sure%20to%20notate%20that%20in%20the%20documentation%20at%20this%20point%20and%20make%20updates%20once%20these%20bugs%20are%20worked%20out%20and%20it%20is%20deployable.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1053088%22%20slang%3D%22en-US%22%3ERe%3A%20Connecting%20to%20the%20broker%20over%20%22private%20links%22%20(WVD%20Network%20Reference%20architecture)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1053088%22%20slang%3D%22en-US%22%3EThank%20you%20%2C%20good%20to%20know%20it%20is%20a%20known%20problem.%20I%20think%20it%E2%80%99s%20really%20important%20to%20provide%20private%20connectivity%20forweb%20%2F%20windows%20%2F%20Linux%20(thin%20client%20)%20WVD%20clients.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1096837%22%20slang%3D%22en-US%22%3ERe%3A%20Connecting%20to%20the%20broker%20over%20%22private%20links%22%20(WVD%20Network%20Reference%20architecture)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1096837%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F439638%22%20target%3D%22_blank%22%3E%40BryanAshley%3C%2FA%3E%26nbsp%3B%20Hello%20Bryan%2C%20any%20update%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1097676%22%20slang%3D%22en-US%22%3ERe%3A%20Connecting%20to%20the%20broker%20over%20%22private%20links%22%20(WVD%20Network%20Reference%20architecture)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1097676%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F455094%22%20target%3D%22_blank%22%3E%40keyaertc%3C%2FA%3E%20None%20as%20of%20yet%20unfortunately%20but%20we%20do%20have%20some%20upcoming%20syncs%20with%20the%20PG%20teams%20so%20I%20will%20see%20if%20I%20can%20get%20an%20update%20on%20timelines.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1327175%22%20slang%3D%22en-US%22%3ERe%3A%20Connecting%20to%20the%20broker%20over%20%22private%20links%22%20(WVD%20Network%20Reference%20architecture)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1327175%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F439638%22%20target%3D%22_blank%22%3E%40BryanAshley%3C%2FA%3E%26nbsp%3BInterested%20in%20that%20update%20too%20if%20you've%20heard%20anything%20back%20Bryan!%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Reading this network architecture for WVD document on github I am wondering if the author made a mistake. 

"WVD URLs – If private link is not used for the broker service or for all other WVD URLs these can be specified with *.wvd.microsoft.com in an NVA or using the App Service service tag built into Azure Firewall."

How do you establish a private link to the WVD broker??? Is there a step by step guide. I tried to create one using the standard private link portal. But got stuck on picking a resource. 

https://github.com/microsoft/WVD_Network_Reference_Architecture

5 Replies
Highlighted
Best Response confirmed by dtg123 (Occasional Contributor)
Solution

@dtg123 - this was in a preview state at the time this document was written however, since its completion we have found an issue with this and are working on resolving it.  This is probably the challenges you are currently facing.  We will make sure to notate that in the documentation at this point and make updates once these bugs are worked out and it is deployable. 

Highlighted
Thank you , good to know it is a known problem. I think it’s really important to provide private connectivity forweb / windows / Linux (thin client ) WVD clients.
Highlighted
Highlighted

@keyaertc None as of yet unfortunately but we do have some upcoming syncs with the PG teams so I will see if I can get an update on timelines.

Highlighted

@BryanAshley Interested in that update too if you've heard anything back Bryan!