In July 2022 I passed AZ-400 and earned Microsoft Certified: DevOps Engineer Expert — the only expert-level Microsoft certification I hold, and the one I think of as the capstone of the path. It didn't arrive out of nowhere. Eighteen months earlier, in January 2021, I'd earned Azure Developer Associate, and that turned out to be the load-bearing prerequisite: you cannot earn the expert credential from AZ-400 alone. You have to already hold either Azure Administrator Associate or Azure Developer Associate before the exam grants you the expert cert. For me it was the developer route, and there's a pleasing logic to that — you prove you can build, then you prove you can build and run.
What DevOps Engineer Expert actually is
Let me start with the thing the name doesn't quite tell you. "DevOps Engineer Expert" sounds like it might be a pipeline-plumbing certification — wire up some YAML, get a green checkmark, collect your badge. It isn't, and Microsoft is unusually explicit about that. The official certification describes a DevOps engineer as "a developer or infrastructure administrator who also has subject matter expertise in working with people, processes, and products to enable continuous delivery of value in organizations." People and processes come first in that sentence, before products. That ordering is deliberate.
The structural detail that surprises people is the prerequisite. This is an expert credential, and Microsoft will not hand it to you on the strength of one exam. Before AZ-400 can grant you the expert cert, you must already hold one of two associate-level certifications: Azure Administrator Associate or Azure Developer Associate. The certification page lists "Prerequisites: 2 certifications" for exactly this reason — the expert badge is the combination of the associate foundation plus AZ-400, not the exam in isolation.
I came through the developer door. I'd earned Azure Developer Associate in January 2021, which meant that when I sat AZ-400 in July 2022, the pieces clicked together into the expert credential. If you've only ever administered Azure and never developed on it, you'd come through the administrator door instead and arrive at the same place. Either way, the design forces you to prove genuine depth on one side of the dev/ops divide before it certifies you as the person who spans both.
It's worth being honest about the "expert" label, too. The exam is broad rather than deep in any single tool. As Microsoft's own exam architects put it when they introduced the certification: "As a DevOps engineer, you need to know something about a lot of different areas." You don't need to be able to write flawless Bash or hand-compile C++; you need to know when a given technique, script, or third-party tool is the right call, and when it isn't. The breadth is the point.
What it actually certifies
Here's where the people-and-process framing stops being a slogan and becomes a syllabus. The AZ-400 exam measures five skill areas, and only one of them is really about pipelines in the narrow sense:
- Design and implement processes and communications (10–15%) — traceability and flow of work, GitHub Flow, feedback cycles, dashboards with metrics like cycle time, lead time, and time to recovery, plus the unglamorous discipline of documentation, wikis, release notes and integrating Boards with GitHub and Teams.
- Design and implement a source control strategy (10–15%) — branching strategies (trunk-based, feature branch, release branch), pull-request workflows, branch policies and protection rules, and the genuinely hard bits like scaling a Git repo and recovering or scrubbing data from history.
- Design and implement build and release pipelines (50–55%) — the heart of it: package management, a testing strategy with quality and release gates, YAML pipelines, runners and agents, deployment patterns (blue-green, canary, ring, feature flags), and infrastructure as code with Bicep and ARM.
- Develop a security and compliance plan (10–15%) — identities and service principals, GitHub and Azure DevOps permissions, and managing secrets and certificates with Azure Key Vault and workload identity federation.
- Implement an instrumentation strategy (5–10%) — monitoring the running system so you actually find out when something is wrong.
Read that list as a whole and the shape is clear. Yes, pipelines are the biggest single chunk. But fully half the exam is about everything around the pipeline: how work flows, how teams communicate, how you trace a bug back to a commit, how you keep secrets out of source control, and how you know — in production, at 2am — that the thing you shipped is healthy. A DevOps engineer who can build a beautiful pipeline but can't design the feedback loop around it has missed the assignment.
There's one more fact worth stating plainly, because it changes how you should read any certification claim, including mine: role-based and specialty Microsoft certifications expire after one year. You renew them for free with a short online assessment that opens six months before expiry, and the renewal focuses only on what's changed in the technology since you last passed. So when I say I've held DevOps Engineer Expert since July 2022, what I really mean is that I've renewed it every year since — which, given how fast Azure DevOps, GitHub Actions and the IaC tooling have moved, is arguably the more meaningful claim. A four-year-old static certificate would tell you very little about today's tooling.
Why I bothered to certify
I'll be candid: by 2022 I'd been doing this work for years. I didn't need a badge to tell me how to design a release strategy or wire up Key Vault. So why sit the exam at all?
Three reasons, in increasing order of importance.
The first is structural honesty. When you've done something for a long time, you accumulate habits — some good, some merely familiar. Studying for a broad exam like AZ-400 drags every corner of your practice into the light and asks: is this still the right way, or just the way you've always done it? I came out of the prep having quietly modernised a couple of things in our own delivery process. That alone was worth the exam fee.
The second is the prerequisite chain itself. I'd earned Azure Developer Associate in January 2021 with no grand plan beyond proving to myself that I could pass it cleanly. Once I had it, the expert credential was right there — one more exam, building directly on what I already had. The path Microsoft designed made the capstone feel less like a separate mountain and more like the natural summit of a ridge I was already walking.
The third, and the real one: I run a company that sells Microsoft-stack delivery to clients who are, quite reasonably, trusting us with systems where failure has consequences. "Trust me, I'm experienced" is a weaker sentence than "here is an independently verifiable expert credential, renewed annually, from the vendor whose platform we're building on." The certification isn't why we're good at this. But it's a credible, third-party shorthand for it — and for a small firm in Ibbenbüren competing on substance rather than logo size, credible shorthands matter.
How it shows up in our work at ThreeBIT
This is the part I care about most, because a certification that never touches the actual work is just wall decoration.
At ThreeBIT we don't just build software and throw it over a wall. We build and we run. Every product we ship — Xircuit, Outastory, the bespoke systems we deliver for clients — lives behind pipelines, infrastructure as code, and observability that we own. That's the DevOps Engineer Expert syllabus, lived out daily rather than memorised for an exam.
The clearest example I can give is from the early pandemic. A client needed a COVID testing platform — registration, scheduling, result delivery, the works — and they needed it fast, because the public-health context didn't care about our sprint cadence. We shipped it in two weeks. That speed wasn't heroics or all-nighters. It was infrastructure as code so environments stood up identically and repeatably, build-and-release pipelines so every change reached production through the same tested path, and instrumentation so that once it was live and under real load, we could see what was happening rather than guess. That is, almost line for line, the AZ-400 skills outline — processes, source control, pipelines, security, instrumentation — applied under genuine pressure. The certification didn't make that possible, but it's the formal name for exactly the muscle we used.
The more recent example is how we run AI-assisted development. We give each automated agent its own isolated worktree — its own clean copy of the repository — so several can work in parallel without colliding, and nothing merges until the checks pass. When Microsoft showed essentially this exact pattern as a first-class product feature at Build 2026, we grinned, because it's how we'd already been working. That instinct — isolate the change, automate the verification, gate the merge — is pure source-control-strategy and pipeline-discipline thinking. It's the DevOps Engineer Expert mindset pointed at a brand-new problem.
That's the through-line. The badge sits on a profile page, but the thinking behind it sits in every repository, every pipeline, and every dashboard we maintain. We build for industries where a bug isn't a cosmetic glitch but a missed test result, a failed export, or a compliance finding — and the whole point of DevOps, done properly, is to make shipping into those environments boringly reliable. That's the work. The certification just gives it a name you can verify.
Sources & further reading
- Microsoft — Microsoft Certified: DevOps Engineer Expert (certification details, "people, processes, and products," 2 prerequisite certifications): https://learn.microsoft.com/credentials/certifications/devops-engineer/
- Microsoft — Exam AZ-400: Designing and Implementing Microsoft DevOps Solutions (skills measured, weightings, passing score 700): https://learn.microsoft.com/credentials/certifications/exams/az-400/
- Microsoft — Study guide for Exam AZ-400 (full skills outline, IaC with Bicep, deployment patterns, instrumentation): https://learn.microsoft.com/credentials/certifications/resources/study-guides/az-400
- Microsoft — Level up with Microsoft Certified: DevOps Engineer Expert (prerequisite: Azure Administrator Associate OR Azure Developer Associate): https://learn.microsoft.com/credentials/certifications/posts/level-up-with-microsoft-certified-devops-engineer-expert
- Microsoft — Introducing the Microsoft DevOps Engineer Expert Certification ("you need to know something about a lot of different areas"; third-party tool awareness): https://learn.microsoft.com/credentials/certifications/posts/introducing-the-microsoft-devops-engineer-expert-certification
- Microsoft — Credential expiration policies (role-based and expert certifications valid for one year): https://learn.microsoft.com/credentials/support/credential-expiration-policy
- Microsoft — FAQs about renewal (free annual renewal assessment, opens six months before expiry, ~45 minutes): https://learn.microsoft.com/credentials/certifications/renew-your-microsoft-certification-faq
Image credits
All images are used under their respective Creative Commons or public-domain terms; we are grateful to the creators.
- 1998.11.16 Pipes — © Hermann Luyken, CC BY-SA 3.0, via Wikimedia Commons (source).
- EFTA00000873 - Control room with multiple monitors a laptop and office supplies on a desk set against a wall-mounted screen setup — Federal Bureau of Investigation, Public domain, via Wikimedia Commons (source).
- The Old Servers — © compujeramey, CC BY 2.0, via Flickr (source).