Microsoft Certified: Azure Developer Associate (AZ-204) often gets mentioned alongside AZ-104, but the two look at Azure from completely different angles. If AZ-104 is the administrator's exam for building and running infrastructure, AZ-204 is the developer's exam for building applications that actually run on top of it. A carpenter builds the structure of a building, while an interior designer fills that structure with spaces people can actually live in. Microsoft recommends one to two years of professional development experience along with Azure exposure before sitting for it, and the gap in perceived difficulty between someone who has deployed code themselves and someone who hasn't is substantial.
Who Needs This Exam, and How Renewal Works
A restaurant chef owns the entire cooking process from prepping ingredients to plating the final dish, and an Azure developer owns a similarly full lifecycle — developing compute solutions, storing data, implementing security, monitoring, and integrating with other services. It fits backend developers deploying applications through Azure Functions or App Service, and full-stack developers building cloud-native apps in .NET, Node.js, or Python. There's no official prerequisite, but like AZ-104, the exam assumes a baseline of Azure fundamentals already in place. True to its Associate level, this certification also needs renewal every 12 months, but a free online assessment on Microsoft Learn handles that without a retake.
Exam Format: Proving Yourself in Code Over 150 Minutes
Like AZ-104, this exam weighs practical response over raw knowledge. It runs 150 minutes across 40 to 60 questions, the passing score is 700 out of 1000, and the exam fee is 165 USD. Question text frequently includes real C#, JavaScript, or Python code snippets and ARM templates, so practice reading code and spotting what's wrong with it matters even more here than it does for AZ-104.
Domain 1: Develop Azure Compute Solutions (25-30%)
Like knowing exactly which size and shape of LEGO brick gets you the structure you want, this domain covers deciding which compute service an application belongs on and actually building it there. It carries the highest weight of any domain, so it decides the outcome of the exam more than any other. The essentials are writing serverless code with Azure Functions and configuring triggers and bindings, deploying web apps through App Service with zero-downtime deployment via slots, and building container images for deployment to Azure Container Apps or AKS. Three related posts cover this domain: Implementing Azure Functions, Implementing App Service Web Apps, and Implementing Container Solutions.
Domain 2: Develop for Azure Storage (15-20%)
Just as a warehouse stores frequently grabbed items differently from ones rarely touched, this domain covers deciding where and how an application stores its data. The essentials are programmatic access to Blob Storage and lifecycle management, choosing a consistency level and designing partition keys in Cosmos DB, and implementing CRUD operations through the SDK. Two related posts cover this domain: Developing Blob Storage Solutions and Developing Azure Cosmos DB Solutions.
Domain 3: Implement Azure Security (20-25%)
A bank doesn't hand its vault key to just anyone, and this domain covers protecting authentication, authorization, and sensitive data at the application code level. The essentials are user authentication through Microsoft Entra ID, service-to-service authentication without credentials via Managed Identity, managing secrets with Key Vault, and controlling access to APIs. The related post Implementing Azure Security Solutions covers this domain in depth.
Domains 4 and 5: Monitor and Optimize, and Connect to Services (25-35%)
Just as a car's dashboard reports engine status while navigation connects you to the wider road network, these two combined domains cover watching how an application behaves and connecting it to other services. The essentials are tracking performance and exceptions with Application Insights, publishing and applying policies to APIs through API Management, and message-based integration through Event Grid, Service Bus, and Queue Storage. Three related posts cover these domains: Monitoring with Application Insights, Developing Message-Based Solutions, and API Management and Event-Driven Solutions.
A Study Order for Beginners, and Common Mistakes
Walking an unfamiliar city without a map means retracing the same streets twice. If you already develop software but Azure is new to you, start with Domain 1 (compute), the highest-weighted domain, and actually deploy Azure Functions and App Service yourself, then move into Domain 2 (storage) and write real data in and out with the Cosmos DB SDK. From there, wire up Managed Identity in Domain 3 (security), and finish by watching your own app through Application Insights across Domains 4 and 5 (monitoring and integration). The most common mistake is skimming a code-snippet question the way you'd skim a knowledge question — without real SDK experience, just figuring out what one line of code does eats up a lot of time. A second common mistake is treating Managed Identity and a Service Principal as the same thing; the key difference is that Managed Identity removes the need to manage credentials at all, and missing that distinction costs points repeatedly.
Exam Key Takeaways
"Runs code in response to events, no server management" -- Azure Functions "Zero-downtime deployment through swappable slots" -- App Service deployment slots "Service-to-service authentication with no credentials to manage" -- Managed Identity "Safely manages secrets and certificates outside your code" -- Azure Key Vault "Globally distributed, tunable consistency levels" -- Azure Cosmos DB "Tracks code performance and exceptions in real time" -- Application Insights "Publishes APIs and applies rate limiting and auth policies" -- API Management "Delivers events to many subscribers via publish-subscribe" -- Event Grid "Message queue where ordering guarantees matter" -- Service Bus "Partition key design determines your actual performance" -- Cosmos DB data modeling
AZ-204 tests whether you've actually deployed something, not whether you know the concept, so the most reliable next step after reading this guide is writing and deploying an Azure Function of your own.