Managing & Deploying Azure Resources
AZ-900 AZ-900 · Describe Azure management and governance
Four ways to manage Azure
Azure can be managed through four main tools, and the exam expects you to describe each and know when to use it. They all do the same underlying job — creating, configuring, and managing resources — but they suit different people and different tasks.
The Azure portal is the web-based graphical interface at portal.azure.com: point, click, and manage everything from dashboards. It is the best tool for learning Azure, for one-off tasks, and for visualising an environment. Every other tool can do things the portal can too, but the portal is where most people start, and it is the only tool that needs no installation and no scripting knowledge.
Azure Cloud Shell is a browser-based shell built into the portal: a command line in the browser, with a choice of Bash or PowerShell, and with the Azure CLI and Azure PowerShell preinstalled. It needs no local setup, and it stores your files persistently in an Azure storage account (Cloud Shell creates one on first use). Cloud Shell is the answer when a question describes managing Azure from a command line without installing anything locally.
The Azure CLI is a cross-platform command-line tool (the az commands) installed on your own machine, for Windows, macOS, and Linux. It is scriptable, automation-friendly, and the standard choice for repeatable command-line work and for CI/CD pipelines. Azure PowerShell is the PowerShell module (the Az cmdlets) for managing Azure from PowerShell — the natural choice for administrators who already work in PowerShell, especially in Windows-heavy environments. The exam distinguishes them simply: CLI is cross-platform command line, PowerShell is the PowerShell module. A question that says "the administrator works in PowerShell and wants cmdlets" points to Azure PowerShell; one that says "a cross-platform command-line tool" points to the CLI.
Azure Arc: managing beyond Azure
Not everything an organisation runs lives in Azure. Azure Arc extends Azure management to resources outside Azure — servers on-premises or in other clouds, Kubernetes clusters anywhere, and even data services. Once a server is Arc-enabled, it appears in the Azure portal, can be governed by Azure Policy, can be monitored, and can be managed with the same tools as native Azure resources. Arc is the exam's answer for hybrid and multi-cloud management: "manage our on-premises servers from the Azure portal" is an Arc scenario. It does not move the servers to Azure — it brings Azure management to where they already are.
Infrastructure as code (IaC)
Infrastructure as code (IaC) means defining infrastructure in machine-readable files instead of configuring it by clicking through a portal. The file describes the desired state — "a resource group, a virtual network, two virtual machines" — and a tool creates it. The benefits are the exam's focus: consistency (the same file produces the same environment every time), repeatability (deploy the same infrastructure to dev, test, and production), version control (infrastructure changes are tracked like code, with history and rollback), and automation (deployments become part of a pipeline). IaC turns infrastructure from a manual craft into a repeatable process, and it is how organisations manage environments too large to click through by hand.
IaC comes in two styles. Declarative IaC describes the desired end state and lets the tool work out the steps — ARM templates and Bicep are declarative ("I want this to exist"). Imperative IaC lists the steps in order — scripts that run command after command ("do this, then this"). The exam tests the distinction lightly: ARM templates are the declarative example.
Azure Resource Manager and ARM templates
Azure Resource Manager (ARM) is the deployment and management layer for Azure: every request to create, update, or delete a resource goes through ARM, whether it comes from the portal, the CLI, PowerShell, or a template. ARM handles authentication, applies policies and locks, and tracks resources. You never "use" ARM directly as a tool — it is the layer underneath all the tools.
ARM templates are JSON files that declare the infrastructure to deploy, and ARM reads them and creates the resources. A template is declarative (it describes the desired state), idempotent (deploying the same template twice produces the same result — the second run changes nothing), and modular (templates can link to other templates and use parameters and variables). Before deploying, you can run a what-if operation to preview what a template would change, without changing anything — the exam likes this detail for questions about safely previewing a deployment. Bicep is a simpler language that compiles to ARM templates — easier to read and write than JSON — and is worth knowing as the modern companion to ARM templates, although the objectives name ARM templates specifically.
Worked example: deploying the same environment three times
A team needs identical dev, test, and production environments. Clicking through the portal three times would produce three slightly different environments and take a day. The IaC approach: write one ARM template (or Bicep file) describing the resource group, network, app service, and database, parameterised by environment name, and deploy it three times with different parameters. Each deployment is identical, takes minutes, is recorded in version control, and can be previewed with what-if before it runs. When the production environment needs a change, the team edits the template, reviews the change, and redeploys — the environment is never modified by hand, so it never drifts. That is the whole IaC story: define once, deploy anywhere, change through code.
Bicep and the Azure mobile app
Two more tools round out the picture. Bicep is Microsoft's domain-specific language for deploying Azure resources: it uses a simpler, cleaner syntax than ARM templates' JSON, and it compiles down to ARM templates before deployment — so everything Bicep does, ARM does underneath. Teams choose Bicep when they find JSON templates hard to read and maintain; the exam mentions ARM templates specifically, but knowing that Bicep is the friendlier front end to the same engine is useful context. The Azure mobile app lets administrators monitor resources, check Service Health, and respond to alerts from a phone — handy for keeping an eye on an environment away from a desk, but a companion to the portal rather than a replacement for it. Neither tool is a headline exam topic; both are worth a passing mention so they do not surprise you if they appear as distractors.
Exam traps to watch for
- Recommending the portal for repeatable deployments. The portal is for learning and one-off tasks; repeatable, consistent deployments need infrastructure as code.
- Confusing Azure CLI with Azure PowerShell. The CLI is the cross-platform az command-line tool; PowerShell uses the Az module cmdlets. Match the tool to the administrator's environment.
- Thinking Azure Arc moves servers to Azure. Arc extends Azure management to servers wherever they are — it does not migrate them.
- Forgetting ARM templates are declarative and idempotent. They describe the desired state, and deploying the same template twice gives the same result.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.An administrator needs to manage Azure from a command line but cannot install any software on their work laptop. Which tool should they use?
Explanation: Azure Cloud Shell is a browser-based shell built into the portal — Bash or PowerShell with the Azure tools preinstalled, needing no local installation. The portal is graphical, not a command line. Azure Arc manages external servers; it is not a shell. An ARM template is a deployment file, not a command-line tool.
Exam objective: AZ-900 Describe features and tools for managing and deploying Azure resources: describe Azure Cloud Shell, Azure CLI, and Azure PowerShell
Q2.A company runs servers on-premises and in another cloud. It wants to manage all of them — including applying Azure Policy — from the Azure portal, without moving them. Which service enables this?
Explanation: Azure Arc extends Azure management to on-premises and multi-cloud servers, so they appear in the portal and can be governed by Policy. Azure Migrate moves workloads to Azure — the opposite of leaving them in place. Azure Monitor collects metrics and logs; it does not manage external servers. ARM is the deployment layer for Azure resources, not a bridge to external servers.
Exam objective: AZ-900 Describe features and tools for managing and deploying Azure resources: describe the purpose of Azure Arc
Q3.A team wants to define its infrastructure in a file so that the same environment can be deployed identically to development, testing, and production, with all changes tracked in version control. Which approach is this?
Explanation: Infrastructure as code defines infrastructure in machine-readable files, giving consistency, repeatability, and version control across environments. Manual portal configuration is the opposite — error-prone and untracked. Azure Policy enforces rules on resources; it does not define them. Service Health reports the health of Azure services.
Exam objective: AZ-900 Describe features and tools for managing and deploying Azure resources: describe infrastructure as code (IaC)
Q4.What is Azure Resource Manager (ARM)?
Explanation: ARM is the deployment and management layer for Azure: all requests to create, update, or delete resources go through it, whatever tool made them. Migration is Azure Migrate's job. Command-line scripting is the CLI or PowerShell. Monitoring is Azure Monitor's job.
Exam objective: AZ-900 Describe features and tools for managing and deploying Azure resources: describe Azure Resource Manager (ARM) and ARM templates
Q5.A team is about to deploy an ARM template to production and wants to preview exactly what will change, without actually changing anything. What should it run?
Explanation: The what-if operation previews the changes a template deployment would make, without applying them. A deployment slot swap changes which version of a web app is live. A budget alert notifies about spending. A secure score assessment is a Defender for Cloud security review — none of them previews a template deployment.
Exam objective: AZ-900 Describe features and tools for managing and deploying Azure resources: describe Azure Resource Manager (ARM) and ARM templates
Q6.Which statement about ARM templates is correct?
Explanation: ARM templates are declarative JSON files describing the desired state, and they are idempotent — deploying the same template twice gives the same result. Imperative scripts list steps; templates do not. Templates can deploy any resource type, not only VMs. They are JSON, not PowerShell (Bicep is the simpler language that compiles to ARM templates).
Exam objective: AZ-900 Describe features and tools for managing and deploying Azure resources: describe Azure Resource Manager (ARM) and ARM templates
Q7.An administrator who works in PowerShell every day wants to manage Azure with cmdlets in their existing scripts. Which tool should they use?
Explanation: Azure PowerShell is the Az module of cmdlets for managing Azure from PowerShell — the natural fit for a PowerShell administrator. The Azure CLI is a separate cross-platform command-line tool (az commands), not PowerShell cmdlets. The portal is graphical. Cloud Shell with Bash is a Bash shell, not PowerShell cmdlets in local scripts.
Exam objective: AZ-900 Describe features and tools for managing and deploying Azure resources: describe Azure Cloud Shell, Azure CLI, and Azure PowerShell
Q8.A new Azure user wants to explore the platform visually, create their first resources, and see dashboards of their environment. Which tool is the best starting point?
Explanation: The Azure portal is the web-based graphical interface — the best tool for learning, visual exploration, and one-off tasks, needing no installation or scripting. The CLI requires command-line knowledge. ARM templates require writing JSON. Azure Arc manages external servers, which is not what a new user exploring Azure needs.
Exam objective: AZ-900 Describe features and tools for managing and deploying Azure resources: describe the Azure portal