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 | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Intro
Microsoft Azure Fundamentals
Microsoft Azure is a cloud computing platform. It provides compute, storage, networking, database, identity, security, monitoring, and management services through a common control plane.
The useful mental model is not a list of product names. Azure is a hierarchy of scopes containing resources. An identity requests an action. Azure Resource Manager authenticates and authorizes the request. The selected resource provider then handles it. Governance, monitoring, and cost controls help you keep the result safe and visible.
This course gives you that map. It prepares you to explore Azure services and the Microsoft Learn material for Azure Fundamentals. It does not replace service-specific design, hands-on practice, or current pricing and availability checks.
Cloud choices come before Azure choices
Cloud computing gives you computing resources on demand instead of requiring you to own every physical server and datacenter. Public cloud services run on infrastructure owned by a cloud provider. A private cloud dedicates a cloud environment to one organization. A hybrid approach connects cloud and on-premises environments.
Service models change how much of the stack you operate:
- Infrastructure as a service gives you virtualized infrastructure. You manage operating systems, applications, and much of the configuration.
- Platform as a service gives you a managed application platform. You focus more on the application and less on operating systems.
- Software as a service gives you a complete application. You configure and use it without operating its platform.
The shared responsibility model follows these choices. Microsoft always operates the physical datacenter, physical network, physical hosts, and hypervisor. You always remain responsible for your data, identities, accounts, and access management. Your other responsibilities change with the service model.
Continue the course
This section is part of the paid course.
See pricing to subscribe, or log in if you already have access.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://learn.microsoft.com/en-us/training/paths/microsoft-azure-fundamentals-describe-cloud-concepts/
Supports
- The Azure Fundamentals path covers cloud concepts, deployment models, shared responsibility, cloud benefits, and service types
- The path assumes only basic familiarity with IT terms and concepts
- https://learn.microsoft.com/en-us/training/paths/azure-fundamentals-describe-azure-architecture-services/
Supports
- The Azure Fundamentals path covers architecture, compute, networking, storage, identity, access, and security
- Azure services are grouped into workload-oriented capability families
- https://learn.microsoft.com/en-us/training/paths/describe-azure-management-governance/
Supports
- The Azure Fundamentals path covers cost management, governance, deployment, resource management, and monitoring
- https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/overview
Supports
- Azure Resource Manager is the Azure deployment and management service
- Management groups, subscriptions, resource groups, and resources form the four management scopes
- Higher-scope settings can apply to lower scopes
- A resource group contains related resources for an Azure solution
- A resource belongs to one resource group at a time
- Portal, CLI, PowerShell, SDK, REST, ARM template, and Bicep operations use the Resource Manager layer
- ARM templates and Bicep use declarative syntax
- https://learn.microsoft.com/en-us/azure/reliability/availability-zones-overview
Supports
- Availability zones are separated groups of datacenters within a region
- Zones have independent power, cooling, and networking
- Zonal and zone-redundant resources have different customer responsibilities
- Zone resilience protects against a zone failure rather than an entire regional failure
- Availability support varies by service, region, and configuration
- https://learn.microsoft.com/en-us/azure/security/fundamentals/shared-responsibility
Supports
- IaaS, PaaS, and SaaS move different operating responsibilities to Microsoft
- Customers always retain responsibility for data, identities, accounts, and access management
- Microsoft operates physical datacenters, physical networks, physical hosts, and hypervisors
- Azure Virtual Machines, App Service, Functions, Storage, and Azure SQL Database represent different service models
- https://learn.microsoft.com/en-us/azure/role-based-access-control/overview
Supports
- Azure RBAC authorizes access to Azure resources
- A role assignment combines a security principal, role definition, and scope
- RBAC scopes include management group, subscription, resource group, and resource
- Security principals include users, groups, service principals, and managed identities
- https://learn.microsoft.com/en-us/azure/governance/policy/overview
Supports
- Azure Policy evaluates resources and actions against organizational rules
- Policy can audit, deny, modify, deploy, or remediate based on its effect
- Azure RBAC controls user actions while Azure Policy evaluates compliance
- https://learn.microsoft.com/en-us/azure/azure-monitor/fundamentals/overview
Supports
- Azure Monitor collects and analyzes metrics, logs, traces, and events
- Azure Monitor supports alerting and actions based on telemetry
- https://learn.microsoft.com/en-us/azure/cost-management-billing/costs/overview-cost-management
Supports
- Microsoft Cost Management provides cost analysis, budgets, and optimization capabilities
- Cost tools support analysis of actual Azure spending
- https://learn.microsoft.com/en-us/azure/well-architected/what-is-well-architected-framework
Supports
- The five pillars are Reliability, Security, Cost Optimization, Operational Excellence, and Performance Efficiency
- The framework presents recommendations, risk considerations, and tradeoffs
- https://github.com/lukemurraynz/awesome-azure-architecture
Supports
- The curated list covers Azure architecture blogs, videos, tutorials, code, tools, and scripts
- The list includes Azure Verified Modules, PSRule for Azure, Azure Monitor Baseline Alerts, and AzAdvertizer
- https://azure.github.io/Azure-Verified-Modules/
Supports
- Azure Verified Modules publishes reusable infrastructure as code modules
- https://azure.github.io/PSRule.Rules.Azure/
Supports
- PSRule for Azure checks Azure infrastructure as code against documented guidance
- https://azure.github.io/azure-monitor-baseline-alerts/
Supports
- Azure Monitor Baseline Alerts provides alert definitions and guidance
- https://www.azadvertizer.net/
Supports
- AzAdvertizer provides searchable Azure governance definition and role metadata
