Azure Services Cheat Sheet
Azure services grouped by compute, data, networking, identity, and operations roles.
Azure is easiest to navigate when you stop treating it as a long list of product names and instead group it by platform jobs. Most teams need the same capabilities regardless of cloud: compute, storage, databases, networking, identity, operations, and delivery. Azure's distinctive strength is how tightly these pieces often connect to Microsoft enterprise tooling and hybrid infrastructure.
Compute and application hosting
Azure offers the familiar spread of virtual machines, container platforms, managed Kubernetes, and serverless functions. The real design choice is operational ownership. Virtual machines maximise flexibility but push patching, scaling, and image hygiene back onto the team. Platform and function services reduce that burden, which helps teams that want faster delivery or more standardised deployment paths.
App hosting decisions also affect identity, networking, and observability later, so they should not be made only on price or novelty.
Data and storage services
Azure storage options cover blobs, files, queues, and disks, while its database portfolio spans relational, document, analytical, and streaming workloads. As in any cloud, matching the data model to the access pattern matters more than memorising the brand names.
Transaction-heavy applications often fit managed relational services. High-scale semi-structured data may fit document or key-value stores. Analytics belongs in systems built for long scans and transformations, not in the same store that handles user-facing writes.
Networking and resource organisation
Azure's networking stack handles segmentation, public ingress, private connectivity, and traffic distribution. Resource groups are a particularly useful organisational concept because they collect related resources for access control, lifecycle management, and automation. They are more than a folder. They shape how teams grant permissions, track cost, and destroy or recreate environments safely.
Identity is central in Azure
Identity and access management are especially important in Azure because many organisations arrive with existing Microsoft directories, enterprise devices, and hybrid estates. Role-based access control, managed identities, and policy enforcement should be designed early. Static secrets and manual access grants do not scale well in a platform that expects automation.
Why Azure often fits certain organisations well
Azure tends to feel natural in environments that already depend on Microsoft tooling, Windows-heavy workloads, or hybrid networking between on-premises systems and cloud resources. That does not make it limited to those cases, but it explains why integration and governance are often part of the value proposition.
A useful mental model
Treat Azure as a platform for composing capabilities, not as a catalogue to memorise. Know your compute model, your data model, your trust boundaries, and your operational needs. Once those are clear, the specific service names become much easier to place, and the platform becomes a practical toolbox instead of a confusing map.