Azure Virtual Desktop (AVD), originally Windows Virtual Desktop (WVD), is not a repaired version of Windows Virtual PC or Hyper-V. It also does not install on your local PC, unlike VMware Workstation or VMplayer. 

Rather, AVD enables the deployment and scaling of virtualized Windows desktops and applications on Azure Windows Virtual Desktops. 

You’ve come to the right place if you want to learn more about Azure Virtual Desktop. This Getting Started Guide is ideal for IT professionals who are exploring AVD, initiating a trial with AVD, or onboarding AVD.

Consider a firm that operates from 9 a.m. to 5 p.m. Monday through Friday; throughout the day, Azure Virtual Desktop is available; however, outside of these hours (using Azure Automation Runbooks or even Scheduled Shutdowns, for example), the session hosts are shut down to decrease operating expenses.

A business user receives some urgent work on Saturday morning and attempts to connect to Azure Virtual Desktop resources to do the job; however, they cannot connect because the resources were shut down after business hours and must contact IT support to have them restarted (an alternative is obviously to leave the Virtual Machines running which may not be needed).

  1. Using ‘Start Virtual Machine on Connect,’ a Virtual Machine has started the instant the user attempts to connect.
  2. Then it lets users connect in and complete their job without having to call IT, saving money overall because the hosts are only launched when they are needed. Additionally, the functionality will only activate additional VMs (if available) after the original VM surpasses the session limit.
  3. Because this is a host-level parameter, enabling ‘Start VM on Connect’ will have an effect on all session hosts in the host pool. As a result, you cannot currently target individual Virtual Machines in a session host. This feature is now available for both the Personal and even Pooled session hosts!

How to start Azure Virtual Desktop?

  • Join the virtual machine.
  • To connect to a VM, go to the Azure site. Look for and choose Virtual machines. Choose a virtual machine from the list.
  • Select Connect at the top of the virtual machine page.
  • You need to select RDP on the Connect to virtual machine tab, and then enter the proper IP address and port number. The default IP address and port should be utilized in most circumstances. Choose Download RDP File. If the VM is configured with a just-in-time policy, you must first choose the Request access option before downloading the RDP file. See Manage virtual machine access using the just-in-time policy for additional information on this policy.
  • When asked, open the downloaded RDP file and click Connect. The warning that the .RDP file is from an unknown publisher will appear. This is to be expected. To proceed, click Connect in the Remote Desktop Connection box.
  • Select More options and then use a different account in the Windows Security window. Enter the credentials for a virtual machine account and then click OK.
  • Local account: This is normally the user name and password for the local account that you selected when you established the virtual machine. The domain is the name of the virtual machine in this example, and it is typed as VM name username.
  • Domain connected virtual machine: If the VM is part of a domain, specify the user name in the format Domain Username. The account must also be a member of the Administrators group or have been allowed remote access to the VM.
  • Domain controller: If the VM is a domain controller, provide the user name and password for the domain’s domain administrator account.
  • Select Yes to confirm the virtual machine’s identification and complete signing in.


Just go through the steps and try to be as strict as you can. You will easily be able to start the Azure Virtual Desktop in your system then.