Azure Virtual Desktop
A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
1,763 questions
When deploying the AVD template, I encountered the issue: 'The hostname is already used by another device in this tenant?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(236.8, 20%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EY%3C/text%3E%3C/svg%3E)
Yogesh
5
Reputation points
VM has reported a failure when processing extension 'AADLoginForWindows' (publisher 'Microsoft.Azure.ActiveDirectory' and type 'AADLoginForWindows'). Error message: 'AAD Join failed with status code: -2145648509. AzureSecureVMJoinOperation: DeviceEnroller::AzureSecureVMEnroll failed 0x801c0083. The hostname is already used by another device in this tenant, please change the VM name to redeploy the extension.'. More information on troubleshooting is available at https://aka.ms/vmextensionwindowstroubleshoot. . Click here for details
But i have no hostname as same how to fix this
Azure Virtual Desktop
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 47%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMR%3C/text%3E%3C/svg%3E)
Mounika Reddy Anumandla 4,385 Reputation points Microsoft External Staff2025-04-22T06:18:38.5+00:00 Hi Yogesh,
The error message is caused by a conflict in the hostname/device name in Microsoft Entra (formerly Azure AD), even if you don't visibly see a duplicate hostname. It is caused by the previous registration. The issue here is with Resource Cleanup.
Sometimes, when VMs are destroyed and recreated, there can be delays in the release of hostnames, especially if soft-deletion is enabled for resources. Ensure that you have completely removed any previous VM instances and associated resources (NICs, storage, etc.) before deploying new VMs with the same host names. Also, go to https://entra.microsoft.com/#view/Microsoft_AAD_Devices/DevicesMenuBlade/~/Devices/menuId/Devices and delete the device from that list.
If this is urgent, you can change the VM name to something new and redeploy the extension.
Hope this helps!
Let me know if you have any further queries!
If the information is helpful, please click "upvote" to let us know.
-
Yogesh 5 Reputation points
2025-04-22T06:25:41.3366667+00:00 Hi ,
I have already done this, and it still isn't working. -
Mounika Reddy Anumandla 4,385 Reputation points Microsoft External Staff
2025-04-22T09:53:22.9833333+00:00 Hi Yogesh,
I would like to understand if you are getting the same error when you change the vm name to something new and redeploy the extension?
Please check the extension logs for more details C:\WindowsAzure\Logs\Plugins<extensionName>.- Sometimes, there may be cached device registration entries that are preventing successful enrollment. To clear these, run the following command to remove the device from Azure AD:dsregcmd /leave. Restart and run: dsregcmd /status. If it reports "AzureAdJoined: No", it’s not registered yet. If "AzureAdJoined: Yes" still appears, try running
dsregcmd /leaveand then try to join again. - Go to the VM's Extensions & applications blade. Ensure that AADLoginForWindows extension has been properly deployed. If the extension failed, try removing it and redeploying: Go to VM Extensions, find AADLoginForWindows, click Remove, and then try adding it back manually. https://learn.microsoft.com/en-us/azure/virtual-machines/extensions/features-windows#rerun-a-vm-extension
- Sometimes, the issue can be specific to the VM image or a previous deployment failure. Try deploying a new VM using a different image or configuration to see if the issue persists.
Please feel free to tag me in the comments for further queries!
- Sometimes, there may be cached device registration entries that are preventing successful enrollment. To clear these, run the following command to remove the device from Azure AD:dsregcmd /leave. Restart and run: dsregcmd /status. If it reports "AzureAdJoined: No", it’s not registered yet. If "AzureAdJoined: Yes" still appears, try running
-
Mounika Reddy Anumandla 4,385 Reputation points Microsoft External Staff
2025-04-23T04:37:48.36+00:00 Hi Yogesh,
Just checking in to see if you had a chance to review the response provided to your question.
Let me know if you have any further queries!
Sign in to comment
Sign in to answer