Azure Virtual Desktop Session Host Routing
Hi, has anyone ever set up a route table on Azure so that the route to Microsoft Login subnets goes out through Cato? When we tried doing this, to make sure our AVD users are protected by Cato, user...
Forum Discussion
Hi
We also have an Azure Virtual Desktop Environment with Internet Access over Cato.
I think you have to make sure that IP 168.63.129.16 is routed with an UDR to "Internet"
Plus what I forgot first: KMS activation IPs 20.118.99.224 and 40.83.235.53 must be routed too to "Internet"
Default route points to Cato.
Best regards,
Andy
we tried paring back to only routing the subnets below (Microsoft Login app) and still were unable to connect through the AVD FQDN. Only the subnets below were being routed through Cato and that was enough to stop authentication in its tracks. I'm going to try disabling TLS inspection to the Microsoft Login app to see if maybe that's interfering with the Windows 365 client app.
20.190.128.0/18
40.126.0.0/18
20.20.32.0/19
20.231.128.0/19
