TenantDiscoveryFailed (0x300) while connecting to AVD Client using Custom URI

Question

Dear Support Team,

I am encountering an error when attempting to connect to the Azure Virtual Desktop (AVD) client using a custom URI. The following error message is displayed:

Error Message:

Something went wrong We failed to fetch the subscription information from https://rdweb.wvd.microsoft.com/api/arm/feeddiscovery. Please contact technical support for help.

Error Details:

• Error Code: 0x300
• Error Symbolic: TenantDiscoveryFailed
• Activity ID: dda59610-cb38-4e29-82d2-1460cd830000
• Timestamp (UTC): 2024-08-05T12:33:07.71Z

Steps to Reproduce:

• Use the following custom URI to connect to the AVD client:

ms-avd:connect?workspaceId={WORKSPACE_RESOURCE_ID}&resourceid={HOST_POOL_RESOURCE_ID}&username={USER_NAME@DOMAIN}&version=0

• Replace {WORKSPACE_RESOURCE_ID}, {HOST_POOL_RESOURCE_ID}, and {USER_NAME@DOMAIN} with the appropriate values.
• Attempt to connect using the custom URI.

Additional Information: I am experiencing this issue consistently.

Network connectivity has been verified and is functioning correctly.

The AVD workspace and host pool resource IDs are confirmed to be correct.

Could you please assist in diagnosing and resolving this issue?

Thank you,

Mahesh Nikam

Answer 1

Hi.
Were anyone able to solve this issue?
We are experiencing the same problem.

We have tried several things, but the correct way (given documentation: https://learn.microsoft.com/en-us/azure/virtual-desktop/uri-scheme ) is this:

ms-avd:connect?workspaceId=WORKSPACEID&resourceid=APPLICATION_GROUP_ID&username=UPN&version=0

It does work if one subscribe and start the app manually from the remote desktop app. It also work if one starts the application from the Start menu. The application appears in the start menu of Windows after the subscription process has been done.

When trying to use ms-avd:connect we are prompted with the log in dialog, but after trying to log in we do get the error: "We failed to fetch the subscription information from https://rdweb.wvd.microsoft.com/api/arm/feeddiscovery [..].

Error Symbolic: TenandDiscoveryFailed
Error code: 0x300

We have tested this in Edge browser, Chrome browser and Powershell. We have also tested creating a new shortcut on desktop, but all attempts results in the same error. We have also tried 3 different versions of the Remote Desktop App (both from App Store, and install via MSI).

Could the problem be related to access, which roles should the user have to be able to connect? Maybe something more is needed to use this protocol?

Answer 2

ResourceId should be the ObjectID of the application within the ApplicationGroup!

Unable to find this ObjectID using the cli, but used a workaround:

Subscribe manually, and navigate to:

C:\Users\USERNAME\AppData\Local\rdclientwpf\

You will find a remote desktop shortcut to your application. That is the GUID that should be used for the "resourceid" parameter. This the object ID of the application within the application group.