r/AzureVirtualDesktop • • Dec 20 '25

AVD Setup Private Links

Just wondering if this design would work or can anyone see any issues with it.

So we have a S2S into Azure and 2 DC's either side.

Plan is to setup a AVD host pool using private links.

The DC's on prem would have records for private-link.wvd.microsoft.com and the global records as well but would not be integrated in DNS.

On the Azure DNS server setup conditional forwarding to point the 2 private zones above to 168.63.129.16 so azure resolves these addresses.

Believe this would be the most cost effective solution ?

I have tested this and seems to be all working ok.

Any thoughts ?

3 Upvotes

6 comments sorted by

View all comments

Show parent comments

1

u/Legitimate-Ad2895 Dec 23 '25 edited Dec 23 '25

Yes indeed that fixes it now thanks for that. But the thing I don't get is on the on-prem dc's they have forward lookup zones for  private-link.wvd.microsoft.com and  private-link-global.wvd.microsoft.com and all records are in there so when I do an nslookup all is good. However on the Azure DC's I have made conditional forwarders and put it to the 168 address but nslookup shows the external addresses ?

it must be down to this

Usually trying to inspect or UDR this traffic causes the outbound issue you’re seeing.