In May 2020 I sat exam AZ-900 and earned Microsoft Certified: Azure Fundamentals. It is the most basic credential Microsoft offers for Azure, and I mean that as a compliment. It was my deliberate entry point onto the Azure certification path — the foundation everything else at ThreeBIT has been built on since, from Developer Associate to AI Engineer to DevOps Engineer Expert. You have to start somewhere, and I am glad I started at the bottom of the ladder rather than halfway up pretending I already knew the floors below me.
What Azure Fundamentals is
Azure Fundamentals is the beginner-level credential in Microsoft's role-based certification program. Microsoft describes the target candidate plainly: a technology professional who wants to demonstrate foundational knowledge of cloud concepts in general and Microsoft Azure in particular, and it calls the certification "a common starting point in a journey towards a career in Azure."
Two facts about it matter more than people expect. First, there are no prerequisites. You do not need another certification, a degree, or a particular job title to take AZ-900. Microsoft has been explicit since the program launched that fundamentals exams "are not required for any of our role-based certifications" — they are an optional first step, not a gate. Second, fundamentals certifications do not expire. Microsoft's own credential expiration policy puts it in one sentence: "Microsoft fundamentals Certifications do not expire." That is unusual. The role-based certifications I hold above it — associate and expert — are valid for one year and have to be renewed annually so that skills keep pace with a platform that changes every week. Fundamentals sits outside that cycle, because the concepts it tests are the slow-moving bedrock rather than this quarter's service names.
So the credential I earned in May 2020 is still valid today, and will stay valid. It is the one line on my transcript that I will never have to renew.
What it actually certifies
It is easy to wave at "the basics" without saying what they are, so here is the real shape of it. The AZ-900 exam is built around three skill domains, and as of the current (14 January 2026) version of the skills-measured guide the weightings are:
- Describe cloud concepts (25–30%) — what cloud computing actually is: the shared responsibility model, public/private/hybrid cloud models, the consumption-based pricing model, serverless, and the difference between IaaS, PaaS and SaaS. This is the vocabulary section, and getting it precise matters more than it looks.
- Describe Azure architecture and services (35–40%) — the largest chunk: regions, region pairs, availability zones and datacenters; resources, resource groups, subscriptions and management groups; compute (VMs, containers, functions); virtual networking (VNets, peering, DNS, VPN Gateway, ExpressRoute); storage tiers and redundancy; and identity, access and security via Microsoft Entra ID, MFA, RBAC, Zero Trust and Defender for Cloud.
- Describe Azure management and governance (30–35%) — cost management and the pricing calculator, governance and compliance with Azure Policy, resource locks and Microsoft Purview, deployment tooling (the portal, Cloud Shell, ARM templates, infrastructure as code), and monitoring with Azure Advisor, Service Health and Azure Monitor.
The exam itself is straightforward to describe: it is the single exam required to earn the certification, and a score of 700 or greater (on a scale to 1000) is required to pass. Microsoft offers a free practice assessment and an exam sandbox so you know exactly what the environment looks like before you sit it. Note that the precise domain weightings and the service list have drifted since 2020 — Microsoft updates the skills guide periodically, and what I quote above is today's version, not the one I sat. The shape, though, has held remarkably steady: concepts, architecture, governance.
What it does not certify is just as important. AZ-900 does not make you an Azure architect. It does not prove you can design a resilient multi-region system or debug a misbehaving Kubernetes cluster at 2 a.m. It certifies that you can speak the language fluently and reason about the platform correctly — which, it turns out, is the thing most teams are actually missing.
Why I bothered to certify
A fair question, especially aimed at a founder. Nobody was going to fire me for not having AZ-900. I run the company.
I did it for three reasons, and they have only gotten more true over the years.
The first is honesty with myself. It is uncomfortably easy, as someone who has shipped software for a long time, to assume you understand a platform because you have used bits of it. Sitting a structured exam forces you to find the corners you have been quietly avoiding. I knew compute and app hosting cold in 2020. I was far shakier on the governance and cost-management side — Azure Policy, management groups, the pricing model — precisely because those were the parts I had been able to fudge. AZ-900 closed those gaps, and closing them changed how I architected things almost immediately.
The second is customer trust. ThreeBIT builds on the Microsoft stack — .NET, Azure, GitHub — for customers in industries where software failing is not a cosmetic problem but a missed export, a failed payment, a compliance finding. When a customer hands us their cloud, "trust us, we're good" is not an answer. A verifiable credential issued by the platform vendor is. It is not the whole story, but it is a clean, externally-checkable signal that the people building on your Azure tenant actually know what the shared responsibility model means and where the lines are drawn.
The third is team credibility. I cannot, in good conscience, tell the engineers at ThreeBIT that certification matters if I have not done it myself. AZ-900 was me walking the path before asking anyone else to. It is now the first thing I point new hires at, regardless of seniority, because it gives everyone — the senior .NET developer and the person three months into their career — a shared, precise vocabulary for talking about the cloud we all work in. Shared vocabulary is underrated. Half the expensive mistakes I have seen in cloud projects came from two smart people using the same word to mean two different things.
How it shows up in our work at ThreeBIT
This is where a "basic" certification quietly earns its keep.
We make two SaaS products — Xircuit and Outastory — and both run on Azure. Every architectural decision behind them touches the AZ-900 domains directly: which compute model fits a given workload, how we structure subscriptions and resource groups so billing and access make sense, how we tier and replicate storage, how identity flows through Microsoft Entra. None of that is exotic. It is exactly the material AZ-900 covers, and having the whole team fluent in it means design conversations move fast and land in the right place.
It shows up most clearly in cost and governance — the domain I was weakest on going in. A consumption-based platform is wonderful right up until a forgotten resource group quietly bills you every month, or an over-provisioned tier triples a storage line item. The fundamentals — tags, the pricing calculator, Azure Policy, resource locks, Azure Advisor — are the difference between an Azure bill you understand and one you merely receive. We design for that from day one, and we can explain it to customers in their language, because it is the same language the exam taught.
And it is genuinely the floor of the ladder. AZ-900 led me to Azure Developer Associate in early 2021, then to the AI and administrator credentials, then to DevOps Engineer Expert. Each one assumed the vocabulary the fundamentals exam drilled in. I have watched the same progression work for people on the team. You do not have to climb the whole ladder. But standing on the first rung — knowing what a region pair is, what RBAC does, why serverless is priced the way it is — makes everyone you work with, and every customer you serve, a little better off.
That is a lot of value from the most basic credential Microsoft offers. Start at the bottom. It holds the rest up.
Sources & further reading
- Microsoft Learn — Microsoft Certified: Azure Fundamentals (certification overview): https://learn.microsoft.com/en-us/credentials/certifications/azure-fundamentals/
- Microsoft Learn — Study guide for Exam AZ-900: Microsoft Azure Fundamentals (skills measured): https://learn.microsoft.com/en-us/credentials/certifications/resources/study-guides/az-900
- Microsoft Learn — Exam AZ-900: Microsoft Azure Fundamentals: https://learn.microsoft.com/en-us/credentials/certifications/exams/az-900
- Microsoft Learn — Credential expiration policies ("fundamentals Certifications do not expire"): https://learn.microsoft.com/en-us/credentials/support/credential-expiration-policy
- Microsoft Learn — FAQs about renewal (fundamentals don't require renewal): https://learn.microsoft.com/en-us/credentials/certifications/renew-your-microsoft-certification-faq
- Microsoft Learn — Exam scoring and score reports (700 to pass): https://learn.microsoft.com/en-us/credentials/certifications/exam-scoring-reports
- Microsoft Learn — Our New Fundamentals Certification Program Launches (no prerequisites; optional first step): https://learn.microsoft.com/en-us/credentials/certifications/posts/our-new-fundamentals-certification-program-launches-with-azure-and-m365
Image credits
All images are used under their respective Creative Commons or public-domain terms; we are grateful to the creators.
- PDC server room — © Esquilo, CC BY-SA 3.0, via Wikimedia Commons (source).
- Children at school — © Lupuca, CC BY-SA 2.0, via Flickr (source).
- meta_creation lab: inter-actors, atractors and the aesthetics of complexity — © dancetechtv, CC BY-SA 2.0, via Flickr (source).