openskills.info
Microsoft Azure Fundamentals logoCourse Preview

Microsoft Azure Fundamentals

Microsoft Azure is a cloud computing platform for running applications, storing data, connecting networks, and managing technology resources. You create those resources on demand while Microsoft operates the underlying datacenters and physical infrastructure.

itCloud computing

Microsoft Azure Fundamentals: a calm map

Microsoft Azure is a cloud platform for renting the computing, storage, networking, data, identity, and management parts of an IT system instead of owning every physical layer. The catalogue is large because a datacenter has many jobs, not because every workload needs every service. Start with the workload and the responsibility it leaves with the customer. The cloud is helpful, but it has not eaten the need to know who owns the data and access.

The first useful anchor is the cloud service model. Infrastructure as a service leaves more operating work with the customer. Platform as a service runs more of the platform for you. Software as a service delivers the application itself. Responsibility moves as the model changes, but data, identities, accounts, and access management remain on the customer side of the desk. That is less exciting than a product launch, which is precisely why it prevents expensive surprises.

Azure's second anchor is its hierarchy: management group, subscription, resource group, then resource. A resource group is not a decorative folder for things that looked related on Tuesday. It gathers resources that share a lifecycle, while a subscription provides a management and billing boundary. Azure Resource Manager is the common control plane that handles management requests from the portal, command line, templates, and code. It is why scope appears everywhere, even when the portal tries very hard to look like a collection of buttons.

Location is the third anchor. A region affects latency, service availability, data location, cost, and recovery. Availability zones can tolerate supported failures inside a region; they are not a tiny, preassembled multi-region recovery plan wearing a reassuring label. Add identity, Azure RBAC, Policy, tags, locks, Monitor, and Cost Management and the map becomes practical: who can change a resource, which state is allowed, and how health and cost become visible.

Read the intro for the full map and the glossary when the names begin to multiply. Use the slides for the relationships between scopes and controls. Keep the cheatsheet nearby when comparing service models, resilience choices, and governance controls. The practice reference turns the map into a workload review, and the exercise asks you to make the tradeoffs explicit. Azure does not need to be memorized as a catalogue. It needs to be approached as a set of boundaries and decisions.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

Sources