Cloud computing means renting standardized computing capabilities through an API instead of buying and maintaining every server yourself. Microsoft Azure is a global cloud platform that provides compute, storage, networking, databases, identity, security, data, integration, developer, and AI services under one control plane and billing system.
Method note: This chapter builds the conceptual model used by every Azure tool; it does not deploy a resource. Equivalent Portal and automation paths begin with subscription context in the portal tour and resource creation in Azure Foundations.
Traditional infrastructure makes you predict demand, buy equipment, wait for delivery, install it, and keep spare capacity. Azure lets you request resources in minutes, scale them, measure consumption, automate their configuration, and delete them when the need ends. You still own architecture, access, data, and cost decisions.
Cloud does not mean “someone else handles everything.” It changes the boundary of responsibility.
A region is a geographic area containing one or more datacenters. An availability zone is a physically separate datacenter grouping within a supported region, with independent power, cooling, and networking. Region choice affects latency, price, legal requirements, feature availability, quota, and disaster-recovery design.
Do not choose a region only because it is first in a list. Ask:
Adding instances can improve availability, but only if traffic is distributed and state is handled safely. Backups improve recoverability, but a backup you never restore-test is only a hope.
Azure meters different units: instance time, requests, tokens, storage capacity, transactions, provisioned throughput, data processing, and outbound transfer. “Serverless” can remove idle compute charges but still has executions, networking, logging, and downstream service costs.
Estimate before you build, set a budget, tag resources, inspect cost daily during a lab, and delete what you do not need.
The portal is a graphical client of Azure's control plane. Azure CLI, PowerShell, Bicep, Terraform, SDKs, and REST ultimately request changes from the same platform. A resource created in one interface is visible in the others because the resource—not the tool—is the source of truth.