For Azure DevOps professionals, earning Microsoft AZ-400 means validating the ability to design and implement DevOps practices for Azure-based software delivery.
Updated for 2026: AZ-400, officially titled Designing and Implementing Microsoft DevOps Solutions, is most relevant to practitioners who already understand how software moves from source control into production and now want to prove they can make that process reliable, secure, observable, and repeatable in Azure.
What AZ-400 Measures
AZ-400 is centred on the practical work of DevOps engineering rather than on a single tool. The exam covers how teams plan delivery, manage source control, build continuous integration and continuous delivery pipelines, use infrastructure as code, secure the delivery process, and collect feedback from running systems.
In real projects, those skills rarely appear as separate tasks. A DevOps engineer may need to connect a repository to a pipeline, build and test an application, provision infrastructure with Bicep or Terraform, deploy through controlled environments, and use Azure Monitor or Application Insights to understand whether the release is healthy. The certification matters because it validates that joined-up view of delivery.
The exam is strongly associated with Azure DevOps, Azure Repos, Azure Pipelines, and Azure Artifacts, but modern preparation should also include GitHub integration where relevant. Teams often operate across both GitHub and Azure DevOps, so the useful skill is understanding how identity, repository strategy, build agents, service connections, approvals, secrets, and deployment governance fit together.
Who the Certification Is For
AZ-400 is designed for developers, administrators, release engineers, cloud engineers, and DevOps practitioners who work with Azure delivery pipelines. It is especially useful for professionals moving from building or operating systems into a role where they are responsible for the delivery platform itself.
Microsoft recommends familiarity with Azure administration or Azure development skills before attempting AZ-400. That recommendation is important, but it should not be read as a strict gate. An operations-focused learner may benefit from first strengthening Azure administration fundamentals, while a software-focused learner may need deeper Azure development knowledge before attempting advanced DevOps scenarios.
In practical terms, someone comfortable with networking, identity, compute, storage, application hosting, Git, and basic deployment concepts will usually have an easier path into AZ-400. A learner who is still new to Azure may find the exam harder because pipeline questions often assume an understanding of the platform being deployed to.
How AZ-400 Compares with AZ-104 and AZ-204
AZ-104 and AZ-204 sit beside AZ-400 as useful foundations, but they answer different questions. AZ-104 focuses on administering Azure resources and services. AZ-204 focuses on developing Azure solutions. AZ-400 focuses on designing and implementing the delivery practices that move application and infrastructure changes safely through the lifecycle.
For administrators, AZ-104-style knowledge helps with the infrastructure side of DevOps: subscriptions, identity, role-based access control, networking, monitoring, and operational controls. For developers, AZ-204-style knowledge helps with application architecture, deployment targets, managed identities, event-driven services, and application diagnostics. AZ-400 then brings those areas together through source control, pipelines, automation, governance, and feedback loops.
The sequencing depends on background. An Azure administrator may move naturally from administration into DevOps automation. A developer may move from application delivery into CI/CD design. A practitioner who already works on release pipelines may go directly into AZ-400 preparation, provided they are ready to fill platform gaps as they appear.
Exam Logistics to Check Before Booking
Microsoft maintains the official AZ-400 exam page, skills outline, pricing information, available languages, registration options, accommodation guidance, and exam policies. Those details can change, so candidates should verify them directly on Microsoft Learn before scheduling.
At a high level, candidates should expect a proctored certification exam with scenario-based questions and case-study-style material. The exam is intended to test judgement across DevOps practices, not recall of isolated menu options. Microsoft also publishes the current scoring approach, retake policy, rescheduling rules, and country-specific pricing through its exam and certification policy pages.
This point is worth taking seriously. A candidate who studies from an old outline may spend too much time on older user-interface workflows and too little time on YAML pipelines, security controls, and modern delivery patterns. Before the final weeks of preparation, the official skills outline should be used as the source of truth for what is currently assessed.
What the Skills Look Like in Real Azure DevOps Work
A realistic AZ-400 scenario might begin with a containerised web application stored in Git. A pull request triggers automated build and test jobs, the pipeline publishes an artefact or container image, infrastructure changes are planned with Bicep or Terraform, and a release moves through development, test, and production environments with approvals at the environment boundary.
From there, the delivery process becomes more operational. A canary deployment may release the new version to a limited slice of users before wider rollout. Application Insights and Azure Monitor can track errors, latency, availability, and custom business signals. If the release behaves poorly, the team needs a rollback route, a clear incident trail, and a way to connect production feedback back into backlog work.
This is where AZ-400 becomes more than a list of Azure services. The real skill is making the path from commit to production repeatable and auditable. That includes deciding when to use hosted or self-hosted agents, how to manage service connections, how secrets are stored, whether OpenID Connect can reduce long-lived credentials, how dependency scanning and software bills of materials fit into the build, and how monorepos affect pipeline triggers and build times.
The following simplified YAML example shows the kind of structure candidates should be comfortable reading and adapting. It is not a full production pipeline, but it illustrates how build, infrastructure planning, and a controlled canary deployment can be expressed as stages.
Example — Multi-stage Azure Pipelines YAML for a canary release
trigger:
branches:
include:
- main
pool:
vmImage: ubuntu-latest
stages:
- stage: Build
jobs:
- job: TestAndPackage
steps:
- task: UseDotNet@2
inputs:
packageType: sdk
version: 8.x
- script: dotnet test src/Contoso.Web.Tests/Contoso.Web.Tests.csproj
displayName: Run unit tests
- script: dotnet publish src/Contoso.Web/Contoso.Web.csproj -c Release -o $(Build.ArtifactStagingDirectory)
displayName: Publish application
- publish: $(Build.ArtifactStagingDirectory)
artifact: webapp
- stage: IaCPlan
dependsOn: Build
jobs:
- job: ValidateInfrastructure
steps:
- script: az bicep build --file infra/main.bicep
displayName: Validate Bicep template
- stage: DeployCanary
dependsOn: IaCPlan
jobs:
- deployment: DeployToAppService
environment: prod-canary
strategy:
runOnce:
deploy:
steps:
- download: current
artifact: webapp
- task: AzureWebApp@1
inputs:
azureSubscription: sc-prod-azure
appType: webAppLinux
appName: app-contoso-prod
package: $(Pipeline.Workspace)/webapp
The important lesson is the separation of concerns. Build and test happen before infrastructure validation, and production deployment is tied to an environment where approvals, checks, and audit history can be managed outside the YAML file. Candidates preparing for AZ-400 should understand both the pipeline syntax and the governance controls around it.
Preparation That Builds Useful Skill
The strongest preparation pattern is to build one production-like delivery path and improve it incrementally. Starting with a small application is enough. The value comes from adding source control policies, pull request validation, automated tests, artefact publishing, infrastructure as code, environment approvals, secrets management, deployment strategy, and monitoring one step at a time.
This approach exposes gaps that memorisation hides. For example, a learner may know the phrase continuous delivery but still struggle to design approvals without blocking every deployment. Another may understand build agents in theory but only discover the trade-offs between hosted and self-hosted agents when build dependencies, private networking, licensing, or performance constraints appear.
Common preparation mistakes include relying too heavily on classic pipeline screens, ignoring security and governance, and under-practising rollback strategies. AZ-400 candidates should be comfortable explaining why a pipeline is structured a certain way, how secrets are protected, how policies reduce risk, and how monitoring data influences future releases.
Structured training can help when it gives learners time to practise rather than passively watch demonstrations. Readynez includes hands-on preparation for the exam through its Microsoft Azure DevOps Engineer course, which is most useful for candidates who want guided labs around the skills Microsoft measures.
How Employers Tend to Read AZ-400
In hiring conversations, AZ-400 is usually strongest when paired with evidence of real delivery work. Interviewers often care less about whether a candidate can name every feature and more about whether they can reason through trade-offs: when to use a managed build agent, how to reduce pipeline cost, how to structure releases for a monorepo, or how to recover from a failed deployment.
The certification can support roles such as DevOps engineer, cloud engineer, platform engineer, release engineer, or Azure-focused developer. It is less persuasive when presented as a substitute for practical experience. A candidate who can discuss reproducible pipelines, governance, observability, and release risk will usually make better use of the credential than someone who has only memorised exam terminology.
Where AZ-400 Fits in a DevOps Career
AZ-400 is a good fit when a professional is ready to move from using pipelines to designing them responsibly. The certification aligns well with work that involves CI/CD, infrastructure as code, secure delivery, release governance, and operational feedback in Azure environments.
Teams planning broader Microsoft upskilling may also look at Microsoft training paths alongside DevOps preparation, because AZ-400 often depends on surrounding Azure administration, development, security, and monitoring knowledge. Readynez also offers Unlimited Microsoft Training for organisations or individuals who want access to multiple Microsoft learning paths rather than a single course.
The key takeaway is that AZ-400 is most valuable when preparation mirrors the work: build a pipeline, secure it, deploy with control, monitor the result, and improve the process. Readers with questions about the Azure DevOps Engineer certification path can contact Readynez for guidance on fitting AZ-400 into a wider training plan.
FAQ
What is the Microsoft AZ-400 certification?
AZ-400 is the exam for Designing and Implementing Microsoft DevOps Solutions. It validates skills in DevOps practices for Azure environments, including source control, CI/CD, infrastructure as code, security, compliance, monitoring, and feedback.
Is AZ-104 or AZ-204 required before AZ-400?
AZ-104 and AZ-204 are not formal prerequisites for AZ-400. Microsoft recommends familiarity with Azure administration or Azure development skills because AZ-400 assumes candidates can understand the Azure services being deployed and operated.
What does the AZ-400 exam cover?
The exam covers DevOps strategy, source control, build and release pipelines, infrastructure as code, security and compliance practices, dependency management, monitoring, and continuous feedback. Candidates should always check the current Microsoft skills outline before studying in detail.
How should candidates prepare for AZ-400?
Candidates should prioritise hands-on practice with Git, YAML pipelines, Azure Pipelines, infrastructure as code, environment approvals, secure service connections, and monitoring. A useful study project is to build one application pipeline from source control through test, deployment, observability, and rollback planning.
What roles can AZ-400 support?
AZ-400 can support Azure DevOps Engineer, DevOps Engineer, Cloud Engineer, Release Engineer, Platform Engineer, and similar roles. Its value is strongest when combined with practical experience designing and operating delivery pipelines.
