Azure Virtual Desktop
A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
1,850 questions
We couldn't connect to the managed resource because of an orchestration error. - Error code: 0x5000056
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(80, 89%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELS%3C/text%3E%3C/svg%3E)
Leonard Schwenk
25
Reputation points
Hello,
I get the following error when I try to connect to a workspace over remote desktop subscription.
***We couldn't connect to the managed resource because of an orchestration error. If this keeps happening, contact your network administrator for assistance. - Error code: 0x5000056
I very weird because it just happends to new users, they are able to login via a downloaded .rdpw file which I can download from the https://client.wvd.microsoft.com/arm/webclient/index.html URL.
But there are not able to log in via the subscription feed of remote desktop.
I already checked if they're not a member of the workspace, but they are.
It seems like there missing a role or something.
Any help appreciated.
Azure Virtual Desktop
{count} vote
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(272, 27%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVV%3C/text%3E%3C/svg%3E)
v-vvellanki-MSFT 4,920 Reputation points Microsoft External Staff2023-11-08T12:54:39.6266667+00:00 Hi @Leonard Schwenk ,
Thanks for contacting Microsoft Q&A.The error message you're encountering, typically indicates a problem related to Windows Virtual Desktop (WVD) or Azure Virtual Desktop (AVD) orchestration.
Here are some steps you can take to troubleshoot and potentially resolve this issue:
1. User Permissions: Ensure that the affected users have the necessary permissions and roles within the Azure portal for Windows Virtual Desktop. The most common role required is the "Virtual Machine Contributor" role. Users should also have access to the specific workspace in which they are trying to connect.
2. Network Connectivity: Verify that the affected users have proper network connectivity to the Windows Virtual Desktop environment. If there are network issues or restrictions, it can lead to connectivity problems. Test the connectivity from different locations and networks if possible.
3. Client Configuration: Ensure that the affected users have a properly configured Remote Desktop client. They should use the latest version of the Remote Desktop client to connect to the Windows Virtual Desktop.
4. Validation of Workspace Membership: Double-check that the affected users are indeed members of the workspace where the resources are hosted. You mentioned you already verified this, but it's crucial to make sure there are no discrepancies.
5. Subscription and Resource Group Access: Check if the affected users have the necessary permissions at the subscription and resource group levels to access the Windows Virtual Desktop resources.
6. Azure AD Roles and Conditional Access: Review any Azure AD roles and conditional access policies that may be affecting the users' ability to access Windows Virtual Desktop resources. Ensure that there are no restrictive policies in place.
7. Azure AD Join Status: Verify if the users' devices are Azure AD joined or registered. Azure AD join is often required for Windows Virtual Desktop access, especially in scenarios where conditional access is in use.
Hope this helps you.
Sign in to comment
Sign in to answer