IntermediateLesson 4 of 9

Azure Resource Management

Learn how resources, resource groups, tags, and hierarchy work together so your environment stays organized and manageable.

What is it? (Simple Explanation)

Azure Resource Manager (ARM) is the control layer where you create and organize everything in Azure.

Why do we need it?

Real-world Analogy

Resource groups are project folders, resources are files, and tags are labels like "owner", "env", and "cost-center" for sorting and reporting.

How it works (Technical)

Hierarchy is typically: Management Group -> Subscription -> Resource Group -> Resource. Tags are key-value metadata attached to resources/resource groups for governance and chargeback style reporting.

Visual Representation

ARM Hierarchy
Management Group
Enterprise boundary
Subscription
Billing and access boundary
Resource Group
Logical project container
Resources
VM, storage, app service, etc.

Commands / Syntax

Azure CLI
az group create --name rg-app-dev --location eastus
az group list --output table
az tag create --resource-id  --tags env=dev owner=platform costcenter=1001

Example (Real-world Use Case)

A team keeps all dev resources in rg-payments-dev with tags env=dev, owner=payments, costcenter=2040 for clear ownership and billing insights.

Hands-on

  1. Create a resource group for a sample app.
  2. Add three tags (env, owner, costcenter).
  3. Create a sample resource (if subscription allows).
  4. Apply consistent naming standard.
  5. Delete resource group to observe lifecycle cleanup behavior.

Try It Yourself

Design naming and tagging standards for three environments: dev, test, prod.

Debugging Scenario

Issue: Team cannot find who owns a costly resource. Fix: enforce mandatory owner/costcenter tags and policy checks on creation.

Interview Questions

Beginner

What is a resource group?

Logical container for related Azure resources.

What are tags used for?

Metadata for governance, filtering, and cost tracking.

Can resources in one app be split across groups?

Yes, but keep organization clear and intentional.

Intermediate

Why use consistent naming convention?

It improves discoverability, automation, and incident response speed.

Where apply RBAC for app team access?

Usually at resource group scope for least-privilege and simplicity.

What is hierarchy role in governance?

It controls inheritance of policy/access from higher scopes.

Scenario-based

Costs rising and ownership unknown.

Standardize tags and enforce policy at subscription level.

Ops team accidentally deleted one resource.

Use role separation and resource locks for critical resources.

Need separate permissions for dev and prod.

Use separate resource groups and scoped RBAC assignments.

Real-world Usage

Strong resource organization is one of the earliest maturity indicators in Azure operations teams.

Summary

ARM gives structure. Resource groups and tags keep Azure environments understandable, governable, and cost-aware.

Previous