I'm deploying AVD hosts using BICEP, and while the deployment itself works fine, the VMs are not appearing in Entra ID under Devices. I can't log in as local Admin or AVD either. The boot diagnostics indicate that the VM is running, and I can execute PowerShell commands from Operations, so the VM seems operational. I've adjusted the typeHandlerVersion from 1.0 up to 2.2. I'm curious, how does the code determine the Tenant? Is it done automatically based on the Subscription? Here's the code I'm using for the extension: resource entraIdJoin 'Microsoft.Compute/virtualMachines/extensions@2024-03-01' = [ for i in range(0, NumberOfHosts):{ parent: VM[i] name: 'AADLoginForWindows' location: Location properties: { publisher: 'Microsoft.Azure.ActiveDirectory' type: 'AADLoginForWindows' typeHandlerVersion: '2.2' autoUpgradeMinorVersion: true enableAutomaticUpgrade: false } } ]
1 Answer
I had a similar issue when I switched to version 2.2. I could connect locally through Bastion, but the VMs still weren't showing up in Entra ID. It seems like something's going wrong with the join process itself. You might want to check the extension logs, which should be located in C:WindowsAzureLogsPlugins.
Thanks for the tip! I'll look there and see what's happening with the logs.