The Azure Portal
The Azure Portal is a web-based graphical interface at portal.azure.com where you can create, configure, and monitor resources by clicking through forms and dashboards rather than typing commands. It is the best starting point for newcomers because it surfaces available options contextually — for example, when creating a VM, the Portal shows you which sizes and images are valid for the region you selected — and it provides visual tools like Azure Monitor charts, Cost Management dashboards, and the Cloud Shell embedded directly in the browser. Its main limitation is that manual point-and-click actions are not easily repeatable or version-controllable, which makes the Portal poorly suited for provisioning the same environment consistently across dev, test, and production.
Cricket analogy: Using the Portal is like a new captain reading the on-screen field-placement diagram on a coaching app before setting fielders, rather than memorizing every position from experience — it's guided and visual for beginners.
Azure CLI and Automation
The Azure CLI (az) is a cross-platform command-line tool that lets you script the exact same operations the Portal performs, making it ideal for repeatable deployments, CI/CD pipelines, and automation. Commands follow a consistent pattern of az <group> <subcommand>, such as az group create or az vm create, and every command supports --output json so results can be piped into other tools like jq for parsing. Because CLI commands are plain text, they can be checked into source control, reviewed in pull requests, and re-run identically any number of times — a property manual Portal clicks simply cannot offer, which is why production environments are usually provisioned through CLI scripts or infrastructure-as-code rather than manual clicking.
Cricket analogy: The CLI is like a team's fielding drill written down as an exact sequence of instructions that any assistant coach can run identically every practice session, rather than relying on memory each time.
Common CLI Patterns
# Log in and set the active subscription
az login
az account set --subscription "Pay-As-You-Go"
# List all resource groups as a table
az group list --output table
# Query specific fields with JMESPath and pipe to jq
az vm list --resource-group myFirstRG \
--query "[].{Name:name, Size:hardwareProfile.vmSize}" \
--output json | jq .Azure Cloud Shell, accessible directly from the Portal or shell.azure.com, gives you a pre-authenticated CLI session in your browser with no local installation required — useful for quick tasks or when working from a locked-down machine.
Actions performed through the Portal and CLI use the same underlying Azure Resource Manager (ARM) APIs and the same role-based access control checks — switching tools does not bypass permission restrictions.
- The Azure Portal is a browser-based graphical interface best suited for exploration, learning, and one-off tasks.
- The Azure CLI is a scriptable command-line tool ideal for repeatable, automatable, and version-controllable deployments.
- Both the Portal and CLI ultimately call the same Azure Resource Manager (ARM) APIs.
- CLI commands follow the pattern az <group> <subcommand>, e.g., az vm create.
- Azure Cloud Shell provides a pre-authenticated browser-based CLI session with no local install needed.
- Production environments typically use CLI scripts or infrastructure-as-code rather than manual Portal clicks.
- Permissions and role-based access control apply identically regardless of which tool you use.
Practice what you learned
1. What underlying API do both the Azure Portal and Azure CLI use?
2. Which tool is generally best suited for CI/CD pipeline automation?
3. What does Azure Cloud Shell provide?
4. What is the general command pattern for Azure CLI commands?
5. Why is the Portal poorly suited for provisioning identical environments across dev, test, and production?
Was this page helpful?
You May Also Like
What Is Microsoft Azure?
An introduction to Microsoft Azure as a public cloud platform, covering its core service models and why organizations adopt it.
Azure Subscriptions and Billing
How Azure subscriptions organize billing and access, and the tools available to monitor, budget, and control cloud spend.
Azure Shared Responsibility Model
How security and operational responsibility is divided between Microsoft and the customer across IaaS, PaaS, and SaaS.