I’ve been trying to enforce authentication with entra id credentials on on-premise servers instead of local user credentials by managing the vms using Azure Arc. It works just fine with linux servers by adding the extension aadloginforlinux but the same does not seem to be possible for windows servers. The equivalent extension aadloginforwindows does not seem to be supported on the hybrid azure arc machine. I could not find any relevant documentation for it either, only for native windows vms. Nevertheless, I used this command 

az connectedmachine extension image list –publisher Microsoft.Azure.ActiveDirectory –extension-type AADLoginForWindows –location <machinelocation> –output table

and I can see the list of available versions for the extension but when trying to install it using 

az connectedmachine extension create

it fails. Specifically it returns a null reference error when trying to retrieve the MDM ID. But this is strange to me since in this case Azure Arc is the device management solution.

​I’ve been trying to enforce authentication with entra id credentials on on-premise servers instead of local user credentials by managing the vms using Azure Arc. It works just fine with linux servers by adding the extension aadloginforlinux but the same does not seem to be possible for windows servers. The equivalent extension aadloginforwindows does not seem to be supported on the hybrid azure arc machine. I could not find any relevant documentation for it either, only for native windows vms. Nevertheless, I used this command az connectedmachine extension image list –publisher Microsoft.Azure.ActiveDirectory –extension-type AADLoginForWindows –location <machinelocation> –output tableand I can see the list of available versions for the extension but when trying to install it using az connectedmachine extension createit fails. Specifically it returns a null reference error when trying to retrieve the MDM ID. But this is strange to me since in this case Azure Arc is the device management solution.  Read More

​