This chapter covers the Azure Portal, Azure CLI, and Azure PowerShell — the primary tools for managing Azure resources. AZ-900 tests this under objective 3.4, "Describe features and tools for managing and deploying Azure resources."
Jump to a section
A simple way to picture Azure Portal, CLI, and PowerShell
A business might let customers place orders three different ways — walking into a storefront and browsing visually, calling a phone line and speaking specific requests, or submitting a direct written order form. Each accomplishes the same goal (placing an order) but suits different situations — browsing visually versus quickly specifying an exact, repeatable request. Azure's management tools work similarly: the Azure portal (a visual, browser-based interface), Azure CLI (a command-line tool for typed commands), and Azure PowerShell (a command-line tool built for PowerShell users) all let you manage the same underlying resources, just through different interfaces suited to different situations.
The Azure Portal
The Azure portal is a web-based, graphical interface for creating and managing Azure resources. It's generally the most approachable option for those newer to Azure, or for tasks that benefit from a visual interface, like reviewing dashboards or exploring available services.
Azure CLI
Azure CLI (Command-Line Interface) is a cross-platform command-line tool for managing Azure resources through typed commands. It's well suited to scripting and automation, letting the same set of commands be run repeatably and consistently, rather than manually clicking through steps each time.
Azure PowerShell
Azure PowerShell is a set of cmdlets built for managing Azure resources using PowerShell, Microsoft's task automation and scripting framework. It serves a similar automation-focused purpose to Azure CLI, but is built specifically for those already working within the PowerShell ecosystem.
Choosing between them
There's no single "correct" tool — the portal suits visual exploration and one-off tasks; CLI and PowerShell both suit scripting and repeatable automation, with the choice between them often coming down to existing familiarity or organizational preference (PowerShell vs. more general command-line scripting).
All three go through the same underlying layer
Regardless of which tool is used, requests ultimately go through Azure Resource Manager (covered in an earlier chapter), meaning the same operations are available and behave consistently no matter which interface is used to perform them.
Use the portal for visual, exploratory tasks
The Azure portal suits tasks that benefit from a visual interface, like reviewing a dashboard, exploring available services, or performing a one-off configuration change.
Use CLI or PowerShell for repeatable, scripted tasks
For tasks that need to be repeated consistently or automated, Azure CLI or Azure PowerShell let the same commands be scripted and run reliably, rather than manually repeating portal steps.
Choose CLI or PowerShell based on existing skills
The choice between CLI and PowerShell often comes down to which scripting environment a team already works in, since both accomplish similar automation goals.
Recognize consistency across tools
Because all three tools go through Azure Resource Manager, the same underlying operations and permissions apply consistently regardless of which interface is used.
A new team member unfamiliar with Azure uses the portal to explore available services and manually create their first few resources, benefiting from the visual, guided interface while learning the platform.
Once the team has a well-understood, repeatable deployment process, they switch to using Azure CLI scripts to automate that process consistently across environments, reducing the manual effort and potential for inconsistency that comes with repeatedly clicking through the portal by hand.
Objective 3.4 expects candidates to recognize the Azure portal, CLI, and PowerShell as different interfaces for the same underlying management capability, each suited to different situations.
A common wrong answer is assuming these tools offer different capabilities from each other — they generally provide access to the same underlying operations through Azure Resource Manager, just through different interfaces. Another common trap is assuming one tool is always objectively "better" — the right choice depends on the task and the team's preferences and existing skills.
Stable terms: Azure Portal, Azure CLI, Azure PowerShell. Recognizing that all three ultimately interact with the same Azure Resource Manager layer is a frequently tested underlying concept.
Memory trick: portal = visual and exploratory. CLI and PowerShell = scripting and automation-friendly, chosen based on existing familiarity with each scripting ecosystem.
The Azure portal, Azure CLI, and Azure PowerShell are different interfaces for managing the same underlying Azure resources.
The portal suits visual, exploratory tasks; CLI and PowerShell suit scripting and repeatable automation.
All three tools ultimately interact with the same Azure Resource Manager layer, providing consistent underlying capability.
The right tool depends on the specific task and the team's existing skills and preferences, not a universal 'best' option.
These come up on the exam all the time. Here's how to tell them apart.
Azure Portal
Visual, browser-based interface
Good for exploration and one-off tasks
Easier starting point for newcomers
Azure CLI / PowerShell
Command-line, script-based interface
Good for repeatable, automated tasks
Preferred for consistent, scripted deployments
Mistake
The Azure portal, CLI, and PowerShell offer different underlying capabilities.
Correct
All three ultimately interact with the same Azure Resource Manager layer, so the same underlying operations are generally available through any of them, just via different interfaces.
Mistake
One of these tools is always the objectively correct choice.
Correct
The right tool depends on the task and situation — the portal suits visual, exploratory tasks; CLI and PowerShell suit scripting and automation, with the choice between them often coming down to existing familiarity.
Mistake
Azure CLI only works on Windows.
Correct
Azure CLI is cross-platform, working on Windows, macOS, and Linux, unlike being tied to a single operating system.
The Azure portal is a visual, browser-based interface, well suited to exploration and one-off tasks. Azure CLI and Azure PowerShell are command-line tools better suited to scripting and automation, letting the same operations be repeated consistently. All three ultimately provide access to the same underlying Azure capabilities.
It depends on the task — the portal is often easier for newcomers or visual, one-off tasks, while CLI or PowerShell are better for repeatable, automated deployments. The choice between CLI and PowerShell specifically often comes down to which scripting environment a team already uses.
Generally no — all three interact with the same underlying Azure Resource Manager layer, so the same operations are typically available regardless of which interface is used to perform them.
You've just covered Azure Portal, CLI, and PowerShell — now see how well it sticks with free AZ-900 practice questions. Full explanations included, no account needed.
Done with this chapter?