Windows App - Mac OS - No able to connect to Azure

Question

HI

I am using the latest version of Windows App on Mac.

When I try to connect to Azure Virtual platform using this URL. https://rdweb.wvd.microsoft.com

I get this error message "No Workspace is associated with this URL"

Also when I try to add Work or school account I get this error message

"Workspace server is unreachable

We cannot find the remote computer that contains the connection. Make sure that you typed the correct connection URL and your computer can connect to the internet."

I have previous workspace added to this app which I deleted. I suspect the Windows App still has some old configuration and trying to connect to something different

When I check Windows App log I see this line many times in the log:

"WORKSPACES(ERR): [3F818D81-553F-4337-B6AF-D3814C48F55C] Subscription failed for request ID 0 with load error: 8

/Users/runner/work/1/s/source/workspaces/libworkspaces/workspaces/workspaces_subscriber.cpp(785): OnError()

I uninstalled Windows App many times, Tried different user profile on Mac and tried to remove any files I can thing of from Mac for Windows App but still I am not able to get it to work

I tried an old version of Windows App from 2021 and that worked fine. But any version after 2022 is not connecting

I appreciate any help or guidance on this

Answer 1

Hello Firas Albazaz,

The issue you're seeing with the message “No workspace is associated with this URL” and “Workspace server is unreachable” on the Windows App for macOS typically happens when the client is either unable to discover valid published workspaces, or is caching old metadata that conflicts with updated feed settings.

Starting from versions released after 2022, the Remote Desktop client for macOS (now rebranded as Windows App) enforces more secure and structured workspace subscription mechanisms. According to Microsoft’s official macOS connection guide, the correct feed URL is https://rdweb.wvd.microsoft.com. However, if there is no valid workspace published for the signed-in user, the app will show the exact message you're seeing. This is confirmed in the same article under the "Subscribe to a workspace" section, where it explains that if the feed URL doesn’t resolve any resources, the client displays: “No workspace is associated with this email address” or fails to subscribe at all.

This is further backed by Microsoft's troubleshooting documentation, which clearly states that if you don't see any resources, you should verify whether the user is assigned to an application group and whether that app group is associated with a published workspace. If that association is missing, even if the feed URL is correct, the client cannot load anything, resulting in a silent failure or feed rejection.

Additionally, your suspicion about cached configuration interfering is valid. Microsoft also recommends clearing cached workspace and user data when strange errors persist. On macOS, simply uninstalling the app doesn’t clear workspace cache, saved tokens, or legacy connection settings. You’ll need to manually delete the app’s container data at paths like ~/Library/Containers/com.microsoft.rdc.macos, and also remove any saved credentials in Keychain Access that reference wvd.microsoft.com or Remote Desktop.

Another important clue is your mention that an older version from 2021 worked fine. That behavior is expected because pre-2022 clients used a legacy authentication model which did not enforce modern Entra ID token validation or strict MSAL-based flow. Newer versions now adhere to stricter authentication, which requires valid Entra ID assignments, a published workspace, and a clean feed subscription.

To resolve this fully, I suggest you make sure the user you're signing in with is properly assigned to an app group that is linked to a workspace in the Azure Virtual Desktop setup. Then fully clean the macOS app cache and try re-subscribing using the URL https://rdweb.wvd.microsoft.com directly. If you're in an enterprise setup, also ensure there are no Conditional Access or firewall rules blocking the app's outbound connections to Microsoft services.

Hope this information was useful for you. It would be great if you could mark the information as accepted for others having similar query on MS QnA forum can refer to it for clarity. Thanks