Requirements

• Azure AD Premium
  • to use “Login with Azure AD Credentials”
  • if you are using Azure Free Trial: you will get Azure AD Basic which did not work for me (“Login with Azure AD Credentials” option was not available while creating VM)
  • If you or your company uses Microsoft 365 Business Premium or any other enterprise plan (i.e E5) then you will get “Azure AD Premium” automatically
• As of February 2021, only following VMs are supported:
  • Windows Server 2019 Datacenter (and later)
  • Windows 10 1809 and later

Points to be noted

• It is possible to create public IP address, NIC, NSG beforehand and use these while creating VM
• It is also possible to assign public IP address and open RDP port 3389 after creating VM but from my practical experience, assigning public IP later and opening RDP 3389 by creating inbound rule in NSG does not work sometimes i.e. public IP did not show up in VM, so could not connect to VM using RDP and therefore ended up deleting & provisioning VM again
• When creating VM in Azure portal using ARP template, let the ARM template create the follwoing resources
  • public IP address
  • Inbound rule (RDP 3389)
  • NIC
  • NSG
  • etc
• You can use existing storage account for VM daignostics

Windows Server 2019 as Compute VM

• Go to: https://portal.azure.com/#create/Microsoft.WindowsServer2019Datacenter-ARM
• Fillup details, especially in Management tab: check “Login with AAD credentials”
• Create

Windows 10 Pro as Jumpbox VM

• A Jumpbox VM is basically a relay VM to connect to another VM
• Jumpbox VM is needed because Azure AD joined VM can only be connected using Azure credentials from another Azure AD joined VM (that “another Azure AD joined VM” is jumpbox VM)

Creating Jumpbox VM in Azure portal

• Go to: https://portal.azure.com/#create/Microsoft.VirtualMachine-ARM
• Fillup details, especially in Management tab: check “Login with AAD credentials”
• Create

Next

• Connecting to Azure AD joined virtual machine
• Using Universal Print from Azure AD joined VM