Introduction
Azure Virtual Desktop is a managed desktop environment where an Operator Client can be deployed.
https://azure.microsoft.com/nl-nl/services/virtual-desktop/
Using IAM Access Control, using role assignments, users or groups that are allowed to use a virtual desktop session, have to be assigned one of the following roles:
- Virtual Machine User Login
- Virtual Machine Administrator Login
In the virtual host pool, the RDP properties have to be costomized in case Azure AD is usted to login:
The following property has to be added in the advanced section:
targetisaadjoined:i:1;
Now it should be possible to login with the following URL;
https://rdweb.wvd.microsoft.com/arm/webclient/index.html
When entering your Azure AD credentials, a virtual desktop will be available.
Virtual Desktop OC Shortcut
To make the Operator Client available to users, a shortcut can be created. You should log in using a Bastion Host to all VMs in the hostpool (or use an ARM template to automate the process). For this example, we assume a multisession Windows 10 is used.
Once logged in to the Virtual Machine, unzip the Delft-FEWS base build to c:/fews/bin
Run the create shortcuts command and enter de database URL and username and password in the URL.
The created shortcut should be copied to the Public/Desktop folder. Make sure the shortcut is not hidden and has the correct permissions for other users to use. This will make sure the shortcut will be visible to all users who login.
Start on Connect
To optimize costs, the Virtual Desktop can be configured to start only when a user tries to connect. Follow the following steps to create a custom role to allow starting a VM on connect.
https://docs.microsoft.com/en-us/azure/virtual-desktop/start-virtual-machine-connect
When the custom role has been assigned, the feature can be enabled as a property of the virtual host pool.
Now when connecting to the Virtual Desktop when the virtual machine is down, the first user will see a message like this:
Schedule OC downtime using Azure Automation.
Once the start on connect feature has been abled, to minimize the usage costs, a schedule should be created to shutdown the host pool virtual machines. For example, the VMs can be shutdown after working hours or on the weekend.
For more information, see:
https://docs.microsoft.com/en-us/azure/automation/automation-solution-vm-management
