Exercise - Create an Azure Resource interactively with Azure PowerShell

15 minutes

In the original scenario, you must create virtual machines (VMs) to test your Customer Relationship Management (CRM) software. When a new build is available, you want to spin up a new VM to test the entire installation experience from a clean image. Once testing is complete, you can delete the VM.

Let's try the commands to create a VM.

Create a Linux VM with Azure PowerShell

Since you're using the Azure sandbox, you don't need to create a resource group. Instead, use the existing sandbox resource group [sandbox resource group name]. Be aware of the location restrictions.

Here's how to create a new Azure VM with Azure PowerShell:

Use the New-AzVM cmdlet to create the VM.
- Specify the sandbox resource group: [sandbox resource group name].
- Name the VM, following your organization's naming standards.
- Choose a location close to you from the list of available Azure sandbox locations.
  - westus2
  - southcentralus
  - centralus
  - eastus
  - westeurope
  - southeastasia
  - japaneast
  - brazilsouth
  - australiasoutheast
  - centralindia
- Use the Ubuntu Linux image: Canonical:0001-com-ubuntu-server-jammy:22_04-lts:latest.
- Use the Get-Credential cmdlet to set the VM administrator credentials.
- Add the OpenPorts parameter with port 22 for SSH access.
- Create a public IP address name for SSH sign-in.
```
$azVmParams = @{
    ResourceGroupName   = '<rgn>[sandbox resource group name]</rgn>'
    Name                = 'testvm-eus-01'
    Credential          = (Get-Credential)
    Location            = 'eastus'
    Image               = 'Canonical:0001-com-ubuntu-server-jammy:22_04-lts:latest'
    OpenPorts           = 22
    PublicIpAddressName = 'testvm-eus-01'
}
New-AzVm @azVmParams
```
Tip

You can use the Copy button to copy commands to the clipboard. To paste, right-click on a new line in the Cloud Shell terminal and select Paste, or use the Shift+Insert keyboard shortcut (⌘+V on macOS).
Enter Credentials:

When prompted, enter a username and password, following the guidelines: passwords must be 12-123 characters long and meet three of the following four complexity requirements: lowercase characters, uppercase characters, digits, and special characters (Regex match [\W_]). For more information, see Linux VM FAQ.
Wait for the VM creation:

The VM creation process takes a few minutes to finish.

Query the VM:

When complete, query the VM and assign the VM object to a variable ($vm).

$vm = Get-AzVM -Name testvm-eus-01 -ResourceGroupName <rgn>[sandbox resource group name]</rgn>

View information about the VM:

To view information about the VM, display the contents of the variable.

$vm

Example output:

ResourceGroupName : <rgn>[sandbox resource group name]</rgn>
Id                : /subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/<rgn>[sandbox resource group name]</rgn>/providers/Microsoft.Compute/virtualMachines/testvm-eus-01
VmId              : 00000000-0000-0000-0000-000000000000
Name              : testvm-eus-01
Type              : Microsoft.Compute/virtualMachines
Location          : eastus
Tags              : {}
HardwareProfile   : {VmSize}
NetworkProfile    : {NetworkInterfaces}
OSProfile         : {ComputerName, AdminUsername, LinuxConfiguration, Secrets}
ProvisioningState : Succeeded
StorageProfile    : {ImageReference, OsDisk, DataDisks}
...

Inspect VM properties:

You can inspect complex objects through the member-access operator (.). For example, to see the properties in the VMSize object associated with the HardwareProfile section, run the following command:
```
$vm.HardwareProfile
```
Or, to get information on one of the disks, run the following command:
```
$vm.StorageProfile.OsDisk
```
Get available VM sizes:

Pass the VM object into other cmdlets to get available sizes:
```
$vm | Get-AzVMSize
```

Get the public IP address:

Retrieve the public IP address to connect to the VM and store it in a variable.

$ip = Get-AzPublicIpAddress -ResourceGroupName <rgn>[sandbox resource group name]</rgn> -Name testvm-eus-01

Connect to the VM:

Connect to the VM with SSH using the IP address from the variable. For example, if the username is bob, use the following command:
```
ssh bob@$($ip.IpAddress)
```
Sign out by typing exit.

Delete a VM

To try more commands, let's delete the VM. Follow these steps:

Shut down the VM:

Run the following command:
```
Stop-AzVM -Name $vm.Name -ResourceGroupName $vm.ResourceGroupName
```
Enter Y and press Enter when prompted to continue.
Delete the VM:

Once the VM stops, delete it by running the Remove-AzVM cmdlet.
```
Remove-AzVM -Name $vm.Name -ResourceGroupName $vm.ResourceGroupName
```
Enter Y and press Enter when prompted to continue.

List all resources in the resource group:

Use the Get-AzResource cmdlet to list all the resources in the resource group. The results are piped to Select-Object to return specific properties:

Get-AzResource -ResourceGroupName $vm.ResourceGroupName | 
    Select-Object -Property Name, ResourceType, ResourceGroupName

You should see several resources, including disks, virtual networks, etc., that still exist:

Name                    ResourceType                            ResourceGroupName
----                    ------------                            -----------------
cloudshell              Microsoft.Storage/storageAccounts       <rgn>[sandbox resource group name]</rgn>
testvm-eus-01           Microsoft.Network/virtualNetworks       <rgn>[sandbox resource group name]</rgn>
testvm-eus-01           Microsoft.Network/publicIPAddresses     <rgn>[sandbox resource group name]</rgn>
testvm-eus-01           Microsoft.Network/networkSecurityGroups <rgn>[sandbox resource group name]</rgn>
testvm-eus-01           Microsoft.Network/networkInterfaces     <rgn>[sandbox resource group name]</rgn>
testvm-eus-01_OsDisk_1  Microsoft.Compute/disks                 <rgn>[sandbox resource group name]</rgn>

The Remove-AzVM command only deletes the VM. It doesn't clean up any of the other resources. To manually clean them up, follow these steps:

Delete the network interface:

Get-AzNetworkInterface -ResourceGroupName $vm.ResourceGroupName -Name $vm.Name |
    Remove-AzNetworkInterface