Bug in Windows App? AVD/WVD/Private Link/Workspace
Hello,
Situation is this:
Both Windows App and Azure Remote Desktop are in private network.
Host pool – both communications are switched to private link – public access is disabled.
We try to use private endpoint also for workspace.
If the workspace access is disabled Windows App stops work, but the older client remote desktop correctly continues.
It look like the new Windows App use some additional URL comparing to Remote Desktop which stays public. (I am not sure whether because of DNS or communication not available inside private endpoint or both.
Do you have similar experience? Is it known bug? Is there workaround?
I did not try switch the global feed discovery to private, because our other workspaces needs be reachable publicly.
How is it with the additional security provided by moving feeds download to private network, does it make sense at all? or Is it over security?
Hello, Situation is this:Both Windows App and Azure Remote Desktop are in private network.Host pool – both communications are switched to private link – public access is disabled.We try to use private endpoint also for workspace. If the workspace access is disabled Windows App stops work, but the older client remote desktop correctly continues.It look like the new Windows App use some additional URL comparing to Remote Desktop which stays public. (I am not sure whether because of DNS or communication not available inside private endpoint or both. Do you have similar experience? Is it known bug? Is there workaround?I did not try switch the global feed discovery to private, because our other workspaces needs be reachable publicly.How is it with the additional security provided by moving feeds download to private network, does it make sense at all? or Is it over security? Read More