Skip to main content
Compare the administrator tools available in Azure and learn when to use each one. This article explains the strengths, typical use cases, and quick examples for the main tools: Azure Portal, Azure Cloud Shell, Azure PowerShell (Az module), Azure CLI (az), and REST APIs / SDKs. The main tools covered:
  • Azure Portal
  • Azure Cloud Shell
  • Azure PowerShell (Az module)
  • Azure CLI (az)
  • REST APIs / SDKs

​
At-a-glance comparison

​
Azure Portal

The Azure Portal is a graphical, centralized hub for discovering, managing, and monitoring Azure resources. It provides an intuitive UI and context-aware help links for most administrative tasks. When to use Azure Portal:
  • Visual exploration of resource properties and relationships
  • One-off tasks (scale a database, create a VM, inspect logs)
  • Quick role assignment or resource tagging
Pros:
  • Rich visualization and guided workflows
  • Contextual documentation and in-portal tutorials
  • Mobile app for quick checks and simple approvals
Consider the portal when you prefer a visual workflow or when doing tasks that do not require automation.

​
Azure Cloud Shell

Azure Cloud Shell is a browser-based shell that automatically authenticates to your Azure account. It supports Bash (Linux-style) and PowerShell and mounts a persisted clouddrive backed by Azure Files. Key details:
  • The first time you launch Cloud Shell, it prompts to create an Azure Files share for ~/clouddrive.
  • Sessions run in a temporary container and will time out after a period of inactivity.
  • You can switch between Bash and PowerShell inside the Cloud Shell UI.
Cloud Shell sessions may time out after inactivity (typically ~20 minutes). For long-running tasks, run jobs in background-friendly mechanisms or use local/VM environments that do not time out.
Example Cloud Shell (Bash) session demonstrating persisted clouddrive:
Use Cloud Shell when you need quick, authenticated CLI access from any machine without installing tools locally.

​
Azure PowerShell (Az module)

Azure PowerShell provides PowerShell cmdlets that return rich objects, making it ideal for PowerShell users and automation that benefits from pipelines and object manipulation. When to use:
  • PowerShell-native automation and scripting
  • Complex object transformations using the PowerShell pipeline
  • Administrative scripts on Windows or cross-platform PowerShell Core
Install and verify examples:
Sign-in examples:
Example device code message:
After authenticating, list subscriptions and storage accounts:
Sample trimmed output:
A browser screenshot showing a Microsoft Azure sign-in confirmation dialog. It asks if you’re trying to sign in to Microsoft Azure PowerShell and shows Cancel and Continue buttons.

​
Azure CLI (az)

The Azure CLI (az) is a cross-platform command-line tool designed for scripting and automation, and it integrates well with shell scripts, containers, and CI/CD pipelines. When to use:
  • Shell-script friendly automation (Bash, sh)
  • CI/CD pipelines and container build workflows
  • CLI-first workflows such as az acr build for ACR image builds
Quick start:
Example common command (restart a VM):
Explore CLI groups and help:
Note: Some operations are more convenient in CLI (e.g., certain container registry commands). Choose PowerShell or CLI based on the environment and scripting style.

​
REST APIs and SDKs

For programmatic control from applications or language-native automation, use Azure REST Management APIs or the language-specific Azure SDKs (available for .NET, Java, Python, JavaScript/TypeScript, Go, and others). When to use:
  • Integrating Azure operations into application code
  • Building platform-agnostic integration layers
  • Scenarios requiring fine-grained REST calls or unsupported CLI/PowerShell operations
Authentication patterns:
  • Service principal credentials
  • Managed identities (for Azure-hosted workloads)
  • OAuth device-code or interactive flows (for development)
Choose the tool that best fits your workflow:
  • Portal for one-off visual tasks and resource exploration
  • Cloud Shell for quick, browser-based CLI sessions with persisted clouddrive
  • Azure PowerShell for PowerShell-native automation and object pipelines
  • Azure CLI for shell-script-friendly automation and CI/CD workflows
  • REST APIs/SDKs for language-native programmatic control

​
Conclusion

Each Azure management tool has trade-offs and strengths:
  • Azure Portal: Visual exploration, guided actions, and immediate documentation.
  • Azure Cloud Shell: Fast, authenticated CLI in the browser with persisted storage.
  • Azure PowerShell: Object-based cmdlets and pipeline-friendly automation for PowerShell users.
  • Azure CLI: Scriptable, container- and CI/CD-friendly commands.
  • REST APIs / SDKs: Programmatic control for applications and advanced automation.
Use one or more tools together depending on task complexity, automation needs, and your preferred scripting or development environment.

Watch Video