'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Link an Existing VM to an Azure Virtual Desktop Host Pool
Question details
The user is trying to link an existing virtual machine to an Azure Virtual Desktop (AVD) host pool after relocating it to a different resource group.
- Product
- Azure Virtual Desktop
- Device & OS
- not provided
- Scenario
- A virtual machine was moved to a new resource group, and the user needs to register it with the destination AVD host pool.
- Observed behavior
- The virtual machine fails to be added or registered to the target destination Azure Virtual Desktop host pool.
Ensure you have the necessary Azure Role-Based Access Control (RBAC) permissions, such as Desktop Virtualization Contributor, and verify that the virtual machine meets the prerequisites for the destination host pool.
Seek Specialized Support on Microsoft Q&A
Since moving a VM across resource groups and re-registering it to a host pool can involve complex backend token issues, consulting Azure experts is the recommended path.
Azure Virtual Desktop architecture relies on specific registration tokens and agent configurations. Moving a VM can orphan these connections, requiring specialized administrative steps.
Open your web browser and go to the official Microsoft Q&A community platform.
Search for and select the 'Azure Virtual Desktop' tag to ensure your question reaches the correct Azure infrastructure experts.
Provide the specifics of your issue, including the original resource group, the new resource group, and any error messages received when attempting to add the VM to the host pool.
Re-register the AVD Agent (General Troubleshooting)
Often, VMs moved between resource groups need their AVD agents reconfigured with a fresh registration token from the destination host pool.
Deploy WPS Office on Your Azure Virtual Desktops
Running virtual machines on Azure Virtual Desktop? WPS Office is a lightweight, cost-effective alternative to Microsoft Office that consumes fewer system resources, making it ideal for VDI environments. Reduce your software licensing costs while ensuring seamless productivity for your end users.
Frequently Asked Questions
Why does my VM fail to join the AVD host pool after changing resource groups?
When a VM is moved to a new resource group, its existing AVD agent registration tokens may become invalid or mismatched. The VM typically needs to have its agents cleanly uninstalled and re-registered with a new token from the destination host pool.
Can I move an active session host to a different Azure Virtual Desktop host pool directly?
No, you cannot do this directly from the Azure portal UI. You must remove the VM from the old host pool, uninstall the AVD agents from the VM itself, and reinstall them using the registration token of the new host pool.
Where can I find my Azure Virtual Desktop host pool registration key?
You can find or generate a new registration key in the Azure Portal by navigating to your Azure Virtual Desktop environment, selecting your target Host Pool, and clicking on 'Registration key' in the left-hand menu or Overview pane.
