Microsoft Azure Virtual Desktop (AVD) offers a comprehensive desktop and app virtualization service in the cloud. It is a key tool for those preparing for the AZ-140: Configuring and Operating Microsoft Azure Virtual Desktop exam and learning to use its advanced features, such as the Start Virtual Machine on Connect, can provide significant professional advantage.
Start Virtual Machine on Connect Feature
The Start Virtual Machine on Connect feature in Azure Virtual Desktop recently came out of preview and is now generally available. This feature provides the ability to start a personal (assigned to one user) or pooled (assigned to multiple users) VM when a user connects. This is useful in scenarios where cost savings are prioritized and VMs are shut down when not in use.
Implementing the Start Virtual Machine on Connect Feature
Personal Desktop Scenario
For Personal Desktops, the “Start VM on Connect” feature can be implemented in the Azure portal. Here are the steps you need to follow:
- Navigate to the Azure Portal, and locate the Azure Virtual Desktop.
- Select the Host pools tab on the left.
- On the Host pool page, select the name of the host pool you want to modify.
- Under Settings, select Properties.
- Under Start VM on Connect, choose Enable.
Remember, this feature can only be enable if the assignment type is set to Personal.
Pooled Desktop Scenario
For Pooled Desktops, the implementation of this feature takes place during the creation of the Host Pool. Follow the below steps:
- On the Basics tab of the Create a host pool wizard, you’ll select Yes for Start VM on connect.
- After you fill out the rest of the tabs in the wizard, select Review + create to make your new host pool.
Limitations and Considerations
It’s important to know that there are a few things you should take into account with the Start VM on Connect feature.
- Require pre-login for Start VM on Connect: You can enable this for both pooled and personal desktops, but it only works for users who access their desktops via Remote Desktop clients that support it.
- Start VM on Connect is currently not supported for MSIX app attach or VMs that use the Remote Desktop REST APIs.
- For the best experience with Start VM on Connect, ensure that the maximum session limit on your host pool is set to 1.
Conclusion
The Start Virtual Machine on Connect feature allows Azure Virtual Desktop administrators to balance user accessibility with cost management goals. Understanding how to accurately implement this feature will be essential for those aiming to ace the AZ-140: Configuring and Operating Microsoft Azure Virtual Desktop exam. Not only that, but it is also a vital skill for successful and economical AVD administration in real-world scenarios. Remember that hands-on practice is fundamental to mastering these skills. Good luck with your AVD journey!
Practice Test
True/False: The Start Virtual Machine on Connect (VMOC) feature is a feature of Azure Virtual Desktop that allows a VM to start when a user logs on to its associated remote app.
– True
– False
Answer: True
Explanation: This feature provides the ability to ensure a VM is running and available when a user tries to connect to it.
What does “VMOC” stand for in the context of Azure Virtual Desktop?
– a) Virtual Machine On Connect
– b) Virtual Memory On Connect
– c) Virtual Machine On Creation
– d) Virtual Memory On Creation
Answer: a) Virtual Machine On Connect
Explanation: VMOC stands for “Virtual Machine On Connect,” a feature of Azure Virtual Desktop.
True/False: To implement the Start Virtual Machine on Connect feature, Azure Virtual Desktops should be configured with power management.
– True
– False
Answer: True
Explanation: VMs should be configured with power management to properly implement the Start Virtual Machine on Connect feature.
What is the main benefit of the Start Virtual Machine on Connect feature in Azure Virtual Desktop?
– a) It helps reduce compute costs by shutting down VMs when not in use.
– b) It ensures a VM is readily available when a user tries to connect.
– c) It allows to instantly create a VM during a connection.
– d) It improves the speed of VM creation.
Answer: b) It ensures a VM is readily available when a user tries to connect.
Explanation: The Start Virtual Machine on Connect feature mainly provides a system where a VM starts and gets ready when a user logs on.
True/False: For Start Virtual Machine on Connect rights, only the Global Administrator role is supported.
– True
– False
Answer: False
Explanation: Either Global Administrator or Windows Virtual Desktop Owner roles can be assigned for Start Virtual Machine on Connect rights.
For which Azure Virtual Desktop service environment can you use the Start Virtual Machine on Connect feature?
– a) Classic
– b) Spring 2021 update
– c) Both Classic and Spring 2021 update
– d) Neither Classic nor Spring 2021 update
Answer: b) Spring 2021 update
Explanation: As of now, the “Start Virtual Machine on Connect” feature is only available in the Spring 2021 update service environment.
True/False: The Start Virtual Machine on Connect feature can be used with both Personal and Pooled host pools.
– True
– False
Answer: True
Explanation: You can use the VM on Connect feature with both Personal host pools and Pooled host pools in Azure Virtual Desktop Services.
Which of the following roles can be assigned Start Virtual Machine on Connect rights?
– a) Virtual Machine Contributor
– b) Virtual Machine Operator
– c) Directory Reader
– d) All of the above
Answer: d) All of the above
Explanation: The VM Contributor, VM Operator, and Directory Reader roles can all be assigned Start VM on Connect rights.
True/False: When using the Start Virtual Machine on Connect feature, you cannot monitor VM activation.
– True
– False
Answer: False
Explanation: When you enable the Start Virtual Machine on Connect feature, you can use Log Analytics to monitor VM activation.
The Start Virtual Machine on Connect feature can lead to decrease in:
– a) Compute costs
– b) Storage costs
– c) Network costs
– d) All of the above
Answer: a) Compute costs
Explanation: By ensuring VMs are not continuously running, this feature can reduce compute costs.
Interview Questions
What is the “Start Virtual Machine on Connect” feature in Microsoft Azure?
The “Start Virtual Machine on Connect” feature is a service in Microsoft Azure that automatically starts up a deallocated personal desktop Virtual Machine when a user tries to connect to it.
How can you enable the Start VM on Connect feature?
The Start VM on Connect feature can be enabled through Azure PowerShell, Azure CLI, or Azure Resource Manager templates.
Which Azure PowerShell command is used to set the StartVMOnConnect feature?
The command used to set the StartVMOnConnect feature in Azure PowerShell is
Update-AzWvdHostPool -ResourceGroupName "MyResourceGroup" -Name "MyHostPool" -StartVMOnConnect $true.
What is the role of the Parameter ‘-StartVMOnConnect’ in Azure PowerShell command?
The '-StartVMOnConnect' parameter is used to enable the Start Virtual Machine on Connect feature in Azure Virtual Desktop host pools.
What permissions are needed to start a VM on connect in Azure Virtual Desktop?
Users need 'Virtual Machine Contributor' and 'Virtual Machine User Login' role assignments to start a VM on connect.
Can you implement the Start VM on Connect feature for pooled host pools?
No, the Start VM on Connect feature is only available for personal desktop host pools.
Does the Start VM on Connect feature incur additional costs?
Yes, starting of Virtual Machines could result in additional costs because you pay for the compute resources used by the machines.
Is the Start Virtual Machine on Connect feature available for all regions?
No, the feature is only available in regions that support proximity placement groups.
What is the Azure CLI command to enable the Start VM on Connect feature?
The Azure CLI command to enable the Start VM on Connect feature is
az desktopvirtualization hostpool update --resource-group "MyResourceGroup" --name "MyHostPool" --start-vm-on-connect.
Which versions of the Azure Virtual Desktop client support the Start VM on Connect feature?
The Start VM on Connect feature is supported on Azure Virtual Desktop client versions 1.2.247 or later.
How can the Start VM On Connect feature help with cost efficiency?
The Start VM On Connect feature can help with cost efficiency as it allows VMs to stay shut down when not in use, reducing costs as you only pay for the compute resources your VMs use when they're running.
Is it possible to set up the Start VM on Connect feature via the Azure Portal?
As of March 2022, it is not possible to set this feature via the Azure Portal, it needs to be done through either Azure PowerShell, Azure CLI or Azure Resource Manager templates.
Does the Start VM on Connect feature work with multi-session VMs?
No, the Start VM on Connect feature is only applicable for single-session, personal desktops.
How long does it typically take for a VM to start operating once it's triggered through Start VM on Connect?
Although the times can vary, typically it could take between 1-2 minutes for the VM to become fully operational.
Can you set the Start VM on Connect feature on a per-user basis?
No, the feature is set at the host pool level, and not on a per-user basis.
extutorials.com