Azure CLI and Cloud Shell - Step-by-Step Execution

Process Flow - Azure CLI and Cloud Shell

Start Cloud Shell

↓

Choose Shell Type

↓

Initialize Environment

↓

Run Azure CLI Commands

↓

Receive Command Output

↓

Continue or Exit Shell

This flow shows how you start Azure Cloud Shell, choose your shell type, run Azure CLI commands, and get outputs.

Execution Sample

Azure

az group create --name MyResourceGroup --location eastus
az vm list --resource-group MyResourceGroup

Creates a resource group named MyResourceGroup in eastus, then lists VMs in that group.

Process Table

Step	Action	Command	Result	Notes
1	Start Cloud Shell	N/A	Cloud Shell environment ready	User opens Cloud Shell in browser or portal
2	Choose Shell Type	Select Bash or PowerShell	Shell environment initialized	User picks preferred shell
3	Run Command	az group create --name MyResourceGroup --location eastus	Resource group created	Azure confirms creation
4	Run Command	az vm list --resource-group MyResourceGroup	Empty list []	No VMs yet in the group
5	Exit Shell	exit	Shell session ends	User closes Cloud Shell
6	End	N/A	Session closed	No further commands

💡 User exits Cloud Shell or closes session

Status Tracker

Variable	Start	After Step 3	After Step 4	Final
CloudShellStatus	Not started	Running	Running	Closed
ResourceGroup	None	MyResourceGroup created	MyResourceGroup exists	MyResourceGroup exists
VMList	None	None	Empty list []	Empty list []

Key Moments - 2 Insights

Why does the VM list show empty after creating the resource group?

Because creating a resource group does not create any VMs. The execution_table row 4 shows the VM list command returns an empty list.

What happens if you close the browser tab without typing 'exit'?

The Cloud Shell session ends anyway, as shown in execution_table row 5 and 6, the session closes when the user leaves.

Visual Quiz - 3 Questions

Look at the execution_table, what is the result of running 'az group create' command at step 3?

A Shell environment initialized

B Resource group created

C Empty list []

D Shell session ends

💡 Hint

Check execution_table row 3 under Result column

At which step does the Cloud Shell environment become ready to accept commands?

A Step 2

B Step 3

C Step 1

D Step 4

💡 Hint

Look at execution_table row 1 and 2 for environment readiness

If you run 'az vm list' before creating a resource group, what would you expect in the VMList variable?

A Empty list or error

B List of VMs in all groups

C Resource group created

D Shell environment initialized

💡 Hint

Refer to variable_tracker VMList before and after step 4

Concept Snapshot

Azure CLI runs commands in Cloud Shell, a browser-based terminal.
Start Cloud Shell, pick Bash or PowerShell.
Run commands like 'az group create' to manage resources.
Outputs show success or data like VM lists.
Exit shell to end session.

Full Transcript

Azure Cloud Shell is a browser-based terminal that lets you run Azure CLI commands without setup. You start Cloud Shell, choose Bash or PowerShell, and get a ready environment. You can create resources like a resource group using commands such as 'az group create --name MyResourceGroup --location eastus'. After creation, you can list virtual machines in that group with 'az vm list --resource-group MyResourceGroup', which will show an empty list if no VMs exist. When finished, you type 'exit' or close the browser tab to end the session. This flow helps beginners see how commands run step-by-step and how the environment changes.

Practice

1. What is the primary purpose of Azure Cloud Shell?

easy

A. To store files permanently in Azure storage

B. To create virtual machines automatically without commands

C. To replace the Azure Portal with a graphical interface

D. To provide a ready-to-use command line interface in the browser with Azure CLI pre-installed

Solution

1. Step 1: Understand Cloud Shell functionality

   Cloud Shell is a browser-based shell environment with Azure CLI and other tools pre-installed, ready for use without setup.

2. Step 2: Compare options

   Options B, C, and D describe other Azure features but not Cloud Shell's main purpose.

3. Final Answer:

   To provide a ready-to-use command line interface in the browser with Azure CLI pre-installed -> Option D

4. Quick Check:

   Cloud Shell = browser CLI with Azure CLI [OK]

Hint: Cloud Shell = browser command line ready to use [OK]

Common Mistakes:

• Thinking Cloud Shell is a GUI tool
• Confusing Cloud Shell with Azure Portal
• Assuming Cloud Shell stores files permanently

2. Which command correctly logs you into Azure CLI in Cloud Shell?

easy

A. az connect

B. az login

C. az start

D. az authenticate

Solution

1. Step 1: Identify the login command in Azure CLI

   The command to log in to Azure CLI is az login.

2. Step 2: Verify other options

   Commands like az connect, az start, and az authenticate do not exist or are incorrect for login.

3. Final Answer:

   az login -> Option B

4. Quick Check:

   Login command = az login [OK]

Hint: Login always uses 'az login' command [OK]

Common Mistakes:

• Using 'az connect' instead of 'az login'
• Trying 'az start' to login
• Assuming 'az authenticate' is valid

3. What will the following command do?

az group create --name MyResourceGroup --location eastus

medium

A. Create a new resource group named MyResourceGroup in the East US region

B. Delete the resource group named MyResourceGroup

C. List all resource groups in East US

D. Create a virtual machine named MyResourceGroup

Solution

1. Step 1: Understand the command structure

   az group create creates a resource group. The parameters specify the name and location.

2. Step 2: Interpret parameters

   --name sets the resource group name to 'MyResourceGroup', --location sets the region to 'eastus'.

3. Final Answer:

   Create a new resource group named MyResourceGroup in the East US region -> Option A

4. Quick Check:

   az group create = create resource group [OK]

Hint: az group create = make new resource group [OK]

Common Mistakes:

• Confusing resource group creation with VM creation
• Thinking it deletes or lists groups
• Misunderstanding --location parameter

4. You run this command in Cloud Shell:

az vm create --resource-group MyGroup --name MyVM --image UbuntuLTS

But get an error saying the resource group does not exist. What should you do?

medium

A. Create the resource group first using az group create

B. Change the VM name to match an existing resource group

C. Run az vm delete before creating the VM

D. Use az vm list to create the resource group

Solution

1. Step 1: Understand the error cause

   The error says the resource group 'MyGroup' does not exist, so the VM cannot be created there.

2. Step 2: Fix by creating the resource group

   You must create the resource group first with az group create --name MyGroup --location eastus (or another location).

3. Final Answer:

   Create the resource group first using az group create -> Option A

4. Quick Check:

   Resource group must exist before VM creation [OK]

Hint: Create resource group before VM creation [OK]

Common Mistakes:

• Trying to delete VM before creating resource group
• Changing VM name instead of resource group
• Using az vm list to create groups

5. You want to automate creating a VM and then immediately open its public IP in your browser using Azure CLI in Cloud Shell. Which sequence of commands is correct?

hard

A. az vm create --resource-group RG --name VM1 --image UbuntuLTS && az vm get-ip VM1 | open-browser

B. az vm create --resource-group RG --name VM1 --image UbuntuLTS; az vm list-ip --name VM1 | open

C. az vm create --resource-group RG --name VM1 --image UbuntuLTS && az vm show --resource-group RG --name VM1 --query publicIpAddress -o tsv | xargs xdg-open

D. az vm create --resource-group RG --name VM1 --image UbuntuLTS && az vm show --resource-group RG --name VM1 --query publicIpAddress -o tsv | xargs open

Solution

1. Step 1: Create VM with az vm create

   This command creates the VM in the specified resource group with the Ubuntu image.

2. Step 2: Retrieve public IP and open in browser

   az vm show --query publicIpAddress -o tsv extracts the IP. Piping to xdg-open opens it in the default browser on Linux-based Cloud Shell.

3. Step 3: Analyze options

   Options B and C use invalid commands or syntax. az vm create --resource-group RG --name VM1 --image UbuntuLTS && az vm show --resource-group RG --name VM1 --query publicIpAddress -o tsv | xargs open uses open which is MacOS-specific, not Cloud Shell.

4. Final Answer:

   az vm create ... && az vm show ... | xargs xdg-open -> Option C

5. Quick Check:

   Use az vm show + xdg-open in Cloud Shell [OK]

Hint: Use az vm show + xdg-open to open IP in Cloud Shell [OK]

Common Mistakes:

• Using MacOS 'open' command in Cloud Shell
• Using non-existent commands like az vm get-ip
• Not piping IP correctly to open command