Urgent: Need VM restarted - AVD desktop unavailable (KAVD-MUSTA-LG3)

Hello @Mustafa Ali

This forum is community-based, so we don't have access to your Azure subscription and can't restart KAVD-MUSTA-LG3 or change its RBAC permissions from here.

The E_PROXY_ORCHESTRATION_LB_NO_SESSIONHOST_AVAILABLE error, combined with the session host showing Agent status: Not Ready, means AVD currently has no healthy session host available for the connection. Since your account only has Reader access and you're receiving AuthorizationFailed, an administrator with the appropriate permissions will need to restart/deallocate-start the VM and then verify its status under Host pool → Session hosts.

Regarding permissions, Virtual Machine Contributor at the individual VM scope allows start/restart/deallocate operations, but it grants far more VM-management permissions than power operations alone.

If you only need to manage VM power state, your administrator should consider a least-privilege custom role with the required start/restart/deallocate actions rather than granting full Virtual Machine Contributor.

Reference: Microsoft – Azure built-in roles for Compute

If the VM becomes available after restart but later returns to Not Ready, investigate the underlying AVD Agent/Boot Loader, network connectivity, and AVD service connectivity rather than repeatedly restarting the VM.

Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.

The error E_PROXY_ORCHESTRATION_LB_NO_SESSIONHOST_AVAILABLE combined with the session host showing Agent Status = Not Ready indicates that Azure Virtual Desktop currently does not have a healthy session host available to broker your connection. In this state, the session host must be brought back to a healthy and available status before users can connect. [learn.microsoft.com]

A few points to note:

No one in the Microsoft Q&A community can directly restart VMs or modify permissions within your Azure subscription. Community members do not have access to customer subscriptions or resources. [learn.microsoft.com]

Since you have confirmed Reader-only access and are receiving AuthorizationFailed errors, a subscription, resource group, or VM administrator must perform the required actions on KAVD-MUSTA-LG3. [learn.microsoft.com]

1. The administrator should:
   • Perform a Stop (Deallocate) -> Start cycle on the VM.
   • Verify that the VM is running.
   • Confirm that the session host status in KAVD-HostPool-Consultants returns to Available and that the Agent Status changes from Not Ready to a healthy state.
   If the session host becomes healthy after a restart but later returns to Not Ready, the underlying issue should be investigated rather than relying on repeated restarts. Common areas to check include:
   • Azure Virtual Desktop Agent and Boot Loader services
     • VM network connectivity
       • Access to required Azure Virtual Desktop service endpoints
         • General VM health and operating system issues
2. For future self-service, your administrator could assign:
   • VM cntributor nor a custom VM operations role grants permission to assign RBAC roles. Any role assignment must still be performed by an Owner or User Access Administrator.

Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.