One change, five domains: following a commit from idea to incident
The exam is easiest to hold in your head as the life of a single change. It starts as a work item, becomes a branch, moves through a pipeline, reaches production under security controls, and is finally watched by instrumentation. Each stop is a domain.
Processes and communications (15-20%) covers the front of that journey. You design the flow of work across plan, build, deploy and operate, set up feedback and notifications, track work in Azure Boards, and trace commits back to bugs and quality. Newer in this exam is the collaboration layer for agents: documenting projects with AI assistance, setting requirements and restrictions for agentic development (agents, skills and loops), and configuring MCP servers for Azure DevOps and GitHub.
Source control strategy (10-15%) is the smallest block and the most mechanical. Expect trunk-based, feature, release, Git flow, GitHub flow and Git worktree strategies, pull request workflows enforced by branch policies and branch protection rules (including rules for GitHub Copilot), Git hooks, tags, recovery and removal of data with Git commands, and migrating a repository from Azure DevOps to GitHub.
Build and release pipelines (35-40%) is where the change spends most of its life. It spans package management with Azure Artifacts and GitHub Packages, versioning with SemVer and CalVer, testing strategy and quality gates, runner and agent infrastructure, YAML triggers, templates and environment checks, GitHub Agentic Workflows, deployment patterns such as blue-green, canary, ring and feature flags, infrastructure as code, and pipeline health and retention.
Security and compliance (15-20%) decides whether the change is allowed to ship. You choose between service principals and managed identities, manage GitHub Apps, GITHUB_TOKEN and personal access tokens, implement secretless authentication, integrate Azure Key Vault, prevent leakage, and configure scanning with GitHub Advanced Security and Defender for Cloud DevOps Security.
Instrumentation (15-20%) closes the loop. You build dashboards for cycle time, lead time and time to recovery, connect Azure Monitor and Log Analytics, deploy and configure the Azure Copilot Observability Agent and Azure SRE Agent, analyze telemetry and distributed traces, collect GitHub Copilot agent logs, and query logs with KQL or natural language.
| Domain | AZ-401 weight | AZ-400 weight (July 27, 2026 update) |
|---|---|---|
| Design and implement build and release pipelines | 35-40% | 50-55% |
| Design and implement processes and communications | 15-20% | 10-15% |
| Design and implement a security and compliance plan | 15-20% | 10-15% |
| Implement an instrumentation strategy | 15-20% | 5-10% |
| Design and implement a source control strategy | 10-15% | 10-15% |
Weights from the AZ-401 and AZ-400 study guides on Microsoft Learn. Our own AZ-400 study guide covers the older exam in full.