Enabling it goes through the Azure CLI with the following command:Īz vm extension set -publisher -name AADLoginForWindows -resource-group VMTemp -vm-name DCTest123Īfter you run this command, a reboot of the VM is needed before the extension is fully deployed. Installing this extension through the GUI is not possible (probably because this is a preview feature). Enabling this for existing machines is pretty easy. Existing machinesīecause we know that this extension needs to be installed for this feature to work. There is just an extra extension ‘AADLoginForWindows’ that is installed on every VM. If you choose a template that does not contain one of the supported OS, you will receive the following error message:īut what exactly is happening in the background while we enable this? The process itself is pretty simple, there isn’t anything configured within the template itself. While creating a VM, go to the management tab and select ‘On’ next to ‘Login with AAD Credentials’. How New machinesĬonfiguring this for new machines is actually pretty easy! This preview is currently in preview for the following Operating Systems:īefore going any further: remember that this feature is still in preview and shouldn’t be used in production. This is why this announcement is pretty huge for customers that don’t have any on-prem servers (and want to avoid AADDS).
What does this mean exactly? If you want to login into a VM with AAD credentials, why don’t you just join it to Azure Active Directory? Well…, this is true for Windows 10 but this is not supported for Windows Server & Linux servers. Last Thursday a new preview feature in Azure was announced for which I was very excited about: AAD Authentication to Windows/Linux VM’s on Azure.
0 kommentar(er)
