Azure Developer (AZ-204): a practical study guide for working developers

AZ-204 is Microsoft's "you ship code on Azure" cert. Not infrastructure (that's AZ-104). Not architecture (that's AZ-305). Not delivery pipelines (that's AZ-400). It's the day-to-day developer cert for people who write App Service apps, Functions, Durable Functions, and the Cosmos DB queries underneath them.

If that's your job, AZ-204 is the most useful Azure cert you can take. The content overlaps with what you actually do, which makes both the studying and the exam less painful. If your job is "Azure admin" or "cloud architect" without much application code, AZ-204 is wasted effort — pick AZ-104 or AZ-305 instead.

Who AZ-204 is for vs AZ-104 vs AZ-400

Quick disambiguation, because Microsoft's role-based naming creates confusion:

• AZ-104 (Administrator). You provision and operate Azure: VMs, storage, networking, identity, monitoring. You read logs, you don't always write the apps.
• AZ-204 (Developer). You write code that runs on Azure. App Service, Functions, container apps, Cosmos DB SDK calls, Service Bus message handlers, Key Vault references. You don't necessarily own the subscription's networking.
• AZ-400 (DevOps Expert). You design and run the delivery pipelines. CI/CD with GitHub Actions or Azure DevOps, IaC with Bicep/Terraform, release strategies, observability. Expert-tier; assumes AZ-104 or AZ-204 underneath.

If you're a backend developer at a company that runs on Azure, AZ-204 is the natural cert. If you're a platform engineer who builds the runways those backend devs ship on, AZ-400 is. Most people get the wrong one because the names sound aspirational.

What AZ-204 actually tests

The official skills outline at learn.microsoft.com/credentials/certifications/azure-developer/, last meaningfully refreshed in early 2024, breaks into:

• Develop Azure compute solutions (~25%). App Service web apps, Azure Functions, container solutions (ACI, ACA, AKS at the developer level — not infra-deep).
• Develop for Azure storage (~15-20%). Blob Storage operations, Cosmos DB SDK across SQL and table APIs, Azure Table Storage. Lots of "given this code, what's wrong" questions.
• Implement Azure security (~20%). Microsoft Entra ID authentication in code (MSAL library), managed identities, Key Vault references, secure access tokens, certificate-based auth.
• Monitor, troubleshoot, and optimize Azure solutions (~15-20%). Application Insights, Log Analytics queries, autoscaling, caching with Azure Cache for Redis, Azure CDN.
• Connect to and consume Azure services and third-party services (~15-20%). API Management, Event Grid, Event Hubs, Service Bus, message-driven patterns.

Notice what's not heavily tested: networking internals, RBAC at admin depth, Azure Policy, governance. That's AZ-104 / AZ-305 territory. AZ-204 stays in the developer's lane.

What's heavily tested in practice

A few areas show up disproportionately on the exam relative to their share of the skills outline:

App Service deployment slots. How they work, when to use them, how slot swaps interact with auto-swap and warmup. There are usually 3-5 questions on slots alone, and they're easy points if you've used them.

Azure Functions triggers and bindings. Specifically the input/output binding syntax, how to consume Service Bus messages from a function, Durable Functions orchestration patterns (function chaining, fan-out/fan-in, async HTTP APIs, monitor pattern). Memorize the durable orchestration patterns by name.

Cosmos DB consistency levels. Strong, bounded staleness, session, consistent prefix, eventual. Microsoft loves asking which to pick under specific latency / consistency / cost trade-offs. Real answer: 90% of production workloads use session and that's almost always the right pick on the exam too. But know the others for the edge cases.

Managed identities (system-assigned vs user-assigned). When you'd pick one over the other, how to grant them access to Key Vault, how the token-acquisition flow works under the hood. This is heavily tested because it's Microsoft's preferred secure-coding pattern and they want you to know it.

Key Vault references in App Service config. The @Microsoft.KeyVault(...) syntax, how App Service resolves it at startup, what happens when the reference fails.

Azure SDK retry patterns. Polly is mentioned. Exponential backoff, circuit breaker, timeout. Real-world useful, often tested.

What's tested less than candidates expect: AKS internals (it's covered, but lightly — Kubernetes-deep questions are AKS specialty territory), networking, and detailed billing. The exam is genuinely developer-focused.

A study plan that doesn't burn you out

Realistic timeline if you've shipped Azure code professionally for 6+ months: 4-6 weeks at 6-10 hours per week. If you're newer to Azure or to backend development in general, 8-12 weeks.

Weeks 1-2: Skim Microsoft Learn for blind spots. The official AZ-204 path is comprehensive but bloated. Don't read it cover-to-cover. Take a practice exam cold first, see which domain you're weakest in, and use Microsoft Learn to fill those specific gaps. If you've never used Durable Functions, that's almost certainly your blind spot — start there.

Weeks 2-4: Build something small. This is the part most candidates skip and shouldn't. Spin up a free-tier Azure account, deploy a basic App Service web app from VS Code, add a Function with a Service Bus trigger, wire in Cosmos DB, secure it with a managed identity, and pull a secret from Key Vault. The whole thing fits in a weekend. Doing it once cements maybe 30% of the exam content in a way that no amount of reading does.

Weeks 4-5: Practice exams. CertLabPro's AZ-204 question bank covers the patterns; MeasureUp is the official partner if you want one premium source. Take 2-3 timed mocks. Pay attention to the code-snippet questions specifically — they're a different style than pure conceptual questions and need practice to read quickly.

Week 5-6: Weak areas and the parts you don't do at work. Most working Azure devs have a heavy lean (App Service / Functions / Cosmos DB) and gaps in messaging or API Management. Spend the final stretch on whichever one you don't touch professionally. The exam will absolutely test the area you haven't used.

Resources I'd actually recommend

• Microsoft Learn AZ-204 path. Free, official, exam-aligned. Don't read it linearly.
• John Savill's AZ-204 study cram on YouTube. Free community resource. Savill's series is faster than the average Udemy course and covers the right material.
• Scott Duffy's Udemy course. Decent, broad, dated in places — refresh-checked in 2024 but the App Service content has shifted slightly since. Use it if you prefer video, but treat it as a starting point.
• Microsoft Learn sample code repos. The Azure-Samples GitHub org has working examples for Functions bindings, Cosmos DB SDK, MSAL flows. Reading working code teaches faster than reading docs about the code.
• Pluralsight's AZ-204 path. Solid for visual learners. The Functions and Cosmos DB modules are the strongest.

What I'd skip:

• Cert dump sites. Question accuracy is bad, the legal exposure is real, and Microsoft's exam content rotates frequently enough that dumps go stale.
• Five-hour deep-dive tutorials on niche services. AZ-204 doesn't reward depth in any single service; it rewards breadth across the developer-relevant Azure surface.

What it pays for

Realistic 2026 US comp for AZ-204 holders is similar to AZ-104: $100k-$150k base for mid-career developers, with $130k-$190k+ in coastal hubs. The cert by itself contributes maybe $5k-$15k to the offer. The compounding signal is: AZ-204 + a real GitHub portfolio of Azure work + 2-3 years of shipped production Azure apps gets you onto senior backend / cloud-native developer shortlists in a way that any one of those alone doesn't.

It's particularly valuable for backend developers pivoting from on-prem .NET to cloud-native .NET, where Microsoft-stack employers use AZ-204 as the explicit "this person has made the jump" signal.

When to skip AZ-204

If your Azure work is 90% writing infrastructure-as-code and tuning App Service plans rather than writing application code, AZ-104 fits better. If you're building real ML pipelines, DP-100 (or DP-203 for data engineering) is closer. If you live in DevOps tooling, AZ-400.

AZ-204 is for people who write code that runs on Azure. If that's not your day job, the cert won't pay you back proportionally.

Bottom line

AZ-204 is one of the more useful Microsoft developer credentials because the content closely matches the work. The exam is fair if you've actually shipped Azure code; it's hard if you've only read about it. Six weeks of focused study, plus one weekend project, gets most working developers comfortably to a passing score.

If you're starting today, browse the AZ-204 question bank or start a timed practice. Then go ship something on Azure this weekend. The cert is mostly an excuse to do that anyway.