Using the Azure Portal and Cloud Shell

• Structured Summary + Deep Technical Understanding

Primary services covered:

• Azure Portal
• Azure Cloud Shell

Official documentation:

Azure Portal:

Cloud Shell:

1️⃣ What is the Azure Portal?#

The Azure Portal is:

• ✔ A web-based graphical user interface (GUI) ✔ Accessible at: https://portal.azure.com ✔ Used to create, manage, monitor Azure resources ✔ Built on top of Azure Resource Manager (ARM)
• It is a control-plane interface for Azure.

Anything you do in the portal:

• Create VM Delete Storage Account Assign RBAC Configure networking
• → Sends REST API calls to Azure Resource Manager → ARM forwards request to the correct Resource Provider
• (From previous lesson: Portal → ARM → Resource Provider → Resource)

2️⃣ Key Portal Components#

🔹 Home Dashboard#

Displays:

• Recently used resources
• Favorites
• Quick-create templates
• Marketplace suggestions

You can customize dashboards for:

• ✔ CPU usage ✔ Memory metrics ✔ Alerts ✔ Resource tiles
• This provides a “single pane of glass” view of your environment.

🔹 Navigation Menu (Hamburger Menu)#

Core options:

• Create a resource
• Dashboard
• All services
• Favorites
• Resource groups
• Subscriptions

🔹 Search Bar (Highly Used Feature)#

Search allows:

• ✔ Find services ✔ Find specific resources ✔ Find documentation ✔ Access marketplace ✔ View search history
• Important for speed in production environments.

3️⃣ Creating a Resource via Portal (Example: Virtual Machine)#

Example resource:

• Azure Virtual Machines

When creating a VM:

You configure:

• Resource Group (mandatory)
• Region
• Availability options
• OS image
• VM size
• Authentication
• Networking
• Disks
• Tags

Important concept:

Deploying a VM automatically deploys dependent resources, such as:

• Network Interface (Microsoft.Network)
• Public IP
• Virtual Network
• Disk
• NSG (optional)
• These dependencies are deployed via ARM and respective Resource Providers.

Example providers:

• Microsoft.Compute
• Microsoft.Network
• Microsoft.Storage
• This demonstrates ARM orchestration in action.

4️⃣ Resource Type Namespaces (Exam-Relevant)#

Every Azure resource has a type format:

• Microsoft.ProviderName/resourceType

Examples:

• Microsoft.Compute/virtualMachines
• Microsoft.Network/networkInterfaces
• Microsoft.Storage/storageAccounts

Understanding this helps in:

• ✔ ARM templates ✔ RBAC ✔ Azure Policy ✔ Troubleshooting

5️⃣ Azure Cloud Shell Overview#

Cloud Shell is:

• ✔ A browser-based shell ✔ Pre-authenticated to your Azure account ✔ Runs inside Azure ✔ No local installation required

Supports:

• Bash (Azure CLI)
• PowerShell (Az module)

6️⃣ Bash vs PowerShell in Cloud Shell#

🔹 Bash#

Uses:

• Azure CLI (az commands)

Example:

• az vm list

Best for:

• Cross-platform scripting
• DevOps pipelines
• Linux-style automation

🔹 PowerShell#

Uses:

• Azure PowerShell (Az module)

Example:

• Get-AzVM

Best for:

• Windows admins
• PowerShell-native automation
• Advanced scripting logic
• Switching shells restarts session.

7️⃣ Cloud Shell Storage Options#

Two options:

🔹 Persistent Storage (Recommended for real work)#

Mounts a storage account:

• Saves scripts
• Persists files
• Keeps configurations

Backed by:

• Azure Files

🔹 No Storage Account#

Ephemeral session:

• No file persistence
• Temporary environment
• Good for quick tests

8️⃣ Cloud Shell Capabilities#

• ✔ Upload / Download files ✔ Multiple sessions ✔ Built-in code editor ✔ Web preview (for apps running in shell) ✔ Settings customization ✔ Documentation help

Cloud Shell environment includes:

• Azure CLI
• PowerShell Az module
• Git
• Terraform
• kubectl
• Helm
• Docker tools
• Python
• Node.js
• It is essentially a preconfigured DevOps environment.

9️⃣ Portal vs Cloud Shell#

🔟 Control Plane Integration#

Both Portal and Cloud Shell:

• ✔ Use REST APIs ✔ Talk to Azure Resource Manager ✔ Operate in control plane
• They do NOT directly manipulate data plane operations (e.g., blob uploads via service endpoint).

1️⃣1️⃣ Security Model#

When using Portal or Cloud Shell:

Authentication handled by:

• Microsoft Entra ID

Process:

• User login → Token issued → Token sent to ARM → RBAC evaluated → Operation allowed or denied.
• Cloud Shell inherits your Entra authentication session.

1️⃣2️⃣ Real-World Usage Scenarios#

Portal is ideal for:#

✔ Learning Azure ✔ One-off deployments ✔ Monitoring ✔ Troubleshooting ✔ Visual configuration

Cloud Shell is ideal for:#

✔ Automation ✔ Bulk operations ✔ CI/CD tasks ✔ Infrastructure scripting ✔ Advanced management

1️⃣3️⃣ Common Exam Pitfalls#

🚩 Cloud Shell runs locally → False 🚩 Cloud Shell requires installation → False 🚩 Portal interacts directly with resources → False (via ARM) 🚩 VM deployment only creates 1 resource → False 🚩 Cloud Shell automatically persists files → Only if storage mounted

1️⃣4️⃣ Architecture Insight#

When you click “Create VM” in portal:

• Portal UI → REST API call → Azure Resource Manager → Microsoft.Compute → Microsoft.Network → Microsoft.Storage → Deployment orchestration → Resource provisioning

This demonstrates:

• ARM dependency management.

1️⃣5️⃣ Key Takeaways#

• ✔ Azure Portal = GUI management interface ✔ Cloud Shell = CLI inside browser ✔ Both use ARM ✔ VM deployments create multiple dependent resources ✔ Resource types follow Microsoft.Provider/resourceType pattern ✔ Cloud Shell supports Bash and PowerShell ✔ Persistent storage optional but recommended

Understanding these tools is foundational for:

• AZ-104
• AZ-204
• AZ-900
• DevOps engineering
• Azure governance

If you'd like next:

• 🧠 30 exam questions on Portal & ARM
• 🏗 ARM request flow deep dive diagram
• 🔐 RBAC + Portal + Cloud Shell interaction guide
• ⚙ Azure CLI vs PowerShell comparison
• 🚀 Beginner-to-Advanced Cloud Shell command roadmap
• Tell me your goal.