The Azure certification path, from fundamentals to expert

Microsoft's certification lineup looks like an intimidating wall of codes until you see the shape underneath it. There are only three tiers, and your job is to walk one branch of them — not to collect the whole set.

New to cloud? CAMPUX is a free, build-first course. Start here →

The Azure certification path is tiered: start with a Fundamentals exam (AZ-900), move to an Associate that matches your role (AZ-104 for administrators, AZ-204 for developers), then an Expert or Specialty (AZ-305 architect, AZ-400 DevOps, AZ-500 security). Pick the branch by the job you want, not by collecting badges. Everything below is the long version of that sentence: what each tier is for, which branch fits which job, and how long the climb actually takes.

One caution before the details. Microsoft renames, retires, and consolidates exams on its own schedule, and it does so more often than most guides admit. As I write this, the developer Associate exam is being wound down and the security Associate is being folded into a broader cloud-and-AI security exam. So treat the specific codes here as a snapshot, anchor on the ones that have been stable for years, and confirm the live list on Microsoft Learn before you register for anything.

How the Azure cert path is structured (the tiers)

Strip away the branding and there are three levels stacked on top of each other:

• Fundamentals. One entry-level exam that proves you know the vocabulary — what a region is, how the pricing model works, what the major service families do. No prerequisites, no hands-on experience assumed. This is where a career-changer starts.
• Associate. The tier that actually maps to a job. These exams assume roughly one to two years of hands-on work and test whether you can do the day-to-day of a specific role: administer, develop, secure, engineer data. An Associate cert is the one most hiring filters are looking for.
• Expert and Specialty. Expert exams sit at the top of a role ladder — architect, DevOps engineer — and assume you already work at that level. Specialty exams run sideways instead of up: narrow, deep credentials for a specific product area rather than a broader role.

The mistake I see most is people treating this as a staircase they must climb one step at a time, from Fundamentals to Expert, collecting every badge on the way. It is not. It is a tree. You pick a branch early — usually at the Associate level — and the exams you skip are not failures, they are just other people's branches.

It isn't a staircase you climb. It's a tree, and you only walk one branch of it.

Start here: Fundamentals

For most people arriving from another field, the first exam is AZ-900, Azure Fundamentals. It has no prerequisites, it is the cheapest exam in the catalogue, and it does two useful things at once. It teaches the shared vocabulary that every later exam quietly assumes you already have, and it proves — to an employer and to yourself — that you can sit a Microsoft exam and pass it. That second point matters more than people expect when the nerves hit.

There is a narrow group who can skip it: if you already work with cloud infrastructure every day and the words resource group, availability zone, and shared responsibility are already boring to you, register straight for the Associate. AZ-900 is recommended, never required. We wrote a full argument for and against it in is the AZ-900 worth it, and a side-by-side of the first two rungs in AZ-104 vs AZ-900.

Microsoft also runs sibling Fundamentals exams that sit next to AZ-900 rather than under it — AI-900 for AI concepts, DP-900 for data concepts. They are optional flavours, not steps you must take. Pick one only if the associated branch (data, AI) is the direction you are actually heading.

Pick your Associate by role

This is the tier that decides your career direction, so it deserves the most thought. An Associate certification is Microsoft's way of saying "this person can hold down this role," and the exam you choose should match the job title you want on your next offer letter — not the one that looks most impressive.

The long-stable administrator exam is AZ-104, Azure Administrator Associate. It is the durable centre of gravity for the infrastructure branch: it maps cleanly to cloud engineer and cloud administrator roles, and it is the prerequisite most Expert paths lean on. For developers, Microsoft has run AZ-204, Azure Developer Associate for years, though it is being retired and its content reorganised, so a developer reading this should check Microsoft Learn for the current replacement before committing. The security Associate has been AZ-500; it is being consolidated into a broader cloud-and-AI security exam, so confirm which code is live when you register. Data engineering has its own Associate track as well.

The through-line: do not agonise over which Associate is "best." There is no best. There is only the one that matches the work you want to be doing on a Tuesday afternoon.

Expert and Specialty tiers

Two exams anchor the Expert tier of the Azure world. AZ-305, Azure Solutions Architect is the design credential — it tests whether you can turn requirements into an architecture that will not fall over. AZ-400, DevOps Engineer sits at the top of the delivery branch, covering pipelines, release strategy, and the automation glue between development and operations. Both assume you already have real Associate-level ground under you; Microsoft has historically pointed candidates at an Associate cert first, so check the current prerequisite guidance rather than assuming.

Specialty exams are a different animal. Instead of climbing higher up a role, they go deeper into one product area — the kind of narrow, focused credential you earn when your job has pulled you into a specific corner of the platform. Most people never need one. You will know if you do, because the work will have taken you there first. If you are still weighing the architect direction against the hands-on engineering one, we compared them in cloud engineer vs solutions architect.

A role-by-role recommended path

Here is the tree drawn out. Read across your target role and the branch is the column of exams to walk. Codes are current as of this writing; confirm each on Microsoft Learn before you book, because the security and developer rows in particular are in motion.

Notice that most branches share the same trunk — AZ-900, then AZ-104 — and only fork near the top. If you are undecided, that is genuinely good news: the first year of study is nearly identical whichever direction you eventually pick, so you do not have to choose your whole career before your first exam.

Timelines, honestly. AZ-900 is a two-to-three-week evening project for most people. AZ-104 is a real exam that takes two to three focused months, more if you are also holding down a full-time job. The Expert exams are not something to rush toward — plan on six-plus months of actual hands-on work between your Associate and an attempt at AZ-305 or AZ-400. Start to Expert, done properly, is closer to twelve to eighteen months than to a summer.

The honest part: certs vs shipped projects

A certification is a key, not a door. It gets you past the automated resume screen and the HR filter that pattern-matches on "AZ-104," and that is a real, worth-having function — plenty of good applications die at that gate for want of a single line. But the cert does not walk you through the interview that comes after. Nobody has ever been hired because a recruiter was moved by a badge on its own.

What actually closes the offer is the thing you can talk about for ten minutes without notes: the network you designed, the pipeline you broke and fixed, the cost you cut. A cert says you passed a test about the platform. A project says you have used it, made decisions, hit a wall, and got past it — which is the only question the person across the table is really trying to answer.

So run both tracks at once. Study for the Associate that matches your branch, and while you study, build the things the exam describes instead of only reading about them. The exam gets you seen; the projects get you hired. That is the whole game, and it is why every class in our track ends in something you built rather than a quiz you passed.

Common questions