Forum Discussion
MicrosoftOptimizing RDP Connectivity for Windows 365
PaulCollingeis there no way to achieve this with only URLs instead of having the quality of our enterprise VDI environment reliant on an IP list that is regularly changing and needs maintained monthly like a pet?
- PaulCollingeHi,
The answer depends on the solution you're using, some VPN/SWG software allows configuration using wildcard FQDNs, where that's possible you can use *.wvd.microsoft.com. Others don't support wildcard FQDNs so you'll have to use the IP list. We're working on consolidating the IP space into a small number of subnets which won't change regularly which will resolve this particular challenge, however that will take some considerable time to complete.PaulCollingeThank you so much for the speedy response and the clarification! Apologies, it was not clear for me from the article that either the IP's OR the URL are used, but both are not needed. We are using zscaler so URLs are supported (step #b confused me since it mentioned using the IPs, but I guess that was included for informational purposes and is not required). When we create an exclusion for *.wvd.microsoft.com do we also still need to exclude 169. 254.169.254 and 168.63.129.16 or does that URL cover them as well?
If we do still exclude those 2 IPs, is there any potential for them to ever change?- PaulCollingeZscaler cannot use wildcard FQDNs in the config above, hence why IPs are used in the example. You should also include the two IPs mentioned in addition as they are both not included in the RDP IP information. I don't expect them to change as they are used pervasively within Azure.
