Version : 1.0 · Date : 2026-10-22
Cours complet pour l'examen AZ-400 : Designing and Implementing Microsoft DevOps Solutions (certification Microsoft Certified: DevOps Engineer Expert, prérequis AZ-104 ou AZ-204), compétences mesurées au 27 juillet 2026. Un chapitre par bloc de compétences, Azure DevOps et GitHub côte à côte, avec schémas draw.io, Mermaid, exemples YAML Azure Pipelines et GitHub Actions, CLI az devops / gh, Bicep et Terraform, labs, pièges d'examen et scénarios corrigés. Toutes les informations viennent de Microsoft Learn et de GitHub Docs, lues les 21 et 22/10/2026. Les noms de services, fonctionnalités, rôles et menus sont en anglais, comme dans les portails et à l'examen.
Relire le guide AZ-400 avant l'examen. Une évaluation d'entraînement officielle et gratuite existe sur Microsoft Learn. Plusieurs fonctionnalités GitHub dépendent du plan (Free, Team, Enterprise) et changent souvent : les vérifier avant l'examen.
Les domaines de l'examen#
| Domaine (intitulé officiel, en anglais) | Poids | Chapitres |
|---|---|---|
| Design and implement processes and communications | 10 à 15 % | 01 |
| Design and implement a source control strategy | 10 à 15 % | 02 |
| Design and implement build and release pipelines | 50 à 55 % | 03, 04, 05, 06 |
| Develop a security and compliance plan | 10 à 15 % | 07 |
| Implement an instrumentation strategy | 5 à 10 % | 08 |
Score de réussite : 700 sur 1000. Le domaine des pipelines pèse plus de la moitié de l'examen : les chapitres 03 à 06 sont prioritaires. Le cours renvoie à SC-500 (identités, Key Vault, IaC sécurisée, Defender for Cloud DevOps security), AKS (GitOps, CI/CD OIDC) et AI-300 (MLOps) au lieu de les répéter.
Les chapitres#
Chaque chapitre suit le même plan : ce que l'examen demande (texte officiel), concepts, schémas, mise en œuvre, tableaux comparatifs, labs conseillés, pièges d'examen, scénarios corrigés, pour aller plus loin, fiche à retenir et références.
Couverture des objectifs de l'examen#
Les 86 compétences du guide d'étude, chacune reliée à la section qui la traite (vérification du 22/10/2026).
Design and implement processes and communications (10 à 15 %)#
| Ch. | Compétence mesurée (guide officiel, en anglais) | Section |
|---|---|---|
| 01 | Design and implement a structure for the flow of work, including GitHub Flow | 2.1 |
| 01 | Design and implement a strategy for feedback cycles, including notifications and GitHub Issues | 2.2 |
| 01 | Design and implement integration for tracking work, including GitHub projects, Azure Boards, and repositories | 2.3 |
| 01 | Design and implement source, bug, and quality traceability | 2.4 |
| 01 | Design and implement a dashboard, including flow of work, such as cycle times, time to recovery, and lead time | 3.1 |
| 01 | Design and implement appropriate metrics and queries for project planning | 3.2 |
| 01 | Design and implement appropriate metrics and queries for development | 3.3 |
| 01 | Design and implement appropriate metrics and queries for testing | 3.4 |
| 01 | Design and implement appropriate metrics and queries for security | 3.5 |
| 01 | Design and implement appropriate metrics and queries for delivery | 3.6 |
| 01 | Design and implement appropriate metrics and queries for operations | 3.7 |
| 01 | Document a project by configuring wikis and process diagrams, including Markdown and Mermaid syntax | 4.1 |
| 01 | Configure release documentation, including release notes and API documentation | 4.2 |
| 01 | Automate creation of documentation from Git history | 4.3 |
| 01 | Configure integration by using webhooks | 4.4 |
| 01 | Configure integration between Azure Boards and GitHub repositories | 4.5 |
| 01 | Configure integration between GitHub or Azure DevOps and Microsoft Teams | 4.6 |
Design and implement a source control strategy (10 à 15 %)#
| Ch. | Compétence mesurée (guide officiel, en anglais) | Section |
|---|---|---|
| 02 | Design a branch strategy, including trunk-based, feature branch, and release branch | 2 |
| 02 | Design and implement a pull request workflow by using branch policies and branch protection rules | 3 |
| 02 | Implement branch merging restrictions by using branch policies and branch protection rules | 4 |
| 02 | Design and implement a strategy for managing large files, including Git Large File Storage (LFS) and git-fat | 5 |
| 02 | Design a strategy for scaling and optimizing a Git repository, including Scalar and cross-repository sharing | 6 |
| 02 | Configure permissions in the source control repository | 7 |
| 02 | Configure tags to organize the source control repository | 8 |
| 02 | Recover specific data by using Git commands | 9 |
| 02 | Remove specific data from source control | 10 |
Design and implement build and release pipelines (50 à 55 %)#
| Ch. | Compétence mesurée (guide officiel, en anglais) | Section |
|---|---|---|
| 03 | Recommend package management tools including GitHub Packages and Azure Artifacts | 2 |
| 03 | Design and implement package feeds and views for local and upstream packages | 3 |
| 03 | Design and implement a dependency versioning strategy for code assets and packages, including semantic versioning (SemVer) and date-based (CalVer) | 4 |
| 03 | Design and implement a versioning strategy for pipeline artifacts | 5 |
| 03 | Design and implement quality and release gates, including security and governance | 6 |
| 03 | Design a comprehensive testing strategy, including local tests, unit tests, integration tests, and load tests | 7 |
| 03 | Implement tests in a pipeline, including configuring test tasks, configuring test agents, and integration of test results | 8 |
| 03 | Implement code coverage analysis | 9 |
| 04 | Select a deployment automation solution, including GitHub Actions and Azure Pipelines | 2 |
| 04 | Design and implement a GitHub runner or Azure DevOps agent infrastructure, including cost, tool selection, licenses, connectivity, and maintainability | 3 |
| 04 | Design and implement integration between GitHub repositories and Azure Pipelines | 4 |
| 04 | Develop and implement pipeline trigger rules | 5 |
| 04 | Develop pipelines by using YAML | 6 |
| 04 | Design and implement a strategy for job execution order, including parallelism and multi-stage pipelines | 7 |
| 04 | Develop and implement complex pipeline scenarios, such as hybrid pipelines, VM templates, and self-hosted runners or agents | 8 |
| 04 | Create reusable pipeline elements, including YAML templates, task groups, variables, and variable groups | 9 |
| 04 | Design and implement checks and approvals by using YAML-based environments | 10 |
| 05 | Design a deployment strategy, including blue-green, canary, ring, progressive exposure, feature flags, and A/B testing | 2 |
| 05 | Design a pipeline to ensure that dependency deployments are reliably ordered | 3 |
| 05 | Plan for minimizing downtime during deployments by using load balancing, rolling deployments, and deployment slot usage and swap | 4 |
| 05 | Design a hotfix path plan for responding to high-priority code fixes | 5 |
| 05 | Design and implement a resiliency strategy for deployment | 6 |
| 05 | Implement feature flags by using Azure App Configuration Feature Manager | 7 |
| 05 | Implement application deployment by using containers, binaries, and scripts | 8 |
| 05 | Implement a deployment that includes database tasks | 9 |
| 06 | Recommend a configuration management technology for application infrastructure | 2 |
| 06 | Implement a configuration management strategy for application infrastructure | 3 |
| 06 | Define an IaC strategy, including source control and automation of testing and deployment | 4 |
| 06 | Design and implement desired state configuration for environments, including Azure Automation State Configuration, Azure Resource Manager, Bicep, and Azure Machine Configuration | 5 |
| 06 | Design and implement Azure Deployment Environments for on-demand self-deployment | 6 |
| 06 | Monitor pipeline health, including failure rate, duration, and flaky tests | 7 |
| 06 | Optimize a pipeline for cost, time, performance, and reliability | 8 |
| 06 | Optimize pipeline concurrency for performance and cost | 9 |
| 06 | Design and implement a retention strategy for pipeline artifacts and dependencies | 10 |
| 06 | Migrate a pipeline from classic to YAML in Azure Pipelines | 11 |
Develop a security and compliance plan (10 à 15 %)#
| Ch. | Compétence mesurée (guide officiel, en anglais) | Section |
|---|---|---|
| 07 | Choose between Microsoft Entra service principals and managed identities for Azure resources (system-assigned and user-assigned) | 2 |
| 07 | Implement and manage GitHub authentication, including GitHub Apps, GITHUB_TOKEN, and personal access tokens | 3 |
| 07 | Implement and manage Azure DevOps service connections and personal access tokens | 4 |
| 07 | Design and implement permissions and roles in GitHub | 5 |
| 07 | Design and implement permissions and security groups in Azure DevOps | 6 |
| 07 | Recommend appropriate access levels, including stakeholder access in Azure DevOps and outside collaborator access in GitHub | 7 |
| 07 | Configure projects and teams in Azure DevOps | 8 |
| 07 | Implement and manage secrets, keys, and certificates by using Azure Key Vault | 9 |
| 07 | Implement and manage secrets and secretless authentication (for example, workload identity federation/OpenID Connect) in GitHub Actions and Azure Pipelines | 10 |
| 07 | Design and implement a strategy for managing sensitive files during deployment, including Azure Pipelines secure files | 11 |
| 07 | Design pipelines to prevent leakage of sensitive information | 12 |
| 07 | Design a strategy for security and compliance scanning, including dependency, code, secret, and licensing scanning | 13 |
| 07 | Configure Microsoft Defender for Cloud DevOps Security | 14 |
| 07 | Configure GitHub Advanced Security for GitHub and GitHub Advanced Security for Azure DevOps | 15 |
| 07 | Integrate GitHub Advanced Security with Microsoft Defender for Cloud | 16 |
| 07 | Automate container scanning, including scanning container images and configuring an action to run CodeQL analysis in a container | 17 |
| 07 | Automate analysis of vulnerabilities of open-source components by using Dependabot alerts | 18 |
Implement an instrumentation strategy (5 à 10 %)#
| Ch. | Compétence mesurée (guide officiel, en anglais) | Section |
|---|---|---|
| 08 | Configure Azure Monitor and Azure Monitor Logs to integrate with DevOps tools | 2 |
| 08 | Configure collection of telemetry by using Azure Monitor Application Insights, Azure VM Insights, Azure Container Insights, Azure Monitor for Storage, and Azure Monitor for Networks | 3 |
| 08 | Configure monitoring in GitHub, including enabling insights and creating and configuring charts | 4 |
| 08 | Configure alerts for events in GitHub Actions and Azure Pipelines | 5 |
| 08 | Inspect infrastructure performance indicators, including CPU, memory, disk, and network | 6 |
| 08 | Analyze metrics by using collected telemetry, including usage and application performance | 7 |
| 08 | Inspect distributed tracing by using Azure Monitor Application Insights | 8 |
| 08 | Interrogate logs using basic Kusto Query Language (KQL) queries | 9 |
Organisation du dossier#
AZ-400/
├── README.md ce plan de révision
├── 01-…md à 08-…md un fichier par bloc de compétences
├── images/ les schémas exportés en PNG (affichés dans les chapitres)
├── DRAWIO/ les schémas sources, modifiables dans draw.io
└── outils/ les scripts qui génèrent les schémas (moteur de GenDoc)
Régénérer les schémas d'un chapitre : python outils/schemas_NN.py [noms…] depuis ce dossier (GenDoc doit être dans ..\..\GENERATEUR-PPT).
Méthode de révision conseillée#
- Lire les chapitres 04 (pipelines) et 07 (sécurité) en premier : ce sont les plus denses et les plus rentables.
- Faire les labs conseillés dans une organisation Azure DevOps et un compte GitHub de test (organisation gratuite, dépôts jetables), jamais sur les projets de production.
- Répondre aux scénarios sans regarder la réponse, puis passer l'évaluation d'entraînement officielle.
- La veille de l'examen : relire les fiches à retenir et les tableaux de pièges.