Microsoft cloud
Azure
Microsoft Azure
Microsoft Azure is Microsoft's public cloud computing platform, offering compute, storage, networking, database, identity, and AI services on a consumption-based model across a global network of data centre regions.
Why Azure matters in a Microsoft estate
Azure matters because Microsoft 365, Azure, Windows 365, Teams, and related services are usually managed as one estate. The term connects to planning, cost, configuration, security, and day-two operational decisions across that estate.
How Azure shows up in practice
It underpins most of the Microsoft cloud estate that IT teams manage day to day, whether they realise it or not: Windows 365 Cloud PCs, Azure Virtual Desktop session hosts, Microsoft Entra ID, and a large share of Microsoft 365's backend infrastructure all run on Azure. This means Azure health, capacity, and cost management indirectly affect services that look, on the surface, like standalone Microsoft 365 or Windows 365 products. Core building blocks include virtual machines and scale sets for compute, blob and disk storage, and virtual networks and network security groups for connectivity. Azure Resource Manager is the deployment and management layer that groups every resource into subscriptions and resource groups and applies role-based access control and policy consistently across them.
Pricing is where Azure differs most sharply from traditional on-premises infrastructure and from fixed-fee SaaS: nearly everything is billed per second or per hour of actual consumption, across dozens of meter types (compute hours, storage transactions, egress bandwidth, reserved capacity discounts). This makes cost genuinely hard to forecast without active monitoring, and it is why tools like Azure Advisor, Cost Management budgets, and reserved instance or savings plan commitments exist as first-class parts of the platform rather than afterthoughts. For estates running Windows 365 or Azure Virtual Desktop, Azure costs typically show up in two places: the underlying compute, storage, and networking consumed by session hosts and Cloud PCs, and any Azure-native services layered on top such as Azure Files for FSLogix profile containers, Azure Backup, or Log Analytics workspaces used for monitoring.
A common estate-level trap is treating Azure spend as a fixed IT overhead rather than an operational variable. Orphaned disks left behind after a virtual machine is deleted, oversized VM SKUs provisioned for peak load but never right-sized down, and dev/test resources left running outside business hours are all extremely common, and collectively account for a large share of avoidable Azure waste in real subscriptions. Governance at scale is handled through management groups, which let policies, budgets, and RBAC assignments cascade down across many subscriptions at once. Azure Policy adds to this, enforcing naming conventions, tagging, allowed regions, or SKU restrictions automatically rather than relying on manual review.