You can help support this website by buying me a coffee!
2 minutes reading time
(499 words)
Create Windows 10 Virtual Machine using Azure CLI
How to create a Windows 10 Virtual Machine using Azure CLI
In this example we are creating a Windows 10 Enterprise 21H1 VM in a resource group with an existing VNet
Resource group: prod-ukw-core-rg
VNet: prod-ukw-core-vnet
Subnet: subnet01
Before you create a Windows virtual machine using Azure CLI, you'll need to find the Publisher, Offer, SKU and Version of the VM image.
Find Azure Windows 10 Virtual Machine Image details: Publisher, Offer and SKU - TechLabs
How to find Azure Windows 10 Image details: Publisher, Offer, SKU and Version for creating Virtual Machines using Azure CLI.
az vm create options
Private IP address
Because we are not specifying a private IP using the --private-ip-address option, the VM will use dynamic IP addressing.
Public IP address
To create a VM without a public IP address, you can specify an empty variable for Public IP.
--public-ip-address ""
Azure will create a public IP address by default when you create a new VM and open port 3389 for remote desktop access. You probably don't want to do this if you already have an existing environment with remote access setup.
Directly exposing port 3389 for RDP to the Internet is a security risk that will allow brute force password attacks against your VM.
Directly exposing port 3389 for RDP to the Internet is a security risk that will allow brute force password attacks against your VM.
Network Security Group (NSG)
We are not creating a Network Security Group (NSG) for the VM because we already have an NSG attached to the VNet subnet. Again using an empty variable for nsg will create the VM without one.
--nsg ""
VNet and subnet
You can specify the Vnet name and subnet using the --vnet-name and --subnet options
If you don't specify an existing VNet and subnet, new ones will be created
You should create VNets and subnets before deploying any virtual machines
You should create VNets and subnets before deploying any virtual machines
Don't wait for commands to finish
If you add the --no-wait parameter Azure CLI will not wait for a command to finish running before accepting another command.
Using --no-wait allows you to execute multiple commands in a row. Azure CLI will continue running the command operations in the background, making it faster to deploy multiple virtual machines simultaneously.
When you use the --not-wait option, you will not see any error messages from the command output.
Storage SKU options
- Standard_LRS creates a standard hdd
- StandardSSD_LRS creates a standard ssd
- Premium_LRS creates a premium ssd
Create a VM using Azure CLI
Admin password should be wrapped in speech marks ""
# define vm variables vmName=prod-ukw-winx01 rgName=prod-ukw-core-rg image=MicrosoftWindowsDesktop:Windows-10:21h1-ent:latest adminuser=cfadmin adminpass="PASSWORD" vnetName=prod-ukw-core-vnet subnet=subnet01 storageSku=StandardSSD_LRS size=Standard_D1_v2 az vm create \ --name $vmName \ --resource-group $rgName \ --image $image \ --admin-username $adminuser \ --admin-password $adminpass \ --vnet-name $vnetName \ --subnet $subnet \ --storage-sku $storageSku \ --size $size \ --public-ip-address "" \ --nsg "" \ --no-wait
Windows 10 VM has been created with no nsg, no public IP and the VMNic is attached to Virtual network/subnet: prod-ukw-core-vnet/subnet01
Reference:
by Author
Azure CLI - az vm create
https://docs.microsoft.com/en-us/cli/azure/vm?view=azure-cli-latest#az-vm-create
Comments