Academmia

Benefits of Manageability in the Cloud

az-900•beginner•

Cloud concepts

Benefits of Manageability in the Cloud

Short Summary

Manageability in the cloud means you can deploy, operate, and update resources in more consistent and repeatable ways. It shows up in two areas: managing your resources (automation, monitoring, and replacement) and the ways you manage them (portal, command line, APIs, and PowerShell). This lesson explains both and the common tools used in Azure.

Learning Objectives

By the end of this lesson, you will be able to:

  • Define cloud manageability and why it matters at scale.
  • Distinguish “management of the cloud” from “management in the cloud.”
  • Describe the main ways to manage Azure resources (portal, CLI, PowerShell, and APIs).
  • Use the idea of templates and Infrastructure as Code (IaC) to explain consistent deployments and reduced drift.
  • Explain how Azure Resource Manager (ARM) supports consistent deployment and management.

Core Concepts

Manageability is the ability to manage cloud resources efficiently and consistently, even when there are many of them. The cloud helps because it gives you standardized tools and automation that are hard to replicate in a fully manual, one-off environment.

Microsoft Learn describes two types of manageability:

1) Management of the cloud (managing your resources) This is about what you can do to keep resources running well and reduce manual work. Common examples include:

  • Automatically scaling resource deployment based on need.
  • Deploying resources from a preconfigured template instead of manually configuring each time.
  • Monitoring resource health and automatically replacing failing resources.
  • Receiving alerts from metrics so you can react quickly.

2) Management in the cloud (how you manage the environment) This is about the interfaces you can use to manage resources:

  • A web portal (in Azure, the Azure portal) for interactive work and quick investigation.
  • A command line interface (Command-Line Interface (CLI)) for repeatable commands and scripting (for example, Azure CLI).
  • Application programming interfaces (Application Programming Interfaces (APIs)) for integrating management into tools and pipelines.
  • PowerShell (in Azure, often Azure PowerShell) for scripting and automation.

Infrastructure as Code (IaC) is a key manageability pattern. Instead of clicking through the same steps, you describe what should exist (resources + configuration) and redeploy it consistently. In Azure, ARM supports deploying and managing resources, and ARM templates are one way to define resources for consistent deployments.

Finally, the cloud provider manages the physical datacenters and underlying platform, but you still manage what you deploy: your resources, configuration choices, access, monitoring, and operational processes. Manageability is about doing that work more consistently and with less manual effort.

Practical Understanding

Practical Situation 1: “I can do it in the portal, but I need to do it 200 times”

A team needs to apply the same change across many resources. Doing it manually in the portal takes a long time and invites small inconsistencies.

How to think about it: This is a manageability-at-scale problem. The portal is great for learning and quick checks, but CLI/PowerShell and APIs are better for repeatable work. If the change can be expressed in a template/IaC approach, you can also redeploy the desired state consistently.

Common misunderstanding: “Manageability means using the portal.” The portal is one tool; manageability is the ability to manage consistently using the right tools for the task.

Practical Situation 2: “Dev, staging, and prod keep drifting apart”

Environments were created manually, and small differences accumulate over time. Deployments become unpredictable because the environments are no longer truly equivalent.

How to think about it: This is a strong case for templates and IaC. Describing the desired resources once and deploying them repeatedly helps reduce drift and makes environments more consistent. It also makes reviews easier because changes are visible as code/configuration.

Common misunderstanding: “Templates mean I don’t need to understand what I’m deploying.” Templates reduce manual steps, but you still choose and own the architecture and settings.

Practical Situation 3: “A resource fails, and someone always has to jump in”

A VM or service instance fails and the team only notices after users complain. Recovery depends on manual intervention.

How to think about it: This is about management of the cloud: monitoring, alerting, and automated recovery reduce downtime and stress. Alerts based on metrics help you notice issues earlier, and some designs can automatically replace failing resources or fail over to healthy ones.

Common misunderstanding: “Cloud means recovery happens automatically by default.” The platform provides capabilities, but you still configure monitoring, alerts, and resilient designs.

Practical Situation 4: “We manage more than just Azure resources”

A team also has servers or clusters outside Azure and wants a consistent way to manage and govern resources instead of using totally separate tools for each environment.

How to think about it: Manageability improves when your tools can cover more of your footprint with consistent processes. In Azure, Azure Arc is designed to extend certain management capabilities to resources outside Azure, helping reduce tool sprawl in hybrid setups.

Common misunderstanding: “Manageability only applies inside one cloud.” Modern environments often span cloud and on-premises, and manageability is about keeping operations consistent across that reality.

Common Pitfalls

  • Mistake: Treating manageability as “only using the portal.” Correction: Manageability includes portal, CLI, PowerShell, APIs, templates/IaC, monitoring, and alerting.

  • Mistake: Mixing up “management of the cloud” and “management in the cloud.” Correction: “Of the cloud” is about automation/monitoring/recovery for resources; “in the cloud” is about the interfaces you use to manage them.

  • Mistake: Continuing to configure environments manually and accepting drift as normal. Correction: Use templates and IaC to deploy the same desired state repeatedly and reduce drift.

  • Mistake: Assuming the provider manages everything you deploy. Correction: The provider manages the underlying infrastructure; you still manage your resource configuration, monitoring, and operations.

  • Mistake: Believing automation is automatic. Correction: Autoscaling rules, alert thresholds, and recovery behaviors must be designed and configured to match your workload.

Check Your Understanding

  1. Explain the difference between “management of the cloud” and “management in the cloud” in your own words.
  2. Name one task you would do in the Azure portal and one task you would automate using CLI/PowerShell or an API. Explain why.
  3. Describe how IaC helps reduce drift between dev, staging, and production.
  4. What is ARM, and why does having a deployment and management layer improve manageability?
  5. Think of one metric you would alert on for a critical workload and explain what action you would take when the alert fires.

Further Reading