Azure / Basic: scope, identity, location, and resources
Azure β Basic: scope, identity, location, and resources
Establish Azure management, permission, failure-domain, network, compute, and storage contracts.
What you will learn
- Separate identity, control plane, data plane, and network boundaries.
- Model capacity and protection with explicit assumptions.
Azure resource hierarchy and responsibility
Distinguish tenant, management group, subscription, resource group, and resource. Build an ownership model before choosing services or making any deployment request.
Start learningMicrosoft Entra identity and Azure RBAC
Separate authentication, directory administration, resource authorization, and data access. Model a principal, role, and scope before interpreting an allowed or denied operation.
Start learningRegions, availability zones, and failure boundaries
Choose location and redundancy from residency, service support, and failure requirements. Distinguish a zone outage from a regional disaster and model surviving capacity explicitly.
Start learningVirtual networks, subnets, and packet decisions
Reason about Azure Virtual Network addressing and traffic boundaries before choosing rules. Separate routing, network security, DNS, service exposure, and application authorization.
Start learningCompute choices and workload responsibility
Choose a hosting model from application requirements rather than service popularity. Compare virtual machines, managed web hosting, functions, and containers while keeping capacity assumptions explicit.
Start learningStorage models, redundancy, and data protection
Choose object, file, or disk storage from access and lifecycle requirements. Separate durability, availability, replication, retention, and recoverability before selecting redundancy.
Start learning