The short version
If you already work with pipelines every week, plan on about 30 to 50 hours over four weeks. If you use only one of Azure DevOps or GitHub today, or you are newer to DevOps, plan on eight weeks and 50 to 80 hours. These are rough planning numbers, not Microsoft figures, and your background changes them a lot. Half of your time belongs to pipelines, because that domain is 50-55% of the exam.
Before you start
Open the Microsoft Learn AZ-400 study guide and keep it beside you. This plan follows the version titled “Skills measured as of July 27, 2026”. Set up what you need for hands-on work: a free Azure DevOps organization, a GitHub account with a test repository, and an Azure subscription you can safely break. Reading about a deployment slot is not the same as swapping one.
Keep a notes table with one row per feature pair that people confuse: what it does, what it does not do, and its neighbor. Examples: Microsoft-hosted versus self-hosted agents, variable groups versus secure files, service principal versus managed identity. Our how to study guide has more on note-taking and spacing.
The 4-week plan (about 8 to 12 hours per week)
Week 1: Source control, collaboration, and planning (domains 1 and 2). Branching strategies, branch policies and branch protection rules, pull request flow, large files, tags, and recovering data with Git. Then GitHub Flow, Boards and Projects, cycle time versus lead time, wikis, and webhooks. About 8 hours. Finish with a short self-quiz.
Week 2: Pipelines, part one. YAML structure, triggers, stages, jobs and dependencies, matrix strategies, templates, variable groups, environments with approvals and checks, agents and runners, and the link between GitHub repositories and Azure Pipelines. Build one real multi-stage pipeline. About 12 hours.
Week 3: Pipelines, part two, and security. Packages and feeds, versioning, testing and code coverage, deployment strategies, slots, feature flags, Bicep and other infrastructure as code, pipeline maintenance. Then service connections, managed identities, Key Vault, OpenID Connect, and scanning tools. About 12 hours.
Week 4: Instrumentation, then review. Azure Monitor, Application Insights, alerts for pipelines, and basic KQL. Spend the rest of the week on your weakest areas and on full practice sets. About 10 hours.
The 8-week plan (about 5 to 8 hours per week)
| Week | Focus |
|---|---|
| 1 | Flow of work, GitHub Flow, Boards and Projects, metrics (cycle time, lead time), wikis, release notes |
| 2 | Branching strategies, pull requests, branch policies and protection rules, tags, large files, recovering and removing data |
| 3 | Pipeline basics in both tools: YAML, triggers, jobs, stages, agents and runners, GitHub-to-Azure Pipelines integration |
| 4 | Reuse and control: templates, variables, environments, checks and approvals, parallelism, packages and feeds, versioning |
| 5 | Testing in pipelines, code coverage, deployment strategies, slots, feature flags, database tasks, infrastructure as code |
| 6 | Pipeline maintenance, then authentication: service principals, managed identities, service connections, GitHub Apps and tokens |
| 7 | Secrets, Key Vault, OpenID Connect, secure files, scanning, then monitoring, alerts and KQL |
| 8 | Full review, timed practice sets, and gap-filling |
Using practice exams in the plan
Take one set early, cold, to find your baseline. It will probably feel humbling, and that is the point. Take the next sets after you finish each block of weeks, and compare the per-domain scores rather than only the total. Read every explanation, including those for questions you got right, since the reasoning on the wrong options is what teaches you to tell similar features apart.
Keep the last, longest set for the end and sit it in one go with a timer. Practice sets measure readiness. They do not replace Microsoft’s learning material or hands-on work, and they are not copies of the real exam.
Weekly rhythm
- Two focused study sessions and one hands-on lab per week.
- After each lab, write down three things that surprised you.
- Once a week, redo the questions you missed, without looking at the answers.
The last 3 days
Three days before: Take a final timed practice set. Review only the domains where you scored lowest, and use your notes table.
Two days before: Redo the hands-on tasks that felt shaky, such as a template reference or a Key Vault access setup. Skim the study guide bullets and mark anything you cannot explain aloud.
The day before: Light review only. Check your booking, ID requirements, and equipment using the exam day guide. Sleep matters more than one more hour of reading.
More guides for AZ-400
- AZ-400 Exam Format: Time, Score, Retakes
- AZ-400 Sample Questions With Answers
- Is AZ-400 Hard? An Honest Difficulty Check
- AZ-400 Prerequisites and Skills Self-Check
- AZ-400 Renewal and Retakes Explained
- Is AZ-400 Worth It? An Honest Look
- AZ-400 Cheat Sheet: Key Facts to Review
- AZ-104 vs AZ-400: Which First?
- AZ-305 vs AZ-400: Which Exam First?
Next step
Once you have a week-by-week plan, check where the points are in domains explained. To add timed practice, our AZ-400 practice tests give you five original sets to work through.
Frequently asked questions
How many hours do I need?
It depends on your experience. A practitioner who builds pipelines weekly may need 30 to 50 hours, while someone newer to DevOps may need 50 to 80. These are planning estimates, not Microsoft figures.
Should I learn Azure DevOps or GitHub first?
Learn the one you use less, early. The exam covers both, and the gaps are usually in the tool you use least.
Do I need to memorize YAML?
You need to recognize the key keywords and what they do, such as dependsOn, matrix, and maxParallel. You can look up exact syntax on Microsoft Learn during the exam, but that costs time.