Bug in Windows App? AVD/WVD/Private Link/Workspace

Occasional Reader

Hello, 

Situation is this:

Both Windows App and Azure Remote Desktop are in a private network.

The host pool communication has been switched to a private link, and public access is disabled (Both).

We are also trying to use a private endpoint for the workspace.

If workspace access is disabled, the Windows App stops working, but the older Remote Desktop client continues to work correctly.

It looks like the new Windows App uses an additional URL compared to Remote Desktop. And the URL remains public. (I am not sure if this is due to DNS, communication not being available inside the 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 need to be reachable  from outside.

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?

1 Reply

@jirimartinek 

 

Please refer below on some insights:

 

1. Additional URL usage

2. DNS and Private Endpoint

3. Global Feed Discovery