Vocabulary and principles
I can identify the services, architectural concepts, security models, governance tools, and tradeoffs covered by the exam scope.
Verified learning + applied evidence
I use certifications to validate a structured technical foundation, then connect that foundation to projects where the architecture, deployment, security boundaries, tests, and limitations can be inspected.
A certificate does not replace implementation evidence. A project does not automatically prove understanding either. I combine both and state clearly what each one supports.
Microsoft Certified
Azure Fundamentals AZ-900 · EarnedVerified credential
Microsoft identifies Azure Fundamentals as a beginner-level credential for foundational knowledge of cloud concepts, Azure architecture and services, and Azure management and governance.
Evidence model
I can identify the services, architectural concepts, security models, governance tools, and tradeoffs covered by the exam scope.
I can explain why a service or boundary exists and distinguish related concepts instead of relying on isolated product names.
I connect the foundation to source code, deployment choices, tests, operational checks, and published limitations.
I do not use a fundamentals credential to claim administrator-level implementation depth or production expertise across every Azure service.
Active learning path
These are learning targets, not credentials I claim to have earned. They form a coherent path from fundamentals through security, administration, automation, and DevSecOps delivery.
Cloud concepts, Azure architecture, services, management, and governance.
EarnedMicrosoft security, compliance, and identity concepts and product capabilities.
Learning targetAzure identities, governance, storage, compute, networking, and monitoring.
Learning targetCI/CD, source control, release strategy, security, compliance, and instrumentation.
Learning targetGitHub Actions implementation, reusable workflows, security, and troubleshooting.
Parallel learning targetApplied proof
TraceHawk connects AZ-900 concepts to a containerized Azure deployment, separate public and protected trust boundaries, operational health checks, reproducible CI gates, and explicit platform limitations.
Read the TraceHawk case study →The workflow library provides inspectable evidence for repeatable engineering, protected-path controls, security review, validation, and GitLab-first delivery practices that support the GH-200 and AZ-400 direction.
Inspect the AI workflow library →My Microsoft Learn links include the Contributor ID assigned through Microsoft Student Ambassadors: wt.mc_id=studentamb_547047. The parameter attributes relevant Microsoft Learn visits. It is not added to portfolio, GitHub, or Azure Container Apps links.
Certification content last reviewed against the official Microsoft Learn certification page and AZ-900 study guide on July 13, 2026. Microsoft can update exam objectives; the official study guide remains the source of truth.