MSDEVBUILD / azure

Manageability

Azure portal · dashboard health $ az vm create --name web01 failed… replacing ✓ auto-healed Fixes itself
Manage everything from one dashboard or one command, and let broken servers fix themselves.

😟 THE PROBLEM

One of 300 servers fails at 3 a.m. and nobody notices until morning.

😊 THE SOLUTION

Monitor, automate and let failed resources replace themselves.

  • Failures go unnoticed✓ Alerts reach the on-call engineer
  • Clicking the same setup 50 times✓ Scripts and infrastructure as code
  • Broken servers need manual fixing✓ Scale sets replace unhealthy instances
🛠️ Solved with: Azure Monitor · Portal · CLI · IaC
Try it yourself in the Azure simulator No Azure account needed. Cloud Shell: deploy a web app ⌨️ Try it ❯
Module 1: Cloud Concepts ⏱ 7 min read Updated 11 Nov 2026

Quick answer

Manageability in the cloud has two sides. Management *of* the cloud means managing your resources themselves: autoscaling, deploying from templates, monitoring health and replacing failed resources automatically, and receiving alerts. Management *in* the cloud means how you do the managing: through the Azure portal, the command line (Azure CLI and Azure PowerShell), APIs and infrastructure as code.

Exam objective: 1.2.4 Describe the benefits of manageability in the cloud. (Skills measured as of July 20, 2026)

Start with a question

Your company has 300 servers. One of them fails at 3 am. Who notices, and who fixes it?

In a traditional server room, maybe nobody notices until users complain in the morning. Then someone drives in, finds the server, and starts repairing it.

In the cloud, monitoring can notice automatically, a scale set can replace the failed instance automatically, and an alert reaches the on-call engineer’s phone. If anyone needs to act, they can do it from a browser anywhere. That is manageability.

Explain it like I’m 10

The technical explanation

Microsoft describes cloud manageability in two parts.

Management OF the cloud

Managing your resources

  • Automatically scale resources based on need
  • Deploy resources from preconfigured templates
  • Monitor health and automatically replace failing resources
  • Receive alerts based on configured metrics

Management IN the cloud

How you manage them

  • Azure portal (web GUI)
  • Azure CLI and Azure PowerShell
  • Azure Cloud Shell in the browser
  • REST APIs and SDKs
  • Infrastructure as code (Bicep, ARM, Terraform)
The two sides of manageability

One control plane, many tools

Whichever tool you use, every management request goes through Azure Resource Manager (ARM). That is why a VM created in the portal looks exactly the same as one created with the CLI or a Bicep file.

For example, creating a resource group with the Azure CLI:

az group create --name rg-exam-portal --location westeurope

…or declaring infrastructure as code with Bicep:

resource storage 'Microsoft.Storage/storageAccounts@2023-05-01' = {
  name: 'stexamportal001'
  location: 'westeurope'
  sku: { name: 'Standard_ZRS' }
  kind: 'StorageV2'
}

You do not need to write code for AZ-900. Just recognise that these tools exist and what each is for. They are covered fully in Module 3.

Architect level From click-ops to platform engineering

Teams usually move through stages:

  1. Click-ops in the portal, which is fine for learning, risky for production.
  2. Scripts (CLI/PowerShell) for repeatable tasks.
  3. Infrastructure as code in source control with CI/CD pipelines, so environments are reproducible and changes are reviewed.
  4. Platform engineering: golden templates, policy-as-code, self-service environments (for example Azure Deployment Environments) and automated operations with Azure Monitor alerts triggering runbooks or Functions.

Measure manageability by how long it takes to stand up a new, compliant environment, and by how much of incident response is automated.

Real-world business scenario

Gaming

An online gaming platform

The problem
Game servers were configured by hand in each region, every region drifted slightly, and outages at night waited for someone to wake up.
What they used
Bicep templates deployed through pipelines for every region, VM Scale Sets with automatic instance repair, Azure Monitor alerts to on-call phones, and Cloud Shell for emergency access.
Why that choice
Templates made regions identical; health monitoring and auto-repair handled routine failures without humans.
The result
Launching a new region went from two weeks to one afternoon, and most night-time failures now resolve themselves before anyone is paged.

When to use it and when not to

✓ Use it when…

  • **Portal** for learning, exploring and quick one-off checks.
  • **CLI / PowerShell / Cloud Shell** for scripted and repeatable tasks.
  • **Infrastructure as code** for every production environment.
  • **Monitoring, alerts and autoscale** on everything that matters to users.

✕ Think twice when…

  • Manual portal changes in production with no record.
  • Alerts on everything. Alert fatigue means real problems get ignored.
Ready for more?The full lesson adds the technical explanation, when to use it, interview questions and revision notes.

Interview preparation

Say your answer out loud first, then open the model answer. Interviewers care more about your reasoning than the exact words.

Beginner What does manageability mean as a cloud benefit?

Model answer

It means the cloud is easier to manage. On one side, resources can scale automatically, be deployed from templates, be monitored and send alerts. On the other side, I can manage everything through a web portal, command-line tools or APIs from anywhere.

Interviewer follows up

What tools can you use to manage Azure?

You

The Azure portal in a browser, Azure CLI and Azure PowerShell (also available in Azure Cloud Shell), REST APIs and SDKs, and infrastructure-as-code tools like Bicep, ARM templates and Terraform.

Intermediate When would you use the portal versus the CLI versus infrastructure as code?

Model answer

The portal suits learning, exploring and one-off tasks. The CLI or PowerShell suit scripting and repeatable admin tasks. Infrastructure as code (Bicep, ARM or Terraform) is for anything that must be consistent across environments or reviewed, especially production. You declare the desired state in source control and deploy through a pipeline.

Experienced developer How does infrastructure as code improve manageability at scale?

Model answer

It makes environments reproducible and reviewable. Changes go through pull requests, drift can be detected, new regions or environments are a parameter change, and disaster recovery can include redeploying infrastructure from code. Combined with CI/CD, policy-as-code and tagging conventions, it turns manual operations into an auditable engineering process.

Scenario An admin needs to restart 40 VMs every night after a batch job. Manual portal clicks are taking an hour. What would you suggest?

Model answer

Automate it. A short Azure CLI or PowerShell script run on a schedule, using Azure Automation or a timer-triggered Azure Function with a managed identity. Better still, check whether the restart is needed at all, or whether the batch job could run on a Scale Set or serverless service.

Test yourself with exercises

4 original practice questions in the AZ-900 style. Pick your answers, then check them. You will see why each option is right or wrong. Score 75% or more and this topic is marked complete.

Question 1

Question 1 of 4 · Select 2

Which TWO are examples of management OF the cloud?

Question 2

Question 2 of 4

Which of the following is an example of management IN the cloud?

Question 3

Question 3 of 4

Which tool provides a browser-based command line with Azure CLI and Azure PowerShell already installed?

Question 4

Question 4 of 4

Defining infrastructure in files that can be version-controlled and deployed repeatably is called what?

Quick revision

Key points

  • Management of the cloud: autoscale, deploy from templates, monitor health, auto-replace failed resources, alerts.
  • Management in the cloud: Azure portal, Azure CLI, Azure PowerShell, Cloud Shell, APIs, SDKs.
  • Infrastructure as code (Bicep, ARM templates, Terraform) makes management repeatable and auditable.
  • All management tools go through Azure Resource Manager, so results are consistent.
  • Manage from anywhere with a browser or a terminal.

Important terminology

Management of the cloud
Managing your cloud resources, such as scaling, deploying from templates, monitoring and alerting, and automatic replacement of failed resources.
Management in the cloud
The interfaces used to manage resources, such as the Azure portal, CLI, PowerShell, APIs and SDKs.
Infrastructure as code (IaC)
Defining infrastructure in files (Bicep, ARM templates, Terraform) so it can be versioned and deployed repeatably.
Azure Cloud Shell
A browser-based shell with Azure CLI and Azure PowerShell preinstalled and already authenticated.

Common mistakes

  • Thinking the portal is the only way to manage Azure.
  • Doing production changes by hand with no record or review.

Exam tips

  • "Manage resources from a browser with a GUI" = Azure portal.
  • "Scripting / command line" = Azure CLI or Azure PowerShell; "browser-based shell" = Cloud Shell.
  • Know the two sides, management of the cloud vs management in the cloud.

Five quick revision questions

  1. 1.What are the two aspects of cloud manageability?Show

    Management of the cloud and management in the cloud.

  2. 2.Give two examples of management of the cloud.Show

    Autoscaling, deploying from templates, monitoring and alerts, automatic replacement of failed resources.

  3. 3.Give three tools for management in the cloud.Show

    Azure portal, Azure CLI, Azure PowerShell (also APIs, SDKs, Cloud Shell).

  4. 4.What is infrastructure as code?Show

    Defining infrastructure in code files so it can be versioned and deployed repeatably.

  5. 5.What is Azure Cloud Shell?Show

    A browser-based shell with Azure CLI and PowerShell preinstalled and authenticated.

Official references

Make it stick: play a quick gameSort It, Match the Pairs, Lightning Round and Who Am I? Earn XP and badges. Play ❯

Finished this lesson? Tick it off. Your progress is saved in this browser.

Next up: Azure Regions, Region Pairs and Sovereign Regions